A website usually drops out of Google for one of a few fixable reasons: a noindex tag added by accident, a robots.txt file blocking crawlers, a broken or missing sitemap, a manual penalty, or a recent algorithm update. Work through them in that order and you will normally find the cause in a few minutes.
Losing your Google listings feels like the site broke, but in most cases the pages are fine. Something is telling Google not to show them, or Google has lost the trail to find them. The fixes below are ordered from most common and easiest to check, to least common.
This is the most frequent cause and the easiest to miss. A noindex tag tells search engines to drop a page from their results. It often gets switched on during development and never switched off after launch, or a setting in a content management system flips it on for a whole section.
How to check: open the page, view source, and search for noindex. If you find <meta name="robots" content="noindex"> in the head, that page is telling Google to remove it. Also check the X-Robots-Tag response header, which does the same thing at the server level.
How to fix: remove the noindex directive. In WordPress, check Settings, Reading for the "Discourage search engines" box, and check your SEO plugin's per-page settings. In Squarespace and Wix, check the page SEO panel. Once removed, resubmit the page in Google Search Console.
Your robots.txt file controls which parts of the site search engines may read. A single line of Disallow: / blocks the entire site. New pages then never get indexed, and existing ones fade out over time.
How to check: visit yoursite.com/robots.txt and look for a Disallow: / under User-agent: *.
How to fix: remove the blanket disallow. Keep only the specific paths you actually want hidden, such as an admin area. Confirm your sitemap is listed with a Sitemap: line.
An XML sitemap is how Google discovers your pages efficiently. If it returns an error, lists no URLs, or was never created, Google has to find pages by following links, which is slower and less reliable.
How to check: visit yoursite.com/sitemap.xml. It should load and list your URLs. In Google Search Console, the Sitemaps report shows whether Google can read it.
How to fix: regenerate the sitemap. Most platforms create one automatically or through a plugin. Submit the working sitemap URL in Search Console.
If Google's team applied a manual action, your site can be removed or demoted. This is less common and applies mostly to sites that bought links or published spam.
How to check: open Google Search Console and look at the Manual Actions report. If there is a penalty, it will be named there with a reason.
How to fix: address the specific issue Google describes, then submit a reconsideration request.
If the site is still indexed but ranks far lower, a Google update may have reassessed it. This is a ranking change, not a removal. Recovery comes from improving content quality, page experience, and the technical health of the site rather than flipping one setting.
Run a free scan. SiteBeat checks for noindex tags, robots.txt blocks, and sitemap problems across your site and tells you which pages are affected.
Scan my website freeThe reason a deindex hurts so much is timing. A noindex tag or a broken sitemap is silent. Traffic erodes for weeks before anyone notices the line going down in analytics, and by then the damage is done.
Monitoring closes that gap. SiteBeat re-checks your site on a schedule and emails you the moment an indexability problem appears, so you fix it the next morning instead of discovering it a month later. For a site that earns from search traffic, that early warning is the whole point.
Usually a noindex tag added by accident, a robots.txt file blocking crawlers, a broken or missing sitemap, a manual penalty, or a recent algorithm update. Checking each in order normally finds the cause within minutes.
View the page source and search for a meta robots tag containing noindex, or check the X-Robots-Tag header. If either tells search engines not to index the page, Google removes it.
A rule of Disallow: / blocks crawlers from reading your pages, which prevents indexing and can drop existing pages over time. Remove the blanket disallow and keep only the paths you genuinely want blocked.
Once the block is removed and the pages are resubmitted in Search Console, recovery usually takes a few days to a few weeks, depending on how often Google crawls your site.