By 
Shreyas M V · Published · 12 min read
How Long Does Google Take to Index a New Post? Tracking Our Own Articles
Google's Search Console Help says it can take a week or so for a new page or site to be crawled and indexed, and a few days for new content. Other published estimates run from hours to eight weeks for a page, and 3 to 4 weeks or more for a whole site, and none of them shows a method. This page lays those figures side by side, explains why they disagree, and gives a log template for timing your own posts. It holds no Kanso indexing log, because none was supplied for this article, so no number here is a Kanso result.
How long does Google take to index a new post?
Google says a week or so, and a few days for new content, but it makes no promise and the published ranges are much wider. The figures on the pages that rank for this question run from hours to eight weeks for a single page, and none of them shows how it was measured.
- Google's own help page, retrieved 28 October 2026, gives a week or so for a new page or site and a few days for new content.
- Three practitioner pages give wider figures, from hours to eight weeks for a page and months for a large site, with no method shown.
- The figures disagree because they measure different events on different units, not because one is wrong.
- The only number that applies to your site is your own, so the log below is how to get it.
The title of this page promises a look at our own articles. We do not have that log, and the last section says what is missing. What follows is the sourced baseline and the method for building the log, so that anyone can produce the missing data.
What do the published figures say, side by side?
They say anything from a few days to several months, depending on who is asked and what is being counted. The table brings every timing figure in the supplied sources together, with what each one appears to measure and whether any method is shown.
| Source | Figure | Appears to measure | Method shown | Status |
|---|---|---|---|---|
| Google, Search Console Help (official) | A week or so for a new page or site to start being crawled and indexed. A few days for new content. | The start of crawling and indexing | None stated. It is guidance, not a measurement | Current help page, retrieved 28 October 2026 |
| StoryChief, relaying John Mueller of Google | Most high-quality content is indexed within about a week | A page | None stated. The statement is undated in the text | Practitioner page quoting a Google Search Advocate |
| StoryChief, relaying Rudzki | 83% of pages indexed within the first week of publication, on average | A page | None stated. No sample size, site count or date in the text | A secondary report of one researcher's figure |
| StoryChief | Hours for some pages, several weeks for others, up to eight weeks at the long end | A page | None stated | Practitioner page |
| Conductor, own rule of thumb | 3 to 4 weeks under 500 pages, 2 to 3 months for 500 to 25,000 pages, 4 to 12 months above 25,000 | A whole website, crawled and then indexed | None stated. Conductor says to take it with a grain of salt | Practitioner estimate, undated |
| IMPACT, from its own experience | As little as 4 days and up to 6 months for a site to be crawled and gain authority | A site, and its authority, not one page | None stated | The heading dates the piece to 2019 |
Only the first row is from Google. The other rows are commercial publishers' estimates, so they are kept apart here instead of being blended into one range.
Why do the published figures disagree?
They disagree because each source counts a different event over a different unit, and none states how it measured. Reading them as one range of "indexing time" mixes things that are not the same.
- Unit. Google and StoryChief talk about a page. Conductor talks about a whole website, and IMPACT talks about a site gaining authority, which is not the same as one page appearing.
- Event. Google says crawling and indexing start in a week or so. Conductor describes a site being fully crawled and then indexed. Those are different finish lines.
- Site size. Conductor separates under 500 pages from over 25,000, and the others do not say what size of site they have in mind.
- Age. The IMPACT piece is headed with the year 2019, so it is several years older than Google's current help page, and the sources do not say whether timing changed in between.
There is a fifth cause that the sources do not mention, and it is the author's inference. An average of pages that were indexed leaves out pages that never were, so a published average can look faster than the real experience of everything that was published.
What does Google itself say about indexing time?
Google says it can take a week or so for it to start crawling and indexing a new page or site, and a few days for new content, and it recommends waiting a few days before acting. The statements are in the Page indexing report help page in Search Console Help, retrieved 28 October 2026.
The same page says that if waiting does not seem to work, or the situation is urgent, you can ask Google to crawl individual pages. It adds that requesting indexing can reduce the lag. It also says not to expect every URL on a site to be indexed, only the canonical version of each important page.
An older Google statement, quoted by IMPACT, is blunter: Google cannot make predictions or guarantees about when or if a URL will be crawled or indexed, and the most common reason a site is not indexed is that it is too new. IMPACT does not date the statement, and its references to Webmaster Guidelines and the old Search Console menus suggest it predates the current help page. Treat the current page as the one that applies.
For anything about how Google Search behaves, Google's documentation outranks every practitioner estimate on this page. It is also the least specific, which is why the log matters.
What happens between publishing and indexing?
A page passes through discovery, crawling, rendering and indexing, and a delay at any one of them shows up as indexing lag. Conductor describes three phases (discovery, crawling, indexing), and StoryChief adds rendering as a step between the last two.
Indexing is when Google finds a page, processes its content and puts it into the Google index, where it may become eligible to appear in Search results.
That definition follows Google's own help page, which also names Discover as another place an indexed page may appear. Note the word eligible: being in the index is not the same as being shown.
Discovery needs a route in. Google says a page must be linked from a known page or listed in a sitemap, and that a site on a hosting service such as Wix or Squarespace will probably have new pages announced to Google automatically. Crawling then needs the page to be reachable, and StoryChief adds that an overloaded server can slow it down.
Rendering and indexing are where content gets processed. Conductor names three things that slow this stage: heavy reliance on client-rendered JavaScript, poor content quality and a very large site. StoryChief says the page must also be indexable, meaning not blocked by robots.txt and not marked noindex.
How do you time your own posts?
Record, for every new URL, the time it went public and the first check that showed it as indexed, using one check method throughout. That gives you indexing lag in days for your own site, which no published range can.
The steps below are the author's design, assembled from Google's two documented check methods. They are a process, not a sourced standard.
- Decide the sample. Log every post you publish for a fixed period, not only the ones you remember, so slow pages are not filtered out by memory.
- Record the publish time in UTC at the moment the page goes public, and record how Google was told about it.
- Check daily for the first week and at least weekly after that. Use the URL Inspection tool or a search for the exact URL with the site: operator, and keep to one of them.
- Write down the last check that showed not indexed and the first that showed indexed. The real lag sits between them.
- Keep every row, including pages that are still not indexed at the end of your window. Record the reason Search Console gives for them.
- Summarise with the median, the share indexed within 7 days, and the count never indexed, not with a mean alone.
Your check interval sets your resolution. Checking once a day pins each lag to within one day, while checking once a week cannot tell "within a week" from "a few days", which is the exact difference Google's wording turns on.
Google's help page adds a useful rule for small sites. If your site has fewer than 500 pages, it says you probably do not need the Page indexing report, and it points to the site: searches instead. The report is also not meant for checking one page, and the URL Inspection tool is.
What should each row of the log contain?
Each row needs nine fields, and the two that matter most are the last check that showed not indexed and the first that showed indexed. The table lists them, with what each is for.
| Field | What to record | Why it is there |
|---|---|---|
| URL | The exact canonical address, with the same host and slash as the sitemap | A duplicate or alternate URL can be marked as not indexed while the canonical is fine |
| Published at (UTC) | The moment the page became public, not the moment it was drafted | Every lag is measured from this time |
| How Google was told | None, sitemap, an indexing request, a link from an indexed page, or a combination | Lets you compare lag by route once you have enough rows |
| Last check showing not indexed | Date and time of the final check before the page appeared | With the next field, it brackets the real lag |
| First check showing indexed | Date and time of the first check that did | The upper bound of the lag |
| Check method | Search Console's URL Inspection tool, or a search for the exact URL with the site: operator | Two methods can disagree, so one log should use one method |
| Lag (days) | First check showing indexed minus published at, with the bracket noted | The number you summarise |
| Page facts at publication | Internal links in, word count, whether it is in the sitemap, anything unusual about rendering | The only way to learn what slows a particular site |
| Status at the end of the window | Indexed, not indexed with the reason Search Console gives, or still unknown | Pages that never index belong in the log, not outside it |
The ninth field is the one most logs skip. A page that is not indexed after the window is a result, and leaving it out would turn the log into a list of pages that worked.
What does one row look like, with invented dates?
One row is a bracket, not a single number. The dates below are invented for illustration and describe no real page.
Say a post goes public at 14:00 UTC on 2 March. A check at 09:00 on 4 March shows it not indexed, and a check at 09:00 on 5 March shows it indexed.
lag is between 1 day 19 hours and 2 days 19 hours, recorded as 3 days (rounded up to whole days)
Working it through: 2 March 14:00 to 4 March 09:00 is 1 day 19 hours, and to 5 March 09:00 is 2 days 19 hours. The bracket is therefore 1 day 19 hours to 2 days 19 hours, and the safe entry is 3 days if you round up to whole days.
Pick one convention, here rounding up to whole days, and keep it for every row. Mixing conventions inside one log is a common way to make an average mean nothing.
What would 60 posts look like if the sourced week figure held?
If StoryChief's relayed 83% held for a log of 60 posts, about 50 would be indexed within 7 days and about 10 would take longer. The arithmetic is 0.83 × 60 = 49.8, and 60 − 49.8 = 10.2.
Treat that as a yardstick, not a forecast. The 83% is a figure attributed to Rudzki and relayed by StoryChief, and the text shows no sample, no date and no definition of indexed. A log of 60 that came in at 40 within the week would not contradict a figure whose basis nobody can inspect.
The number 60 is a round example for the arithmetic, and not a count of anything Kanso has measured. A sample that small also moves a lot on a few pages: each post is about 1.7% of the total, so ten pages moving across the 7-day line is the difference between 83% and 67%.
How should you read the lag once you have it?
Read it against the sourced ranges in four bands: within 7 days, 8 to 28 days, 29 to 56 days, and past 56 days. The cut-offs are the author's, taken from the figures in the first table, not a Google standard.
| Observed lag | Where it sits against the sources | What to do |
|---|---|---|
| Indexed within 7 days | Matches Google's own description and the StoryChief and Rudzki figures | Nothing to fix. Keep logging |
| Indexed between 8 and 28 days | Inside the range the practitioner pages give for a small site, but slower than Google's wording | Check that the page is in the sitemap and linked from an indexed page |
| Indexed between 29 and 56 days | Inside StoryChief's eight-week outer figure and past Conductor's 3 to 4 weeks for sites under 500 pages | Run the checks in the troubleshooting steps below |
| Not indexed after 56 days | Outside every page-level figure we read | Treat it as a diagnosis, not a wait. Read the reason Search Console gives |
A page in the last row is the one case where waiting is no longer a plan. The reason Search Console gives for it, such as a robots.txt rule, a noindex tag or a duplicate, is the next thing to read.
What slows indexing down?
The sources name site size, client-rendered JavaScript, thin content, weak internal links, an overloaded server, a blocked or noindexed page, and a low crawl priority. They are listed here by what kind of source says so, because only one is Google.
- Official guidance (Google): a page that cannot be found because nothing links to it and it is not in a sitemap. A robots.txt block, a noindex tag, a duplicate of another page.
- Practitioner opinion (Conductor): reliance on client-rendered JavaScript, content quality and site size, plus a weak internal link structure.
- Practitioner opinion (StoryChief): crawl budget, which it splits into a crawl limit and crawl demand, and says Google prioritises pages with more backlinks or traffic. It also names server overload.
- Practitioner opinion (IMPACT): a newer domain, fewer and weaker inbound links, and lower traffic, from its own experience.
None of these has a measured effect size in the text we read, so none can be ranked. You can test your own site's version of each by recording the "page facts at publication" field in the log and sorting by it once you have enough rows.
What can speed indexing up?
Google's own list is short: a link from a known page, a sitemap, and an explicit indexing request through Search Console. Everything past that on the ranking pages is practitioner opinion and carries no guarantee.
- Official guidance (Google): request indexing for individual pages, which it says can reduce the lag. For a brand-new site, request indexing of the homepage first, since Google says the rest can be reached from it if navigation is sound.
- Official guidance (Google): use a sitemap or other methods to tell Google about a new site or page, unless a hosting service already does it for you.
- Practitioner opinion (Conductor, IMPACT): link to the new page from older, already-indexed pages, and earn links from other sites.
- Practitioner opinion (StoryChief): the Google Indexing API for pages that qualify. The research for this article contains no Google document on who qualifies, so check Google's own documentation before relying on it.
Both Conductor and StoryChief state that none of this guarantees speed. A log lets you check whether a route helps on your site by comparing the lag of pages that used it with the lag of pages that did not.
What should you do when a page stays unindexed?
Confirm the page is allowed to be indexed, confirm it is the canonical, give Google a route to it, and then read the reason Search Console reports. Work through these in order before requesting indexing again.
- Open the URL Inspection tool for the page and read the status and reason it gives. Google says this is the tool for the status of a specific page.
- Check the page is not blocked by a robots.txt rule or marked noindex, which StoryChief and Google both list.
- Check the canonical. Google says duplicate and alternate pages should not be indexed, and a page marked that way usually means Google found and indexed the canonical.
- Check the page is linked from an already-indexed page and is in the sitemap.
- Check the server answered reliably around the time Google would have crawled, since StoryChief says overload can slow crawling.
- Request indexing once the checks above pass. Google says a request can reduce the lag, and StoryChief and Conductor both say it guarantees nothing.
If the reason is one of Search Console's "discovered" or "crawled" statuses, the Kanso guide to finding which stage is broken matches each status to its likely cause. For the basics of Search Console reports, how to read Google Search Console as a founder covers where the Page indexing report and the URL Inspection tool sit.
What is documented, and what is the author's analysis?
The documented facts are Google's statements and the figures the three practitioner pages give, and everything else here is analysis. The two lists keep them apart.
Documented:
- Google's help page says it can take a week or so for a new page or site to be crawled and indexed, and a few days for new content.
- Google's help page says not every URL should be indexed, only the canonical version of each important page.
- Google's help page says requesting indexing can reduce the lag, and that an indexed page will not appear in every search.
- StoryChief, Conductor and IMPACT each give a timing range, and none states the method or sample behind it.
- Conductor gives its estimates by site size and tells readers to treat them with caution.
Analysis:
- The figures disagree mostly because they measure different things: a page, a site, or a site's authority.
- A secondary figure such as 83% within a week cannot be compared with a log until its method is known.
- A log that drops pages which never indexed will make indexing look faster than it is.
- The four-row reading table and its 7, 28 and 56 day cut-offs are the author's thresholds, built from the ranges above, not a standard.
- A median and a share-within-7-days describe a log better than a mean, because a few slow pages pull a mean up.
The weekly checks in the weekly growth checklist include a look at the Page indexing report, which is where a log like this one would be reviewed.
What does this page not have?
It has no first-hand indexing log, no per-URL timings for Kanso's own articles, and no independent test of Google's behaviour. The title names our own articles, and that data was not available when this page was written.
- No Kanso indexing log. Nothing here states how long any Kanso article took to be indexed.
- No method behind the practitioner figures. We can attribute them, but cannot verify them.
- No time series, so the sources cannot say whether Google has become faster or slower.
- No figure for how long a re-index or an indexing request takes.
When a log exists, the right way to add it is a dated table with the sample rule, the check method and the full set of rows, including pages that never indexed. A companion post on Kanso's first 90 days of content is planned but not published, so it is not linked here.
Frequently asked questions
These are the questions the search results and community threads raise about indexing time, answered from the sources above.
How long does it take Google to index a new page?
Google's Search Console Help says it can take a week or so for Google to start crawling and indexing a new page or site, and a few days for new content. Practitioner pages give wider ranges, from hours up to eight weeks for a page, and none of them states the method behind its numbers. Nobody can promise a date.
How long does Google take to index a new website?
The published answers differ by source. Google says a week or so for a new site to start being crawled and indexed, Conductor estimates 3 to 4 weeks for a site under 500 pages by its own rule of thumb, and an IMPACT piece dated to 2019 gives 4 days to 6 months. They measure different events, so they are not in conflict.
How long does Google Search Console take to index a page after I request it?
None of the sources we read gives a time for a request. Google says requesting indexing can reduce the lag, and Conductor and StoryChief both say it guarantees nothing, including that the page will be recrawled straight away. The only way to learn the real figure for your site is to log it.
What is the longest Google has taken to index a page?
No source we read states a maximum. StoryChief says some pages wait up to eight weeks, and the IMPACT range for a site runs to six months, but some pages are never indexed at all. StoryChief also reports Mueller saying that even a high-quality page is not guaranteed to be indexed.
How long does it take Google to re-index a website?
The sources we read give no time for a re-index. Conductor says you can ask for a recrawl of a URL in the URL Inspection tool and check its crawl table for the last crawl date, and that a sitemap kept up to date lets Google recrawl pages that changed. Google's two-week figure for validating a fix is a different process.
Is Google indexing new content faster than it used to?
The sources do not show a trend either way. They give no dated series, and the figures they do give use different wording, units and methods, so a 2019-era range cannot be compared with a current help page. Only your own log can show whether your lag is changing.
Does a sitemap guarantee that Google will index my pages?
No. A Google statement quoted by IMPACT says a sitemap helps Google learn about a site but does not guarantee indexing or raise ranking. Google's current help page names a sitemap as one way to tell Google about new pages, alongside links from a known page.
Will Google index every page on my site?
No. Google's Page indexing report help says you should not expect all URLs to be indexed, only the canonical pages. It lists reasons a page can be left out for good cause, such as a robots.txt rule, a noindex tag, a duplicate, or a deleted page with no replacement.
Is an indexed page guaranteed to appear in search results?
No. Google says results are customised by search history, location and other variables, so an indexed page will not show in every search or at the same position. If Search Console says a URL is indexed and it does not appear for you, Google says to assume it is indexed and eligible.
How can I check whether a new page is indexed?
Search for the exact URL with the site: operator, or inspect the URL in Search Console's URL Inspection tool. Google says a site with fewer than 500 pages probably does not need the Page indexing report, and recommends those searches first. The report is not built for checking one page.
Sources
Google's help page is the only primary source. The three practitioner pages are cited for the figures they give, not as verified measurements.
- Page indexing report, Search Console Help, Google, retrieved 28 October 2026
- How long does it take for Google to index a website?, Conductor Academy, retrieved 28 October 2026
- How Long Does Google Take to Index a New Website?, StoryChief, retrieved 28 October 2026
- Google Index: How long does indexing take and 11 ways to get your pages listed faster, IMPACT, retrieved 28 October 2026
Note: Timing figures are attributed to the four pages named, as supplied to us and read on 28 October 2026. Only Google's Search Console Help is a primary source, and none of the four shows the method behind a timing figure. The log template, the day thresholds and the worked arithmetic are the author's own, and every date in the worked example is invented. Kanso reports no indexing results on this page because none were supplied. Kanso has no affiliation with the sources named. Re-check Google's help page before relying on any figure here.
Research & experiments