Website

Rewrite meta titles of WooCommerce product pages with low organic CTR

Finds product pages that rank on page one or two but get few clicks, matches each one to its WooCommerce product, drafts sharper meta titles and descriptions, and applies only the rows you approve, then verifies them.

When to use it

When your WooCommerce product pages rank on page one or two of Google but get few clicks, and you suspect weak meta titles and descriptions.

What you get

A table of proposed meta titles and descriptions per product, applied only for the rows you approve and then verified, with a reminder to re-check CTR in 4 to 6 weeks.

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, WordPress

Fill in before sending

[WordPress site][property][product URL path]

Site: [WordPress site]. Search Console property: [property]. Product URLs contain: [product URL path]. 1. Pull the last 90 days of organic performance with gsc_performance, dimension=page, sorted by impressions, with a limit high enough to cover all product pages. Keep only URLs containing [product URL path]. 2. Keep only pages that meet all of these: - at least 500 impressions - average position between 3 and 15 - CTR under 2% 3. For each remaining page, get its top 3 queries by impressions: run gsc_performance with dimension=query, page=<that URL>, sort=impressions, limit=3. 4. Match each URL to its WooCommerce product: - Take the slug from the URL and find the product post with wordpress_list_posts (type=product, search=the slug words). Use the post whose slug matches the URL exactly to get its ID. - Look up price and stock with wordpress_woo_products, searching by the product name you just found. Accept the result only if the name matches that product exactly. - If there is no exact match or more than one candidate, do not guess. Mark the row "unmatched" and list it separately so I can give you the product ID. 5. Skip products whose stock data shows them as out of stock. 6. For each matched page, read the current meta title and meta description with wordpress_seo (id=the product ID). For each remaining page, draft: - A new meta title: max 60 characters, with the main query near the start. - A new meta description: max 155 characters, with the price or a concrete benefit and a reason to click. Do not invent claims, shipping terms or discounts. Deliver a table with these columns: URL, product ID, top query, position, CTR, current title, proposed title, current description, proposed description. Show character counts for the proposed title and description. Treat this table as the preview. Change nothing until I reply with the rows I approve. Then: 1. Write the approved title and description with wordpress_set_seo for each approved product ID (overwrite=true, since these fields already have values). 2. Read each one back with wordpress_seo and confirm the stored title and description match what I approved. Report any row that did not save. 3. Purge the cache with wordpress_purge_cache. 4. Remind me to compare CTR for these URLs in Search Console in 4 to 6 weeks.

Site: [WordPress site]. Search Console property: [property]. Product URLs contain: [product URL path].

1. Pull the last 90 days of organic performance with gsc_performance, dimension=page, sorted by impressions, with a limit high enough to cover all product pages. Keep only URLs containing [product URL path].
2. Keep only pages that meet all of these:
   - at least 500 impressions
   - average position between 3 and 15
   - CTR under 2%
3. For each remaining page, get its top 3 queries by impressions: run gsc_performance with dimension=query, page=<that URL>, sort=impressions, limit=3.
4. Match each URL to its WooCommerce product:
   - Take the slug from the URL and find the product post with wordpress_list_posts (type=product, search=the slug words). Use the post whose slug matches the URL exactly to get its ID.
   - Look up price and stock with wordpress_woo_products, searching by the product name you just found. Accept the result only if the name matches that product exactly.
   - If there is no exact match or more than one candidate, do not guess. Mark the row "unmatched" and list it separately so I can give you the product ID.
5. Skip products whose stock data shows them as out of stock.
6. For each matched page, read the current meta title and meta description with wordpress_seo (id=the product ID).

For each remaining page, draft:
- A new meta title: max 60 characters, with the main query near the start.
- A new meta description: max 155 characters, with the price or a concrete benefit and a reason to click. Do not invent claims, shipping terms or discounts.

Deliver a table with these columns: URL, product ID, top query, position, CTR, current title, proposed title, current description, proposed description. Show character counts for the proposed title and description.

Treat this table as the preview. Change nothing until I reply with the rows I approve. Then:
1. Write the approved title and description with wordpress_set_seo for each approved product ID (overwrite=true, since these fields already have values).
2. Read each one back with wordpress_seo and confirm the stored title and description match what I approved. Report any row that did not save.
3. Purge the cache with wordpress_purge_cache.
4. Remind me to compare CTR for these URLs in Search Console in 4 to 6 weeks.

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.