New Website Not Indexed by Google? A Step-by-Step Diagnosis

First identify which stage has stopped

“Google has not indexed my new website” can describe several different situations. Google may not know a URL exists, may know it but not have crawled it, may have crawled it without choosing it for the index, or may have indexed it without showing it for the search you tried. Each state points to a different next step. Re-submitting the sitemap does not solve all four.

Open Search Console's Page indexing report for the broad pattern, then inspect one representative URL. The report is useful for groups; URL Inspection gives page-level information such as whether the URL is on Google, what canonical Google selected, and when it last crawled the page. A live test checks what Google can fetch now, but a successful live test does not mean the URL is already indexed.

• Google Search Console: URL Inspection toolInspect a URL's indexed status and run a live test.
• Google Search Central: crawling and indexing FAQGoogle's explanation of common discovery and indexing delays.

Inspect one URL before changing the whole site

Choose one important page that should be indexed, not a random URL. In URL Inspection, compare the indexed result with the live test. Record the user-declared canonical and Google's selected canonical, the last crawl, crawl permission, fetch status, and any indexing directive. Then view the tested page as Google received it and confirm that the main text and links are present.

If Google selected a different canonical, investigate duplicate URL versions first: HTTP versus HTTPS, www versus non-www, trailing slash, query parameters, or a second route serving the same page. Keep internal links, sitemap entries, redirects and canonical tags aligned to the preferred URL. Do not use robots.txt to tell Google which duplicate is canonical; it is a crawl control, not a canonicalization method.

• The preferred URL returns a stable 200 response without a login wall or browser challenge.
• The page does not accidentally carry a noindex meta tag or X-Robots-Tag header.
• robots.txt allows Googlebot to fetch the page so it can see the page's indexing instructions.
• The canonical points to the intended public URL, and the sitemap lists that same version.
• Important content is visible in the rendered page, not only after a fragile client-side interaction.

• Google Search Central: block indexing with noindexExplains how noindex works and why Google must be able to crawl a page to see it.
• Google Search Central: canonical URL guidanceBest practices for consolidating duplicate URL versions.

If Google has not crawled the page, make it easy to discover

A sitemap is a discovery hint, not an indexing command. Keep it limited to canonical, public pages that return successfully. For a small site, also make every important page reachable through ordinary links from the homepage, a relevant category, or a related article. A URL that exists only in an XML file has a weaker place in the site's information structure than a page that readers can actually navigate to.

Check the exact URL that Search Console reports, not just the homepage. A sitemap can be fetched successfully while individual URLs are blocked, redirecting, returning errors, or using a different canonical. Review DNS, TLS, server logs, CDN rules and WAF events if Googlebot receives timeouts, 5xx responses or challenges. Avoid loosening security across the whole site; fix the rule affecting the public route.

• Link to the page from a relevant, already public page using a normal anchor link.
• Use the final HTTPS URL in internal links and the sitemap; remove redirecting or non-canonical variants.
• Check robots.txt, sitemap.xml and the target page from outside your signed-in browser session.
• If several pages fail at once, investigate a shared template, deployment, DNS or firewall change before editing every URL.

• Google Search Central: sitemap guidanceWhat sitemaps can and cannot do for URL discovery.
• Debug robots.txt and sitemap URL mismatchesA focused walkthrough of URL normalization, redirects and sitemap responses.
• Diagnose crawler blocks from a WAF or CDNSeparate application errors from bot challenges and firewall rules.

If Google crawled it but did not index it, review the page itself

A successful fetch answers “could Google access this page?” It does not answer “is this page useful enough to keep as a separate search result?” Start by stating the page's unique purpose in one sentence. Then compare it with the other pages on your own site and with the results a searcher already sees. If several URLs answer the same question with nearly the same material, consolidate them or give each page a genuinely distinct job.

Look for a real reason to keep the page: original analysis, a useful comparison, firsthand product details, accurate instructions, source links, or evidence a reader can act on. Adding generic paragraphs, repeating the target phrase, or changing the publication date without a substantive update does not address a lack of value. Do not assume Search Console reveals Google's full internal reason; use the status as a signal to inspect the page and its place in the site.

• Google Search Central: helpful, reliable, people-first contentQuestions to assess whether content is original, complete and useful to its intended audience.

Use one indexing request after fixing the cause

Once the page is accessible, points to the right canonical and contains the intended content, use Request indexing for a small number of important URLs. For a larger set, submit or update the sitemap. Repeatedly requesting the same URL does not make Google crawl it faster, and Search Console has request quotas. Give the change time to be crawled and processed before making another round of edits.

Google says crawling can take from a few days to a few weeks and that a crawl request does not guarantee search inclusion. Keep monitoring the URL Inspection result and the Page indexing report. If the same issue persists, return to the evidence—response, canonical, page content, internal links and server behavior—rather than resubmitting the URL every day.

• Fix a specific technical or content issue first.
• Request indexing for a few high-value pages once, or refresh the sitemap for many URLs.
• Save the date of the fix and compare Search Console again after Google has had time to recrawl.
• Judge indexing separately from impressions, rankings, clicks and conversions.

• Google Search Central: ask Google to recrawl URLsOfficial timing, quota and sitemap guidance for recrawl requests.
• See how Launcholio checks a public websiteReview the evidence behind the automated pre-launch checks.

A short decision path

If the URL is unknown, improve discovery through internal links and a clean sitemap. If it is discovered but not crawled, check crawl access, server stability and whether the page merits priority. If it is crawled but not indexed, inspect canonicalization and the page's distinct usefulness. If it is indexed but missing for a query, work on relevance and the search result itself; do not keep changing robots.txt. This sequence helps keep indexing diagnosis separate from ranking work.