Your keyword sits firmly at position 3 on page one, impressions even ticked up 10%, yet clicks fell by half versus last month. This kind of “ranked but not clicked” decoupling usually isn’t a problem with your page — it’s that the search results page itself has changed shape.
When rankings hold but clicks drop, eight times out of ten the SERP layout shifted — featured snippets, AI overviews, map packs, video carousels, and People Also Ask are siphoning off clicks that should be yours. The diagnostic order is fixed at three steps: first use Search Console to see whether the drop is site-wide or page-specific, then look at the actual search results to see which module is taking clicks, and finally decide whether to rewrite the title or actively fight for that module.
Step 1: Pin down which layer the CTR drop sits in
Open the Search Console performance report, set the comparison to “last 28 days vs previous period”, then export CTR along both the page and query dimensions. Three patterns map to three causes — don’t mix them up.
| Dimension | Phenomenon | Most likely cause |
|---|---|---|
| Site-wide CTR | All types of pages dropping together | A new generic module appeared in the SERP |
| Single-page CTR | Only specific pages dropping | Title rewritten by the search engine, or meta description failing |
| Single-query CTR | Only certain keywords dropping | Those terms triggered a featured snippet or Q&A box |
| Impressions up, clicks flat | Average position also sliding back | Gaining long-tail impressions while head positions recede |
Looking only at the site-wide average is the easiest way to misjudge: even if overall CTR drops just one percentage point, a specific content cluster may already be halved. Don’t draw conclusions before breaking down the dimensions — same principle as not tracking rankings by average position alone.
Step 2: Identify which module is taking your clicks
Take the keywords you screened in the previous step and search each one in an incognito window, once on desktop and once on mobile, logging the modules that appear above the fold into a table. On mobile, the first screen often shows only two or three organic results, so the siphoning is far worse than on desktop.
- Featured snippet: puts the answer right at the top, users read it and leave — especially for definitional and numeric queries.
- AI overview / generative summary: blends multiple sources into one paragraph, pushing organic results below the fold.
- Map pack: nearly always appears for location-intent terms and eats most local traffic.
- Video and image carousels: most common for tutorial and appearance-type terms; text long-form struggles to compete.
- People Also Ask: keeps users’ second clicks looping inside the results page itself.
- Shopping cards: exclusive to commercial terms, squeezing organic results to the second screen.
While logging, note which screen your result lands on. When your position goes from “third on the first screen” to “only visible after scrolling”, the click halving makes complete sense.
Step 3a: Win clicks back by rewriting titles and descriptions
If the diagnosis points to a single-page problem, the lowest-cost move is rewriting the title and meta description. The first 30 Chinese characters of the title matter most — anything beyond gets truncated on mobile.
- Put concrete numbers in: “9 checkpoints” gives more reason to click than “complete guide”.
- Add freshness markers: the year or “latest” works clearly for tool and policy-type queries.
- State the audience or scenario: “for small teams”, “no development needed” filters for clicks that actually convert.
- Parentheticals grab attention on desktop but risk truncation on mobile — verify both ends separately.
- Don’t repeat the title in the meta description; use it to answer the half-question the title left open.
After the change, don’t rush to check rankings — watch CTR instead, and a trend usually shows in 7–14 days. For finer details and anti-examples, go through the CTR details of titles and meta descriptions item by item.
Step 3b: Actively fight for the module that’s siphoning
Since the featured snippet took your clicks, take it back. When extracting snippets, search engines prefer clearly structured paragraphs with the answer up front — your job is to make the page easier to extract.
- Right after the corresponding H2, give the answer directly in 40–55 words, no lead-in.
- Write answer paragraphs in directly quotable patterns like “X is…” or “It takes three steps:…”.
- Turn step-type content into ordered lists and comparison content into tables — both formats get extracted as whole blocks most easily.
- Make PAA questions into H3s verbatim, each with an answer under 60 words.
- Add matching structured data so the crawler understands the page type more easily.
Don’t overdo structured data — only add the one or two types that genuinely match the content; markup that contradicts the page gets the whole block ignored. For the markup approach, refer to the structured data guide for FAQ, article, and breadcrumb markup.
When siphoning is severe, divert with long-tail and video
Some head keywords already have their first screen stuffed with modules, and fighting for them head-on has poor ROI. Instead, split the core content into long-tail pages for comparison, pricing, and troubleshooting — long-tail results usually still show a clean ten blue links, with CTR several times higher.
Turning the same content into a 60–90 second explainer video also recovers some traffic from video results. The video doesn’t need polish — putting the conclusion first and completing the captions matters more than production quality.
| Siphoning module | Priority response | Time to effect |
|---|---|---|
| Featured snippet | Answer-first + structured markup | 2–6 weeks |
| People Also Ask | Turn questions into short H3 answers | 2–4 weeks |
| Video carousel | Add a short explainer video | 3–8 weeks |
| Map pack | Improve business profile and local pages | 4–8 weeks |
| AI overview | Diversify with long-tail instead of fighting head terms | Ongoing |
When it actually comes to execution, the moves aren’t complicated: today, sort by query in Search Console and export the 10 terms with the biggest CTR drops; then search each in an incognito window, recording the above-the-fold modules and your position on both desktop and mobile; for single-page problems, rewrite the title and meta description this week, changing only one variable so attribution stays clean; for module siphoning, pick 3 terms for answer-first restructuring with matching structured data; two weeks later, recheck CTR on the same batch and turn what worked into a template. After one round, “ranked but not clicked” stops being an unsolvable mystery and becomes a checklist you can just follow.
