SEO and content

Diagnose ranking drops before reporting them

A read-only diagnosis of tracked keywords that lost 3 or more positions: rank history, click loss, live SERPs, index status and on-page SEO fields, ending in a cause and fix table.

When to use it

When tracked keywords have lost positions and you need to understand why before telling your boss or client.

What you get

A table of each dropped keyword with drop size, clicks lost, likely cause, evidence, recommended fix and owner (content or dev).

Does it change anything in my account?

No. The assistant only reads your data and reports back.

Works with

SEO Intelligence, Search Console, WordPress

Fill in before sending

[domain][country][language][number of days]

Several tracked keywords on [domain] have lost positions. I need a diagnosis before I report this upward. Market: [country], language: [language]. 1. From rank history, list every tracked keyword that dropped 3 or more positions in the last [number of days] days. Show the old position, the new position and the ranking URL. If the history shows a different ranking URL over the period, flag it, because that signals cannibalisation. If the history does not carry URLs, check Search Console page and query data instead: two of my pages taking impressions for the same query is the same signal. 2. From Search Console, pull clicks for those queries over the last [number of days] days and over twice that period, and derive the previous period by subtracting. Take the 5 drops that lost the most clicks. 3. Check seo_history for SERP analyses already run on these keywords and reuse them. For the rest, tell me how many new SERP analyses you need, since each costs add-on credits, and wait for my go-ahead. Then run them: who now ranks above us, and which SERP features appear. 4. Inspect those ranking URLs in Search Console in one batch. Report the index status, the last crawl date and the Google-chosen canonical. 5. Check whether [domain] is a connected WordPress site. If it is, find each page's post ID with wordpress_list_posts and read its SEO fields: meta title, meta description and canonical. If it is not, skip this step and say so. Output a table with these columns: keyword, drop size, clicks lost, likely cause, evidence, recommended fix, owner (content or dev). Choose the likely cause from: deindexed, canonical conflict, URL swap, new competitor, SERP feature, unclear. Use "unclear" whenever the evidence does not point to one cause. This is diagnosis only. Do not change anything.

Several tracked keywords on [domain] have lost positions. I need a diagnosis before I report this upward. Market: [country], language: [language].

1. From rank history, list every tracked keyword that dropped 3 or more positions in the last [number of days] days. Show the old position, the new position and the ranking URL. If the history shows a different ranking URL over the period, flag it, because that signals cannibalisation. If the history does not carry URLs, check Search Console page and query data instead: two of my pages taking impressions for the same query is the same signal.
2. From Search Console, pull clicks for those queries over the last [number of days] days and over twice that period, and derive the previous period by subtracting. Take the 5 drops that lost the most clicks.
3. Check seo_history for SERP analyses already run on these keywords and reuse them. For the rest, tell me how many new SERP analyses you need, since each costs add-on credits, and wait for my go-ahead. Then run them: who now ranks above us, and which SERP features appear.
4. Inspect those ranking URLs in Search Console in one batch. Report the index status, the last crawl date and the Google-chosen canonical.
5. Check whether [domain] is a connected WordPress site. If it is, find each page's post ID with wordpress_list_posts and read its SEO fields: meta title, meta description and canonical. If it is not, skip this step and say so.

Output a table with these columns: keyword, drop size, clicks lost, likely cause, evidence, recommended fix, owner (content or dev). Choose the likely cause from: deindexed, canonical conflict, URL swap, new competitor, SERP feature, unclear. Use "unclear" whenever the evidence does not point to one cause.

This is diagnosis only. Do not change anything.

Open in Claude Open in ChatGPT Discuss in the forum

More prompts

SEO and contentRead-only

Build intent-based keyword clusters from a few seed keywords

A ranked list of keyword clusters with volume, difficulty and the right page type or ad group for each.

When to use itWhen you are starting keyword research for a business and only have a few seed keywords.

I sell [product or service] in [city or country]. Start from these seed keywords: [3 to 5 seed keywords].

First check seo_history so you reuse earlier results instead of paying for the same query twice. Then use Keyword Planner and SEO keyword research to collect ideas with average monthly searches, competition and keyword difficulty.

Clean the list:
- remove keywords under 30 monthly searches
- remove job, free, DIY, course and competitor-brand terms unless they clearly fit my business
- merge close variants and plurals

Cluster the rest by search intent, with one cluster per distinct need a searcher has. For each cluster give:
- cluster name and head keyword
- 5 to 10 supporting keywords
- combined monthly volume and average difficulty
- intent: informational, commercial or transactional
- best use: service page, blog post or a Google Ads ad group

Rank the clusters by volume and fit for a small business with a limited budget. Mark the top 3 to start with and explain why in one line each.

SEO and contentChanges after your approval

Turn search terms that convert in ads into organic content clusters

Uses 90 days of converting Google Ads and Microsoft Ads search terms to find topics where you pay for conversions but have weak or no organic visibility. Returns a prioritized content plan and a preview-only list of keyword additions.

When to use itWhen you pay for conversions on search terms but are unsure which topics deserve organic content so you can rely less on ads.

I want to use my ad data to decide what to write about. Use the last 90 days on every source.

1. Pull my Google Ads search terms for the last 90 days (days=90, or an explicit start and end date), sorted by conversions. Keep only terms with at least 1 conversion. If the response is truncated, page through until you have every converting term.
2. If Microsoft Ads is connected, find the default account and pull its search terms for the same 90 days. Keep only terms with at least 1 conversion and add them to the pool, marking which platform each term came from.
3. Group all converting terms into topic clusters by search intent. For each cluster show total cost, conversions and cost per conversion, split by platform where both are present.
4. Find my Search Console property (use [site property] if I named one) and pull organic data for the last 90 days with dimension query, plus a page,query pull so you can see which page ranks for each query. Use a high enough limit to cover the long tail.
5. Match each cluster to the Search Console queries that express the same intent. Use your judgement for close variants and wording differences, and say which queries you counted. Report organic clicks, impressions and average position per cluster, and the page that ranks best for it if there is one.

Classify each cluster:
- Content gap: converts in ads, organic average position worse than 10 or no organic impressions. I should build a page.
- Improve: converts in ads, organic position 4 to 10. Name the existing page that needs strengthening.
- Covered: organic position 1 to 3. Note it as a possible place to test lower ad spend later.

Deliver a table sorted by ad conversions, then the top 5 content-gap clusters with a suggested page title and URL slug for each.

Separately, list my Google Ads keywords (list_entities, entity keywords) and show converting Google search terms that are not yet keywords in the account. For Microsoft terms, just flag them; do not check or change Microsoft keywords. Do not add anything. If you think some Google terms should be added as exact match, tell me which ad group each one belongs in and run add_keywords with confirm=false so I see the exact preview. Wait for my approval before applying.

SEO and contentChanges after your approval

Cluster the searches that find my Business Profile and fix my services

Clusters of the real Google Search and Maps queries behind your listing, compared with your services and categories, plus a previewed fix.

When to use itWhen your Business Profile gets views but you suspect your services and categories do not match what people really search for on Google and Maps.

For my Business Profile location [location name], pull the search terms people used on Google Search and Maps to find the listing over the last 3 months.

Cluster the terms into:
- brand searches
- service searches, with one cluster per service
- "near me" and neighborhood or district searches
- problem-based searches, such as a symptom or an issue the customer has

For each cluster show total impressions and the top 5 terms.

Then read my listing details: primary and additional categories, and the services list. Compare them with the clusters and tell me:
- service clusters with real demand that are missing from my services list
- services I list that get almost no searches
- whether an additional category would match a strong cluster. Search the category names to confirm they exist.

Draft the new service entries, with a name and a description of up to 300 characters for each, written around the words people actually search.

Show me the exact changes as a preview first. Do not update the listing until I approve.

SEO and contentRead-only

Build a seasonal content and ad calendar from keyword demand

A 12-month calendar showing when each keyword cluster peaks, when to publish content and when to raise or lower ad budgets.

When to use itWhen you want to time content and ad budgets around real seasonal demand instead of guessing when interest peaks.