Test whether Google can actually see you

The fastest check is a site: search. Type site:yourdomain.com into Google and read the results. Zero results means an indexing problem, full stop. Partial results invite narrower checks, site:yourdomain.com/blog for a section, or a unique sentence from a key page searched in quotes to confirm whether that specific content made it into the index. Note that the old cache: operator is gone, Google retired cached links and the operator itself back in 2024, so if your checklist still includes it, that line is dead.

Then get the authoritative answer from Google Search Console. Verify a Domain property so every protocol and subdomain is covered, and open the Pages report under Indexing, which shows exactly how many URLs are indexed and, for the rest, why not. URL Inspection on your highest-priority pages tells you the indexed status, which canonical Google chose (not always the one you declared), and how the page renders in a live test, with Request Indexing available for pages that qualify. Two supporting checks round it out: server logs or analytics confirming Googlebot actually visits, and everything evaluated mobile-first, since Google crawls primarily with a smartphone agent and content your mobile rendering hides is content Google doesn’t have.

Read the warning signs correctly

Some symptoms deserve immediate escalation. Your homepage missing from a search for your own brand name. New content not surfacing after weeks. Organic traffic dropping sharply with no seasonal explanation. Pages that used to rank, contact, pricing, core services, simply gone. Any of these means assuming an indexation or discoverability problem until proven otherwise.

The Pages report translates symptoms into causes, and the statuses are worth learning to read. “Discovered, currently not indexed” means Google knows the URL exists and hasn’t crawled it yet, often a crawl-priority or site-quality signal. “Crawled, currently not indexed” means Google looked and declined, which usually points at thin or duplicative content. “Excluded by noindex,” “Blocked by robots.txt,” “Soft 404,” and “Server error (5xx)” are the mechanical red flags with direct fixes, while the canonical-related statuses (“Alternate page with proper canonical tag,” “Duplicate without user-selected canonical”) mean Google is consolidating pages in ways you may not have intended.

On-page structure creates its own invisibility. Content that only renders after user interaction, infinite scroll without crawlable pagination, and parameter-heavy URLs spawning near-duplicates can all sideline indexing, and site migrations, protocol or domain switches, and canonical tags accidentally pointing off-site or at staging can erase a presence overnight. If the timeline of your disappearance matches the timeline of a redesign, start there.

Audit the three usual culprits

First, robots.txt, at yourdomain.com/robots.txt. Look for an accidental Disallow: / or wildcards broad enough to block critical paths, and be precise about what’s genuinely worth blocking. Two specifics trip people up: noindex directives in robots.txt do nothing, since Google dropped support years ago, and blocking CSS or JavaScript resources can be as damaging as blocking pages, because Google can’t evaluate a layout it isn’t allowed to load.

Second, the meta and header layer. Remove noindex and none directives from pages that must rank, check for server-level X-Robots-Tag rules blanket-blocking directories or file types, and audit canonicals with suspicion, since a canonical pointing at the wrong protocol, the wrong host, a parameter variant, or a staging URL is an instruction to Google to index something other than the page you care about, delivered in your own voice.

Third, sitemaps. A sitemap should contain only 200-status, canonical, indexable URLs, with noindexed, blocked, redirected, and parameterized pages excluded, lastmod dates that are actually accurate, and host and protocol matching the canonicals. Submit it in Search Console and compare submitted against indexed counts, since a persistent gap between the two is a systemic signal, the reading we detailed in how to know when to update your sitemap. One clean sitemap beats five messy ones every time.

Fix what’s holding indexing back

Once the mechanical blockers are cleared, the remaining work is earning the index rather than requesting it. Consolidate duplicates with 301s or correct canonicals, expand thin pages until they actually match the intent of the searches they target, and fix orphan pages by linking to them from relevant, well-trafficked sections, since a page with no internal links is a page you’ve told Google doesn’t matter. Structured data clarifies what each page is where it’s ambiguous, and content that holds attention once visitors arrive compounds the effort, which connects to the engagement work we covered in improving time on site without adding more content.

Technical delivery runs in parallel. Core Web Vitals (LCP, INP, CLS) improved through compressed images, trimmed render-blocking scripts, caching, and a CDN. Every 404 and 500 resolved, redirect chains flattened, and, for JavaScript-heavy sites, critical content pre-rendered or server-rendered so the primary text exists without interaction, with mobile rendering exposing the same content desktop does.

Then authority, the slowest lever and the one that governs how eagerly Google crawls and ranks what it indexes. Reclaim unlinked brand mentions, pursue the digital PR and industry resources your niche actually reads, and skip anything that smells like a shortcut. After each round of fixes, resubmit the sitemap, request indexing on the priority pages, and watch the Pages report and the logs until index coverage matches your site’s real footprint. Invisibility on Google is nearly always a specific, findable cause rather than a mystery, and the whole discipline is testing before fixing, then fixing in order, mechanical blockers first, content quality second, authority as the long game.