Why did my Google rankings drop?

To check why your rankings dropped, first pin down what dropped, because “rankings dropped” can describe several different events. Clicks may have fallen while impressions held steady. A handful of commercial pages may have lost position while the rest of the site grew. Reported traffic may have disappeared because consent or analytics code changed. None of these observations alone meets the definition of a Google penalty. Each case requires a different response.

Open Search Console's Performance report and compare the loss period with both the preceding period and the same period a year earlier. Use the available 16 months when seasonality or a slow change matters, and check Google's Data Anomalies record before treating the newest points as complete. Then separate the data by Search type, page, query, country, device, and search appearance. The useful unit is not “the site.” It is the smallest affected group that shares the same change. The first-party Google penalty checks put the relevant reports in a bounded order without turning them into a score.

If impressions are stable but clicks are down, start with the result itself: position, title, snippet, rich-result changes, and what else now appears on the page. If both impressions and clicks fell, continue to indexing, demand, and ranking explanations. When the first sustained loss overlaps a broad rollout, the Google core-update comparison defines what that timing can and cannot establish.

Compare analytics against Search Console before treating either as ground truth. A tracking deployment, consent change, hostname mismatch, or channel reclassification can create a traffic loss that never happened in Search. Once that site timeline exists, the official Google Search update history can supply a rollout window without replacing it.

Next, inspect the Page indexing report and representative URLs with URL Inspection. Look for new noindex directives, robots rules, canonical changes, redirects, server errors, rendering failures, and accidental URL migrations. Check release history, CDN rules, CMS updates, and template changes around the first affected date. A broad technical change matching the exact affected section is stronger evidence than a public update that happened in the same month.

Finally, use Google Trends and business data to test demand. If impressions fell across your site and the wider market, the site may be holding its share of a smaller search market. No amount of canonical-tag theatre repairs seasonality.

Open Search Console's Manual Actions report and Security Issues report. A manual action is a specific status issued after human review; it is not a synonym for a bad graph or every kind of Google penalty. If the report names an issue, follow the affected pattern and remediation instructions. Remediation comes before any review request.

If the report is clean, there is no manual action to remove, and the website’s ranking loss has another cause: automated spam systems, broad ranking changes, competitive changes, relevance shifts or ordinary site defects, none of which has a reconsideration request.

Once the affected pages and start date are clear, compare them with the official update history. A close date makes an update worth investigating; it does not establish that the update caused the loss. Use a core-update comparison when a broad rollout overlaps the window. Look for a coherent difference between winners and losers inside the site. If all URLs using one template fell, inspect the template. If queries in one intent class fell, compare what the results now reward. If the entire market moved, widen the comparison.

The output of this work should be a ranked set of explanations with evidence for and against each one. That is enough to decide what to change. A dramatic label is not. From there, a Google penalty recovery service makes the change on the site and reads what Google does with it before making the next.