We create digital solutions that work for businesses
You published a website or a new page, but it is missing from Google even when you search for the exact title. This does not always mean something is broken. Google must first discover the URL, crawl it, process its content, and then decide whether to add it to the index.
This guide provides a practical diagnostic sequence, from inspecting one URL in Google Search Console to finding site-wide technical issues.
Do not begin by repeatedly clicking “Request indexing.” Identify the status of the affected URL and fix the underlying cause first.
Crawling means Googlebot visited a URL. Indexing means Google processed the page and may show it in Search. Ranking determines where the indexed page appears for a particular query.
A page may be indexed without ranking for its target keywords. A site: search can offer a quick hint, but the URL Inspection tool in Search Console provides the more reliable status.
The live test shows whether Google can access the current version. The main report may describe an earlier crawl, so the two results can temporarily differ.
| Status | Meaning | What to check |
|---|---|---|
| URL is unknown to Google | Google has not discovered the address | Sitemap, internal links, and public accessibility |
| Discovered – currently not indexed | The URL is known but has not been crawled yet | Site structure, server capacity, and excessive technical URLs |
| Crawled – currently not indexed | Google visited the page but did not index it | Original value, duplication, canonical signals, and internal links |
| Excluded by noindex | The page explicitly prevents indexing | Meta robots and X-Robots-Tag |
| Blocked by robots.txt | Googlebot cannot crawl the URL | robots.txt rules |
| Page with redirect | The URL redirects elsewhere | Redirect destination and chains |
| Duplicate | Google selected another canonical page | Canonical, sitemap, linking, and duplicate URLs |
| Server error (5xx) | Google did not receive a valid response | Logs, hosting, application, CDN, and timeouts |
An indexable URL should normally return 200 OK. Check for 404 and soft-404 responses, 5xx failures, redirect loops, security tools blocking bots, and different responses being served to users and Googlebot. Intermittent failures require server logs and uptime monitoring rather than a one-time test.
This rule blocks crawling across the entire website:
User-agent: *
Disallow: /
It is sometimes copied from a staging environment to production by mistake. Robots.txt controls crawling; it is not a reliable removal mechanism. Do not block a page that Google must crawl in order to see its noindex directive.
Look for this tag in the page head:
<meta name="robots" content="noindex">
Non-HTML resources may be blocked with an HTTP header:
X-Robots-Tag: noindex
On WordPress, also check the global search-engine visibility option and the SEO plugin settings for the post, taxonomy, or content type.
A canonical tag tells Google which URL should represent a group of similar pages. If page A declares page B as canonical, Google may exclude A. A unique page will commonly use a self-referencing canonical:
<link rel="canonical" href="https://example.com/page/">
Internal links, sitemap entries, hreflang, and redirects should all reinforce the same HTTPS hostname and URL format.
An XML sitemap helps Google discover new and updated URLs but does not guarantee indexing. Include only canonical 200-status pages that should appear in Search.
Link to the page from a relevant category, service page, or article using a standard HTML link. An orphan URL with no internal links receives a weak priority signal and is harder to discover.
“Crawled – currently not indexed” is often not solved by a technical switch. Confirm that the page satisfies a distinct search intent, includes original examples or practical guidance, does not paraphrase another page, and is not a thin filter, tag, or internal-search result.
Merge weak duplicates, improve the strongest resource, and use redirects or canonical tags where separate pages are unnecessary.
Google can process JavaScript, but rendering may be delayed or fail. In the live URL test, inspect the screenshot and rendered HTML. Googlebot should be able to see the main copy, headings, and links without clicking or scrolling. Important SEO content is safer in the initial HTML or reliable server-rendered output.
Once the cause is resolved, test the live URL and request indexing. For many affected pages, update the sitemap and internal linking. Repeated submissions do not accelerate crawling.
Do not use Google’s Indexing API for ordinary articles or service pages. Google officially limits it to qualifying job-posting and livestream pages.
There is no fixed deadline. An established website may have an important page processed quickly, while a new domain or large catalogue can take longer. Requesting indexing never guarantees inclusion.
When Google does not index a website, determine where the process breaks: URL discovery, crawling, rendering, canonical selection, or quality assessment. Search Console identifies the status; your task is to correct its cause.
For a systematic review of technical barriers, architecture, and content, explore SEO services from BB STUDIO. You may also need the guides to robots.txt, hreflang, and 301 and 302 redirects. Verify these localized URLs before publishing.
Connect Search Console, submit an XML sitemap, create internal links, and request indexing for priority URLs. These steps improve discovery but do not guarantee indexing.
Google fetched the URL but chose not to index it yet. Common reasons include duplication, limited original value, orphan pages, and conflicting canonical signals.
No. A sitemap helps Google discover preferred URLs, but Google decides whether each page belongs in the index.
No. Repeated requests do not guarantee faster indexing. Fix the cause, update discovery signals, and submit once after the live test succeeds.
Let’s create something amazing together