Did Google drop my page from the index?

Q: Did Google drop my page from the index?

Before assuming Google dropped a page, check whether the URL still allows indexing: robots meta, X-Robots-Tag, and robots.txt. Still Indexed fetches URLs and returns BLOCKING or ALLOWED with the quoted directive. Optional Search Console inspect is separate from the live fetch.

“Did Google drop my page?” usually starts in the wrong place. Before you assume a ranking or index purge, check whether the URL still allows indexing. Accidental noindex, an X-Robots-Tag, or a robots.txt Disallow will keep Google out even when the page looks fine in a browser.

What to check first

Live HTML robots meta. Look for noindex or none on the URL you care about (staging themes and “temporary” banners are common culprits).
Response headers. CDNs and edge workers sometimes inject X-Robots-Tag: noindex on preview hosts that later become production.
robots.txt path rules. A broad Disallow can block crawl of the URL even when the HTML itself is clean.
HTTP status and canonical. Soft 404s, unexpected redirects, and a canonical that points elsewhere explain many “missing from Google” reports.
Search Console coverage (optional second pass). coverageState from URL Inspection describes Google’s stored view—not a live fetch of today’s HTML.

What Still Indexed does

Still Indexed fetches 1–20 URLs (or expands a sitemap to the first 20 locs). For each URL it reports HTTP status, meta robots, X-Robots-Tag, robots.txt allow/disallow for the path, canonical, and a verdict: BLOCKING (quoted directive) or ALLOWED.

It does not scrape Google search results and does not invent an index status from the fetch path. Optional Search Console inspect uses Google’s official URL Inspection API after you grant read-only access.

How this page differs from the homepage

The homepage H1 already asks whether Google dropped your page—that is the product. This Q&A page is the checklist: what to verify, what BLOCKING vs ALLOWED means, and when to open Search Console. Use the tool for the live wire check; use How it works for the decision rules.

If the fetch says ALLOWED and GSC still shows excluded, dig into coverage reasons next—not another robots guess.

BLOCKING versus ALLOWED in practice

BLOCKING means Still Indexed quoted a directive that stops indexing or crawling for that URL. ALLOWED means no such directive showed up on the fetch path. ALLOWED plus a 404 is still ALLOWED—the tool will not rename a missing page as “dropped by Google.” That honesty is intentional: inventing index state from a Worker fetch would be misleading.

When you connect Search Console, treat coverageState as a second column. A page can be ALLOWED on the wire and still excluded in GSC for reasons outside robots meta. Conversely, a page can be BLOCKING today while GSC still shows an older indexed snapshot until Google recrawls.

Checklist before you panic about rankings

Run the homepage checker on the exact URL from Search Console.
If BLOCKING, fix the quoted directive and re-run.
If ALLOWED, open How it works and then GSC inspect for coverage reasons.
Watch for staging noindex that survived a go-live copy.

This Q&A URL exists so the core search phrase has a dedicated English answer page. The product remains the checker on /.

Check URLs now · How it works · Home