Write PMax headlines from the words customers actually search
Turns real Search Console queries for a landing page into themed PMax headlines and long headlines, proposes which weak assets to replace, and applies only approved lines.
When to use it
When your Performance Max headlines sound generic or like your own marketing and you want them to use the words customers really type.
What you get
Themed new headlines and long headlines built from real queries, a list of weak assets to replace, and only the lines you approve applied to the asset group.
Does it change anything in my account?
Only with your approval. The assistant first shows a preview of every change and waits for your go-ahead.
Works with
Search Console, Google Ads
Fill in before sending
[landing page URL][brand terms][asset group name]
My Performance Max headlines sound like me, not like my customers. Fix that using real search language.
1. Find my property with gsc_list_sites. With gsc_performance, pull queries for the last 90 days filtered to the page [landing page URL], sorted by clicks. Exclude brand queries, meaning anything containing [brand terms], and keep the top 50 that remain.
2. Group them into 4 to 6 themes, such as price, location, urgency, comparison or a specific product. For each theme, show total clicks and impressions.
3. Find my Google Ads account with list_accounts, look up the asset group [asset group name] with google_ads_query, and read its current text assets with get_pmax_assets. Also run a google_ads_query on asset_group_asset for that asset group to get each text asset's performance_label. If that field comes back empty, say so and rank weak assets by your own judgement of how generic or repetitive they are instead.
4. Write new copy for each theme:
- 2 headlines (30 characters max) and 1 long headline (90 characters max)
- Reuse the customers' exact wording where it reads naturally.
- Do not overlap with existing assets.
- Include character counts.
- No keyword stuffing, no all caps, no unverifiable claims.
5. Suggest which existing assets these should replace. Prioritise any asset labelled "Low", respect the limits of 15 headlines and 5 long headlines, and never drop below 3 headlines or 1 long headline.
Show the result as a proposed add/remove list, with the resource_name of each asset to remove. Make no changes until I confirm. Then run update_pmax_assets with confirm=false for only the approved lines, show me the preview, and apply it with confirm=true only after I say go. Finally, re-read the asset group and show the updated text assets.
Reads every enabled RSA in a campaign, matches each final URL to its WordPress page (Elementor included) and rates whether the page repeats the ad's keyword, offer and CTA. Proposes the smallest fix and applies nothing without approval.
When to use itWhen people click your ads but the WordPress landing page does not repeat what the ad promised, hurting conversions or Quality Score.
Lists disapproved and limited RSAs with Google's policy reason and evidence, rewrites only the assets Google flags, and edits the existing ad after a before and after preview. Flags issues that text changes cannot fix.
When to use itWhen some of your Google Ads are disapproved or running with limited serving and you need to fix the wording that Google flagged.
A list of fatigued Meta ads by frequency, CTR and cost thresholds, with two replacement copy versions for each and a safe in-place swap after approval.
When to use itWhen your Meta ads have been running a long time and results are slipping while frequency climbs.