How Long Does Google Take to Index a New Page? 81 Timed

By Ugur Saritepe · October 28, 2026

How long does it take Google to index a new page? I timed 81 of my own and got two answers with nothing between them. On one site, 35 of 40 new pages were fetched within twelve hours. On the other, 28 of 29 have never been fetched, and the oldest is 40 days old. Same owner, same framework, same host.

Where the question came from

I run two sites. game-scout.app is a games site with roughly 2,500 Google clicks a month. traffictriage.com, this one, earned 2 clicks in the last 28 days. Both publish most days, and for two months I have been asking the assistant I work with some version of the same question. On 2026-08-15, about game-scout:

I already request indexing for most does not work. indexnow already run.

And on 2026-09-08, opening a session on the same site:

lets start with not indexed pages. Is there anything that got indexed lately ?

Each time the answer was a handful of pages checked on one day. On 2026-10-13 I had the assistant inspect every page either site had published in the last seven weeks, one URL at a time, and set each result against the minute the page went live.

The 81 pages

The publish time is the merge to the main branch, read from git, and both sites deploy a few minutes after a merge. The crawl time is the last crawl that Search Console's URL Inspection reports. All times are UTC.

inspected 2026-10-13                 pages  indexed  never fetched  age in days
game-scout.app, live 09-07 to 10-12     40       39              0      0 to 35
game-scout.app, live 08-25 to 09-05     12        4              8     37 to 48
traffictriage.com, live 09-03 to 10-12  29        1             28      1 to 40

Of 81 pages, 44 are indexed and 36 have never been fetched. One was fetched and left out. There is no middle group of pages that took two or three weeks. The one exception to "never fetched" on this site is a post Google crawled 17 days after it went up.

The pages that took hours

Of the 40 game-scout.app pages that went live from 2026-09-07 on, 35 show a crawl within 24 hours of their merge, and every one of those 35 is within 11.3 hours. The median is just under three hours. The fastest was ten minutes.

get_index_status

https://game-scout.app/best/best-train-games

result

coverageState: Submitted and indexed
lastCrawlTime: 2026-09-16T08:34:57Z   (merged 08:24Z)
canonicalMatches: true

2026-10-13

The other five have been crawled again since, so the tool shows the latest visit and their first one cannot be read back. 34 of the 35 are indexed. The one that is not was fetched 26 minutes after it went live and filed as "Crawled - currently not indexed", which is a decision about the page, not a delay.

Six of the 40 are Turkish versions of existing lists, the first pages this site has ever had in a second language, in a new /tr/ folder. They merged at 18:11 on 2026-10-12 and all six were fetched between 1.4 and 6.7 hours later. By the next morning all six read as indexed.

The pages that were never fetched

On traffictriage.com I have published 29 posts since 2026-09-03. One is indexed. The other 28 have an empty last crawl date, and 27 of those are at least a week old.

11 read "Discovered - currently not indexed". Google knows the address and has not requested it.
17 read "URL is unknown to Google". That includes posts listed in the sitemap Google downloaded on 2026-10-01.
The page they all link up to was last crawled on 2026-07-22. Google has not revisited the hub for this series in 83 days, so its copy of that page lists none of the 29.

I ran the same inspection a week earlier on the 27 posts that existed then. Discovered was 18 and is now 11. Unknown was 8 and is now 15. Nothing was crawled in between. The two labels trade places on pages Google has never visited, so I have stopped reading them as stages.

The older game-scout.app group is the same picture on a site Google visits daily. Twelve lists went live between 2026-08-25 and 2026-09-05. Four are indexed, two of them with a crawl 9 and 10 days after their merge. Eight have never been fetched as lists at 37 to 47 days: six Discovered, one unknown, and one where Google still shows a redirect it recorded on 2026-07-13, before that list was published. On 2026-09-09 I was already asking about them:

pc games should started getting impression, can you check again

Five weeks later, five PC lists from that fortnight are among the eight.

Across both sites, a page was either fetched within twelve hours or it joined a queue that has released 3 pages out of 39 in up to seven weeks. If your page has no last crawl date two days after it went live, more waiting is unlikely to be the fix.

The sitemap was not the path

The usual first advice is to submit a sitemap. On 2026-10-13 Search Console reported the game-scout.app sitemap as last downloaded on 2026-10-04 at 13:15. Sixteen of the 40 fast pages went live after that, including all six Turkish ones. All sixteen are indexed. Google found them some other way, most likely by revisiting pages that link to them, within hours.

On this site the sitemap was downloaded on 2026-10-01, 67 URLs, 0 errors. That is the case in a sitemap that reads Success while nothing gets discovered: the file was read and the posts in it were not visited.

What the ranked pages say

I read the pages that rank for this question on 2026-10-13. Google's own recrawl documentation says "Crawling can take anywhere from a few days to a few weeks," and adds that asking repeatedly does not speed it up and that a request does not guarantee inclusion. Conductor gives a rule of thumb of 3 to 4 weeks for a site under 500 pages. Search Engine Journal reports hours to weeks, and cites a study in which 83% of pages were indexed inside a week. One plugin vendor reports an average of 18 days across 200 pages on 8 sites it does not name.

None of them publishes a page-by-page timing for a site you can look at. And every one gives a range or an average. My 81 pages have a median of three hours in one group and no fetch at all in the other. Any average across the two describes a wait that no page of mine had.

What I cannot tell you

I do not know why game-scout.app changed around 2026-09-07. Git shows three things in that week and I cannot separate them.

On 2026-09-05 we shipped a robots.txt change that stopped blocking the /_next/folder, which had been hiding the site's CSS and JavaScript from Googlebot. That story is in blocked by robots.txt but indexed.
On 2026-09-05 the publishing routine began building new lists only in groups that already contain a list earning clicks, and by mid-September it was linking each new list from that sibling on day one.
On 2026-09-02 IndexNow began firing on every content merge. Google is not one of the engines that take part in IndexNow, so I would not expect this one to matter, and I have not ruled it out.

Three lists merged on 2026-09-05 itself. One is indexed and two are stuck, so the line is not clean. I also cannot say from the record whether I pressed Request indexing on any of the 40.

The two sites differ in age, traffic and topic all at once. This is not an experiment. It is one inspection per URL on one day, and the same tool once told me 40 indexed pages were not indexed. The cross-check here is Search Console's own performance data: every indexed list published before 5 October has impressions, and no unfetched page has a row.

We have not done anything about the eight stuck lists or the 28 unfetched posts on this site. I recorded 26 of the same posts as unfetched on 2026-10-06 and nothing has changed since.

How to time your own pages

Write down when the page went live. The deploy time, to the hour. Without it you are estimating both ends.
Inspect the URL two days later. In Search Console, paste the address into the bar at the top. Good: a last crawl date on or just after the day you published. Bad: no last crawl date at all, whatever the label above it says.
Inspect a page that links to it. If that page was last crawled before your new page existed, Google has not seen the link yet. On this site the linking hub was last crawled in July.
Check when the sitemap was last read. The Sitemaps report shows the date. A read date after your publish date with no crawl means the sitemap was not enough, which is the usual case in Discovered, currently not indexed.
Line up all your recent pages by last crawl. If most were fetched in a day and a few were not, look at what the few have in common. If none were, the question is about the site, not the page, and the free triage report rules out the blocking causes from the URL alone.

What a stalled batch looks like from the inside, and what moved it, is in Google not indexing new pages. The rest of these measured reads are in the AI-assistant SEO series.

FAQ

How long does it take Google to index a new page?

On the 81 new pages I timed on two of my own sites, it was either hours or not at all. On game-scout.app, 35 of 40 pages published since 2026-09-07 were fetched within twelve hours of going live, half of them within three hours, and 39 of the 40 are indexed. On traffictriage.com, 28 of 29 posts published since 2026-09-03 have never been fetched, the oldest 40 days old.

How long should I wait before worrying that a page is not indexed?

Check the last crawl date two days after publishing. On my faster site no page that was fetched at all waited longer than twelve hours for its first visit. Among the pages that missed that first window, three were picked up 9, 10 and 17 days later and 36 are still unfetched at up to 47 days. Waiting four weeks tells you little that day two did not.

Does submitting a sitemap make Google index pages faster?

Not on these two sites. Sixteen game-scout.app pages went live after Google last downloaded that sitemap on 2026-10-04, and all sixteen were indexed within hours. On traffictriage.com Google downloaded the sitemap on 2026-10-01 with 67 URLs and 0 errors, and 22 posts that were in it are still unfetched. A sitemap tells Google a URL exists. It did not decide when Google came.

What is the difference between Discovered and URL is unknown to Google?

Less than the names suggest when the page has never been fetched. I inspected the same 27 unfetched posts a week apart: Discovered went from 18 to 11 and unknown from 8 to 15, with no crawl on any of them in between. The field that carries information is the last crawl date. If it is empty, both labels mean Google has not visited.

Time your own pages from a chat. Create a free account, connect Search Console, and the MCP server gives your assistant the URL Inspection check this post ran 81 times: coverage state, last crawl time and the canonical Google chose. It is one URL per call, because Google offers no bulk version, so a batch of fifty takes a few minutes.

Create an account

Claude running a scheduled TrafficTriage daily check: a Search Console report on a real site, summarized with clicks, impressions, and the one query cluster that lost rank

In your AI assistant

Ask your AI about your own site

TrafficTriage plugs into Claude, Cursor, and ChatGPT. Your assistant runs the 8 checks, reads your Search Console data, and can even check your site every morning. Free account, no API key, nothing to install.