TRAFFIC & RANKINGS · FIELD GUIDE

Google rankings dropped: isolate the affected searches

Verify that the same page and query lost position under comparable country, device and date filters. A worse site-wide average position can be a change in query mix rather than a ranking loss for your important searches.

Confirm the loss on a consistent set of searches

Start with completed Search Console dates and the pages that lost meaningful clicks. Compare queries present in both periods. Record country and device. If you use a separate rank tracker, keep its location and keyword set constant; its point-in-time observation is different from Search Console’s aggregate.

Worked example

Illustrative case: your established queries stay around positions 3–5, while new queries appear around position 30. The site’s average position worsens, but those established rankings did not fall. A site-wide average alone would send the investigation in the wrong direction.

Map the scope before changing content

Group affected URLs by template or site section. A single URL, all product pages and the entire site suggest different investigation priorities. Also inspect unaffected pages: they help identify whether the problem follows a shared deployment or is limited to particular searches.

  • Record lost clicks alongside position changes.
  • Identify whether the original URL was replaced by another URL.
  • Separate a missing indexed page from a page that still appears lower.

Rule out observable technical problems

Check redirects, HTTP errors, noindex and canonical targets for representative URLs. Compare the last known indexed version with today’s page. A page that stopped returning useful content needs a different response from an accessible, indexed page whose competitors have changed.

Treat an algorithm update as context

Consult Google’s published ranking-update information and compare the timing with your observed decline. Do not conclude causation from the dates alone. If technical checks are clean, review how well affected pages meet the actual search task, including freshness and missing information. There is no universal recovery edit.

Keep a reversible investigation plan

Prioritize confirmed faults, then evaluate one content hypothesis at a time. Record what changed and what subsequent evidence would support or weaken that hypothesis. Avoid deleting useful sections or rolling back an entire site simply because an aggregate chart moved.

Worked example

A practical note: “Only comparison pages lost clicks on matched mobile queries. No new response errors. Next: compare whether the pages answer current comparison questions and review dated search results.” This states a testable next step without pretending the cause is known.

Browse all diagnosis guides

Primary references

These references describe Google’s reporting and crawling behavior. The worked examples above are illustrative, not customer results.