New Website Indexing Troubleshooter
New pages often take time to appear in Google, especially on a fresh domain with few links and little search history. This guide helps you separate normal waiting from fixable problems such as blocked pages, missing sitemaps, noindex tags, redirects, duplicate canonicals, or thin pages that are not ready to stand on their own.
Last updated: June 2026
Who this is for
Built for practical launch reviews
- Non-technical website owners wondering why a new page is not showing in Google yet.
- Small-site, indie-tool, and AI-built-app owners checking Search Console for the first time.
- Builders who need a calm order of operations before changing sitemap, robots, canonical, or metadata settings.
What to check first
Start with the checks most likely to block launch
Check the live URL
Open the exact page in a private browser window. If it redirects, errors, requires login, or still points to a preview domain, fix that before investigating Search Console.
Inspect the page in Search Console
Paste the final URL into URL Inspection. Compare the indexed status with the live test, because the live page may have changed since Google last checked it.
Check sitemap and crawl rules
Confirm the page is in /sitemap.xml, is not blocked in /robots.txt, and does not include a noindex instruction.
Practical checklist
Work through these checks before launch
Understand the three stages
Search Console is easier to read when you separate discovery, crawling, and indexing.
Discovered
Google knows the URL exists, usually from a sitemap, link, redirect, or previous crawl. It has not necessarily visited the page yet.
Crawled
Google visited the page and saw the response, content, redirects, canonical tags, robots instructions, and other signals available at that time.
Indexed
Google has chosen to include the page in its index. This does not guarantee rankings, traffic, or that the snippet will look exactly like your metadata.
Step-by-step troubleshooting flow
Work through the basics in this order so you do not fix the wrong thing first.
1. Open the final page
Check the exact production URL users should visit. Confirm it loads publicly, shows the intended content, and does not require a login.
2. Inspect the URL
Use Search Console URL Inspection. Look at the current status, then run a live test to see what Google can access now.
3. Check sitemap and robots
Open /sitemap.xml and /robots.txt on the live domain. The page should be listed in the sitemap and not blocked by robots rules.
4. Check noindex and canonical
Make sure the page is not marked noindex and that its canonical URL points to the version you want Google to index.
5. Improve the page if needed
If the page is crawlable but still not indexed, review whether it is thin, duplicated, unclear, or missing useful content compared with similar pages.
6. Request indexing carefully
After fixing blockers, use Request Indexing for important pages. Treat it as a prompt for recrawl, not a promise that the page will rank.
What to do first
This checklist catches the most common causes before you spend time rewriting pages.
Confirm the page is public
The page should return normal public content on the final domain. Avoid login gates, password protection, preview URLs, and broken redirects.
Submit a clean sitemap
Use the Google Search Console checklist to submit the live sitemap and make sure it contains the page you care about.
Check the snippet basics
Use the meta title and description preview to make sure the page has a specific title and useful description once it can appear in search.
When not to worry
Some messages are normal during the first days or weeks of a new site, especially when the technical basics look clean.
The page is newly published
If the page is crawlable, listed in the sitemap, and not blocked, it may simply need time before Google crawls and evaluates it.
Utility pages are excluded
Terms, privacy, redirected URLs, duplicate filters, tag pages, and internal utility pages may be excluded without harming the main launch pages.
Search data is sparse
A fresh site may show little impression or click data at first. Focus on blockers before reading too much into low-volume reports.
When to fix something
These are the cases where action is usually better than waiting.
Important pages are blocked
Fix public pages blocked by robots.txt, noindex, login requirements, server errors, or accidental redirects.
Google sees the wrong URL
Align sitemap URLs, canonical tags, redirects, internal links, and preferred www or non-www domain choices.
The page is too thin or duplicated
If Google crawled the page but did not index it, make sure the page has a clear purpose, helpful content, and a reason to exist separately from similar pages.
Search Console statuses
What the common indexing messages mean
Use these messages as clues. A status can be normal for one URL and a problem for another, depending on whether the page should appear in Google.
| Status | What it usually means | What to do first |
|---|---|---|
| URL is on Google | Google has indexed the URL, though the page may still have warnings or may not rank for the searches you expect. | Check that the indexed URL is the preferred version, then improve title, description, content, and internal links if search presentation is weak. |
| URL is not on Google | Google has not indexed this exact URL. It may be new, blocked, redirected, duplicated, or not selected for indexing. | Run the live test, then check sitemap inclusion, robots.txt, noindex, canonical tags, redirects, and page quality. |
| Discovered, currently not indexed | Google knows the URL exists but has not crawled it yet, or has not prioritized crawling it yet. | Confirm the page is in the sitemap, internally linked, public, and useful. Wait if it is new and there are no blockers. |
| Crawled, currently not indexed | Google visited the page but did not add it to the index at that time. | Check for thin content, duplicate content, weak internal links, canonical issues, or pages that are not useful as standalone search results. |
| Blocked by robots.txt | Google is being told not to crawl the URL by a robots.txt rule. | Open /robots.txt, find the matching rule, and remove or narrow the block if the page should be public in search. |
| Excluded by noindex | The page contains a noindex instruction, so Google should not include it in search results. | Remove the noindex instruction only if the page should be searchable, deploy, run a live test, then request indexing. |
| Page with redirect | The URL redirects somewhere else, so Google is likely to evaluate the destination rather than index this URL. | Make sure the redirect is intentional and that sitemaps and internal links point to the final destination URL. |
| Duplicate without user-selected canonical | Google found duplicate or very similar content and chose another URL as the main version. | Add or fix canonical tags, clean up duplicate routes, and make sure internal links and sitemaps use the preferred URL. |
Practical examples
What good launch checks look like
Normal early signal
A new resource page is listed in the sitemap and says Discovered, currently not indexed. If it is crawlable and useful, give Google time before making major changes.
Fixable blocker
URL Inspection says Excluded by noindex for a public landing page. Remove the noindex instruction, deploy, test the live URL, then request indexing.
Canonical mismatch
The sitemap lists the www URL, but the page canonical points to the non-www URL. Make sitemap, canonical, redirects, and metadata use the same preferred domain.
Good indexing result
The page is public, appears in the sitemap, passes the live URL Inspection test, is not blocked by robots.txt or noindex, and has a self-referencing canonical URL.
Status to investigate
Crawled, currently not indexed means Google visited the page but did not index it. Check whether the page is duplicated, thin, unclear, or canonicalized elsewhere.
Related pages
Keep checking the same launch path
Google Search Console Setup Checklist for New Websites
Set up Google Search Console for a new website with clear checks for verification, sitemap submission, URL inspection, indexing basics, and launch follow-up.
Open checklist ->SEO filesSitemap and Robots.txt Checker
Review sitemap.xml and robots.txt before launch so public pages are discoverable, blocked paths are intentional, and search crawlers get clear instructions.
Open checklist ->MetadataOpen Graph Preview Checker
Check Open Graph preview basics before sharing a page, including title, description, image, URL, canonical metadata, and search snippet fallbacks.
Open checklist ->FAQ
Short answers before launch
Why is my new website not on Google yet?
Google may not have discovered, crawled, or indexed the pages yet. Check the live URL, sitemap, robots.txt, noindex, redirects, and URL Inspection before assuming something is wrong.
Does submitting a sitemap guarantee indexing?
No. A sitemap helps Google discover URLs. A page still needs to be crawlable, indexable, canonicalized correctly, and useful enough to include.
Should I request indexing for every page?
Start with the homepage and important public pages. Do not waste time requesting indexing for duplicate, redirected, private, thin, or intentionally excluded URLs.
Can metadata stop a page from being indexed?
A weak title or description usually does not block indexing, but a noindex tag can. Metadata is still worth improving because it affects clarity when pages appear in search and social previews.
When should I ask for technical help?
Ask for help if important pages are blocked, Search Console cannot fetch your sitemap, the live test fails, canonicals point to the wrong URL, or many public pages return errors.
Related checks
Related ShipCheckr checks
Follow these links to keep the launch review moving across search, metadata, deployment, and AI-specific checks.
Start Here
Follow a guided path through ShipCheckr launch checks.
Open check ->PrintableWebsite Launch Checklist PDF
Print a practical website launch checklist or save it as a PDF.
Open check ->SEO guideGoogle Search Console Setup Checklist
Verify the property, submit the sitemap, and inspect key URLs.
Open check ->SEO guideSitemap and Robots.txt Checker
Review crawl files before launch.
Open check ->ToolMeta Title and Description Preview
Preview search title and description copy.
Open check ->GlossaryWebsite Launch Glossary
Plain-English definitions for launch, SEO, metadata, and AI terms.
Open check ->ShipCheckr tools
Useful tools for this review
Meta Title and Description Preview
Check how your page title and description read in search results.
Open toolLaunch Readiness Scorecard
Score the basics that make a small app feel ready to use.
Open toolAI App Launch Checklist
Run through the core checks before you publish an AI-built app.
Open tool