Why Did My SEO Rankings Drop? 7 Checks to Find the Cause

You checked your traffic this morning and something is wrong. The graph that was slowly climbing for months just fell off a cliff. Your best-performing page is gone from page one. Leads are down. Revenue is down. You are Googling "why did my rankings drop" with a knot in your stomach.

Take a breath. This is fixable. But speed matters — the longer a problem goes undiagnosed, the longer recovery takes. Here is a systematic checklist that covers the most common causes, ordered by severity and how fast you need to act.

The short answer: when a website drops in Google rankings, the cause is almost always one of seven things — pages fell out of the index (often an accidental noindex), a manual action, a Google algorithm update, a change to the page itself (title, content, canonical), lost backlinks, a technical problem (slow pages, server errors, redirects), or no real drop at all, just seasonality or a reporting artifact. Check them in that order: the first ones are the most damaging and the fastest to fix.

Step 1: Check If Your Pages Are Still Indexed

This is the first thing to check because it is the most severe. If Google has removed your pages from its index entirely, you are not just ranking lower — you are invisible.

Open Google Search Console. Go to Pages. Look at the "Not indexed" section. If you see a spike in pages being excluded, you have found the problem.

Common causes:

A noindex tag was added during a deployment. This happens more than you would think. A developer adds noindex to a staging environment to prevent Google from indexing test pages. The staging branch gets merged to production. The noindex tag goes live. Google obeys it within days. Your pages disappear from search results.

A robots.txt change is blocking pages. Someone edited the file and accidentally disallowed an entire directory. Google cannot crawl what robots.txt blocks, and blocked pages eventually get deindexed.

Canonical tag confusion. A plugin update changed your canonical URLs. Google sees two different URLs claiming to be the canonical, gets confused, and deindexes one or both while it sorts things out.

Fix: If pages were accidentally deindexed, fix the root cause (remove the noindex tag, fix robots.txt, restore canonical URLs) and request reindexing through Search Console. Recovery takes days to weeks depending on how long the problem existed.

Step 2: Check for Manual Actions or Security Issues

In Search Console, go to Security & Manual Actions. If Google has applied a manual penalty, it will be listed here. This is rare for legitimate sites, but it happens — especially if someone built spammy backlinks to your site or if the site was hacked and is serving malware.

Fix: If there is a manual action, follow Google's specific instructions to fix it and submit a reconsideration request. If the site was hacked, clean it thoroughly before requesting review.

Step 3: Was There a Google Algorithm Update?

Google runs core algorithm updates several times per year. Each one reshuffles rankings based on updated quality criteria. If your drop coincides with a confirmed update, the cause is likely algorithmic rather than technical.

How to check: search for "Google algorithm update [current month]" or check the Google Search Status Dashboard. SEO news sites track these closely.

What this means: Algorithmic drops are harder to fix because there is no single broken thing to repair. Google changed what it considers a good result for your queries. Usually this means your content needs to be substantially better, more comprehensive, or more aligned with what searchers actually want.

Fix: Look at what is now ranking above you. Read those pages. Be honest about whether they are better. If they cover topics you missed, have better structure, or answer the query more directly — that is your roadmap.

Step 4: Did Someone Change Your Pages?

This is the cause most site owners miss because nobody logs content edits.

A content editor rewrites a title tag and drops the target keyword. A designer removes the H1 heading because it clashed with the new layout. A developer redirects a high-traffic URL to a new page structure. Each of these can cause a ranking drop within days.

What to check:

• Title tags — was the target keyword removed from the title of the page that dropped?
• H1 headings — was the H1 changed or removed entirely?
• Content — was significant text removed or rewritten?
• URL structure — was the URL changed without a proper 301 redirect?
• Internal links — were links to the affected page removed from other pages?

This is where content change monitoring becomes essential. If you are not tracking what changes on your site between crawls, you are flying blind. You cannot diagnose a ranking drop if you do not know what changed.

Fix: If a title or content change caused the drop, revert it. If a URL changed, make sure the old URL has a 301 redirect to the new one. If internal links were removed, restore them.

Step 5: Did You Lose Backlinks?

Backlinks from other websites are one of Google's strongest ranking signals. If a page with many backlinks suddenly loses several of them — the linking sites removed them, changed their pages, or went offline — your rankings can drop.

How to check: Use Google Search Console's Links report to see your current backlink profile. If you have historical data, compare the current count to previous months. A sudden drop in referring domains is a red flag.

Fix: If important links were removed, you can reach out to the linking sites and ask why. But this is often not recoverable. The better long-term strategy is to keep earning new links through useful content rather than depending on a few specific ones.

Step 6: Check for Technical Problems

Sometimes the cause is not SEO-specific at all. It is the site itself.

Server issues. If your site was down or slow when Googlebot tried to crawl it, Google may have reduced your crawl rate or temporarily demoted your pages. Check your server logs and uptime monitoring for outages.

Speed degradation. A new script, a larger image, an additional tracking pixel — each adds load time. If your page got slow enough to cross Google's Core Web Vitals thresholds, it can affect rankings. Check PageSpeed scores and compare to previous measurements.

Mobile rendering issues. Google primarily uses mobile rendering for indexing. If your page looks fine on desktop but is broken on mobile — overlapping elements, unclickable buttons, content hidden behind menus — Google may demote it.

Fix: Fix server stability, optimize page speed, and test mobile rendering. These fixes tend to have gradual positive effects rather than immediate ranking recovery.

Step 7: Is It Actually a Drop?

Before you panic, verify that the drop is real and not a data artifact.

Seasonal variation. Many industries have natural traffic cycles. A tax accountant's traffic drops every May. A ski resort's traffic drops every summer. Compare year-over-year, not just week-over-week.

Tracking issues. Did someone break the analytics tracking code? A missing Google Analytics snippet will show zero traffic even though real users are visiting. Check Search Console clicks as a second data source — if clicks are stable but GA shows a drop, your tracking is broken, not your rankings.

Position fluctuation. New and recently updated pages bounce around in rankings for weeks before stabilizing. A page that jumped to position 5 last week and is now at position 12 may simply be in Google's testing phase. Give it two to three weeks before concluding the drop is permanent.

Average position fell, but nothing actually dropped. Search Console's average position is an average over every query your page appeared for. When a page starts showing for new, broader queries at position 60–90, the average gets worse — even if it holds its place on every query it ranked for before. Before you call it a drop, compare positions for the same queries across both periods (Performance → Queries, compare date ranges). If those held steady, your page didn't lose anything; it gained visibility.

How to Prevent This From Happening Again

Every ranking drop listed above has one thing in common: the problem existed for some time before anyone noticed. The noindex tag sat in production for a week. The title change went unreviewed. The speed regression accumulated over three deploys.

The fix is monitoring. Not checking Search Console manually every Friday — by then the damage is done. Automated monitoring that watches your pages and tells you the moment something changes.

What to monitor at minimum:

• Indexation status — are your pages still in Google's index?
• Noindex tags — did any page gain a noindex directive?
• Title and meta changes — was a critical title rewritten?
• Broken links — did a batch of internal links break?
• Page speed — did Core Web Vitals cross a threshold?
• Uptime — was the site unreachable when Google tried to crawl?

You can cobble this together from Search Console email alerts, a speed monitoring tool, and periodic manual checks. Or you can use a tool that watches all of these in one place.

Seodile monitors your site daily and alerts you on exactly these changes — noindex additions, title edits, broken link spikes, speed regressions, and content modifications. It catches the problem when it happens, not when you notice the traffic drop two weeks later.

Start a free audit → — no credit card, no setup. Enter your URL and see what Seodile finds.

Related

• 5 Website Changes That Kill SEO Rankings Overnight — the specific changes to watch for
• SEO Ranking Alerts: Get Notified Before You Lose Traffic — automated ranking monitoring for small teams
• How to Know if Your SEO Is Working — the 5 metrics that tell you whether things are on track