Google Search Console Setup Checklist for a New Site Launch

Launching a new website without setting up Google Search Console first is like opening a store without a phone number. Google might eventually find you — but you're leaving indexing speed, error visibility, and ranking data on the table.

This checklist covers everything you need to do in Google Search Console during a site launch, in the correct order, so you don't miss anything.

Before You Flip the Switch (Pre-Launch)

1. Create Your GSC Property Before Going Live

You can add a property to GSC before the site is publicly accessible. Do this now so you're collecting data from day one and can spot indexing issues immediately after launch.

Go to Google Search Console → Add property.

Choose property type carefully:

| Property Type | What It Covers | When to Use | |---|---|---| | Domain property | All subdomains + http/https | Recommended for most sites | | URL prefix | Specific URL prefix only | If you can't verify DNS |

A domain property covers yourdomain.com, www.yourdomain.com, blog.yourdomain.com, and both http and https versions. One property to rule them all.

2. Verify Ownership

Option A: DNS record (recommended for domain properties) Add a TXT record to your domain's DNS. This is the most reliable method and works even if your site is down.

Option B: HTML tag Add a <meta name="google-site-verification" ...> tag to your <head>. Works for URL prefix properties.

Option C: Google Analytics If you're already running GA4, you can verify via your analytics snippet. Requires the GA tracking code to be on every page.

Option D: Google Tag Manager Similar to GA — verify via GTM container snippet.

Verify ownership now. If you don't, you lose access to all the data GSC would have collected from day one.

3. Check robots.txt Before Launch

This is critical. Many staging environments block all crawlers with:

User-agent: *
Disallow: /

Make sure this gets changed before launch. Test your robots.txt with GSC's robots.txt tester: Settings → robots.txt.

Common issues to check:

No Disallow: / for all crawlers
Your important paths aren't accidentally blocked
Crawl delays aren't set too high

4. Prepare Your XML Sitemap

Your sitemap should be ready at /sitemap.xml before launch. It should:

Include only 200-status, canonical pages you want indexed
NOT include noindex pages, paginated pages (unless deliberate), or parameter URLs
Have accurate <lastmod> dates
Be under 50,000 URLs (split into a sitemap index if larger)

If you're using WordPress, Yoast SEO or RankMath auto-generates a sitemap. For Next.js, use next-sitemap. For Shopify, the sitemap is auto-generated at /sitemap.xml.

Day of Launch Checklist

5. Submit Your Sitemap

Once the site is live:

Go to Index → Sitemaps
Enter your sitemap URL (usually sitemap.xml or sitemap_index.xml)
Click Submit

GSC will validate the sitemap within minutes and show you the number of URLs submitted and how many are indexed. If you see errors, address them immediately.

6. Request Indexing for Your Key Pages

Don't wait for Googlebot to discover your pages organically. Use the URL Inspection tool to fast-track your most important pages:

Go to URL Inspection (or press / in GSC)
Enter your homepage URL
Click Request Indexing

Repeat for your top 5–10 priority pages: homepage, product/service pages, category pages, key blog posts.

Limit: You can request indexing for about 10 URLs per day. Prioritize pages you need indexed immediately.

7. Verify Your Preferred URL Format

Decide now: www or non-www. Make sure:

Your server redirects one to the other (301)
Your canonical tags use the consistent format
Your sitemap uses the canonical format

In GSC, if you set up a domain property, this is handled automatically. If you set up a URL prefix property, add both versions as separate properties or pick one.

8. Connect Google Analytics

In GSC, link your property to Google Analytics (if you haven't already). This enables:

Richer data in GA4's Search Console report
Cross-referencing organic traffic with conversion data

Go to Settings → Associations and link your GA4 property.

First Week: Active Monitoring

9. Monitor the Coverage Report Daily

During launch week, check Index → Coverage every day for:

Errors: Crawl errors that need immediate fixing (5xx server errors, blocked pages)
Valid with warnings: Pages Google indexed but flagged (e.g., indexed despite noindex — usually a conflict between canonical and noindex)
Excluded: Pages not indexed and why. Look for unexpected exclusions.

Common early errors after launch:

Submitted URL returns unauthorized request (401) — authentication blocking crawl
Submitted URL blocked by robots.txt — forgot to remove staging robots.txt
Redirect error — redirect loop or chain too long

10. Check Mobile Usability

If your site isn't mobile-friendly, Google will penalize your rankings. Check immediately:

Enhancements → Mobile Usability

Look for:

Text too small to read
Clickable elements too close together
Content wider than screen

Fix any issues within the first week — mobile issues significantly affect your ability to rank.

11. Verify Core Web Vitals Baseline

Go to Experience → Core Web Vitals to see your initial CWV scores. You likely won't have data immediately (Google needs a few weeks of real user data), but establish a baseline early so you can track improvements.

For a brand new site with no data yet, use the URL Inspection tool → Test live URL → View tested page to see what Google sees.

12. Check the Performance Report for First Impressions

Within 1–2 weeks of launch, your pages should start appearing in the Performance report with impressions (even if no clicks yet). This confirms:

Google has indexed your pages
Your pages are appearing in search results (even if low-ranking)
GSC is collecting data correctly

If you see zero impressions after 2 weeks, something is blocking indexing.

First Month: Foundation Building

13. Set Up Regular Monitoring Cadence

Schedule these recurring checks:

Weekly: Coverage report for new errors; Performance for impression/click trends
Monthly: Mobile usability, Core Web Vitals, manual actions check, links report

14. Check for Manual Actions

Go to Security & Manual Actions → Manual actions. A manual action means a Google quality reviewer has penalized your site. New sites occasionally trigger manual actions if they were previously used for spam.

This should be clear on a legitimate new site, but check anyway.

15. Review Security Issues

Go to Security & Manual Actions → Security issues. Google will flag hacked content, malware, or deceptive practices here. Clear for most legitimate launches, but verify.

16. Connect Search Console Tools for Ongoing Analysis

Once your data is flowing, Search Console Tools gives you deeper analysis without the 1,000-row cap:

All your pages' performance data, not just the top 1,000
Easy identification of which new pages are gaining traction
Impressions vs. indexed page tracking

Common Launch Mistakes and How to Avoid Them

Mistake 1: Forgetting to remove staging robots.txt block Check robots.txt on day of launch. Use GSC's robots.txt tester immediately after going live.

Mistake 2: Setting up URL prefix property instead of domain property A URL prefix property only covers one URL format. A domain property covers everything. Use domain property unless there's a specific reason not to.

Mistake 3: Not verifying both http and https If you're using URL prefix properties, verify both http and https versions. If one gets crawled first, you want data.

Mistake 4: Submitting a sitemap with noindex pages Run through your sitemap and verify every URL returns 200 and has no noindex tag. Submitting noindex pages to GSC creates confusing Coverage errors.

Mistake 5: Only requesting indexing for the homepage Use the URL Inspection tool on your 10 most important pages. The homepage will get crawled quickly — your deep content pages need help.

FAQ

How long does it take Google to index a new website?

After proper GSC setup (verified property, sitemap submitted, indexing requested), most new sites see initial pages indexed within 3–7 days. Full site indexing can take 2–8 weeks depending on site size and link profile. If pages aren't indexed after 2 weeks, check Coverage errors for blocking issues.

Do I need both a www and non-www property in Google Search Console?

If you set up a domain property, no — it covers all variations. If you use URL prefix properties, you'd need to add both. Domain property (verified via DNS) is almost always the better choice.

What's the most important thing to do in GSC immediately after launch?

Submit your sitemap and request indexing for your top pages via the URL Inspection tool. These two actions are the fastest way to get indexed. Also verify your robots.txt isn't blocking Googlebot.

Can I add a property for a site that's not live yet?

Yes. You can verify ownership via DNS even before a site is publicly accessible. Adding the property early means GSC starts collecting any crawl data from launch day, and you can use URL Inspection to test pages before going fully live.

How do I know if Google has indexed my new site?

Check the Coverage report for "Valid" pages. Also search Google for site:yourdomain.com — if results appear, those pages are indexed. In the Performance report, you'll see impressions start appearing once pages are in Google's index and appearing in search results.

Should I use a sitemap index or individual sitemap files?

For sites under 50,000 URLs, a single sitemap file is fine. For larger sites, or sites with distinct sections (blog, products, categories), use a sitemap index at /sitemap.xml that references individual sitemap files. This makes it easier to diagnose which section has indexing issues.

Next steps: How to Add Your Website to Google Search Console and Google Search Console Sitemap Guide for a deeper dive into sitemap best practices.