How Long Does Google Take to Crawl a New Blog Post?
You hit Publish, open URL Inspection in Search Console, paste in the new address, and get this result: "URL is not on Google." The post is live on your site, but Google has not picked it up yet.
That wait is frustrating, especially when you publish on a schedule and every post is supposed to support a content cluster. How long Google takes to crawl a new blog post follows a predictable sequence, though, and you can influence most of the delay.
This guide gives you a realistic timeline for each stage, from discovery through ranking. It also covers the exact steps to get Google to discover new posts faster and the status checks that confirm each stage worked. Along the way, you'll see why the popular "indexed in 2 minutes" claim skips one important step.
Before you start: you need a verified Search Console property and a live, submitted XML sitemap. The post also has to be indexable, which means it has no noindex tag and is not blocked in robots.txt.
How Long Does Google Take to Crawl a New Blog Post?
Google typically crawls a new blog post within a few days to a few weeks. Google Search Central's documentation describes crawling as taking anywhere from several days to several weeks. Indexing is a separate step that can take longer, and the speed of both depends on how Google discovers the URL, your site's history, and crawl demand.
Crawling is the process where Googlebot, Google's automated fetcher, requests your page and reads its content. Think of it like a library: crawling is the librarian picking up your book, indexing is adding it to the catalog, and ranking is deciding which shelf it goes on.
Each of those steps can stall on its own. A crawled page is not automatically indexed, and an indexed page is not automatically ranking. The Crawl Clock below separates the stages. The timing ranges are typical estimates, not guarantees.
| Stage | Typical timing | Confirmation signal | Failure signal |
|---|---|---|---|
| Discovery | Hours to days | URL appears in sitemap reports or in URL Inspection's referring data | "URL is unknown to Google" |
| Crawl | Days to weeks | URL Inspection shows a "Last crawl" date | "Discovered â currently not indexed" |
| Index | Days to weeks after the crawl | "URL is on Google" | "Crawled â currently not indexed" |
| Rank | Weeks to months | Impressions appear in the Performance report | Indexed, but zero impressions |
Several factors shift this clock. Google crawls new sites more slowly because it has little history to judge how often their pages change or how valuable they are, so it assigns them lower crawl demand. Pages linked from URLs Google already crawls often get found faster. An accurate sitemap lastmod date (the field that records when a page last changed) tells Google the post is fresh. Slow server responses reduce how much Googlebot fetches per visit, and duplicate content gives Google a reason to skip the page. Together, these factors determine your crawl budget.
BloGoose publishes finished articles directly to WordPress or your custom API. That means the discovery clock starts as soon as each post goes live.
How to Get a New Blog Post Crawled Faster
You get a new post crawled faster by giving Google clear discovery paths: an updated sitemap, internal links from frequently crawled pages, structured data, and a single indexing request. Before you begin, confirm you have Search Console access and edit rights to your CMS.
- Submit or refresh your XML sitemap (about 5 minutes). Make sure the new post is listed with an accurate lastmod date. Then open Search Console, go to Indexing, then Sitemaps, and resubmit the sitemap URL. A successful submission shows the status "Success" along with an updated "Last read" date. If you need to build the file first, follow this XML sitemap setup guide.
- Link the post from pages Google already crawls often (about 10 minutes). Add links from your homepage, the relevant category hub, and two or three related posts. Googlebot follows those links on its next visit, so the new URL no longer depends on the sitemap alone.
- Add article schema markup (about 15 minutes). Schema is code that labels the headline, author, and publish date for search engines. Use this article schema markup guide, then run the page through Google's Rich Results Test. Success looks like "Article" listed as a valid detected item.
- Request indexing once through URL Inspection (about 2 minutes). Paste the URL into the inspection bar at the top of Search Console, wait for the live test to finish, and click Request Indexing. You should see "Indexing requested." For example, a Blogger user publishes a post, pastes its URL into URL Inspection, and clicks Request Indexing. This is the step the "2-minute indexing" claim skips over: the request only adds the URL to a crawl queue and does not guarantee indexing.
Pro tip: Request indexing only once. Practitioners widely agree that repeated requests do not move a URL up the queue, although Google has not stated this directly.
- Skip the Indexing API for blog posts. Google's Indexing API documentation lists support only for pages with JobPosting or BroadcastEvent markup. Using the API for regular blog posts falls outside that scope, so treat it as a risk rather than a shortcut.
Once these steps are done, the next task is confirming what Google actually did with your post.
How to Check Whether Google Crawled and Indexed Your Post
Open URL Inspection in Google Search Console first, because it shows the post's last crawl date and current index status. The Page Indexing report and a site: search are useful cross-checks, but they are less precise.
- URL Inspection: Paste the URL and read the "Last crawl" date. This is best for confirming a single new post.
- Page Indexing report: This shows statuses across the whole property. It is best for growth leads who track an entire content cluster.
- site: search: This method is fast and needs no login, but the results are incomplete. It is best for a quick check by solo operators.
| Status | What it means | Likely cause | Next action |
|---|---|---|---|
| URL is not on Google | Google has not discovered the post yet. | The post is missing from the sitemap or has no internal links. | Add the post to the sitemap, link to it, and request indexing. |
| Discovered â currently not indexed | Google knows the URL exists but has not crawled it. | The post sits in the crawl queue or has weak priority signals. | Add internal links from strong pages, then wait. |
| Crawled â currently not indexed | Google fetched the post but chose not to index it. | Thin content, near-duplicate pages, or a canonical conflict. | Audit content quality and the canonical tag. |
| Indexed | The post is eligible to appear in results. | No problem. | Monitor impressions. |
Wait-or-act matrix (practitioner heuristic, not a Google rule):
- Days 0â3: Wait. Confirm the post appears in the sitemap.
- Days 3â14: Check URL Inspection and strengthen internal links.
- Day 14 and later: Diagnose the problem using the status table above.
Here is how to handle a post stuck on "Crawled â currently not indexed." Google fetched the page and judged it not worth indexing yet, so resubmitting it will not change the outcome. Instead, audit the content for depth and originality against the pages that already rank. Then search your own site for near-duplicate posts that target the same query, and merge or differentiate them. Finally, confirm that the canonical tag points to the post itself, because canonical URL mistakes often cause this status. Request indexing once you have fixed these issues.
Manual uploads add another delay between finishing a draft and making it live. BloGoose publishes directly to WordPress or a custom API, which removes that delay. Our Google indexing setup docs explain how to connect your publishing workflow to Search Console.
Frequently Asked Questions About New Post Crawl Times
How long does it take a brand-new website to get indexed?
A brand-new website usually takes longer to get indexed than an established one. With little site history and few inbound links, Google has fewer paths for discovering its pages. Submitting a sitemap and building internal link depth both shorten that discovery phase.
Can you really get indexed in 2 minutes?
It is possible, but it is not guaranteed. Requesting indexing adds your URL to Google's crawl queue, and Google still decides when to crawl the page and whether to index it. Some posts are indexed quickly, while others wait days.
Should you resubmit a post after updating it?
Yes, but only once. Update the post's lastmod date in your sitemap, then request indexing a single time, because repeated requests do not move a post up the queue. For a full process, see our guide to refreshing older posts.
Is the Indexing API safe for blog posts?
The Indexing API is not meant for blog posts. Google documents the API only for pages with JobPosting or BroadcastEvent structured data, so using it for articles falls outside its supported scope. Follow the caveat in step 5 and rely on sitemaps instead.
What to Do After You Hit Publish
Your crawl time depends less on luck and more on the signals you send Google. Every new post moves through the same Crawl Clock: Discovery, Crawl, Index, and Rank.
Only three actions reliably move a post from one stage to the next:
- Add the post to your sitemap and link to it from pages that already rank.
- Submit one URL Inspection request, and then stop requesting.
- After 14 days, diagnose the post's Search Console status instead of waiting longer.
Indexing gets you into search results, and getting quoted by AI assistants is the next step. Learn more about getting cited in AI answers.
Plan and publish your next cluster with BloGoose so that every post goes live with clear discovery signals.