How to Check if a Domain Is Deindexed by Google

What Does “Deindexed” Actually Mean?

A URL is deindexed when it was previously in Google’s index but is no longer indexed. That does not automatically mean Google imposed a site-wide “ban.” Buyers often use that word for several different situations that require different evidence and different remedies.

A domain may have no visible results because its old URLs expired, redirect, return errors, use noindex, are blocked from crawling, duplicate another canonical, were temporarily removed, or no longer provide content Google chooses to index. A confirmed manual action is a separate state shown to verified owners in Google Search Console.

This distinction matters during domain vetting. An empty, long-parked domain with no current indexable pages is not equivalent to a formerly active site with an unresolved site-wide spam action.

Six States That Can Look Similar

Not discovered or recrawled

Google has not found the URL, or has not revisited it since a material change.

Evidence: URL Inspection discovery and crawl details, sitemap status, server logs.

Technical exclusion

A noindex directive, crawl block, authentication, error, redirect, or other delivery issue prevents indexing.

Evidence: Live inspection, response headers, rendered HTML, crawl logs.

Canonical or quality selection

Google selected another canonical, treated the page as a duplicate or soft 404, or did not consider it useful enough to index.

Evidence: Page indexing reason and Google-selected canonical.

Manual action

A human reviewer found a spam-policy violation affecting some or all pages.

Evidence: Search Console Manual Actions report—not a third-party score.

Security issue

Hacking, malware, phishing, harmful downloads, or deceptive behavior can trigger warnings and affect visibility.

Evidence: Security Issues report, Safe Browsing warnings, server investigation.

Removal or ranking loss

A temporary owner request, legal removal, SafeSearch classification, or ranking decline may hide results without a technical indexing failure.

Evidence: Removals report, notices, URL status, and Search performance data.

Public Checks Before You Control the Domain

1. Use `site:` as a Screening Signal

Search Google for site:example.com, the exact homepage URL, a few known historical URLs, and the former brand name. Results confirm that Google can show at least some URLs. No results justify further investigation, but they do not prove a penalty or enumerate every indexed URL.

Compare the result with the domain’s documented history. Zero results are more consequential when archives and traffic evidence show a substantial site operated recently than when the domain has been parked for years.

2. Inspect the Current Technical State

Check HTTP status, redirects, canonical tags, robots meta tags, and X-Robots-Tag headers.
Review robots.txt, but remember that a crawl block and a noindex directive are different controls.
Test representative historical URLs, not only the homepage.
Look for parking templates, empty pages, soft errors, hacked paths, or an unrelated repurpose.
Check whether www, non-www, HTTP, HTTPS, and important subdomains resolve consistently.

3. Record What Public Checks Cannot Establish

Without verified property access, a buyer cannot conclusively verify the absence of manual actions, security issues, temporary removals, owner messages, or historical Search performance. Bulk “Google index checker” tools generally automate public queries; they do not gain privileged access to Google’s index or the property’s Search Console records.

Request a Supervised Search Console Review

For a consequential purchase, ask the seller to grant appropriate read access or conduct a live screen-share. Screenshots can be stale, cropped, or taken from the wrong property. Confirm the exact domain property and date during the session.

Manual Actions: Record whether Google reports no issues or identifies a specific action and affected scope.
Security Issues: Check for hacked content, malware, social engineering, or harmful downloads.
Removals: Review temporary removals, outdated-content requests, and SafeSearch filtering history.
Page indexing: Compare indexed and excluded groups and open the reasons affecting important URL patterns.
URL Inspection: Inspect the homepage plus representative category, content, and historically linked URLs.
Search performance: Compare pages, queries, countries, devices, and dates around major losses or site changes.
Messages and ownership: Review relevant notices and confirm that the property covers all protocols and subdomains.

A clean Manual Actions report means no current manual action is reported for that verified property. It does not certify the backlink profile, content quality, legal status, security outside Google’s detection, or future rankings. Our domain penalties guide explains how to distinguish manual actions from algorithmic, technical, security, and demand-related losses.

How to Inspect Representative URLs

Do not draw a site-wide conclusion from one homepage inspection. Choose URLs that represent the assets you are valuing: the homepage, strong historical link targets, former high-traffic pages, important directories, and pages with different templates.

Indexed status: Is the URL on Google, and when was it last crawled?
Discovery: Which sitemap or referring page led Google to it?
Crawl: Was crawling allowed and was the fetch successful?
Indexing permission: Was a robots meta tag or HTTP header blocking indexing?
Canonical: What canonical did the owner declare, and which did Google select?
Live test: Can Google access the current version after a fix?

The live test checks whether the current URL appears technically available to Google; it does not test every condition for appearing in Search. Google specifically notes that it does not resolve questions about manual actions, security issues, removals, or overall quality.

How to Interpret the Evidence

Proceed

Important URLs are understood, Search Console evidence is consistent, and exclusions have ordinary, documented causes.

Condition: Value only assets likely to survive the planned use.

Investigate

Public results conflict with history, key URLs have unexplained exclusions, or property access is incomplete.

Condition: Define the missing evidence before paying.

Renegotiate

Recoverable technical work or lost index coverage materially reduces the useful asset.

Condition: Price the domain without unverified traffic or index assumptions.

Reject

An unresolved manual action, security compromise, deceptive seller evidence, or unacceptable recovery uncertainty remains.

Condition: Record the specific evidence—not merely “zero site results.”

Recovery Depends on the Cause

Technical Exclusion

Fix the exact response, directive, crawl, canonical, rendering, internal-link, or sitemap problem. Test the live URL, then request indexing for a small number of important pages or submit an accurate sitemap for larger sets. A successful request asks Google to recrawl; it does not guarantee indexing.

Manual Action

Read the action’s scope and instructions, identify the underlying spam-policy violation, remediate the complete pattern, document the work, and submit a reconsideration request from the report. Buying the domain, replacing the design, or filing a disavow file does not automatically resolve the action.

Security Issue

Contain the compromise, remove malicious content, patch the entry point, rotate credentials, examine logs and persistence mechanisms, and request a security review when the site is clean. Do not launch on infrastructure inherited from an unknown owner without a controlled rebuild.

Quality or Algorithmic Re-evaluation

There is no reconsideration request for an ordinary algorithmic ranking or quality reassessment. Improve the site for users, remove low-value or deceptive patterns, and allow time for recrawling and re-evaluation. Separate loss of rankings from actual removal from the index.

Post-Purchase Indexing Checklist

Verify a domain-level Search Console property under the new owner.
Save the initial Manual Actions, Security Issues, Removals, Page indexing, and Performance state.
Map valuable historical URLs to retained, relevant destinations; avoid redirecting everything blindly to the homepage.
Launch crawlable, indexable, useful pages with consistent canonicals, internal links, and XML sitemaps.
Inspect a representative sample after launch and watch server logs for Googlebot activity.
Track indexed pages, impressions, queries, security alerts, and important URL status over time.

Use the first 90 days after buying an aged domain workflow to turn these checks into a monitored launch plan.

Minimum Evidence Record

Domain, property type, reviewer, date, access level, and seller present
Public searches and exact URLs tested, with stated limitations
Manual Actions, Security Issues, Removals, messages, and ownership status
Page indexing groups and representative URL Inspection results
HTTP responses, directives, canonicals, historical URLs, and archive dates
Performance-change date and plausible technical, content, algorithmic, or demand events
Proceed, investigate, renegotiate, reject, or recover decision with responsible owner

Primary Sources

Bottom line: Treat missing Google results as a prompt to investigate, not proof of a ban. For a domain purchase, insist on current Search Console evidence, inspect representative URLs, identify the precise cause, and price any uncertainty into the decision. See the complete domain buying checklist before committing funds.