One asset group holds every headline, image, and listing filter
Offers collide. We split groups by offer and landing. We do not treat a single group as a strategy.
Performance Max
Performance Max spends across Google inventory from asset groups: text, image, video, and listing filters. Signals hint. Brand exclusions keep PMax off queries you still want in Search. Reporting will not give you a Search-style query list as the default object. We work that architecture. We do not write the Shopping feed as this H1. We do not treat query control as the whole job. We do not sell a black-box return.
Position
Performance Max is Google mix of inventory from one campaign type. The unit is the asset group, not the Search ad group. Search intent still has to show in the text assets and on the landing. Keyword targeting is one job: the queries you still buy in Search, plus an honest note that PMax will not hand you those queries as a default report. If PMax is on brand while Search has no negatives, the architecture is leaking.
Quality Score inputs and Google conversion actions live there. PMax may sit in that account. Asset-group architecture stays here.
Open Google AdsTitles, GTINs, disapprovals, and product groups live on Shopping ads. Listing filters can live in PMax. Feed as H1 stays there.
Open Shopping adsMatch, RSA, and search-term mining live on Search ads. Brand exclusions here exist so that format can keep control. They are not a query report.
Open Search adsThe hub names whether PMax is in the program. This page does not reprint that map. Use this URL when asset groups already spend.
Open the PPC hubThe Google Ads account holds Quality Score and conversion actions those PMax campaigns train on. Shopping ads hold the feed in the auction. Search ads hold match, RSA, and search terms. A PPC audit can list PMax waste as a finding and then stop. This URL owns asset groups, signals, brand exclusions, and how you will read limited reports.
We will not sell PMax as a replacement for Search. We will not write Merchant title recipes as this H1. We will not invent a conversion-count floor as a SKU. If learning cannot run, we say so in the conversation. If the question is GTINs, open Shopping. If the question is RSA pinning, open Search ads.
When this fits
This page fits when Performance Max is in the Google account and the missing object is architecture: assets, signals, exclusions, reporting honesty. If you needed feed eligibility, Search format, or conversion actions only, start there instead.
Offers collide. We split groups by offer and landing. We do not treat a single group as a strategy.
Signals hint. They do not define a list window. Remarketing stays on its page. We label signals as hints in the note.
Brand exclusions exist so brand Search can stay a Search job. We write the exclusion. We do not pretend PMax is brand defense.
Reporting limits are the object. Insights you can get are listed. Search-style query lists are named as absent.
Process
Four PMax jobs in this order. We do not start a Shopping title recipe in the last step. The point is asset groups you can defend, with reporting limits written down.
We inventory text, image, video, and listing filters per asset group. Search intent on landing and ad copy is checked against those text assets. Keyword targeting remains the Search query list you will still buy. A missing landing for an asset group is a defect.
Outcome An asset-group inventory, including groups that mix two offers.
We list audience signals and label them as hints. Topical relevance of a signal to the asset group is the test. Keyword density in a headline is not a metric and not a PMax score. Customer lists used as signals are named. Membership duration still lives on remarketing.
Outcome A signal note that says hint, not membership window.
We write brand exclusions (and other exclusions you will stand behind) so PMax does not eat brand Search. Semantic keywords you still want as Search queries stay on Search ads. Entity names in assets belong in schema and AI work. We do not use PMax as the negative-keyword OS.
Outcome An exclusion note, including brand, with Search still in control of those queries.
We document what PMax reporting will and will not show. Channel and asset-group reads we can stand behind are listed. A fake query report is refused. If conversion actions in Google are fiction, we stop reading PMax and point you to Google Ads or an audit.
Outcome A reporting-limit note the stakeholder can keep.
Deliverables
You leave with an asset-group inventory, a signal note, an exclusion note, and a reporting-limit note. You do not leave with a query report PMax cannot give, a feed recipe, or a conversion-count floor as a SKU.
Text, image, video, listing filters, landings. Dated. Last month screenshot is not this inventory.
Hints only. Remarketing windows are pointed at remarketing. Lists dumped as if they were membership rules are named.
Brand and other exclusions you will stand behind. Search still owns those queries as a format.
What you can read. What you cannot. A promised search-term dump is not a deliverable.
When Shopping, Search, Google conversion actions, or an audit must take the next hour.
Benefits
Each group has a landing. Mixed headlines are listed as defects.
Hints are labeled. Membership duration stays on remarketing.
Exclusions are written. PMax is not brand defense by accident.
Nobody is promised a query list PMax will not print. Reads you can stand behind are named.
Methodology
This works when someone can publish assets in Google Ads and someone will accept that query lists are not the default read. If both are missing, we are decorating a black box. We are not holding PMax.
We start with live asset groups, brand-exclusion status, and the Search campaigns that should own brand. If any of those is missing, we name it first.
We fetch landings for each group. We do not trust the asset library alone. Does search intent on the first screen match the text assets? Are the queries you will buy still in Search?
You may rename the roles below. You may not leave brand exclusion implied. An implied exclusion is how PMax eats brand.
First working session
The first hour is whether PMax is on brand while Search has no exclusions or negatives. It is not a tour of Merchant titles.
We open PMax. We check brand exclusions and a brand Search campaign. If PMax is on brand unprotected, that is the job. If the real question is GTINs, that is Shopping ads. If the real question is RSA pinning, that is Search ads. If the real question is Quality Score, that is Google Ads.
Then we open one asset group and its landing. Mixed offers and empty video slots are usually the job. A PMax dashboard that looks efficient while brand is leaking is not evidence of architecture.
We leave with a first exclusion note or a stop. A list names groups, signals as hints, and what reporting will not show. A stop names what is missing: access, a Search home for brand, or a job that is actually the feed. Both are outcomes. A query-report promise is not.
AI search
Honest assets and landings can help later extraction. This page cannot sell AI Overviews, a chat mention, or LLM visibility as a score.
PMax creative will not land the brand in Google AI Overviews (AIO). If asset groups mix two offers, generative search has a messy claim to lift. That is ours to tidy as architecture. If the landing already tells the truth and models still invent a headline you do not run, that is an AI search audit. A program across search UIs is AI SEO.
AI search needs a page it can fetch. An image-only group with a vague URL does not help. We do not sell Overview presence.
We check names across text assets and landings. That is entity optimization as a PMax input. It is not a Knowledge Graph project from this page.
LLM visibility needs a sentence a model can quote, then measurement on LLM SEO. A reporting-limit note can show what you cannot see. It does not sample answers.
Schema
JSON-LD helps a machine read an offer the landing already states. This work can flag a mismatch with PMax headlines. It is not a schema campaign as the whole job.
If schema says one offer and the text assets say another, extractors guess. We name the mismatch. We do not stuff types to feed the mixer.
Keyword targeting for queries you will buy still lives in Search. FAQ schema is not a substitute query list.
Markup will not force generative search to cite the landing. Eligibility is not a purchased mention.
Who we work with
Someone has to accept the reporting limit. We work with that person. We do not replace them with a fake query export.
Edits asset groups, signals, exclusions. Rechecks after a creative dump.
Holds negatives and RSA on Search ads. Confirms PMax stays off those queries.
Can keep going once feed eligibility and conversion actions are named. If they try to run this as a search-term OS, two jobs collide.
Questions
We do not treat PMax as a replacement for query-controlled Search. Brand Search and query insight stay on Search ads and on the Google Ads account page. This URL owns asset groups, signals, brand exclusions, and what reporting will not show.
You will not get Search-style query lists as the default object. This page owns that limit. We will not pretend otherwise. If you need query control as the whole job, open Search ads.
No. Signals hint PMax. Membership duration, converter exclusions, and return creative live on remarketing. Do not collapse them because both mention people.
No. Merchant eligibility, GTINs, and product groups live on Shopping ads. Listing-group filters can sit inside PMax. Feed titles as the ad object stay on Shopping.
No. We will not sell PMax as a ROAS machine you cannot inspect. We name reporting limits. We refuse a fake query report.
No. Honest assets and landings can help later extraction. This work does not buy a place in Google AI Overviews (AIO), a generative-search mention, or an LLM visibility score. If models invent an asset claim you do not publish, that measurement sits on an AI search audit and on LLM SEO.
The Google Ads customer ID, whether brand exclusions are on, and a screenshot or export of one asset group. A homepage walkthrough is not an architecture brief.
Asset groups with reporting limits
Share a screenshot or export of one PMax asset group, whether brand exclusions are on, and the Google Ads customer ID. We will say if PMax architecture fits, or whether Search ads, Shopping ads, or a PPC audit should go first.
Groups, hints, brand exclusions, report gaps. Not a query OS.