Why Did My Google Rankings Drop? What to Check

Why did my Google rankings drop?

Google rankings drop for five reasons, and the order you check them in matters more than the list. Start with your own data: confirming the drop is real takes ten minutes, while the expensive responses, rewriting content and disavowing backlinks, do damage when the diagnosis is wrong.

1. It isn't a ranking drop. The average moved because the mix of queries changed, a rank tracker measured one location, or the last two days of data are still provisional.
2. Google can't crawl or index the page. A robots.txt rule, a noindex, a canonical pointing elsewhere, a broken redirect, server errors, or a CDN rule refusing Googlebot.
3. Google updated its systems. A core update or a spam update re-ranked the results. Google confirmed two core updates and four spam updates in 2026 up to 24 September.
4. The results page changed around you. A competitor published something better, you lost backlinks, the search intent behind the query shifted, or new result types moved in above you.
5. A penalty. A manual action from a Google reviewer, or an automated demotion for breaking Google's spam policies.

Before working down that list, run what we call the real, wide, fast test: is the drop real, how much of the site does it touch, and how quickly did it happen? The answers usually point at one of the other four causes before you open a single page.

Is the ranking drop real? Check Google Search Console first

Every guide on this question tells you to check Search Console. None of the six we read on 24 September 2026 mentions that its headline number can move a long way with no ranking lost. Google Search Console calculates average position across every impression, using the topmost position your site held each time. In Google's words, the metric "averages the position value for all impressions".

That makes it a blend. When a site starts appearing for new queries deep in the results, the average gets worse while every existing ranking holds. When those deep queries fall away, the average improves with nothing improved.

Split the average before you trust it

• Branded and non-branded. Search Console's branded queries filter, open to all eligible sites since March 2026, separates searches for your name from everything else. Falling branded impressions mean fewer people searched for you, which no SEO change fixes. The filter isn't offered for sub-properties such as example.com/blog/ or for sites with few impressions.
• By query, not by site. List the queries that earned clicks last period and read their positions this period. If they held, the average moved because of queries that never mattered.
• By device and country. A drop confined to mobile or one market points at a template or a local competitor.

Four reporting effects look like a ranking drop and aren't one:

• Provisional days. The newest day or two in Search Console are not final and rise as Google completes them. A dip at the right-hand edge of the chart is usually the chart.
• Rank tracker snapshots. A rank tracker such as Semrush or Ahrefs checks keyword rankings from one location on one device at one moment, so it and Search Console often disagree, and one tracker reading is not evidence of a ranking loss.
• A broken analytics tag. If Google Analytics shows organic sessions falling while Search Console clicks hold steady, the tracking broke, not the rankings. A release that drops the tag from one template produces exactly this pattern.
• Clicks down, position steady. That is a click problem, and impressions without clicks in Search Console is a separate diagnosis with different causes.

The check that settles it: in the Performance report, choose Compare on the date filter, set the last 28 days against the previous period, and read the Queries tab rather than the chart. If the queries that earned your clicks still hold their positions, you don't have a ranking drop.

How wide and how fast did your rankings drop?

Width and speed narrow the cause faster than any list of causes. This table is the core of a ranking loss audit: find the row that matches what you see, and start where it tells you to.

Google draws a similar line. Its guide calls moving from position 2 to 4 for a query a small drop, and says you might see a noticeable fall in traffic without a big change in impressions. It calls a drop across a wide range of terms, from the top 10 to position 29, a large drop, and tells you to assess the whole website rather than individual pages.

Speed matters because causes have signatures. A robots.txt mistake, a stray noindex or a deleted page takes effect the next time Google fetches it, and important pages are fetched often. A core update works over the one to two weeks it takes to roll out. A page that is simply being outcompeted rarely loses its ranking on a single day.

Is a technical issue stopping Google crawling the pages?

Rule out technical SEO issues next, because they're the cause you can fix in an afternoon and the one that gets worse the longer it runs. Run the URL Inspection tool in Google Search Console on the exact pages that fell, including the live test, and read four things: whether the page is indexed, whether crawling is allowed, whether a noindex is present, and which canonical Google chose.

• robots.txt. A rule added during a deploy, or a staging file shipped to production, stops Google crawling everything it matches.
• noindex. A meta tag or an X-Robots-Tag header left over from staging removes pages from the index outright.
• Canonical. If Google chose a different canonical from the one you declared, the URL it ranks isn't the one you're measuring.
• Redirects and status codes. A redirect chain, a redirect to an irrelevant page, a soft 404, or a run of 5xx server errors during an outage.
• Security issues and removals. Search Console's Security issues report flags a hacked site, and the Removals tool shows whether anyone with access asked Google to hide a URL.
• Your CDN or firewall. A bot rule at the edge can refuse Googlebot while every check on your own server passes, because your server never sees the request.

Indexing isn't permanent even when nothing is wrong. Google reassesses pages, and a live page with no error can move from indexed to crawled, currently not indexed with no change on your side. Our guide to checking when Google indexed a page covers how to confirm it and what each verdict means.

The Cloudflare setting that now blocks Googlebot

Since 15 September 2026, choosing Block for AI training in Cloudflare also blocks Googlebot, Applebot and Bingbot, because each of them crawls for search and for training with the same crawler. Cloudflare's announcement (opens in a new tab) says Block and Block on pages with ads "now apply to mixed-use crawlers, including Applebot, Bingbot, and Googlebot, so either setting impacts search as well as training".

Existing settings weren't switched to Block. Cloudflare migrated earlier training blocks to a new option, Disallow AI Training, which refuses training while leaving those crawlers free to index for search. The risk is a Block chosen after 15 September by someone who thought they were only stopping AI training. Blocking AI crawlers at Cloudflare covers the robots.txt side of the same decision.

You'll recognise it by a mismatch. The page loads normally in your browser, but the URL Inspection live test, which fetches as Googlebot from Google's own network, fails or returns a 403. That combination points at the edge, not the page.

Did a Google algorithm update cause the drop?

Check the date against Google's Search Status Dashboard (opens in a new tab) next. It takes two minutes, and a confirmed update on the day your rankings dropped changes everything you do after it. Google lists every confirmed ranking update there with its start date and how long the rollout took.

Google began the September 2026 spam update on 24 September 2026, said it applies globally and in all languages, and gave the rollout up to two weeks. If your rankings dropped inside that window, check the dashboard for its end date and measure after it, because nothing measured during a rollout is final.

Core updates are not small events. SE Ranking tracks the same 100,000 keywords (opens in a new tab) across 20 niches in New York results through every core update. Across the March 2026 spam and core updates combined, measured from 16 February to 9 April 2026, 79.5 per cent of top-three results changed position and more than 24 per cent of top-10 pages fell out of the top 100 entirely. After the May 2026 core update, that second figure was 19.87 per cent.

Don't read too much into who won. Lily Ray's analysis for Amsive compared SISTRIX visibility on 27 March and 8 April 2026 across the 2,076 domains that moved most, and read the March core update as a first-party, official-source correction favouring brand-owned and government sites over user-generated content and comparison aggregators. YouTube alone lost 567 visibility points. After the May 2026 core update, SISTRIX measured YouTube up 591.66 points in the US.

How to confirm a core update hit you

Google's core update guidance (opens in a new tab) is specific: wait at least a full week after the update completes, then compare that week with the week before the rollout started. Measuring during a rollout compares a moving target with a fixed one.

If you lost Google rankings after an update and the drop is site-wide, the answer isn't on any single page. Google's advice for a large drop is to assess the site as a whole for content that is helpful, reliable and written for people.

Did website changes cause the ranking drop?

Line the ranking drop up against your own website changes before blaming Google. The self-inflicted drops worth looking for come from changes nobody thought of as SEO work: a redesign, a template edit, a CMS or plugin update, a navigation change that removed internal links, or a URL change without redirects.

Site migrations belong on this list in their own right. Google's guide says that if you change the URLs of existing pages you may see ranking fluctuations while Google recrawls and reindexes the site, so a migration with every redirect mapped can still take weeks to settle. One with missing redirects doesn't settle at all, because the old URLs lead nowhere.

A new page can compete with an old one. If you published a page on the same topic, open Search Console's Pages tab for the query that dropped. If two of your URLs appear for one query, Google is choosing between them, and each URL on its own can look as if it lost ground.

Internal links are the change people miss most. A page that loses the links pointing at it from established pages loses part of the signal telling Google it matters, and nothing on the page itself looks different. Compare the internal links to the page before and after the drop.

Core Web Vitals get blamed for sudden drops more often than the timing allows. Google's page experience data comes from real users over a rolling 28 days, so a slow release can't show up in it overnight. Fix a genuinely slow page, but look elsewhere for the cause of a drop that happened in a day.

A change log only explains what it recorded. Edits made directly in a CMS, hosting incidents and DNS changes often leave no trace, so an empty log means nothing was recorded, not that nothing changed.

Did competitors, backlinks or search intent change?

If Google can reach the page, no update lines up and nothing on your site changed, look at the search results themselves. Search the query in a private window and compare the first page with what ranked before.

• A competitor improved. A page that is more specific, more current or better sourced takes the position. Google's core update guidance makes the point with a list of restaurants: one that moves down a top-20 list isn't necessarily bad, there are just others that made the list.
• You lost backlinks. A strong page that linked to you was deleted, redirected or edited. Check your backlink profile in Ahrefs or Semrush for high-quality links lost around the date the ranking dropped.
• The search intent shifted. Google decided the query wants a different kind of page, a comparison instead of a guide or a product page instead of an article. Your page stopped matching what searchers want.
• New result types moved in. AI search features such as AI Overviews, a video carousel or a forum block push organic results down the screen. That costs clicks even when the position number barely moves.
• Seasonality. Demand for the query fell. Google suggests loading 16 months of data to see a yearly pattern, and checking Google Trends for the topic.

A search intent shift is the hardest cause to reverse and the easiest to spot. If the pages now ranking are a different type from yours, rewriting yours won't bring the ranking back. Building the type of page the results now reward might.

Is it a Google penalty or a manual action?

Probably not, and Google Search Console tells you in a minute. A manual action is a penalty applied by a person at Google, and it appears in the Manual actions report. If that report shows a green check mark, you don't have a manual penalty.

Algorithmic demotions arrive without notice. A spam update is the automated version, and Google's documentation says a site can improve if its systems learn over a period of months that the site complies with the spam policies.

Link spam is the exception to know about before you pay for a recovery. Google says that when its systems remove the effect of spammy links, any ranking benefit those links generated is lost and "cannot be regained". A disavow file won't restore those positions, because the value those backlinks once carried no longer exists.

How long does it take to recover from a Google ranking drop?

How fast you recover lost rankings depends entirely on the cause, from days for a technical fix to never for rankings that rested on spam links. Every timescale below comes from Google's own documentation rather than from case studies.

SE Ranking put a number on months. Of the domains that lost top-10 positions in the March 2026 updates, 32.2 per cent were back in the top 10 after the May core update, and 67.8 per cent were not.

Google's core update page adds a caveat worth applying to every row: there is "no guarantee that changes you make to your website will result in noticeable impact in search results". It also runs smaller core updates it never announces, which it describes as another way improved content can rise between the big ones.

What not to do in the first week after a ranking drop

Wait, unless the cause is technical. For a core update Google recommends waiting at least a full week after it completes before analysing. For anything else, a week of data turns one bad day into either a trend or nothing.

• Don't rewrite pages that still rank. Changing the pages that held their positions adds a second variable and makes the first impossible to read. Google's own debugging guide says the same: avoid radical changes to a page that is already performing well.
• Don't disavow backlinks in a panic. A disavow file is for links you built or bought and cannot remove. It is not a response to a core update, and disavowing good links by mistake removes value you had.
• Don't change titles across the site. A title rewrite can help a page in the top ten that answers a different question from its query. Applied site-wide, it's a change you can't measure.
• Don't delete or redirect the pages that fell. A page that dropped is still indexed and still earning something. Deleting it turns a ranking problem into a missing page.
• Do fix a technical block the moment you find it. A robots.txt rule or a CDN block is the one cause that gets worse every day it stays.

The ranking drop checklist, in order

Ten checks, cheapest first. Stop at the first one that explains the drop, fix that, and measure again before you touch anything further down the list.

1. In Search Console, compare the last 28 days with the previous period and read positions by query, not the site average.
2. Split branded from non-branded queries, then by device and country.
3. Compare Google Analytics organic sessions with Search Console clicks to rule out a broken tag.
4. Find your row in the width and speed table.
5. Run URL Inspection, with the live test, on the pages that fell.
6. Check robots.txt, noindex, canonicals, redirects, and the Security issues and Removals reports.
7. Check CDN and firewall bot rules, including Cloudflare's Training setting.
8. Match the start date against the Search Status Dashboard, and wait a week after any update completes.
9. List everything shipped to the affected pages or templates in the week before, including internal link changes.
10. Compare the live results with what ranked before, check lost backlinks, then open the Manual actions report.

How RankX AI helps diagnose a Google ranking drop

RankX AI connects to Google Search Console and reports position by query and by page as well as the site average, so you can see whether a worse average came from new, deeper queries or from the queries that already earned your clicks. It also reads Google's URL Inspection verdict for your pages: whether each is indexed, whether robots.txt or a noindex blocks it, and which canonical Google chose.

The RankX AI website audit crawls your site for the on-site causes in this article: broken internal links, redirect chains, canonicals that point at broken pages and sitemap URLs that no longer resolve. Google rankings tracking records positions on a schedule you set, from daily to every 30 days depending on plan, so a drop can be dated against the update log above.