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.
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 that URL in Search Console.
Inspect key launch pages
Start with 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
Use the sitemap URL generated by the site, usually /sitemap.xml, and make sure it contains only public pages you want crawled.
Inspect the homepage
Run URL inspection for the homepage and request indexing when the page is ready. Treat this as a check, not a guarantee of immediate ranking.
Inspect priority pages
Check product, pricing, resource, and important landing pages for crawlability, canonical tags, and unexpected redirects.
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.
Useful note
Requesting indexing can help Search Console discover a page, but it does not guarantee immediate indexing or ranking.
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 ->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.
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 ->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 ->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