Diagnosing a ranking drop before you change anything
Confirm the drop is real in the keyword's stored history, check whether the ranking URL changed, compare Search Console clicks and impressions for the same window, then audit the affected page. Change nothing until one of those names a cause.
A drop is a symptom with four common causes: the measurement moved, a different page of yours took the slot, the page broke, or competitors got better. Each leaves a different trace, and checking them in order stops a fix being aimed at the wrong one.
1. Confirm the drop is real
Open the tracker and choose History on the keyword to see every stored position. One check is one observation:
- A keyword that moved from 6 to 9 and back over three checks is normal movement. Wait for the next check.
- A keyword that sat at 4 for two months and has read 15 for the last three checks has dropped.
- A keyword that reads not ranking may have fallen past the tracker’s depth rather than out of the index. At the default depth of 20, position 25 reads as not ranking. Look it up once on Keyword research with Who ranks at a depth of 100 before treating it as gone.
The Position matrix shows whether one keyword moved or a whole group did. A group moving on the same check points at the site or at Google; one keyword alone points at its page.
2. Check whether the ranking URL changed
Each stored position carries the URL that held it. Ask the
assistant for the keyword’s ranking URL at each
check, or read get_keyword_rank_history over MCP. If the
URL changed when the position dropped, two of your pages are competing for the
term and Google swapped them. The fix is to make one page the clear answer:
merge them, or point one at the other with a canonical or a redirect.
3. Compare Search Console for the same window
On Search performance, filter queries by the keyword and compare the last 7 days with the 28- or 90-day window, which still holds the weeks before the drop:
| What moved | Likely cause |
|---|---|
| Position down, impressions steady | competitors improved, or the result page gained features |
| Impressions down sharply, position steady | fewer people search for it; check the keyword’s monthly volume |
| Clicks down, position and impressions steady | the title or snippet stopped earning the click |
| Everything down across many queries | a site-wide problem; go to step 4 for the whole site |
Search Console reads cost no credits.
4. Audit the page, then the site
Run a site audit with the dropped page as the Start URL and a small page count. The issues that explain sudden drops are the critical and warning ones: Page is set to noindex, Server error, Page returns an error, Redirect chain, Conflicting canonical and Duplicate page content. A crawled page costs 1 credit, so a 50-page check of one section costs 50.
If many pages dropped at once, crawl the whole site and look for the same issue across one URL shape; see auditing by template.
5. Write down what you found
Record the cause and the fix in the project’s research log under context. The next person, or the assistant, reads it before suggesting the same investigation again, and the tracker’s history after the fix shows whether it worked.