Why Google Rankings Drop: A Step-by-Step Checklist

You open your dashboard and your most valuable keyword has slipped from position 3 to 14. The instinct is to change something immediately: rewrite the title, add more words, chase links. But changes made without knowing the cause rarely fix the problem, and they can make recovery harder to read.

This checklist is designed to help you work through a Google ranking drop methodically. The order is deliberate: the quickest, cheapest checks come first and the heavier investigations come last.

First, is it actually a problem?

Google's guide to debugging traffic drops is refreshingly direct: positions are not fixed, and because the web keeps changing, results keep changing too. The same guide says small position shifts (say, from 2 to 4) can happen at any time, can reverse without you doing anything, and recommends avoiding radical changes to a page that is already performing well.

So the first question is not "what should I change?" but "is this a meaningful drop at all?" We explain the nature of everyday movement in why Google rankings change.

Define the drop

Before you start the checklist, answer three questions:

The Google ranking drop checklist

1. Rule out measurement and reporting errors

Make sure the data itself is right. Google's guide lists reporting glitches among possible causes and suggests checking the Search Console data anomalies page.

• Do Search Console, your rank tracker and Analytics all point the same way?
• Are you measuring the right country or region and device? Mobile and desktop rankings can differ; see mobile vs desktop rankings.
• Could a lower Search Console average simply reflect new, weaker queries you have started appearing for? More in our guide to average position.
• Did an analytics tag go missing or change? A traffic "drop" may be a tracking issue, not a ranking one.

2. Check for technical issues

According to Google, technical issues are errors that stop Google from crawling, indexing or serving your pages: server availability, robots.txt fetch failures, "page not found" and so on. They can be site-wide (the site is down) or page-level (a stray noindex).

• Do the site and the affected pages load? Any 5xx errors?
• Is there an accidental noindex or a wrong canonical on the pages that dropped?
• Did robots.txt change recently, and does it block important sections?
• Do the Page indexing and Crawl stats reports show a spike in issues around the date of the drop?
• Any recent theme, plugin, CMS or hosting change?
• Is the SSL certificate valid?

Google also notes that a misplaced noindex shows up gradually, since it depends on Google recrawling the page. The technical mistake may predate the drop by days.

3. Site moves, URL changes and redirects

• Did you change URL structure, domain or protocol in recent weeks?
• Does every old URL 301-redirect to its new equivalent in a single hop?
• Have internal links been updated, and are there redirect chains?

Google's site move documentation says to expect temporary ranking fluctuation during a move with URL changes. Short-term turbulence is normal; broken redirects can turn it into a lasting loss.

4. Check for algorithm updates

Google announces notable changes such as core updates on its ranking updates list and the Search Status Dashboard.

• Does the drop line up with the rollout window of an announced update?
• Is the drop concentrated in one content type (reviews, how-to guides, product pages)?

Google says a drop after an update does not necessarily mean something is fundamentally wrong with your content. For large losses (for example from the top 10 to position 29), its guide recommends assessing your whole site, not just individual pages, for whether it is helpful, reliable and people-first. It also states that some changes take effect in days and others in months, and that there is no guarantee any change will produce a noticeable impact.

5. Check security and spam issues

• Does the Security issues report in Search Console show anything? Google may warn users away from sites with malware or phishing, which cuts traffic.
• Does the Manual actions report list anything?
• Has spam been injected into user-generated areas (comments, forums, profiles) without your knowledge?
• Are there past practices, such as paid links, that may conflict with Google's spam policies?

Google's documentation states plainly that content not complying with its spam policies may rank lower or not appear at all.

6. Look at competitors and the results page

The results page may have changed even if your site did not.

• Search the keyword: who replaced you? A new competitor, or an older one that improved?
• Did new SERP features appear (images, videos, AI overview, featured snippet, map)? Your blue-link position may be unchanged while your visibility shrank.
• Has intent shifted? If product pages now rank where guides used to, your content type may no longer fit.
• Did another page on your own site take the dropped page's place? That is a sign of keyword cannibalization.

7. Check seasonality and changing interest

Google's guide notes that shifts in user behaviour and seasonality can change demand for some queries, and suggests filtering the Performance report one query at a time and comparing with Google Trends.

• Did clicks fall while position stayed flat? That points to lower demand, not lower rankings.
• Was there a similar dip at the same time last year?
• Has overall interest in the query declined on Google Trends?

Year-over-year comparisons need long history, and Search Console only shows the last 16 months. We explain the limit and how to keep your data in the Search Console 16-month data limit.

8. Review your own content changes

• Did the page's title, H1 or main content change recently?
• Were important sections removed or moved to another page?
• Did the page lose internal links after a menu or category restructure?
• Is the information on the page out of date?

What to do once you know the cause

Whatever you change, write down what and when. A few weeks later, that log is the only way to know what actually worked.

Catching drops early

The sooner you notice a drop, the easier it is to explain: fewer changes have happened in between and your server logs are still around.

SEOLOK's SEO alerts watch part of this checklist for you. You get an email and an in-app notice when a tracked keyword drops noticeably, when Google traffic falls, when your site goes down (checked every five minutes) and comes back, when an SSL certificate is about to expire, and when Search Console access is lost. With Google rank tracking, positions are measured as real rankings for the country or Turkish province you choose, on mobile or desktop, so you can look at "did the Search Console average fall, or the actual rank?" separately.

To quickly calculate how much a ranking has moved between two dates, try our free rank change calculator.

Printable summary

1. Define the drop: scope, timing, size.
2. Verify the data: second source, right location and device.
3. Technical checks: access, noindex, canonical, robots.txt, indexing report.
4. Migration and redirect checks.
5. Compare with the update timeline.
6. Security and manual action reports.
7. Results page, competitors and intent.
8. Seasonality and demand.
9. Your own content changes.
10. Log the fix and monitor for a few weeks.

A ranking drop is stressful, but it is usually explainable. Work through this list and you will either find a concrete cause or learn that the movement was outside your control and worth waiting out. Both outcomes beat changing things at random.