Sign in Start free

CTR Anomaly Triage

This pattern gets misread as a ranking problem and answered with content rewrites that do nothing. Flat position with falling CTR means the result page around you changed, or your snippet changed, or the query mix behind those impressions shifted. Each has a different fix and only one of them is content.

CATEGORY
Analytics & reporting
FORMAT
ctr-anomaly-triage.md
STEPS
6
PRICE
Free - no account
WHEN TO REACH FOR THIS

Use when impressions are stable or rising but clicks are falling, and rankings have not moved.

The skill file

ctr-anomaly-triage.md 
---
name: ctr-anomaly-triage
description: Use when impressions are stable or rising but clicks are falling, and rankings have not moved.
---

# CTR Anomaly Triage

This pattern gets misread as a ranking problem and answered with content rewrites that do nothing. Flat position with falling CTR means the result page around you changed, or your snippet changed, or the query mix behind those impressions shifted. Each has a different fix and only one of them is content.

## What you need first

- Search Console page-level clicks, impressions, CTR and position, daily
- current rendered titles and descriptions as Google displays them
- a manual look at the live SERP for the top affected queries

## Method

1. Confirm position is genuinely flat at query level, not just at page level. A page average can hold steady while its best query drops and a weak query gains impressions.
2. Check the query mix. Rising impressions on new, looser queries dilute CTR without anything getting worse - this is the most common false alarm and needs no action.
3. Look at the live SERP for the top three affected queries. An AI overview, a video carousel or an expanded feature block above you takes CTR that no snippet edit recovers.
4. Compare the title Google displays against the title you wrote. Rewritten titles are common and often worse; if Google is substituting, the usual cause is a title that is too long or does not match the query.
5. Split desktop and mobile. Mobile SERPs push organic further down, so a mix shift towards mobile alone can move blended CTR by several points.
6. Only if all of the above are clean, treat it as a snippet problem and test title and description changes on a handful of pages with a clear before-and-after window.

## What this produces

A named cause for the CTR fall and either a snippet test plan or an explicit decision that no action will help.

## Where this goes wrong

- Rewriting titles across the whole site at once, which removes any chance of measuring the effect and often loses ranking on pages that were fine
- Comparing CTR across periods with different device or country mixes
- Assuming a lost featured snippet is a loss - some pages get more total clicks after losing one, so check clicks, not the snippet

---

From the QuQi skill library - https://www.quqi.io/skills/ctr-anomaly-triage
Free to download · no account, no email

What you need first

  • Search Console page-level clicks, impressions, CTR and position, daily
  • current rendered titles and descriptions as Google displays them
  • a manual look at the live SERP for the top affected queries

Method

  1. 01 Confirm position is genuinely flat at query level, not just at page level. A page average can hold steady while its best query drops and a weak query gains impressions.
  2. 02 Check the query mix. Rising impressions on new, looser queries dilute CTR without anything getting worse - this is the most common false alarm and needs no action.
  3. 03 Look at the live SERP for the top three affected queries. An AI overview, a video carousel or an expanded feature block above you takes CTR that no snippet edit recovers.
  4. 04 Compare the title Google displays against the title you wrote. Rewritten titles are common and often worse; if Google is substituting, the usual cause is a title that is too long or does not match the query.
  5. 05 Split desktop and mobile. Mobile SERPs push organic further down, so a mix shift towards mobile alone can move blended CTR by several points.
  6. 06 Only if all of the above are clean, treat it as a snippet problem and test title and description changes on a handful of pages with a clear before-and-after window.

What this produces

A named cause for the CTR fall and either a snippet test plan or an explicit decision that no action will help.

Where this goes wrong

  • Rewriting titles across the whole site at once, which removes any chance of measuring the effect and often loses ranking on pages that were fine
  • Comparing CTR across periods with different device or country mixes
  • Assuming a lost featured snippet is a loss - some pages get more total clicks after losing one, so check clicks, not the snippet

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Claude Code Save it as ~/.claude/skills/ctr-anomaly-triage/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.

Questions about this skill

When is CTR triage the right method rather than treating the fall as a ranking problem?

When impressions hold or rise while clicks fall and position has not moved. That pattern gets read as a ranking problem and answered with content rewrites that change nothing. Flat position with falling click-through means the result page around you changed, your displayed snippet changed, or the query mix behind those impressions shifted, and only one of the three is a content job.

What do I need in hand before starting, and what happens if I start without it?

Daily page-level clicks, impressions, click-through rate and position, the titles Google actually displays rather than the ones you wrote, and a manual look at the live result page for the worst queries. Skip the manual look and you will miss an AI overview or a video carousel sitting above you, then spend a sprint testing snippets against something no snippet recovers.

What do I end up with, and which part of it actually gets used?

A named cause, then either a snippet test on a handful of pages with a clear before-and-after window, or an explicit decision that no action will help. The second outcome is the valuable one and the one people skip. Rising impressions on new, looser queries dilute click-through without anything getting worse, and that case needs recording rather than fixing.

What is the mistake that most often ruins this, and what does it cost?

Rewriting titles across the whole site at once. It removes any chance of measuring the effect and often loses ranking on pages that were performing, with no way to tell the two apart afterwards. The cheap guard before any conclusion is splitting desktop from mobile, since a mix shift towards mobile alone moves blended click-through by several points.

More in Analytics & reporting

Striking Distance Query Analysis

Use when you have Search Console data and need to decide which queries are worth working on this...

Separating Algorithm Updates From Your Own Changes

Use when organic traffic drops and someone asks whether it was Google or something you shipped.

Annotation Discipline

Use when setting up or repairing the record of what changed on a site and when.

Organic Attribution Reality

Use when someone asks what organic search actually contributed to revenue and last-click says le...