Manual Action vs Algorithmic Ranking Drop: How to Tell

A sudden decline in search traffic can come from a manual action, an algorithmic ranking change, or a technical problem—and each calls for a different response. Use the checks below to identify the strongest evidence before changing your site; you will need access to Google Search Console and, ideally, analytics and server records.

What You’ll Need

• Verified access to the site’s Google Search Console property.
• Search performance data, including clicks, impressions, queries, pages, and dates.
• Analytics or other reliable records of visits from organic search.
• A record of site changes, deployments, migrations, and SEO work around the time the decline began.
• Optional: server logs or help from a developer to check crawling and indexing.

Step-by-Step

1. Confirm that a real search decline occurred. In Search Console, open Performance and compare the affected period with a suitable previous period. Use the same number of days and account for weekly patterns. Compare clicks and impressions, and inspect queries, pages, countries, and device types. Check analytics separately, but treat Search Console as the primary record of Google Search impressions and clicks. A reporting delay or tracking change can make analytics look different without a ranking loss.
2. Check the Manual Actions report. In Search Console, open Security & Manual Actions, then Manual Actions. If Google has applied a manual action to the property, the report should describe the issue and affected scope. Read the notice closely: it may affect only certain pages or a specific type of search result rather than the entire site. A message in this report is the clearest way to distinguish a manual action from an algorithmic ranking change.
3. Check the Security Issues report separately. A hacked site or harmful content can cause search visibility problems, but a security issue is not the same thing as a manual action. Review the Security Issues report and any Search Console notifications. If it identifies a problem, secure and clean the site before requesting a review or assuming the decline is algorithmic.
4. Look for a matching timeline, not just a matching date. Put the first confirmed decline beside known Google ranking-system updates, site releases, content changes, migrations, and outages. Google updates can affect visibility without generating a Manual Actions notice. Timing is a clue, not proof: an update may overlap with a technical failure or a change in demand. Avoid labeling a decline as an update impact from a date match alone.
5. Find out what changed in the data. In Performance, compare the same queries and pages before and after the decline. Lower impressions across many pages may indicate lost visibility or demand; stable impressions with fewer clicks can point to changed result presentation, snippets, or click-through behavior. Losses concentrated on a page group, country, or device suggest a narrower cause than a sitewide drop. Compare average position cautiously because it is an aggregate metric and can shift when the query mix changes.
6. Rule out technical and indexing causes. Check Page indexing and inspect representative affected URLs with URL Inspection. Look for unintended noindex directives, robots.txt blocks, incorrect canonical URLs, redirects, server errors, soft 404s, or pages that are unavailable to Google. Check important templates as well as individual pages. A crawl or indexing problem can reduce rankings without being either a manual action or an algorithmic penalty.
7. Review changes and crawl evidence. Ask developers and editors what changed before the decline, including deployments, URL structures, internal links, templates, and content. If available, review server logs for Googlebot requests and responses. A site migration or widespread errors can create a decline that resembles a ranking update. Do not make several large changes at once; that makes it harder to identify the cause and assess recovery.
8. Choose the response based on evidence. For a manual action, correct the specific issue described in Search Console across all affected pages, then submit a reconsideration request when the report provides that option. Explain what you fixed and where. For a suspected algorithmic or technical issue, fix confirmed technical faults, improve pages where evidence points to a quality or relevance problem, and monitor results. There is no reconsideration request for an ordinary algorithmic ranking change.
9. Measure recovery with consistent comparisons. Record the changes and dates, then monitor affected pages and queries in Search Console. Allow time for Google to recrawl and reassess corrected pages; recovery is not guaranteed or necessarily immediate. Keep comparing like with like, and distinguish a partial recovery from normal fluctuations in demand or seasonality.

Common Mistakes

• Calling every traffic loss a penalty. A ranking decline does not prove that Google applied a manual action.
• Checking only total clicks. Changes in demand, seasonality, query mix, or search-result features can affect clicks without an equivalent ranking change.
• Assuming a Google update caused the decline because the dates overlap. First rule out site-specific and technical causes.
• Submitting a reconsideration request for an algorithmic change. Use that process only when Search Console reports a manual action and the issue has been corrected.
• Making broad, rushed edits before diagnosing the affected pages. Preserve a record of changes so you can connect actions with later results.

Tips

• Save Search Console exports and deployment records regularly; historical comparisons are more useful when you have a clear baseline.
• Compare equivalent periods and, where appropriate, the same season from a prior year. Check whether the data range is complete.
• Segment by page and query instead of relying on a sitewide average. A few high-traffic pages can hide a different pattern elsewhere.
• Use URL Inspection to investigate representative examples, not just the homepage. Confirm that affected pages can be crawled and have the intended canonical URL.
• Keep a dated log of findings, fixes, and results. Change one well-defined group at a time when practical.

Troubleshooting

The Manual Actions report is empty, but traffic is still down: That makes a reported manual action less likely, but it does not identify the cause. Check Security Issues, indexing, site availability, and the affected query and page patterns. Google may also change rankings without issuing a manual action notice.

Search Console and analytics do not agree: Confirm that analytics tracking, consent settings, filters, and property selection did not change. Compare the dates and search channel definitions. Search Console and analytics measure different things, so their totals are not expected to match exactly.

Only some URLs appear affected: Inspect those URLs and compare them with unaffected pages using the same template. Look for page-specific indexing directives, canonicals, redirects, content changes, and internal-link differences. Avoid assuming that a sitewide fix is needed.

You fixed a manual action but rankings have not returned: Confirm the action is no longer shown and that corrected pages are crawlable. A reconsideration review and subsequent recrawling can take time, and removing a manual action does not guarantee former rankings. Continue checking for separate technical or ranking issues.

You cannot identify a clear cause: Keep the evidence organized and avoid repeated speculative changes. Check with a qualified SEO or developer if the decline is substantial, especially after a migration, security incident, or complex technical release.

Frequently Asked Questions

Does an algorithmic ranking drop appear in the Manual Actions report?
No. That report is for manual actions. A ranking-system change can affect visibility without appearing there.

Can a manual action affect only part of a site?
Yes. The report may describe an issue affecting particular pages or a narrower part of the property. Follow its stated scope.

How can I tell whether a Google update caused the drop?
Compare the timing and affected queries or pages with the update, but treat that as a hypothesis. Rule out technical faults, site changes, and demand shifts before drawing a conclusion.

Should I request reconsideration after an algorithmic decline?
No. Reconsideration requests are for resolving a reported manual action, not for asking Google to reverse an ordinary ranking change.

How long does recovery take?
There is no fixed timetable. Google must recrawl and reassess changes, and rankings may not return to their previous level. Track affected pages over time rather than expecting an immediate result.

Related

• Fix Fast Battery Drain on a Foldable Phone
• How to Buy Cement: Types, Freshness and Storage
• Magic: The Gathering Universes Beyond Enters a New Era?