Noindex Removed, but Search Console Still Excludes the Page

Removing a noindex tag changes your website immediately after publication, but it does not rewrite Google's last crawl. First establish whether the exclusion describes an old response or a directive still served today. The answer determines whether to change the site again.

Keep three pieces of evidence separate

Use this worksheet for one exact production URL. These entries are illustrative, not a real Search Console account or a measured recovery.

Evidence	Example observation	What it establishes
Indexed inspection	Crawled September 20; indexing disallowed	Google saw noindex on that crawl
Current response	September 28; 200; no noindex in HTML or headers	This particular response no longer declares noindex
Live URL test	Fetch successful; indexing allowed	Google's live test can access the current page

A successful live test is not proof that the page is already indexed. Conversely, an old exclusion is not proof that the current deployment failed. Google's Page indexing documentation recommends testing the live URL when diagnosing noindex.

Check the response that is actually being served

Copy the affected URL from the report, preserving its hostname, path and query string.
Open it while logged out. Record redirects and the final URL. A CMS preview can differ from the public page.
Inspect the document response headers and HTML. Look for both robots and googlebot meta directives and X-Robots-Tag headers.
Repeat on the canonical target if the URL points to another page.
Run URL Inspection's live test and record its date separately from the indexed inspection.

This command saves a GET response; it does not authenticate as Googlebot:

curl -sS -L -D response-headers.txt -o response-body.html 'https://example.com/article'

-L follows redirects, so the header file can contain several responses. Read the final response and any redirect destinations. Do not assume a successful test from your computer proves that Google's network can fetch it.

The invisible header case

Suppose the HTML contains index, follow, but the server sends:

X-Robots-Tag: noindex

The page still has an exclusion directive. An HTML-only search missed it. Check the host/CDN configuration, an SEO plugin, or a staging header rule carried into production. Remove the rule only from URLs intended for search, publish, then capture the response again. Google's robots directive specification explains the interaction of page and response-header directives.

Choose the next action

Current finding	Next action	Avoid
Live test still finds noindex	Find the remaining source and republish	Repeated indexing requests before fixing it
Current response is clear; Google cannot fetch	Investigate robots/access/status errors	Assuming the old noindex is the only issue
Live test is clear; report has an older crawl	Request indexing where appropriate and record the date	Inventing a guaranteed processing deadline
URL redirects or canonicalizes elsewhere	Inspect the destination and intended URL	Forcing every duplicate into the index

Use the noindex directive tool to interpret copied directives; it is not a live Googlebot test. If the page is indexed despite a crawl block, use the separate robots-blocked workflow.

Completion checklist

The intended public URL and canonical target are recorded.
No unwanted directive remains in either HTML or response headers.
The live inspection result is saved with a date.
The original report date and any request date are preserved.
Later indexing or traffic observations are recorded without attributing them automatically to this change.

If noindex is gone but the page remains unindexed for a different reason, continue with crawled, currently not indexed diagnosis. RankCrab's paid workspace is prelaunch; launch notifications are optional.