← All questionsPerformance Max Targeting

How do I use search themes in PMax, and how are they different from classic keywords?

A quick primer

The core difference from classic keywords is built into the tool's purpose: search themes let you flag queries your customers use are searching for, but they're optional and additive — layered on top of the queries and placements PMax already predicts will perform well based on your assets, feeds, and landing pages. That's a fundamentally different logic from Search: a keyword there is a serving condition; a search theme here is a hint layered on top of a model that will keep searching on its own regardless.

The technical limits and rules of use are documented too: you can add up to 50 unique themes per asset group, and exclusions and negative keywords still apply on top of them as usual — search themes don't override or bypass a campaign's existing restrictions. Google's own guidance on list composition is to avoid meaning-duplicates: avoid semantic duplicates together, since both reach the same audience — otherwise part of the 50-slot budget gets spent on semantic duplicates for nothing.

On auction priority, search themes are wired into PMax and Search's overall matching logic the same way: they carry the same priority as phrase match and broad match keywords in Search — meaning an exact query match against an exact-match Search keyword still wins priority over a PMax search theme, not the other way around.

What to check before you touch anything

  • Whether existing search themes duplicate each other in meaning (like the "car"/"automobile" example) — semantic duplicates waste slots out of the 50-per-group limit.
  • Whether the themes are set at the right asset group — matching its topic — rather than at the campaign level as a whole.
  • Whether search themes conflict with already-set negative keywords or brand exclusions — those still apply and can block traffic a theme would otherwise seem to generate.
  • Whether there are exact-match Search keywords overlapping in meaning with the themes — an exact query match still gets priority in Search, not PMax.
  • Whether the search themes are grounded in real data about how customers search for the product (from an existing Search campaign's search terms report), or picked intuitively.

Possible approaches

  • Use search themes to flag specific directions of semantics the model might have missed on its own, rather than copying an entire Search keyword list into them — high semantic redundancy just wastes the slot budget.
  • If the campaign already shows good reach without search themes — treat them as a targeted expansion into specific, business-known query niches rather than a mandatory setup step.
  • If cannibalization with your own Search campaign is suspected because of similar-meaning search themes — check prioritization first: exact-match Search keywords should still win priority, and if that's not happening, look at the Search campaign's own settings.
  • If overlap is partial (not 80%+, not near zero) — before deciding, explicitly separate the shared and unique portions of the semantics and weigh whether the unique volume justifies its own theme entry, or whether it's simpler to leave things as-is.
  • If Sitelinks/Callouts/Snippets are unevenly connected between the ads — bring them to parity so any difference in results is explained by headline copy alone, not asset coverage.
  • Periodically review the search theme list for duplicates and stale entries — query language shifts over time, and the 50-slot limit per group is finite, so keeping irrelevant or duplicate themes is a missed opportunity for something more useful.