If you are asking why did my google ranking drop, the honest first answer is that you do not know yet, and neither does anybody who replies within thirty seconds. Rankings fall for at least a dozen distinct reasons, and the fix for one is useless against the others. Working through them in the wrong order is how businesses lose months rewriting content when the real cause was a checkbox somebody ticked during a redesign.
This is the elimination order we use, arranged so the free checks come first.
Step 1: Confirm the drop is real
A surprising share of ranking emergencies turn out to be measurement problems. Rule that out before you touch the site.
The comparison window trap
Search Console defaults to comparing the last 28 days against the 28 before it. If your business has any seasonality, or if the earlier period contained a spike from one piece of coverage, that comparison will show a fall that means nothing.
Compare like with like. Set the current period against the same period last year rather than the month before. For an Indian business, check whether a festival period, an exam season or a monsoon month sits inside one window and not the other.
Average position is an average, not a rank
This is the single most misread number in Search Console. Average position covers every query your site appeared for. Start ranking on page four for two hundred new terms and your average position gets worse while your actual business improves.
Filter before you panic. Look at the ten or twenty queries that produce real clicks and check those individually. If they are stable, you do not have a ranking problem.
Check one term by hand, properly
Search your target term in a private window, logged out, with location set to the city you care about. Personalisation and location both shift results enough to invent a drop that is not there. What you see logged in on your own laptop is not what a customer sees.
Open Search Console, set the date range to Compare, choose the same period last year, then filter to the five queries that bring you the most business. If those five are flat, close the tab. Whatever the overall graph is doing, your business is not losing anything that matters.
Step 2: One page, or the whole site?
This single question narrows the field more than anything else you can do, and it takes two minutes. Open the Pages report in Search Console, compare the same two periods, and sort by the biggest fall in clicks.
If everything fell together on roughly the same day, look for one site-wide event: a deployment, a migration, a server outage, a plugin update, a DNS change. Ask what happened on that date, not what is wrong with the content.
If one page fell while the rest held steady, it is about that page and the results around it. Site-wide causes do not produce single-page falls.
Step 3: The technical causes, which are free to check
These take about twenty minutes in total and account for a large share of sudden drops. None of them need a specialist.
An accidental noindex
The most common cause of a site vanishing outright. WordPress has a checkbox under Settings, then Reading, called Discourage search engines from indexing this site. Developers switch it on for staging and it travels to production more often than anyone admits.
Check it in Settings. Then check the page itself: view source and search for noindex. Rank Math and Yoast can also set noindex per post, per category, or across a whole post type, so a settings change can deindex a section without anyone touching a page.
robots.txt blocking
Visit yourdomain.com/robots.txt and read it. A line reading Disallow: / blocks the entire site. Blocks on /wp-content/ can stop Google rendering your pages properly, which affects how it judges them.
Use the URL Inspection tool on an affected page. It reports whether the URL is blocked by robots.txt in plain words.
Redirects that went wrong
After any URL change, three faults are common: a redirect chain several hops long, a redirect loop, or a bulk redirect that sends every old URL to the homepage rather than to its matching page. That last one destroys rankings while looking tidy, because Google treats it as the old page being gone rather than moved.
The server was down when Google crawled
Check the Crawl Stats report under Settings in Search Console. A spike in 5xx responses tells you the site was unreachable when Googlebot arrived. Cheap shared hosting under load does this quietly, and the site is fine again by the time anyone looks.
Canonical tags pointing somewhere else
A canonical tag tells Google which version of a page to index. Set wrongly, sitewide, it can tell Google that every page is a duplicate of the homepage. Migrations and some caching or SEO plugin conflicts cause this. View source on a fallen page and check that the canonical URL matches the page you are on.
If rankings fell within a fortnight of a redesign or a migration, the cause is almost certainly in this section. Redesigns change URLs, shorten copy for visual balance, drop internal links from the new navigation, and carry staging settings into production. Check the redesign before you check Google.
Step 4: Check for a manual action
Search Console, then Security and Manual Actions. If there is a manual action, Google states it outright and describes what triggered it. There is no ambiguity and no need to guess.
If that report is clean, you do not have a penalty. Most of what people call a penalty is an algorithmic reassessment, which behaves differently: no notice, no appeal, and recovery comes from improving the page rather than filing a reconsideration request.
Step 5: Content, competitors and the results page itself
Only now is it worth looking at the expensive explanations.
Somebody simply did it better
Open the term in a private window and read what now sits above you. Often the answer is obvious within a minute: a page that covers the question more fully, more recently, with clearer structure. This is not a fault in your site. It is a competitor doing the work.
Two of your own pages competing
If you have published several pages targeting near-identical terms, Google has to pick one, and it may not pick the one you meant. Search site:yourdomain.com plus the term and see how many of your own pages appear. Two thin pages usually perform worse than one merged page.
The page went stale against a dated query
For queries where users want current information, an older page slides regardless of quality. If the results above you carry this year in their titles and yours does not, freshness is doing the work rather than authority.
The results page changed, not your position
You can hold the same rank and lose most of your clicks. An AI Overview, a featured snippet, a shopping row or a larger local pack above you pushes the first organic result further down the page. Search Console will show impressions steady and clicks falling, which is the signature of this rather than of a ranking drop.
Step 6: Algorithm updates and seasonality
Google confirms broad updates publicly. Check the date your drop began against the confirmed update dates before attributing anything to one. Drops that begin on a random Tuesday with no update running are almost never algorithmic.
Seasonality deserves the same discipline. Search demand for a great many Indian categories moves with festivals, the academic calendar, the financial year end and the monsoon. Falling impressions with a stable position usually means fewer people are searching, not that anything is wrong with the site.
Search Console, screen by screen
Most people open Search Console, look at the big graph, and close it again. Four other screens carry the answers.
| Screen | What it answers | What to look for |
|---|---|---|
| Performance, then Pages tab | Is this site-wide or one page? | Sort by click difference. One page falling alone rules out most site-wide causes immediately. |
| Performance, then Queries tab | Did you lose rankings or lose clicks? | Impressions flat with clicks down means the results page changed above you, not your position. |
| Indexing, then Pages | Is Google still indexing you? | A jump in Excluded, especially Crawled but not indexed or Blocked by robots.txt, dated to your drop. |
| Settings, then Crawl stats | Could Google reach the site? | 5xx responses or a sharp fall in crawl requests around the same date. |
| Security and Manual Actions | Is this a penalty? | Either a notice exists or it does not. No interpretation needed. |
| URL Inspection, per page | What does Google see right now? | Coverage status, the canonical Google chose, and whether indexing is allowed. |
The URL Inspection tool deserves particular attention because it reports the canonical Google selected, which can differ from the one you set. When Google picks a different canonical, your page is being treated as a duplicate of something else, and that alone can explain a fall that looks inexplicable everywhere else.
Tools worth having, and how to use them
- Google Search Console, freeThe only source that reports what Google actually did. Everything else estimates. Set up the Compare view, the Pages report and URL Inspection before you install anything else.
- Rank Math or Yoast, freeCheck the indexing settings per post type. A section can be deindexed from one screen without anyone editing a page.
- Redirection plugin, freeShows 404 errors as they happen and lets you map old URLs to new ones properly. After a migration this is the fastest way to find URLs that lost their destination.
- Screaming Frog, free to 500 URLsCrawls the site as a search engine would and lists every noindex, canonical, redirect chain and broken link in one table. The free tier covers most small business sites.
- Query Monitor, freeUseful when the problem looks like performance or a plugin conflict rather than content.
The cause of a ranking drop is usually mundane and recent. Something changed on the site, or something changed above you in the results. An algorithm update is the explanation people reach for first because it requires nothing of them, and it is the least likely to be true on any given Tuesday.
What to do in the first 48 hours
- Write down the date it startedFrom the Search Console graph, not from memory. Then find out what changed on the site that week.
- Run steps one to fourAround thirty minutes of work, and it settles most cases.
- Fix only what you findOne change at a time, so you learn which one worked.
- Request indexing on affected pagesThrough URL Inspection, once the fault is corrected.
- Then waitReindexing takes days, not hours. Making five more changes while waiting removes your ability to tell what helped.
What not to do
- Do not rewrite every page at once. If it recovers, you will not know why, and you may have removed the pages that were still working.
- Do not file a reconsideration request without a manual action. There is nothing to reconsider and it achieves nothing.
- Do not disavow links speculatively. Google ignores most poor links already, and disavowing can remove ones that were helping.
- Do not change your domain or URL structure as a fix. It is the single fastest way to turn a recoverable drop into a permanent one.
- Do not buy links to compensate. That converts an algorithmic dip into a genuine manual action.
Working through this properly is a morning’s work for someone who has done it before. If the elimination order runs out and rankings are still down, the cause is usually competitive rather than technical, and the answer sits in content and internal linking rather than in settings. That is the slower half of SEO work, and it is worth being honest that it takes longer than a checkbox. If the drop began around a rebuild, our development team can audit what the migration changed before anyone rewrites a word.
Parshant Hadala