Deindexing is the removal of a page, section, or entire website from a search engine’s index, which means it can no longer appear in organic search results. A page can be deindexed intentionally, such as when you add a noindex directive, or unintentionally because of technical errors, low-quality content, duplicate pages, or a manual action.
Why deindexing matters for SEO
If an important page is deindexed, it loses its ability to rank, earn clicks, and support conversions from search. For beginners and growing teams, this matters because traffic drops can sometimes be caused by indexing problems rather than rankings alone. Deindexing can affect product pages, blog posts, landing pages, and even whole site sections if a technical issue spreads across templates or CMS settings.
It also matters strategically. Not every page should stay indexed. Thin thank-you pages, internal search results, staging pages, and duplicate filter URLs can waste crawl budget and clutter search results. In those cases, controlled deindexing helps search engines focus on the pages that actually deserve visibility.
Common causes of deindexing
Intentional deindexing
This usually happens when a site owner adds a noindex meta tag, sends an X-Robots-Tag header, password-protects content, or removes URLs through search engine tools. These are normal actions when managing low-value or private pages.
Unintentional deindexing
Pages can disappear from the index because of accidental noindex tags, canonical tags pointing elsewhere, blocked resources, server errors, soft 404s, or major content quality issues. Search engines may also deindex pages that appear duplicated, outdated, or unhelpful compared with stronger alternatives.
How to check if a page has been deindexed
Start by searching for the exact page title or URL in the search engine. Then verify the page in Google Search Console by using the URL Inspection tool to see whether it is indexed and, if not, why. Review the page source for noindex directives, check canonical tags, confirm the page returns a 200 status code, and make sure it is linked internally from relevant pages.
For larger sites, compare your XML sitemap with indexed page counts in Search Console. A sudden gap can point to template-level problems or sitewide directives.
Practical example: fixing an accidental deindexing issue
A SaaS company updates its blog template and accidentally adds a noindex tag to every article. Within two weeks, blog traffic drops sharply. The marketing team checks Search Console, sees affected URLs marked as excluded by noindex, removes the tag from the template, republishes the pages, and requests reindexing for key articles. Once search engines recrawl the pages, rankings and traffic begin to return.
The key lesson is simple: when pages vanish from search, check indexing signals before assuming it is only a ranking problem.