Verified against ChatGPT · 2026-08-12
Triage a page's traffic drop into an actual cause before rewriting anything
Works through a declining page's traffic data and content history to identify the most likely cause of the decay — outdated information, SERP feature displacement, cannibalization, or a real ranking drop — before committing to a rewrite.
The prompt
Ready to copy — highlighted parts are example details you can swap.
A page's traffic has dropped and I need to figure out why before deciding whether a rewrite is even the right fix. Walk through this as a triage, ruling causes in or out based on the evidence given, not defaulting to "refresh the content" as the answer before checking. PAGE AND TRAFFIC HISTORY Blog post ranked position 3 for 8 months, organic clicks dropped 60% over the last 6 weeks; average position reported as still around 4-5. CONTENT AGE AND LAST UPDATE Published 14 months ago, no updates since, references pricing that changed 3 months ago. WHAT ELSE CHANGED AROUND THE DROP No known site-wide technical changes; unsure if there was a relevant algorithm update in that window. OTHER PAGES ON THE SITE THAT MIGHT OVERLAP A newer post published 2 months ago covers a very similar topic with a different title. CHECK THESE CAUSES IN ORDER, using only the evidence given — do not assume a cause you can't support from what's provided, and say explicitly which causes you can't confirm or rule out with the current information: 1. Cannibalization — did another page on the site start ranking for the same keyword around when this one dropped, splitting traffic rather than losing it? 2. SERP feature displacement — did a new SERP feature (AI overview, featured snippet, a new result type) appear around the drop date that could be taking clicks without this page's ranking position actually falling? 3. Genuine ranking drop — did the position itself fall, and if so, does the timing line up with anything else that changed (a core algorithm update, a competitor publishing something new, a technical site change)? 4. Content staleness — is the actual information on the page now outdated in a way a visitor or Google would notice, separate from ranking position? For whichever cause the evidence best supports, state what specific fix follows from that specific cause — a rewrite is the right fix only for genuine ranking drops tied to content quality or for content staleness; it's the wrong fix for cannibalization or SERP feature displacement, which need a different kind of intervention entirely. Output as: a checked/unchecked/insufficient-evidence status for each of the four causes with your reasoning, then a single recommended next action tied to whichever cause is best supported.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The instruction to check causes in a specific order rather than jumping to a conclusion counters the strongest default behavior GPT-5.1 has around traffic-drop questions, which is to reach immediately for "the content is outdated, refresh it" because that's the most common advice pattern in SEO content the model was trained on — but that diagnosis is frequently wrong, since a stable or even improving average position paired with a real traffic drop is actually the signature of cannibalization or SERP feature displacement, not content staleness, and applying a rewrite to that situation wastes real effort while leaving the actual cause (a competing internal page, or a new AI overview eating clicks) untouched. Requiring the model to explicitly mark a cause as "insufficient evidence" rather than confirming or denying it on a guess is the load-bearing accuracy control, since the input data given here is often genuinely incomplete (no algorithm-update timeline, no cannibalization check run yet), and a model under pressure to give a confident diagnosis will otherwise fill that gap with a plausible-sounding but unverified explanation. Tying the final recommendation explicitly to the specific cause identified — rather than giving a generic list of things that might help — is what makes this triage actionable rather than just descriptive, since a cannibalization fix (consolidate or differentiate the two competing pages) and a staleness fix (update specific facts) are different work with different owners, and conflating them under one "refresh the content" recommendation would send the wrong team down the wrong path.
What you get back
Cannibalization: likely — a newer post on a very similar topic was published 2 months ago, right before the traffic decline started, and average position for the original page has stayed roughly flat, which fits a traffic-splitting pattern better than a genuine ranking loss. SERP feature displacement: insufficient evidence — no information given on whether a new SERP feature appeared. Genuine ranking drop: unlikely — average position hasn't meaningfully changed. Content staleness: partially relevant but secondary — outdated pricing should be fixed regardless. Recommended action: audit whether the newer post targets the same primary keyword; if so, consolidate or differentiate them rather than rewriting the original page first.
Verified against
ChatGPT GPT-5.1 · 2026-08-12
Changelog
- 2026-08-12 — Initial publish, verified against ChatGPT GPT-5.1.
Building this for real?
This is a free starting point. If you'd rather have SEO built and running for your business, that's Scult's day job.
EXPLORE SEO
