Fill in before sending
[asset group name][campaign name][candidate URLs, or leave empty]
Use my Opus Growth connection for this. If you cannot see the tool you need, search among the Opus Growth tools (with search_tools if it is in your list); if you cannot reach the tools at all, do not guess, tell me.
Check whether the landing page behind my Performance Max asset group [asset group name] in campaign [campaign name] supports the ads or works against them.
1. Find the campaign and asset group IDs. Read the asset group's final URL, all of its headlines, long headlines and descriptions, and its ad strength. Read its display paths (path1, path2) with a GAQL query on asset_group if they are not in the asset group read.
2. Pull the asset group's performance for the last 30 days with a GAQL query on asset_group: cost, conversions, cost per conversion and conversion rate (conversions divided by clicks). Show the campaign's figures next to it for context.
3. Read the landing page as a visitor sees it: title, H1 and heading structure, plus the page text.
4. Run an SEO and speed audit on that URL on mobile, and pull its Core Web Vitals on mobile. Note which measurement tags the audit finds on the page (Google Ads conversion, GTM, GA4). Also run a conversion tracking health check on the account so a tag that is present but not recording shows up.
5. Score the match between the ads and the page:
- Does every offer, price or promise in the assets appear on the page? Treat the title, H1 and the first block of text as the top of the page and say whether each claim appears there or only further down.
- Is the main call to action on the page the same as the one the ads lead to?
List each mismatch with the exact asset text and what the page says instead.
6. Flag these problems: mobile LCP over 2.5 seconds, CLS over 0.1, INP over 200 ms, no Google Ads conversion or GTM tag found on the page, or a primary conversion action recording zero.
Then give a verdict using this rule:
- Keep the page if it matches and passes the speed and tag checks.
- Fix the page if it matches but is slow or missing tags. List the top 3 fixes from the audit.
- Change the final URL if the page does not match and one of these candidate pages fits better: [candidate URLs, or leave empty]. Run the same match and speed checks on each candidate before recommending it. If I gave no candidates, tell me what the right page should contain instead of guessing a URL.
If you recommend a different final URL or new display paths, show the exact before and after as a preview. Do not apply it until I approve.