Google ranking drop recovery – find the cause, then fix it in the right order

Your rankings dropped: what to check in the first hour

Before treating it as a Google ranking drop, confirm what actually happened, when it started and which pages are affected. Broken tracking and seasonal swings in demand are often mistaken for a ranking drop, and ruling them out changes everything that follows.

• Search Console performance report: compare date ranges and see when impressions, clicks and average position moved
• Filter by page and query: is the whole site down, or only certain pages or keywords?
• Cross-check with GA4: if Search Console looks stable but GA4 traffic fell, suspect a missing tag or a settings change
• Manual actions and security issues: check both reports in Search Console for messages
• Recent changes: write down any redesign, hosting move, plugin or theme update or URL change made just before the drop

The start date and a list of affected pages narrow the possible causes a lot. Note the date down so you can compare against it later.

The four usual causes of a ranking drop

In practice, almost every drop falls into one of four groups. The shape of the drop (sudden or gradual) and its date are your best clues.

• Google updates: core or spam updates move the whole site, or a group of related pages, during the rollout window
• Technical errors: a stray noindex, a robots.txt block, server errors or wrong canonical tags make pages vanish from one day to the next
• Migration or redesign problems: missing 301 redirects, deleted high-value pages or broken internal links cause a drop right after launch
• Competitors and search layout: stronger competing pages, ads, AI answers or a bigger map pack can cut clicks even when your position holds

Causes can overlap – a core update landing a week after your redesign, for example. In that case, clear the technical problems first, then review content quality. If you want a full health check of the site, our SEO audit page lists what to review.

Recovering from a core update

Core updates are broad changes to how Google evaluates results, released several times a year. A rollout usually takes about two weeks, and Google announces start and end dates on its Search Status Dashboard. If your drop falls inside that window, a core update is the likely cause.

Google says pages that lose ground in a core update may have nothing specific wrong with them, so there is no quick fix to apply. The work is to review how well each page answers what searchers really want to know.

• Read the pages now ranking above you for the lost keywords and note what yours is missing
• Make it clear who wrote the content and what experience or evidence stands behind it
• Update outdated pages, and merge thin or overlapping ones
• If many articles exist only to chase rankings, prune them

Results may not show until the next core update. Heavy rewrites during a rollout make the cause harder to read, so wait until Google confirms it is complete, then make changes calmly.

Finding and fixing technical errors and migration mistakes

When pages disappear within days, or a whole section stops showing, the cause is usually technical or a migration slip – and these tend to recover faster once fixed. Check in this order:

• Indexing: look for a sudden rise in excluded URLs in the Search Console Pages report
• noindex and robots.txt: make sure staging settings did not go live, and that WordPress is not set to discourage search engines
• Redirects: open old URLs and confirm each one 301-redirects to the right new page
• Server and speed: watch for 5xx errors, timeouts or very slow mobile loading
• Canonicals and duplicates: look for every page pointing its canonical to the home page, or both http and https versions loading

After fixing, request indexing for key pages with the URL Inspection tool and resubmit your sitemap. If the drop followed a redesign or move, our guide to SEO during a site renewal covers the full checklist.

How recovery works – and what to avoid

Once you know the likely cause, fix the pages with the most impact first. Working in priority order and keeping a log shows you what actually helped.

• Start with the 10–20 pages that earned the most clicks before the drop
• Log each change and its date, and compare it with the Search Console trend
• Typically, technical fixes show results within weeks; content work takes months
• Track inquiries and sales in the same log, alongside positions

Avoid rewriting titles and copy again and again right after a drop, deleting low-ranking pages in bulk, or buying links and mass-producing AI articles to win rankings back. All of these blur the diagnosis and can make things worse. Once you are back and aiming higher, see how to improve search rankings.

How UNANOBO handles ranking drop recovery

Send us your site address and roughly when the drop started. We review the public pages, sort the likely cause into technical, migration, update-related or competitive, and build a free demo of improved versions of the pages that lost the most. You compare them side by side with your current pages and decide whether to go ahead.

The process is simple: free demo, feedback, launch, growth. The founder handles every project personally, from diagnosis to watching the numbers after the fixes go live, so you keep one contact throughout. Everything runs by message, in Japanese or English. Search Console and GA4 stay in your name; you simply share view access.