Journal
How Long to Index on Google? Check a Page and Fix Delays
Google has no fixed indexing deadline, but a URL-level check can show whether a page needs time, better discovery, or a specific fix.
- google indexing
- google search console
- technical seo
- crawlability
- xml sitemaps
A sitemap can be submitted while individual pages remain unindexed weeks later. The sitemap helps Google discover URLs; it does not confirm that Google has crawled or accepted each one. For anyone searching how long to index on google, the useful next step is to inspect the specific URL and act on its status.
A page may be indexed within hours or take days to weeks. Google sets no indexing deadline, and some URLs are never indexed. Google Search Console can show whether a URL has been discovered, crawled, or indexed. Check that result before changing the page or requesting another crawl. Indexing does not guarantee a ranking.
How long does Google take to index a page?
Google says a requested crawl can take a few days to a few weeks. That is a recrawl estimate, not a deadline for indexing. A new website with few links may first need time to be discovered. Even an indexed page appears for a particular search only when Google considers it relevant to that query.
The stages are separate:
- Discovery: Google finds a URL through a link, an XML sitemap, or another route.
- Crawling: Googlebot fetches the URL. A discovered page may still be waiting for a crawl.
- Indexing: Google processes the page, including rendering where needed, and evaluates whether to index it. A crawled page may remain unindexed.
- Serving: Google may show an indexed page in results for relevant searches.
Google explains these distinctions in its guide to how Search works. They also explain why a page can be technically accessible without appearing in results.
Check the URL in Google Search Console
Enter the exact page address in Search Console’s URL Inspection tool. Read the indexing status, Google-selected canonical, and last-crawl information. Then use Test live URL if the indexed-version result suggests a problem that might since have changed. The live test checks the current page; it does not mean Google has indexed that version.
Use the Page Indexing report to see whether multiple important URLs share a status. Its reporting can lag behind crawling and indexing activity, so use URL Inspection for a page-level diagnosis rather than treating a report update as the moment indexing happened.
Here is a worked example for a hypothetical article at https://example.com/guides/widget-sizing/:
| URL Inspection result | Likely diagnosis | Next action |
|---|---|---|
| Crawled – currently not indexed | Google fetched the example article, so a discovery or crawl block is not the immediate issue. Google has not selected it for indexing. | Check the Google-selected canonical. If it points to this URL, compare the article with similar site pages and improve any substantial overlap or missing information. |
| Discovered – currently not indexed | Google knows the URL but has not crawled it. | Confirm it loads, link to it from a relevant page, and include its canonical URL in the sitemap. |
| Excluded by ‘noindex’ tag | Google detected an instruction not to index the page. | Remove the directive if it was unintended, then request a recrawl. |
The first row does not prove the article is low quality; it identifies which checks are more useful than another sitemap submission. If Search Console cannot fetch the sitemap, start by diagnosing the sitemap error.
Why a known page may remain unindexed
A URL may have no navigable internal links, return an intermittent server error, or require a login. A robots.txt rule can block Googlebot from crawling; a noindex directive can prevent an accessible page from being indexed. If crawling is blocked, Googlebot may not see a noindex change on that page.
Google describes crawl budget in terms of crawl demand and the site’s crawl capacity. That distinction matters particularly for large sites with many URLs. For a smaller site, checking whether an important page is reachable and internally linked is usually a more useful first move than trying to optimize crawl budget.
Duplicate URLs create another possibility: Google may choose a different canonical page. Rendering failures can also leave important text unavailable to Google. And meeting basic technical requirements does not oblige Google to index a page; substantially repetitive content may need a clearer purpose and more useful, verifiable detail. For a lean team, choosing a distinct, realistic topic is often more productive than publishing several near-identical articles.
Help Google crawl a page and reassess changes
Work in this order so a request to crawl points Google toward a page that is ready:
- Confirm indexability. Check the response,
robots.txt,noindex, and the intended canonical URL. - Add a relevant internal link. A visitor should be able to reach the page from an existing, related page.
- Maintain an XML sitemap. Include preferred canonical URLs and submit the sitemap through Search Console. Google’s sitemap guidance identifies sitemaps as particularly useful for new sites with few external links.
- Request indexing for an important new or substantially changed URL. Use URL Inspection after resolving any identified problem. Google says repeated requests for the same URL do not make crawling faster.
How long does Google take to reindex a page?
An updated page must be recrawled and reprocessed before its indexed version can change. After a substantial revision, use URL Inspection to request a recrawl, then compare the reported last crawl and indexed result later. Keep the same URL when updating an existing article unless there is a separate reason to move it. A new publishing schedule alone cannot replace accessible pages, useful links, and meaningful revisions.
The Indexing API is not a blog-post shortcut
Google limits the Indexing API to pages containing eligible JobPosting or BroadcastEvent embedded in a VideoObject, for job postings and livestream content. It is not a general fast-track for ordinary articles. For those pages, use the sitemap and URL Inspection workflow instead.
FAQ
How long does Google take to index a new website?
A new site has no single indexing status: its homepage and individual articles can be discovered and processed at different times. Submit a sitemap in Search Console and add navigable links between important pages. Then inspect a few representative URLs individually. An indexed homepage does not establish that every article is indexed.
Does requesting indexing in Search Console guarantee inclusion?
No. A request asks Google to consider crawling the URL; it does not override a noindex directive or require Google to add the page to its index. If a requested URL stays excluded, read its URL Inspection status and fix the reported issue. Repeatedly sending the same request will not accelerate the crawl.
Why does a site: search disagree with URL Inspection?
A site: query is a rough way to explore results, not a definitive indexing check for one URL. Search results can vary, and Google may show a different canonical URL from the one entered. Inspect the exact address in Search Console and compare it with the Google-selected canonical before deciding that the page is missing.
Should a team submit a sitemap again if only one page is missing?
First inspect that page. A sitemap submission does not confirm that each listed URL was indexed. If other sitemap URLs are indexed and the missing page is marked Crawled – currently not indexed, another submission is unlikely to address the immediate issue. Investigate its canonical choice and how it differs from similar pages instead.
Seovyn uses Google Search Console data in its keyword and content workflow, including queries a site almost ranks for. Teams deciding what to improve next can pair that workflow with URL-level indexing checks. Start free.