Removed Noindex but Page Still Not Indexed? Read This Date
By Ugur Saritepe · October 28, 2026
You removed noindex but the page is still not indexed, and Search Console still says Excluded by noindex tag. The first thing to read is the last crawl date. On one of my pages the tag came off on 2026-09-29. On 2026-10-14 Google still held the verdict from its last visit, on 2026-09-11.
The page: what it serves and what Google holds
game-scout.app is my other site, a games catalogue. The page is its entry for Ace Combat 8. On 2026-10-14 I fetched the live HTML and then asked Search Console about the same URL through the product's index-status tool.
live page, 2026-10-14 <meta name="robots" content="index, follow"/> X-Robots-Tag header: none
game-scout.app/game/ace-combat-8-wings-of-theve-10060
coverageState: Excluded by 'noindex' tag indexingState: BLOCKED_BY_META_TAG pageFetchState: SUCCESSFUL lastCrawlTime: 2026-09-11T10:16:15Z
Both are true. The page allows indexing today, and Google's record says it does not, because the record is 33 days old. The tag was removed 14 days before I looked. Google has not fetched the page since 2026-09-11, so it has never seen the page without the tag.
Why the page was noindex in the first place
On 2026-09-10 the site started adding upcoming and newly released games from a public games database. A new row often arrives with a name, a date and artwork, and no description. A change merged on 2026-09-11 keeps those pages out of search until the description and the artwork are both present. The comment in the code gives the reason:
// Keep it out of the index until enrichment fills both, so a thin // page never represents the site in search results.
A weekly routine goes back for the missing descriptions. It exists because of this request, typed to the assistant the same morning:
Now this is merged, can you create new routine that will work once a week to fetch coming soon games and update old list so if there is anyone already published we can fetch information like release date and if we can enrich their data we will.
Ace Combat 8 was one of those rows. Its description arrived on 2026-09-29 at 18:31 UTC, the page cleared the rule, and the tag flipped to index, follow on its own. The release date we hold for the game, 2026-10-02, passed while Google still had the page filed as excluded.
What Google did with every placeholder page
One page is one page, so I looked at all of them. The catalogue held 119 of these added rows on 2026-10-14. 106 clear the rule. 13 are still placeholders, every one missing its description. I inspected all 13, plus Ace Combat 8, which makes 14 pages that have carried the tag.
14 pages that have carried noindex Google's record, 2026-10-14 last fetched within 26 hours of going live 6 excluded by noindex last fetched later (2026-09-16, 2026-10-02) 2 excluded by noindex never fetched 6 URL is unknown to Google
Google fetched eight of the fourteen, and six of those eight were last fetched inside their first 26 hours. Four of them, Ace Combat 8 included, were fetched 95 minutes after the rule was merged and have not been fetched in the 33 days since. One was fetched nine hours after its row was created. The inspection shows the latest fetch only, so the two pages with a later date may also have had an early visit that I cannot see, and I cannot prove the other six were fetched only once.
What the pages without the tag did
The rows that arrived complete are the comparison. Seventeen rows were added in the first batch on 2026-09-10. Eleven were complete and six were placeholders, and Google fetched at least twelve of the seventeen in the same minute.
first batch, added 2026-09-10 pages Google's record, 2026-10-14 complete when added 11 8 indexed, 3 unknown placeholder when added 6 6 excluded by noindex
The eight indexed pages earned 82 impressions and 2 clicks between 2026-09-10 and 2026-10-13. That is 1 to 21 impressions a page in 34 days. The six placeholders earned none, which is what the rule is for. The cost is Ace Combat 8: complete since 2026-09-29, and still earning none.
The stakes here are small: a handful of impressions a page. The tag is also not the only way a page stays out. In the second batch, added on 2026-09-11, I inspected a sample of 21 complete pages (every fourth of 84) and Google had fetched one of them. A page Google never visits is not indexed with or without a tag.
What the ranked pages say about the wait
I read the results for this question on 2026-10-14. The guides that rank give a range. One plugin vendor says a week or two. One audit tool says a few days to a few weeks. An older crawler vendor guide says a month or longer. None shows a page with the date the tag came off next to the date of Google's last fetch. Google's own page on blocking indexing with noindex (dated 2025-12-10) is the blunt one:
it may take months for Googlebot to revisit a page
That sentence is written about adding the tag. It applies the same way to removing it. The ranges in the guides are all estimates of one thing, the time until the next fetch, and you do not have to estimate it. Search Console prints the date of the last one.
Our own tool repeated the stale verdict
I ran the product's page check on the same URL in the same minute. It fetched the live page and scored access as healthy, with 534 words in the raw HTML. Then it scored the index section Critical with this line:
Index: The page tells Google not to index it. Search Console reports indexingState BLOCKED_BY_META_TAG.
The second sentence is accurate. The first is wrong today: the page told Google that on 2026-09-11 and has not said it since 2026-09-29. The check had just fetched the page and never compared the tag it saw with the record it was quoting. If your tool reports a noindex, ask whether it read your page or read Google's memory of your page.
What we have not done
We have not told Google that Ace Combat 8 changed. The weekly routine pings IndexNow when a page clears the rule, and Google does not read IndexNow. None of the 119 pages is in either of the site's sitemaps: I fetched both on 2026-10-14, 246 URLs and 150 URLs, and found none of them. Nobody has requested a recrawl in Search Console as far as the record shows. We have not changed the page check to compare the live tag with Google's record either. All of that is still open as I write this.
How to check your own page in five minutes
- Read the live tag. Run
curl -s https://yoursite.com/page | grep -i -o '<meta[^>]*robots[^>]*>'. Good: no output, or a tag containingindex. Bad: a tag containingnoindex. Then the tag is not removed and nothing else matters yet. - Read the header. Run
curl -sI https://yoursite.com/page | grep -i x-robots-tag. Good: no output. Bad: a line containingnoindex. A header blocks indexing with no tag in the HTML at all, and the X-Robots-Tag version of this problem has its own causes. - Read the last crawl date. In Search Console, paste the URL into the inspection bar and open Page indexing. Compare Last crawl with the date you removed the tag. Older than your change: the record is out of date and the page is fine. Newer than your change: Google fetched the page after your fix and still saw a noindex, so go back to steps 1 and 2 and check what a crawler receives, not what your browser shows after scripts run.
- Give Google a reason to come back.Press Request indexing on that inspection screen. For more than a handful of pages, put them in your sitemap with a current last-modified date. Google's page on asking for a recrawl says there is a quota and that asking twice does not make it faster.
- Check again by date, not by feel. Inspect the URL again in a week. The thing to look for is the Last crawl date moving past your change. Until it moves, the verdict cannot.
Two cautions about reading the inspection. The label can be wrong in the other direction: I once got a not-indexed verdict on pages that were indexed. And if you are deciding whether to hold pages back at all, the wider question is in do pages with no traffic hurt SEO. The IndexNow half of this is in IndexNow returned 200 but the pages were never submitted. Our free triage report reads the live robots tag on your homepage from the URL alone, and the rest of these measured reads are in the AI-assistant SEO series.
FAQ
I removed noindex. Why is the page still not indexed?
Because Google has not fetched the page since you removed it. Search Console shows what Google saw on its last crawl, not what the page serves now. On one of my pages the noindex came off on 2026-09-29 and Search Console still reported Excluded by noindex tag on 2026-10-14, with a last crawl dated 2026-09-11. Compare the last crawl date with the date of your change before you look for anything else.
How long after removing noindex does Google index the page?
As long as it takes Google to fetch the page again, plus the normal time to index it. Google's own documentation says a revisit can take months for a page it considers unimportant. On my site four placeholder pages fetched once on 2026-09-11 had not been fetched again 33 days later. A page with no sitemap entry and no recrawl request has nothing pulling Google back.
Search Console says Excluded by noindex tag but the tag is gone. Is that a bug?
Usually not. The report is a record of the last crawl. Check the live page yourself: look for a robots meta tag in the page source and an X-Robots-Tag response header. If neither says noindex and the last crawl date is older than your change, the report is out of date and the page is fine. If the last crawl is newer than your change, something is still serving noindex to Google.
Should I noindex pages until their content is ready?
It keeps thin pages out of search, and it has a cost you should plan for. Google tends to fetch a new URL quickly, and that first fetch records the noindex. On my site six of eight placeholder pages were last fetched within 26 hours of going live. When the content arrives, Google has to come back before anything changes, so give it a reason: a sitemap entry with a fresh date, and a recrawl request.
Ask your assistant for a page's last crawl date instead of guessing how long to wait. Create a free account, connect Search Console, and the MCP servergives your assistant the per-URL inspection this post ran: coverage state, whether indexing is allowed, and the time of Google's last fetch. It returns Google's record as Google holds it. It does not yet compare that record with the tag on your live page. That comparison is not built.
