The Technical SEO Checklist Every New Site Must Pass Before Launch

You've spent weeks — maybe months — building your new website. The design looks sharp, the copy is polished, and your hosting is sorted. But before you flip that "Go Live" switch, there's one more thing you absolutely cannot skip: a technical SEO audit.

I've watched too many well-designed sites limp out of the gate because they launched with a noindex tag left over from staging, or a sitemap pointing to the wrong domain, or structured data that threw validation errors. Google doesn't care how pretty your homepage looks. It cares whether it can find, crawl, understand, and index your pages — in that order.

This checklist walks you through every technical layer your site needs to pass before it goes public. Work through it top to bottom. Don't skip sections because they sound boring. The boring ones are usually the ones that bite you.

1. Crawlability — Can Google Actually Get In?

Check your robots.txt file. Visit yourdomain.com/robots.txt directly in a browser. Make sure it exists and that you haven't accidentally disallowed / (the whole site). A misconfigured robots.txt from a staging environment is one of the most common launch disasters. It should allow Googlebot and other major crawlers access to everything you want indexed.
Remove any staging-era blocks. Many developers add Disallow: / or a password protection plugin during build. Double-check that every single staging restriction has been removed.
Test your robots.txt in Google Search Console. Use the robots.txt tester (found under Index > Coverage in older GSC, or via the URL inspection tool) to confirm your key pages aren't being blocked.
Check for meta robots tags site-wide. Search your codebase or CMS templates for <meta name="robots" content="noindex">. This is the silent killer — it won't show an error anywhere, but Google will quietly ignore every page it touches.
Verify crawl depth. Your most important pages should be reachable within 3 clicks from the homepage. Deep buried pages get crawled less frequently and ranked less consistently.

2. Indexing — Are You Letting Google Remember You?

Connect Google Search Console on day one. Verify ownership before launch if possible. This lets you submit your sitemap, catch crawl errors early, and monitor for manual actions from the moment you go live.
Set your preferred domain. Decide: www or non-www? Both should work, but one should redirect to the other. Set this as canonical in GSC and in your site's settings.
Confirm HTTPS is enforced. All HTTP traffic should 301-redirect to HTTPS. Check this for both www and non-www variants. Mixed content warnings (HTTP resources on HTTPS pages) also need to be cleaned up.
Request indexing for your priority pages. After launch, use the URL Inspection tool in GSC to manually request indexing for your homepage, key category pages, and any cornerstone content. Don't just wait for the crawl — ask for it.
Do a "site:" search once you're live. A few days after launch, run site:yourdomain.com in Google. If nothing returns, there's a problem. If unexpected pages show up (like old staging paths), investigate immediately.

3. XML Sitemaps — Your Map to Google's Front Door

Generate a clean XML sitemap. It should include only indexable URLs — no noindex pages, no paginated archive pages unless they're important, no parameter-heavy URLs. Tools like Screaming Frog or your CMS plugin can auto-generate these, but always review the output manually.
Submit your sitemap to Google Search Console. Go to Index > Sitemaps in GSC and paste the full URL (yourdomain.com/sitemap.xml). Watch for "Couldn't fetch" errors — those usually mean a wrong path or server block.
Reference your sitemap in robots.txt. Add this line: Sitemap: https://yourdomain.com/sitemap.xml. It's a small thing but it makes the sitemap discoverable to any crawler, not just ones that check GSC.
Check for sitemap errors. Open your sitemap in a browser and look for malformed URLs, HTTP links on an HTTPS site, or pages that return 404s. A sitemap full of dead links is worse than no sitemap at all — it wastes crawl budget.
Use a sitemap index if you have a large site. If you're launching with hundreds of pages (e-commerce, news sites), split your sitemap by category or content type and use a sitemap index file to link them together.

4. Canonical Tags — Telling Google Which Page Counts

Every page needs a self-referencing canonical tag. Even if there are no duplicate versions of a page, add <link rel="canonical" href="https://yourdomain.com/page-url/"> in the <head>. This is defensive SEO — it prevents accidental duplicate content problems from URL parameters, session IDs, or tracking codes.
Audit for unintentional canonicals. CMSs sometimes set every page's canonical to the homepage (a common WordPress plugin bug). Crawl your site with Screaming Frog and check the canonical column for anomalies.
Handle pagination correctly. Don't use rel="prev/next" (Google deprecated it), but do make sure paginated pages either have their own canonical or point to the first page — depending on whether you want them indexed individually.
Match canonical protocol and subdomain. If your canonical tag says http:// but the site runs on https://, you've created a conflict. Canonical URLs must exactly match the preferred version of the page, including trailing slashes if that's your standard.

5. Core Technical Health — The Under-the-Hood Stuff

Run a full site crawl before launch. Use Screaming Frog (free up to 500 URLs) or Sitebulb to crawl your entire site. Look for: 404 errors, redirect chains longer than one hop, duplicate title tags, missing or duplicate meta descriptions, and pages with no internal links pointing to them (orphan pages).
Fix all 4xx and 5xx errors. A 404 on launch day isn't the end of the world, but a cluster of them is. Every important page should return a clean 200 status. Check all internal links and navigation items manually.
Audit page speed with Core Web Vitals in mind. Use PageSpeed Insights (free, powered by Lighthouse) on your homepage and 2-3 representative inner pages. Focus on LCP (Largest Contentful Paint), CLS (Cumulative Layout Shift), and INP (Interaction to Next Paint). Google has made these ranking factors — they're not optional anymore.
Confirm mobile-friendliness. Test with Google's Mobile-Friendly Test tool. Your viewport meta tag should be set correctly, fonts should be readable without zooming, and tap targets should be large enough. Google indexes mobile-first now, so a broken mobile experience is a broken SEO experience.
Check for orphan pages. Pages with no internal links can't be discovered by crawlers unless they're in the sitemap. Make sure every page on your site is linked from at least one other page — preferably one that's close to the homepage.
Validate your HTML. Severe HTML errors can interfere with how Google parses your page content. Use the W3C Markup Validator on key templates. You don't need perfection, but critical structural errors (unclosed tags around main content, broken <head> sections) should be fixed.

6. Structured Data — Speaking Google's Language

Implement schema markup relevant to your content type. A blog needs Article schema. A local business needs LocalBusiness. An e-commerce product page needs Product with Offer and AggregateRating. Don't add schema for its own sake — only implement types that match what's actually on the page.
Validate every schema implementation. Use Google's Rich Results Test (richresults.google.com) to paste your URL or code and check for errors. A single missing required property can prevent your rich snippet from ever appearing in search results.
Add Organization or WebSite schema to your homepage. At minimum, your homepage should have Organization schema with your name, URL, logo, and social profiles. WebSite schema with a SearchAction enables the sitelinks search box in Google results — worth having even if Google doesn't always show it.
Don't mark up content that isn't visible on the page. Google's guidelines explicitly prohibit structured data for content that users can't see. This includes hidden reviews, invisible product descriptions, or off-screen FAQs. If it's not on the page, it doesn't belong in your schema.
Check for JSON-LD syntax errors manually if needed. JSON-LD (the recommended format) breaks silently if you have a stray comma or unclosed bracket. Paste your structured data block into JSONLint.com before deploying.

Final Pre-Launch Checklist (Quick Reference)

robots.txt — no Disallow: / in production
No noindex meta tags lingering from staging
Google Search Console verified and sitemap submitted
HTTPS enforced with a valid SSL certificate
www/non-www redirect configured consistently
XML sitemap is clean, accurate, and referenced in robots.txt
Canonical tags present on every indexable page
Zero 404s on pages linked from navigation or sitemap
Core Web Vitals scores acceptable on mobile
Structured data validated with no critical errors

Technical SEO isn't glamorous. It doesn't get the same attention as a great piece of content or a strong backlink. But it's the foundation everything else stands on. A site that Google can't properly crawl, index, or understand will underperform no matter how good the content is.

Run through this checklist before launch — not after. Fix the invisible problems while you still can do it quietly, before real traffic (and real disappointment) enters the picture.