How to Use Search Themes in Performance Max

A search theme is a word or phrase that tells Performance Max what customers may search for. Google says themes add information to the campaign's existing signals from URLs, assets, feeds, and other inputs. They can be useful when the business knows a customer vocabulary, seasonal need, or product use case that the landing page does not yet express clearly. They are not the same as a Search campaign keyword and should not be governed as exact query targets.

Write the intended customer question beside every theme before adding it. Record which asset group receives the theme, which landing pages and products support it, and what information the theme contributes beyond existing inputs. If the theme merely repeats visible page text or a neighboring theme, it may add little. Use the control to supply genuine context, not to create a long wish list of every phrase the team wants to rank or advertise for.

Start with product category, problem, use case, audience need, and time-bound event language that the business can support. Merge synonyms and close variants into one theme. Google specifically recommends distinct themes and warns against near duplicates that reach the same audience. Keep each theme broad enough to describe a meaningful demand area, but specific enough that the associated asset group and landing page can answer the resulting interest honestly.

Use a review table with raw research phrase, normalized theme, customer intent, supporting page, asset group, inclusion reason, and exclusion conflicts. Reject navigational phrases owned by another campaign, unsupported product claims, prohibited categories, and themes whose destination cannot satisfy the request. This prevents themes from becoming disconnected labels. It also makes later edits explainable when products, pages, or campaign structure change.

Google describes search themes as broader signals to its AI. They do not replace keyword match types in Search campaigns. Google also says exact-match keywords identical to a query can receive priority over search themes, while phrase and broad keywords share prioritization behavior with themes under documented conditions. Record neighboring Search campaigns so the operator can understand which campaign may be eligible without assuming a theme reserves the query for Performance Max.

Negative keywords, brand exclusions, and other exclusions still apply. Review account-level and campaign-level controls before adding a theme, especially if the proposed language names a restricted brand, unsupported product, or unwanted query family. A theme that conflicts with an exclusion is an operating contradiction. Resolve the intended boundary first rather than adding both and waiting for reporting to reveal which setting controlled the auction.

Google's current workflow places search themes inside an asset group's Signals card. Select the asset group, open its signal settings, enter each theme, and save. Google documents a limit of up to fifty unique search themes per asset group. Treat that number as a ceiling, not a target. A compact, intentional set is easier to review and connects more clearly to the products, creative, and pages assigned to that asset group.

Before saving, capture the current theme set and asset-group configuration. Confirm that the destination pages are eligible and that final URL expansion, page feeds, and URL exclusions match the campaign's landing-page policy. Search themes can guide discovery, while those other settings influence where traffic may land. Record them together as context without treating them as one control.

Set a review date before launch and avoid changing themes, creative, budget, bidding, products, and landing pages simultaneously. Preserve the campaign change history, theme list, asset-group membership, conversion configuration, and reporting period. If the team wants causal evidence, use an approved experiment that changes one question at a time. A before-and-after chart with several concurrent changes cannot isolate the effect of search themes.

Review search-term insights, landing pages, channel performance, conversion quality, and exclusions together. Classify observed queries as supported, adjacent, ambiguous, or unsuitable. Do not invent volume or conversion impact when the interface withholds a breakdown. Theme reporting and query reporting can be aggregated, so retain an unknown bucket instead of forcing every impression into a named theme.

Promote a new theme only when it contributes distinct context and the asset group can support the customer intent. Remove a theme when the underlying product, page, or campaign objective no longer exists, or when it duplicates another signal. Do not add every observed search as a new theme. Performance Max uses keywordless targeting beyond the supplied list, and the purpose of themes is to guide that system with business knowledge rather than reproduce a Search campaign structure.

When an unsuitable query appears, decide whether the right response is a negative keyword, brand exclusion, landing-page correction, or no action. Do not use a new opposing theme as a blocking mechanism. Record the query evidence, selected control, expected scope, and verification date. This keeps additive guidance and restrictive controls understandable for the next operator.

For every asset group, keep the current themes, normalized intent, supporting page, owner, created date, last reviewed date, and change reason. Retain prior versions so a performance review can line up with the configuration that existed during the reporting window. Include conflicts with negative keywords, brand exclusions, and URL exclusions. The ledger should answer what changed and why without requiring the reviewer to reconstruct the campaign from screenshots.

Review themes when the catalog, creative, landing pages, customer language, or campaign structure changes. Retire unsupported themes deliberately and verify the saved state in Google Ads. Keep outcome language measured. A theme can be present while another signal drives matching, and a campaign result can change for many reasons. Report observed associations, configuration changes, and unresolved uncertainty separately.