Website

Test the contact form end to end and reconcile it with Ads and GA4

Checks every Contact Form 7 form's recipients, sends approved test entries, verifies the GTM success trigger and the tags it fires, and reconciles 14 days of GA4 form events with Google Ads lead conversions.

When to use it

When you are not sure your website form leads are really being received and counted, or GA4 and Google Ads show different lead numbers.

What you get

A pass/fail checklist per form and a GA4 vs Google Ads reconciliation table with the gap in % and the likely causes, with any fix shown for approval first.

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

WordPress, Tag Manager, GA4, Google Ads

Fill in before sending

[site URL][company domain][test email][GTM-XXXX]

Check that leads from my WordPress site [site URL] are captured and tracked correctly. Steps 1, 3 and 4 are read-only. 1. List the Contact Form 7 forms and show each one's required fields and notification email addresses. Flag any recipient address that looks wrong or outdated. Our current domain is [company domain]. 2. Test submissions send a REAL notification email to each form's recipients, and the entry may also reach any CRM or autoresponder connected to the form. Before sending anything, run each test as a preview (confirm=false). Show me, per form, the fields and values that would be sent and which addresses would receive the mail, then wait for my approval. For each form I approve, submit one entry with name and message set to "TEST - please ignore" and email [test email]. Report the result: mail_sent, mail_failed, validation_failed (with the rejected fields) or spam. Note that this test goes through CF7's server-side REST endpoint, so no browser tags fire. It proves the mail works, not the tracking, and it adds no conversions to GA4 or Google Ads. 3. Check what actually fires on the site. List every GTM and GA4 source on the site and flag it if two different containers are live at once. In GTM container [GTM-XXXX], list the triggers and tags and check for a trigger that listens for a successful CF7 submission (a custom event such as wpcf7mailsent or equivalent), not just a click on the submit button or a generic form submission. Confirm which GA4 event tag and which Google Ads conversion tag it fires. Match that Ads tag's conversion ID and label against the conversion tags in the account, so we know it feeds the right lead conversion action. Check the workspace for unpublished changes, because those do not run on the live site. 4. For the last 14 days, compare the GA4 count of the form event (GA4 report broken down by event) with Google Ads conversions for the lead conversion action. Deliver a pass/fail checklist per form (recipients, mail delivery, success trigger, tags fired, conversion label match) and a reconciliation table showing GA4 count, Ads count and the gap in %. If the gap is above 20%, list the likely causes in order: trigger on click instead of success, consent or ad blockers, a duplicate tag or second container, or a wrong conversion action or label. This is diagnostic only. Propose fixes, but do not edit forms, site tracking or GTM until I approve each one. For every approved fix, show the confirm=false preview first and wait for my go-ahead. Never publish the GTM container without my explicit approval.

Check that leads from my WordPress site [site URL] are captured and tracked correctly. Steps 1, 3 and 4 are read-only.

1. List the Contact Form 7 forms and show each one's required fields and notification email addresses. Flag any recipient address that looks wrong or outdated. Our current domain is [company domain].
2. Test submissions send a REAL notification email to each form's recipients, and the entry may also reach any CRM or autoresponder connected to the form. Before sending anything, run each test as a preview (confirm=false). Show me, per form, the fields and values that would be sent and which addresses would receive the mail, then wait for my approval. For each form I approve, submit one entry with name and message set to "TEST - please ignore" and email [test email]. Report the result: mail_sent, mail_failed, validation_failed (with the rejected fields) or spam. Note that this test goes through CF7's server-side REST endpoint, so no browser tags fire. It proves the mail works, not the tracking, and it adds no conversions to GA4 or Google Ads.
3. Check what actually fires on the site. List every GTM and GA4 source on the site and flag it if two different containers are live at once. In GTM container [GTM-XXXX], list the triggers and tags and check for a trigger that listens for a successful CF7 submission (a custom event such as wpcf7mailsent or equivalent), not just a click on the submit button or a generic form submission. Confirm which GA4 event tag and which Google Ads conversion tag it fires. Match that Ads tag's conversion ID and label against the conversion tags in the account, so we know it feeds the right lead conversion action. Check the workspace for unpublished changes, because those do not run on the live site.
4. For the last 14 days, compare the GA4 count of the form event (GA4 report broken down by event) with Google Ads conversions for the lead conversion action.

Deliver a pass/fail checklist per form (recipients, mail delivery, success trigger, tags fired, conversion label match) and a reconciliation table showing GA4 count, Ads count and the gap in %. If the gap is above 20%, list the likely causes in order: trigger on click instead of success, consent or ad blockers, a duplicate tag or second container, or a wrong conversion action or label.

This is diagnostic only. Propose fixes, but do not edit forms, site tracking or GTM until I approve each one. For every approved fix, show the confirm=false preview first and wait for my go-ahead. Never publish the GTM container without my explicit approval.

Open in Claude Open in ChatGPT Discuss in the forum

More prompts

WebsiteChanges after your approval

Rewrite meta titles and descriptions for pages with low organic CTR

Finds page-one pages that get impressions but few clicks, compares them to your site-wide CTR, and rewrites their meta title and description around the queries that actually bring them traffic.

When to use itWhen your pages rank on page one and get impressions but few clicks, so your titles and descriptions are probably not convincing.

Use Search Console property [Search Console property] and WordPress site [WordPress site].

Step 1. Baseline. Pull the last 90 days with dimension "date" and add up total clicks and total impressions. Site average CTR = total clicks / total impressions. Show this number first.

Step 2. Candidates. Pull the last 90 days by page, sorted by impressions. Keep pages with at least 500 impressions, an average position between 1 and 10, and a CTR below 2%. Take the top 10 by impressions.

Step 3. For each of those 10 pages:
- Pull the queries for that page only (dimension "query", filtered to the page URL, sorted by impressions) and keep the top 5.
- Find the matching WordPress post or page ID by searching for its slug. If a URL has no clear match (archive, category, home page), mark it and move on.
- Read its current meta title and meta description from the SEO plugin.

Skip any page whose current title already contains its main query AND whose CTR is within 20% of the site average from Step 1. Say why you skipped it.

Deliver a table with these columns: URL, post ID, impressions, CTR, position, main queries, current title, current description, proposed title, proposed description.
- Proposed title: max 60 characters, main query near the start.
- Proposed description: max 155 characters, one concrete benefit and a call to action.
- Use only facts that are on the page. Do not invent prices, guarantees or numbers.

This table is the preview. Do not write any SEO field until I approve. After I approve, write only the approved rows (overwrite the existing values only for those rows), then purge the cache so the new tags go live, and read the SEO fields back for each changed page to confirm they landed.

WebsiteChanges after your approval

Rebuild the site menu around pages that actually convert

Matches GA4 landing-page performance against your WordPress menus, flags valuable pages missing from the navbar, dead weight and broken links, and proposes a leaner main menu.

When to use itWhen your site menu feels cluttered or outdated and you suspect it does not point visitors to the pages that actually bring conversions.

Compare my navigation menu with what actually converts.

From GA4 property [GA4 property], pull the last 90 days by landing page: sessions and key events. Calculate key event rate as key events / sessions.

Then read every menu on [WordPress site], including the main navbar and the footer, with all their links.

Match menu links to GA4 rows by URL path (ignore the domain, trailing slashes and query strings). Where a link has no GA4 row, treat it as zero sessions and say so.

Check every menu link for problems:
- Fetch each linked URL and record its HTTP status. Anything 4xx or 5xx is broken; redirects are worth noting.
- Flag links that point to draft or private pages, to old slugs, or to http instead of https.

Deliver three lists:
1. Pages with at least 20 key events that are not in the main menu.
2. Menu links pointing to pages with fewer than 50 sessions or zero key events in 90 days.
3. Broken or outdated links, with the reason for each.

Then propose a new main menu:
- Max 7 top-level items, ordered by commercial importance.
- Exact labels of 2 to 3 words, in plain language a customer would use.
- The contact page stays as the last item.
- Move low-value pages to the footer menu instead of deleting them.

Show the current menu and the proposed menu side by side, with the exact list of menu actions you would run (add, rename, relink, reorder, remove), as a preview. Do not edit anything until I approve. After approval, apply the changes, purge the cache and read the menus back to confirm the final structure.

WebsiteChanges after your approval

Plugin and tracking health check before it breaks your conversions

A plugin-by-plugin action list that flags outdated, duplicate and conflicting plugins and double-firing tags.

When to use itWhen your WordPress site has too many plugins, updates piling up, or you fear duplicate tags are inflating the conversions your ads optimize toward.

WebsiteChanges after your approval

Replace an old phone number everywhere on the site, safely

A full map of where the old number appears, a dry-run diff of the bulk replace, and a list of places that need manual fixes.

When to use itWhen your phone number has changed and you need to be sure the old one no longer shows anywhere on your website.