How Long Google Takes to Index a New Site (And Why Nobody Can Tell You)
Search for how long Google takes to index a new site and you’ll find confident numbers everywhere: three days, two weeks, a month. None of them come from Google, because Google doesn’t publish one — and its own documentation explains why it can’t.
That sounds like an evasion. It isn’t. Once you understand what actually has to happen between publishing a page and seeing it in search results, the absence of a fixed timeline stops being frustrating and starts being useful, because it points at the specific things you can control.
This article covers what Google officially says about timing, the four separate stages most people compress into one word, and the single technical failure that can silently stop everything — which I ran into on my own site while writing this.
How Long Google Takes to Index a New Site: Google’s Own Answer
Start with the uncomfortable part, stated plainly in the documentation for how Search works:
“Google doesn’t guarantee that it will crawl, index, or serve your page, even if your page follows the Google Search Essentials.”
And more directly:
“Indexing isn’t guaranteed; not every page that Google processes will be indexed.”
There is no queue you join, no ticket number, no service level. Google decides whether a page is worth storing, and some pages never are.
Where Google does give figures is in Search Console’s URL Inspection tool, which says indexing “typically takes only a day or so, but can take much longer in some cases,” and elsewhere that it “can take up to a week or two.”
So the honest range for a page on an established, healthy site is roughly a day to two weeks. For a brand-new site with no history and no inbound links, it is commonly longer, and for some pages it is never.
The Four Stages Hiding Inside One Word
Most confusion about how long Google takes to index a new site comes from treating “getting on Google” as a single event. It’s four, and they fail differently.
Discovery. Google has to learn the URL exists. It finds pages by revisiting known pages, by following links from pages it already knows, or through a submitted sitemap.
Crawling. Googlebot downloads the page. This depends on your server responding, on your robots.txt permitting it, and on Google deciding the page is worth the bandwidth.
Indexing. Google analyses what it downloaded and decides whether to store it. This is the stage with no guarantee attached.
Serving. The page is eligible to appear for a query. Being indexed makes you eligible; it does not make you visible.
A site stuck at stage one has a discovery problem. A site stuck at stage three has a quality or duplication problem. They look identical from the outside — nothing in Google — and they need completely different fixes.
| Stage | What can go wrong | Where you’d see it |
|---|---|---|
| Discovery | No links in, no sitemap submitted | URL unknown to Search Console |
| Crawling | robots.txt blocking, server errors, timeouts | “Crawled” errors in Search Console |
| Indexing | Thin, duplicate, or low-value content | “Discovered – currently not indexed” |
| Serving | Indexed but outranked | Indexed, but zero impressions |
How Google Finds a New Site at All
A brand-new domain has a specific problem: nothing links to it. Google’s primary discovery mechanism is following links from pages it already knows, and a site nobody has linked to is invisible to that mechanism.
This is why the first weeks of a new site feel like shouting into a void. It isn’t that Google is evaluating you slowly. It’s that Google may not know you exist.
Two things solve discovery. A sitemap submitted through Search Console tells Google your URLs directly, and Google’s sitemap documentation recommends one specifically for sites that are “new with few external links.” Note what it also says, though:
“A sitemap helps search engines discover URLs on your site, but it doesn’t guarantee that all the items in your sitemap will be crawled and indexed.”
The second is any genuine link from a site Google already crawls. One real mention is worth more for discovery than a hundred submissions, because it also signals that someone thought the page was worth pointing at.
Worth knowing: Google defines a small site as “about 500 pages or fewer,” and says a small, well-internally-linked site may not strictly need a sitemap. Submit one anyway when you’re new — the cost is nothing and the discovery problem is real.
The Failure That Stops Everything Silently
This is the part almost no article on this topic covers, and it’s the one that can waste months.
Before Googlebot crawls anything on your site, it fetches your robots.txt file. If that file returns a server error or times out, Google does not assume permission. It assumes the opposite. From Google’s robots.txt specification:
“For the first 12 hours, Google stops crawling the site but keeps trying to fetch the robots.txt file.”
Read that again. Not the page — the site. An unreachable robots.txt halts crawling of everything you’ve published.
After that first period, Google falls back: for the next 30 days it uses the last good version it managed to fetch, while continuing to retry. Past 30 days, if the site is otherwise reachable, Google behaves as though there is no robots.txt at all; if the site has broader availability problems, it stops crawling and only periodically checks back.
The reason this is so dangerous is that nothing about it is visible to you. Your site loads perfectly in a browser. Articles publish normally. Nothing looks broken. Meanwhile the file that grants crawl permission is intermittently timing out, and during those windows your newest work is invisible.
I hit exactly this while checking my own site for this article — repeated attempts to read published pages failed at the robots.txt fetch, and only intermittently, which is the worst version because it looks like noise rather than a fault.
How to check it yourself: open yoursite.com/robots.txt directly in a browser. It should load instantly and show plain text. If it hangs, loads slowly, or errors even occasionally, that’s the problem — and it’s a hosting issue, not an SEO one.
Crawled, But Still Not Indexed
A page can be found, downloaded, and then simply not stored. In Search Console this appears as “Crawled – currently not indexed” or “Discovered – currently not indexed,” and it is the most common complaint from new sites.
The usual causes are unglamorous. The page is thin — not short, but lacking anything a reader couldn’t get elsewhere. It substantially duplicates another page on your own site, so Google picks one and drops the rest. Or the site is new enough that Google hasn’t yet decided how much of it to store.
That last one matters more than people expect. Crawl budget isn’t distributed evenly; an unknown domain gets less attention than an established one, and that’s a reason to prefer fewer strong pages over many weak ones early on. It’s also part of why a blog behaves like a slow business model even though nobody formally gatekeeps it — the delay is baked into how discovery and trust accumulate.
What Actually Helps
Five things, in rough order of impact.
Fix technical access first. A reachable robots.txt, a working sitemap, fast server responses, and HTTPS. None of this is optional and all of it precedes anything else — there is no content strategy that survives being uncrawlable. This is also the strongest argument for paying for proper hosting rather than the cheapest available: the domain and hosting are the two purchases with no worthwhile free alternative, and unreliable server response is exactly what breaks crawling.
Verify the site in Search Console. Without it you’re guessing. With it you can see whether a URL is known, crawled, indexed, or excluded, and why.
Use URL Inspection to request indexing for genuinely new pages. It works, within limits: Google states that “submitting a request does not guarantee that the page will appear in the Google Index,” there’s a daily cap per property, and repeated submissions of the same URL don’t accelerate anything. For bulk updates, Google points to sitemaps with accurate lastmod dates instead.
Link internally, deliberately. Every new article should be linked from at least one existing page. This is how Google walks through your site, and an orphaned page relies entirely on the sitemap.
Earn one real external link. Harder than the rest combined, and worth more than all of them for a new domain.
What Doesn’t Help
Resubmitting the same URL repeatedly. Google’s documentation is explicit that this doesn’t speed anything up, and the daily quota exists precisely because people try.
Paid “instant indexing” services. Crawl rate cannot be purchased — Google states this directly — and services claiming otherwise are either using the same free tools you have or doing nothing at all.
Publishing more, faster, to seem active. On a new domain this more often produces a pile of thin pages competing with each other, which makes the indexing decision harder rather than easier. Volume is only an advantage when each piece carries something the others don’t — which is the difference between producing content at scale and producing the same article repeatedly.
Endless technical tweaking while the real problem is elsewhere. Meta tags don’t fix a robots.txt that times out.
Indexed Is Not the Same as Ranking
The distinction that saves the most confusion: being indexed means your page is eligible to appear for a query. It says nothing about whether it will.
A new site can be fully indexed within two weeks and receive essentially no traffic for months, and that is the normal sequence rather than a malfunction. Indexing is a technical state. Ranking is a competitive outcome, and it depends on whether your page is genuinely better than the ones already there.
This gap is worth planning around rather than enduring. If you need income before search traffic arrives, a service business priced from published wage data produces revenue in weeks rather than months, and can fund the site through the period when it earns nothing.
Which means the correct question after two weeks is not “why am I not ranking” but “is this page actually indexed?” — because those two situations have completely different answers, and people routinely spend months optimising for the second problem while having the first.
Frequently Asked Questions
How long does Google take to index a new site? Google publishes no guaranteed timeline. Its Search Console documentation says indexing “typically takes only a day or so, but can take much longer,” and elsewhere “up to a week or two.” New domains with no inbound links commonly take longer, and some pages are never indexed at all.
Why isn’t my site on Google after a month? Most likely a discovery or crawling problem rather than a quality one. Check that robots.txt loads, that a sitemap is submitted in Search Console, and use URL Inspection to see whether Google knows the URL exists.
Does submitting a sitemap guarantee indexing? No. Google states plainly that a sitemap helps discovery but “doesn’t guarantee that all the items in your sitemap will be crawled and indexed.”
Can I pay to be indexed faster? No. Crawl rate and ranking cannot be bought from Google, and any service claiming to sell indexing is either using the free tools available to you or providing nothing.
What does “Discovered – currently not indexed” mean? Google knows the URL but chose not to store it, usually because the content is thin or duplicates another page, or because the domain is new and receiving limited crawl attention. It’s a content and trust signal rather than a technical fault.
Should I request indexing for every article I publish? For genuinely new pages it’s reasonable, within the daily limit. Repeated requests for the same URL don’t help, and for many pages at once a sitemap with accurate lastmod dates is the tool Google recommends.
My pages are indexed but get no traffic. What’s wrong? Nothing, necessarily. Indexed means eligible, not visible. Ranking is a separate, competitive process that typically takes months on a new domain.
Does publishing more often make Google index faster? Not reliably, and on a new site it can backfire by creating thin pages that compete with each other. Consistency helps; volume for its own sake doesn’t.
Conclusion
Nobody can tell you how long Google takes to index a new site because Google itself refuses to promise it will happen at all. That’s not evasiveness — it’s an accurate description of a system that decides, page by page, whether storing something is worthwhile.
What you can control sits earlier in the chain. Make the site technically reachable, starting with a robots.txt that never times out. Submit a sitemap. Verify in Search Console so you’re reading data instead of guessing. Link your pages to each other. Then publish things worth storing.
And separate the two questions that look identical from the outside. “Am I indexed?” is technical and answerable today. “Am I ranking?” is competitive and takes months. Confusing them is how people end up rewriting meta descriptions while their crawl access is quietly broken.
A Note from Lucas
I started this article expecting to write a straightforward timeline piece, and ended up somewhere more useful because of something I found on my own site. While trying to verify my published articles, the requests kept failing — not on the pages, on the robots.txt file, and only some of the time. Reading Google’s specification afterwards was genuinely unsettling: twelve hours of a failed robots.txt fetch and crawling stops for the entire site, with nothing visibly wrong from a browser. I’d spent weeks thinking about content quality while a hosting-level file was intermittently deciding whether any of it could be seen. If you take one thing from this, open your own robots.txt right now and watch how fast it loads.
About the Author
Lucas Palma is the founder and editor of Info Is The Key. He writes about online business, entrepreneurship, and the practical mechanics of building income independently, working from primary sources and official data rather than recycled advice.
Last Updated: September 2026 | Reading Time: 9 minutes
Editorial note: This article summarises Google’s own published documentation as of September 2026. Search behaviour and documentation change over time — always check the current Google Search Central pages linked below before acting on anything time-sensitive. This is educational content, not a guarantee of search performance.
