Why was my site deindexed from Google, and how do I get it back in search results?
Deindexing means Google has removed your pages from its search index, so they no longer appear in results even when someone searches your exact brand name. It comes in two flavors: partial, where only some pages vanish, and full, where the entire domain disappears. The fastest way to confirm which one you are facing is the site: operator. Search site:yourdomain.com in Google. If nothing comes back, or far fewer pages than you expect, you have an indexing problem worth diagnosing rather than a normal ranking dip.
The single most common cause is an accidental noindex directive. A meta robots noindex tag or an X-Robots-Tag header tells Google to drop the page after it crawls it. This happens constantly during redesigns and migrations: a staging site ships with noindex applied sitewide, the deployment carries that tag to production, and within days organic traffic collapses to zero. A related trap is robots.txt. Blocking a section in robots.txt only stops crawling, not indexing, and the two can cancel each other out. If you block a page in robots.txt, Google can never crawl it to see your noindex tag, so the page you wanted removed can linger while the pages you wanted kept get starved of crawl access. The correct combination is to allow crawling and use noindex only where you genuinely want a page hidden.
The second cause is a manual action. This is a penalty applied by a human reviewer at Google when a site violates Search Essentials, for things like pure spam, unnatural links, or cloaking. You will find it in Search Console under Security & Manual Actions, with the action type, a short description, and the affected URL patterns. If it reads "No issues detected," you do not have one and the problem lies elsewhere.
The third and most urgent cause is hacked content and malware. If your site gets compromised, serves malware, or redirects visitors to scam pages, Google treats user safety as the priority and pulls it from results, often surfacing a "This site may be hacked" or interstitial warning. A common attack pattern is cloaking, where intruders quietly hijack a handful of higher-ranking pages to funnel visitors to scams, which makes the damage hard to spot until traffic is already gone. Glenn Gabe documented a 2026 case where a single hacked page got the whole site flagged as spam and deindexed, with the manual action arriving the next morning rather than before. The lesson: if you suspect a hack, treat it as a security incident first and an SEO problem second.
To diagnose, start in Google Search Console with three reports. Open Indexing, then Pages, and read the "Why pages aren't indexed" breakdown. Look specifically for "Excluded by noindex tag," "Blocked by robots.txt," server errors, and canonical or duplicate selections. Use the URL Inspection tool on a few affected URLs to see exactly what Googlebot received, since the live fetch shows whether a noindex or block is still visible to the crawler. Then check Security & Manual Actions for both a manual action and a security issue. Together these three views tell you whether you are dealing with a technical mistake, a penalty, or a compromise.
Recovery depends on the cause. For a technical issue like an accidental noindex or a bad robots rule, no reconsideration request is needed. Remove the offending tag or directive, confirm with URL Inspection that Googlebot no longer sees it, resubmit your sitemap, and use "Request indexing" to prompt a recrawl. Reindexing typically takes a few days to a few weeks. For a hacked site, clean it completely before requesting anything: remove malicious code, suspicious plugins, and unauthorized admin accounts, restore from a known-clean backup, patch the vulnerability that let them in, and run a full malware scan. Only once every affected page is clean should you request a security review, which Google says can take from a few days to a few weeks. For a manual action, fix the underlying violation across the whole site, not just the sample URLs, then submit a reconsideration request, which usually returns within roughly two to six weeks. Never resubmit while a request is pending, because repeated submissions slow the queue and can flag you as a repeat offender.
A few realities worth setting expectations around. Getting a flag lifted is not the same as fully recovering traffic; rankings can return quickly or take months depending on how much ground competitors gained while you were dark. Also, not every "missing" page is a penalty. Google has grown more selective about which URLs earn crawl budget and index space, so thin or duplicate pages may simply not be indexed by design. The work is to confirm your important pages are indexed, investigate anything genuinely stuck, and ignore the routine exclusions like checkout or thank-you pages that were never meant to rank.
If your site goes dark and you cannot tell whether it is a deploy mistake, a penalty, or a hack, this is the kind of incident a Pineido Stabilization sprint is built for: we triage the Search Console signals, confirm whether it is a security event, and get the recovery path moving without guesswork. If the trigger was a deployment that shipped a staging noindex to production, our website builds bake in the deployment discipline and password-protected staging that prevent it from happening again, and our Data Cleanup work keeps your Search Console signals and indexing rules clean over time.
Ready to ship?
Tell us where you are stuck. We will review it and send a focused recommendation within one business day.