Manual Action vs Algorithmic Deindexing: What Changes When No Notice Arrives

Google can remove a site from its results in two ways, and they feel very different from the owner's side.

A manual action is a decision by a person at Google that a site breaks a spam policy. It shows up in Search Console's Manual actions report. You know it happened, you know roughly why, and you have something specific to fix.

Algorithmic removal is done by Google's automated systems. There is no reviewer message and no report entry. Pages simply stop appearing, and impressions fall. Deindexing of this kind is easy to mistake for a seasonal dip or a tracking bug, which is why it does the most damage.

The practical difference: with a manual action, Google tells you. With algorithmic removal, you have to notice.

The row that matters most for AI visibility is the fifth. Either path removes you from Google's AI answers, but only one of them warns you.

OtterlyAI ran a public test in 2026. It launched two new domains about capybaras, each loaded with roughly 1,000 AI-generated posts. One site showed a fictional expert author box. The other had no author. The method and its limits are worth reading before you quote it.

The Google result was clear:

• Both sites were removed from Google's index.
• Otterly reports zero manual actions in Search Console on either domain.
• capybara-world.com, the site with the author box, lasted about 14 days. Its daily impressions fell from 1,629 to 15 on April 9.
• capybaraverse.com lasted about 90 days. Its daily impressions fell from 859 to 85 on June 26, then to single digits.

This matches Google's written policy. Google's spam policies describe scaled content abuse as many pages "generated for the primary purpose of manipulating search rankings and not helping users," and list generating many pages with AI tools "without adding value for users" as an example. Google's AI content guidance also says "Appropriate use of AI or automation is not against our guidelines." The tool was not the problem. The volume without value was.

Keep the limits in view. It was one site per arm, with no human-written control, in a low-competition topic, run by a vendor that sells AI visibility tracking. It shows that silent removal happens. It does not show how often.

Google states that to appear as a supporting link in AI Overviews or AI Mode, a page "must be indexed and eligible to be shown in Google Search with a snippet." There is no separate path in. So when Google drops a page from its index, it also drops out of Google's AI citations.

That is what Otterly observed. Google AI Overviews, AI Mode and Gemini almost never cited the sites. Other engines behaved differently:

• Bing never deindexed either site. Combined Bing impressions reached 119,935 in July.
• Microsoft Copilot, which grounds on Bing, produced 2,718 of the 3,934 citations Otterly tracked for capybara-world.com.
• ChatGPT produced effectively zero citations, even while its crawlers visited and the sites ranked in Bing.

What this means for you: a Google removal is a Google-wide event, covering classic results and its AI surfaces. It says nothing about Bing, and Bing being healthy says nothing about Google. Being indexed is necessary for a citation, but it is not sufficient.

Since algorithmic removal sends no message, you need your own tripwires. Check these on a schedule, not only when traffic looks off.

In Google Search Console

1. Performance report impressions. Both Otterly sites showed a cliff, not a slope. A drop of that shape on a whole site is the clearest early sign.
2. Page indexing report. Look for indexed page counts falling while your published page count stays flat.
3. URL Inspection. Spot-check key URLs. It tells you whether a page is indexed and when Google last crawled it.
4. Manual actions report. Check it anyway. An empty report plus collapsing impressions points to an algorithmic cause.
5. Generative AI report. As of October 2026 it shows impressions only for AI Overviews and AI Mode, with no clicks or position. Note that a confirmed Google-side bug depressed impressions from roughly 12 August 2026, so be careful reading trends from that window.

Rule out self-inflicted causes first

Before assuming Google removed you, check the things you control: a stray noindex, nosnippet or max-snippet:0 from a template, a robots.txt rule blocking Googlebot, or the Search Console generative AI inclusion control set to opt out (child properties can inherit it from a parent). Each of these can look like a penalty.

In Bing Webmaster Tools

Run the same checks separately. Bing's AI Performance report also shows citations and the grounding queries Copilot actually ran. Our guide on how to tell if Google has deindexed your site walks through the Google side, and checking index status engine by engine covers both.

You don't choose between a manual action and algorithmic removal, but you do choose how to respond. Use the signals to sort your situation into one of these.

• Manual actions report shows an entry. Treat it as a specific instruction. Fix the named issue on the named pages, then request review in Search Console.
• Report is empty, impressions fell off a cliff, indexed pages dropped. Assume algorithmic removal. Audit the site against Google's spam policies, starting with scaled content. If you published many thin pages quickly, remove or substantially improve them. Expect no confirmation from Google.
• Report is empty, impressions fell, but pages are still indexed. This is probably not deindexing. Look at snippet directives, the generative AI inclusion control and normal ranking changes.
• Google looks healthy but AI answers ignore you. Indexing is only the first gate. Check whether AI crawlers can reach you at all, since a firewall or CDN can block a crawler that robots.txt allows.
• Google dropped you but Copilot still cites you. Don't read that as a recovery. Google remains the larger channel, and its AI surfaces follow its index.

If you are planning AI-assisted publishing, read whether Google penalizes AI content first. The safest position is the one Google describes: use AI where it adds value, and don't publish at a volume your editing can't support.

Does Google penalize AI-generated content? Not for being AI-generated. Google's guidance says appropriate use of AI or automation is not against its guidelines. It acts against scaled content abuse, meaning many pages produced to manipulate rankings without adding value for users. In OtterlyAI's 2026 test, two sites with about 1,000 AI posts each were removed from Google's index, and neither received a manual action.

Can I file a reconsideration request after algorithmic deindexing? Review requests in Search Console apply to manual actions. If the Manual actions report is empty, there is nothing to request review of. Your route is to fix the underlying problem, such as thin or mass-produced pages, and let Google's systems reassess the site. The evidence gives no reliable timeline for that, so don't plan around one.

If Google deindexes my site, will Bing do the same? Not necessarily. Bing runs its own index and makes its own decisions. In OtterlyAI's test, Google removed both sites while Bing kept them, and Bing impressions kept growing. Microsoft Copilot, which grounds on Bing, went on citing one site thousands of times. Check Google Search Console and Bing Webmaster Tools separately, because one tells you nothing about the other.

Does blocking AI crawlers get a site deindexed from Google? Blocking AI training crawlers is a separate control from Google Search. Google says Google-Extended does not affect a site's inclusion in Google Search and is not a ranking signal. Blocking Googlebot itself is different: Googlebot rules in robots.txt are the control for all Google surfaces, including AI Overviews and AI Mode, so check that you haven't blocked it by accident.

Will Search Console warn me if I drop out of AI Overviews? No. As of October 2026, the generative AI report in Search Console shows impressions for AI Overviews and AI Mode, with no alerts, clicks or position data. A fall in those impressions is the signal, and you have to watch for it. Because AI Overviews only cite indexed pages, a sudden drop alongside falling indexed pages points to deindexing rather than an AI-specific change.