Google Search Console Setup Checklist for New Websites
Use this checklist when a new website is live on its final domain and you want search engines to discover the right pages. It is written for launch week: verify the property, submit the sitemap, inspect important URLs, and catch crawl blockers before they become confusing indexing issues.
Last updated: June 2026
Who this is for
Built for practical launch reviews
- Founders and indie builders launching a marketing site, SaaS landing page, directory, or small web app.
- Vercel and Next.js site owners who need a practical Search Console pass before sharing a production URL.
- Teams that want the basics covered without turning launch day into a full SEO audit.
What to check first
Start with the checks most likely to block launch
Verify the right property
Use the production domain users will visit. If the site lives at https://www.example.com, do not accidentally verify only a preview or staging URL.
Submit the live sitemap
Open /sitemap.xml first, confirm it lists public pages, then submit the full sitemap URL in the Sitemaps area of Search Console.
Inspect key launch pages
Use URL Inspection for the homepage, pricing page, product page, docs landing page, and any page you expect people to find from search.
Practical checklist
Work through these checks before launch
Set up the property
Start by making sure Search Console is looking at the same site your users see.
Use the final production domain
Add the domain or URL prefix that matches the public version of the site, including the preferred protocol and any subdomain you use.
Complete verification
Choose a verification method you can maintain. Avoid temporary files or tags that may be removed during a later deployment.
Check every important variant
Confirm that old staging domains, www/non-www variants, and alternate protocols redirect to the version you want indexed.
Submit and inspect URLs
Give search engines a clear map, then spot-check the pages that matter most.
Submit your sitemap
In Search Console, open Sitemaps, paste the sitemap path such as sitemap.xml or the full URL, submit it, and check whether Search Console can fetch it.
Inspect the homepage
Paste the live homepage URL into URL Inspection. If the live test shows it is available to Google, request indexing when the page is ready.
Inspect priority pages
Check product, pricing, resource, and important landing pages for crawlability, canonical tags, and unexpected redirects.
Understand common indexing statuses
Search Console language can sound alarming. Start by separating normal discovery states from real launch blockers.
Discovered, currently not indexed
Google knows the URL exists but has not crawled it yet. For a new site, this can be normal while crawl demand and priority settle.
Crawled, currently not indexed
Google crawled the page but has not indexed it. Check whether the page is thin, duplicated, blocked by canonical choices, or not useful enough on its own.
Duplicate or alternate canonical
Google thinks another URL is the main version. Check canonical tags, redirects, trailing slashes, query strings, and www versus non-www variants.
What to ignore at first
New site owners can waste time chasing noise. Prioritize blockers before small Search Console details.
Tiny impression changes
Early impression and click data can be sparse. Do not judge the site from a few days of low-volume search data.
Excluded utility pages
Privacy pages, terms pages, tag pages, filtered URLs, or duplicate routes may be excluded for reasonable reasons.
Every enhancement warning
Handle crawlability, indexing, titles, descriptions, and sitemap health before polishing optional enhancements.
When to worry
Some signals deserve attention quickly because they can affect many pages at once.
Important pages are blocked
Investigate quickly if your homepage, main landing pages, or tool pages are blocked by robots.txt, noindex, login walls, or server errors.
The sitemap cannot be fetched
Fix sitemap errors if Search Console cannot fetch the file, sees non-production URLs, or finds pages that redirect unexpectedly.
Canonicals point to the wrong domain
Mixed canonical domains can confuse crawling. Keep sitemap URLs, canonical tags, and Open Graph URLs on the same preferred live domain.
Review the basics after launch
Search Console is most useful when it becomes part of your launch review rather than a one-time setup step.
Watch for coverage issues
Look for pages that are blocked, redirected unexpectedly, duplicated, or excluded for reasons you do not understand.
Fix sitewide mistakes first
A bad robots.txt rule, accidental noindex tag, or broken sitemap can affect many pages, so handle those before polishing individual snippets.
Keep notes on intentional exclusions
Some pages should not be indexed. Record the reason so future checks do not turn deliberate choices into false alarms.
Practical examples
What good launch checks look like
Good launch check
The sitemap lists https://example.com/, https://example.com/pricing, and https://example.com/tools, and those pages return normal public pages.
Needs attention
Search Console is verified for a preview deployment while the live domain is somewhere else. Submit and inspect the live domain instead.
Request indexing
After URL Inspection says the live page can be indexed, use Request Indexing for your most important pages. Treat it as a discovery signal, not a ranking promise.
Indexing status example
Discovered, currently not indexed usually means Google knows the URL exists but has not crawled it yet. Blocked by robots.txt or Excluded by noindex means there is something specific to fix.
Good result
Search Console can fetch the sitemap, URL Inspection shows the live page is available to Google, and the page uses the same canonical domain as your sitemap.
Related pages
Keep checking the same launch path
Sitemap 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 ->SEO troubleshootingNew Website Indexing Troubleshooter
Understand why a new website or page is not showing in Google, with plain-English Search Console status explanations and a practical troubleshooting flow.
Open checklist ->Launch checksVercel Launch Checklist for New Websites
Launch a new Vercel website with practical checks for domains, redirects, production builds, environment values, SEO files, metadata, and final smoke tests.
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
Do I need Search Console before launch?
You can launch without it, but setting it up early helps you spot crawl and indexing issues while the site structure is still fresh in your mind.
Should I use a domain property or URL prefix property?
A domain property is broad and covers subdomains and protocols when verified correctly. A URL prefix property is narrower and can be useful when you only control one exact site variant.
What pages should I inspect first?
Inspect the homepage, main landing pages, pricing or signup pages, important resource pages, and any page linked from your launch announcement.
Will submitting a sitemap make pages rank?
No. A sitemap helps discovery. Rankings depend on many other factors, including page quality, relevance, crawlability, and competition.
How long should I wait before worrying?
For a new site, give Search Console time to crawl and process the sitemap. Worry sooner if important pages are blocked, noindexed, redirected incorrectly, or returning 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 guideNew Website Indexing Troubleshooter
Troubleshoot new pages that are not showing in Google yet.
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 ->Deploy guideVercel Launch Checklist
Check domains, redirects, builds, metadata, and smoke tests.
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 toolVercel Deployment Checklist
Check common Vercel settings before you send people to production.
Open tool