Ad copy and creative

Audit RSA claims against the live landing page before they cost ROAS

Checks every factual claim in your 20 highest-spend RSAs against what the live landing page actually says, flags broken URLs and overpromises by severity, and drafts corrected copy for approval.

When to use it

When you suspect your top-spending Google ads promise prices or offers that the landing page does not actually show.

What you get

A claim-by-claim table of your 20 top-spend RSAs against the live page with severity ratings, plus corrected copy previewed for approval.

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

Google Ads

Fill in before sending

[customer ID]

In Google Ads account [customer ID], run an ad-level performance report for the last 30 days and take the 20 responsive search ads with the highest cost. Read each ad's headlines, descriptions and final URL. Open every unique final URL as a visitor would, record the HTTP status, and read the page text. Then check each factual claim in the ad copy against the page: - price or "from" price - discount percentage - free shipping threshold - delivery time - returns window - installment offer - stock or "new season" claims Some prices and offers are loaded by JavaScript and will not appear in the served HTML. When a claim is missing from the page text, mark it "not found in served HTML" rather than mismatch, and list those for me to check in a browser. Return a table with these columns: ad, final URL, claim in ad, what the page says, status (match / mismatch / not found in served HTML), severity. Severity is high if the ad promises more than the page delivers or the URL does not return 200. It is medium if the page has a better offer the ad does not mention, and low otherwise. For high and medium rows, write corrected headlines or descriptions within the 30 and 90 character limits. For URLs that do not return 200, do not edit the ad; tell me which ad is affected and what to fix. Show the update_rsa preview (confirm=false) for each ad you would change and wait for my approval before changing anything.

Open every unique final URL as a visitor would, record the HTTP status, and read the page text. Then check each factual claim in the ad copy against the page:
- price or "from" price
- discount percentage
- free shipping threshold
- delivery time
- returns window
- installment offer
- stock or "new season" claims

Some prices and offers are loaded by JavaScript and will not appear in the served HTML. When a claim is missing from the page text, mark it "not found in served HTML" rather than mismatch, and list those for me to check in a browser.

Return a table with these columns: ad, final URL, claim in ad, what the page says, status (match / mismatch / not found in served HTML), severity.

Severity is high if the ad promises more than the page delivers or the URL does not return 200. It is medium if the page has a better offer the ad does not mention, and low otherwise.

For high and medium rows, write corrected headlines or descriptions within the 30 and 90 character limits. For URLs that do not return 200, do not edit the ad; tell me which ad is affected and what to fix.

Show the update_rsa preview (confirm=false) for each ad you would change and wait for my approval before changing anything.

Open in Claude Open in ChatGPT Discuss in the forum

More prompts

Ad copy and creativeChanges after your approval

Find weak RSA headlines and descriptions and replace them in place

A per-asset performance table with clear weak-asset flags and two tested-angle replacements for each, applied only after approval.

When to use itWhen your responsive search ads have headlines or descriptions that drag down CTR or spend without converting.

Ad copy and creativeChanges after your approval

Check message match between RSAs and WordPress landing pages

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.

Check whether my ads and landing pages say the same thing. Google Ads account: [account]. WordPress site: [site].

Step 1: Ads
List the ad groups in campaign [campaign] and read every enabled RSA with its headlines, descriptions and final URL.

Step 2: Find each page
- Strip tracking parameters from each final URL and match it to a page or post on [site] by its slug.
- If a URL is not on [site], or matches more than one page, list it and ask me instead of guessing.

Step 3: Read each page
- First check how the page is built. On an Elementor page the visible headings and buttons live in the page design data, so read them there. On other pages, read the full content.
- Pull: the H1 heading, the first paragraph, the main offer or first button text, and the meta title from the SEO fields.
- You cannot see the rendered page. Treat the H1, the first paragraph and the first button in page order as the "first screen." Say so when the order is unclear, for example when a slider shortcode sits at the top.

Step 4: Rate each ad and page pair
Does the page repeat the ad's main keyword, offer and call to action on the first screen?

Show a table with these columns:
- ad group
- final URL
- page builder
- what the ad promises
- what the page says
- match (good, partial or missing)

Step 5: Fixes
For every partial or missing match, suggest one fix: either a headline edit in the ad or a heading edit on the page, whichever is the smaller change. Headlines must stay within 30 characters. Show the character count.

Preview the ad edits and the page edits separately:
- Ad edits: run each RSA change as a preview first, keeping every other headline, description and pin as it is.
- Page edits: the WordPress tools have no dry run, so show me the exact current text, the proposed text and the element or field you will change.

Do not apply anything until I confirm. After I approve:
- Apply the approved RSA edits. Note that edited ads go back through Google review.
- Apply the approved page edits, then purge the site cache (and regenerate Elementor CSS on Elementor pages).
- Confirm each change landed. Remind me that Elementor edits can be rolled back to the previous version and other edits are kept as WordPress revisions.

Ad copy and creativeChanges after your approval

Rewrite RSA headlines that caused disapprovals or limited serving

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.

Some of my ads are disapproved or limited.

List every responsive search ad in [account] that is disapproved or "Eligible (limited)." For each one, show:
- campaign, ad group and ad ID
- the policy topic and its type
- the exact headline or description that triggered it, from Google's evidence
- the countries it is limited in, if Google reports that

Read each ad's full copy, including pins, so you can match the evidence to specific assets.

Explain each reason in plain language. Examples include trademark use, excessive capitalization, unproven claims like "best" or "No. 1," symbols or punctuation, and restricted categories such as health or finance.

Rewrite only the offending assets:
- Rewrite an asset only when Google's evidence points to it. If Google gives no detail for a topic, do not rewrite anything for that ad. Instead, list the assets you suspect and why, and ask me.
- Keep the same meaning but make it comply.
- Headlines can be up to 30 characters and descriptions up to 90. Show the character count for each.
- Edit the existing ad rather than creating a new one, so its history is kept. Leave every other asset and pin as it is.

Some problems cannot be fixed by rewriting text. Examples are a trademark that needs authorization, a missing certification, or an issue on the landing page such as a broken destination. For those, tell me what I need to do instead.

Show a before and after preview for each ad and wait for my approval before changing anything. Remind me that an edited ad goes back into review.

Ad copy and creativeChanges after your approval

Meta creative fatigue check with copy-only replacement creatives

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.

Run a creative fatigue check on Meta ad account [account]. Compare the last 28 days with the previous 28 days at ad level using spend, impressions, frequency, link CTR, CPM, results and cost per result.

Flag an ad as fatigued only when all three conditions hold:
- frequency is above 3.0
- link CTR is down at least 25% versus the prior period
- cost per result is up at least 20%

Skip ads that spent less than [minimum spend] in the last 28 days.

Deliver:
1. A table of fatigued ads with these columns: ad name, ad set, days running, frequency, CTR change, cost per result change.
2. For each fatigued ad, read the current creative (headline, primary text, description, CTA, destination link). Write 2 replacement versions that keep the same offer, image or video and link, and change the hook and the first line of the primary text.
3. For the versions I approve, prepare an in-place creative swap so each ad keeps its ID, learning and history.

Render a preview of every new creative first. Wait for my explicit confirmation before applying any change.