How long does Google take to index a submitted URL?

A few months ago a client emailed me: “We submitted 40 URLs on Monday. It’s Wednesday. Why isn’t everything indexed?”

They weren’t wrong to be annoyed. They’d done the usual checklist: sitemap updated, a few URL Inspections, API notices for the rest. Search Console still looked empty.

I pulled our numbers instead of guessing. The figures below are as of July 25, 2026. Among pages that did get indexed after submission over the trailing year, the median wait was about 124 hours (roughly five days). 32% landed within 48 hours. 56% within a week. That’s from about 8,700 successful indexings. We watch 1.3M+ pages across active sites. The speed stats only cover the ones that actually made it into the index.

These aggregates refresh on an ongoing basis. If you read this later, treat July 25, 2026 as a snapshot and get current numbers from the live page: Google Indexing Statistics.

Those figures help. They’re also easy to misuse. This is how I read them.

The number everyone wants (with a catch)

People hear “median five days” and turn it into an SLA: submit Monday, show up in Search by Friday.

That isn’t what the data says.

We only time URLs that eventually show as indexed in Search Console after a recorded submission. Pages that stay unknown, stuck, or crawled but not indexed never enter that median. So this is not “how often submission works.” It’s “when submission is followed by indexing, how long did that usually take?”

If your page is a thin affiliate clone, Google can fetch it Tuesday and still refuse to keep it. The median won’t save you. Neither will submitting it three more times.

What “crawled, not indexed” is actually telling you

In plain language: Google’s bot opened the URL, then Google declined to put it in the searchable catalog.

That’s different from “Google never found it.” Discovery and inclusion are separate. Submission mostly helps with the first one (getting a fetch on the calendar sooner). The second question is whether the page deserves a slot.

When I see crawled-not-indexed after a clean submit, I stop looking at the API log and start looking at the page. Is it unique? Does it do a job another URL already does? Is it blocked by a weird canonical, soft 404, or noindex you forgot? Are there any real internal links pointing at it?

Sometimes the fix is boring: merge duplicates, expand the thin URL into something someone would bookmark, or stop publishing near-identical location pages. Not glamorous. Works more often than another batch job.

More pings feel productive. They’re usually not.

How we count (short version)

Clock starts at first submission for that URL. Clock stops at first indexed status in Search Console. Trailing twelve months. No customer domains in the public write-up, aggregates only.

We’re not running a randomized “submit vs don’t submit” experiment on the whole web. These are sites already using submission workflows. Your niche might be faster or slower. Search Console can lag. Because the public page keeps updating, cite the date you checked it (this article’s snapshot is July 25, 2026).

Still, if someone asks whether 48 hours is realistic, I finally have something better than vibes. Sometimes yes. Often no. Five days to a week is a saner default when the page is going to index at all.

Where submission actually helps

I’ve seen it matter for launches that are live but barely linked: new locale folders, seasonal product grids, posts that only exist in a CMS list and a sitemap. Without a nudge, Google may get there eventually. “Eventually” is a bad answer when the campaign starts Thursday.

Same for migrations. You move a chunk of URLs, the 301s are clean, the new templates work, and you still want Google to re-fetch the important stuff instead of discovering the rewrite by accident three weeks later. One coordinated submit after the cutover beats a month of anxious re-checks.

It’s also fine for real updates: you replaced the page, it returns 200, something material changed. Tell Google. Once.

What it’s bad at: turning garbage into an indexed asset, or replacing a site architecture that has no internal links worth following.

I still catch teams celebrating “2,000 API calls this week” like it’s output. Calls are input. If coverage didn’t move and the pages are still thin variants of each other, you mostly generated log lines.

The Indexing API’s own docs lean toward specific page types like job postings and livestreams. Plenty of teams still use Search Console tooling more broadly. Whatever channel you pick, treat it like tapping someone on the shoulder in a crowded room. They might turn around. They might not stay for the conversation.

What I tell clients now

I used to oversell speed because everyone wants a number. Now I say something closer to this:

If this URL is going to index after we submit it, history says think in days, not hours. Median around five in our sample, with some faster and a long tail slower. If it gets crawled and still doesn’t index, we don’t submit harder. We fix why Google would skip it.

That conversation is less fun than “we have an API.” It’s also how you keep trust when Wednesday arrives and half the batch is still invisible.

One last thing

Submission volume is a vanity metric. Indexed coverage of URLs that deserve to exist is the real one.

The old line still holds: content is king. Submission is just the courier. Use the API, Inspection, and sitemaps to shorten the wait for a look. Use the page itself (substance, uniqueness, technical access) to earn a place in the index. Our dataset is public if you want the live medians. Just don’t quote a frozen screenshot as forever-true. The numbers in this piece are as of July 25, 2026.

Source (live): Google Indexing Statistics.

Author bio

Anton P works on URL indexing tooling and Search Console-based monitoring. This article uses aggregated stats from that work. It isn’t a product review.