The Complete SEO Audit Checklist for New Website Launches

Launching a new website without an SEO audit is like opening a store without checking whether the doors are unlocked. Everything might look ready from the inside, but if search engines can't find your pages — or if they find the wrong version of them — you'll start your site's life with an invisible handicap that takes months to undo.

The first few weeks after launch are when Google forms its initial impression of your site. Crawl errors, missing directives, and broken pages discovered during that window can delay indexing and suppress rankings for far longer than the issues themselves persist. Getting SEO right at launch is dramatically easier than fixing it afterward.

This checklist covers everything you need to verify before, during, and after launch.

Pre-Launch Checklist

These items must be verified before your site goes live. Fixing them after launch means search engines may have already crawled and cached the broken versions.

Robots.txt Configuration

Verify robots.txt is accessible at yourdomain.com/robots.txt
Remove any Disallow: / directives left over from staging — this is the single most common launch mistake, and it blocks all search engine crawling
Allow access to CSS, JavaScript, and image files — search engines need to render your pages fully to evaluate them
Block only what should be blocked — admin panels, internal search results, duplicate filtered views, and staging subdomains
Reference your XML sitemap — include a Sitemap: directive pointing to your sitemap URL

XML Sitemap

Generate a complete XML sitemap including all indexable pages
Exclude pages you don't want indexed — login pages, thank-you pages, internal utility pages
Validate the sitemap format — ensure it follows the sitemap protocol with correct <loc>, <lastmod>, and <changefreq> tags
Keep the sitemap under 50,000 URLs per file (use a sitemap index for larger sites)
Verify every URL in the sitemap returns a 200 status code — no 404s, no redirects, no 500 errors

Canonical Tags

Every indexable page should have a self-referencing canonical tag — <link rel="canonical" href="https://yourdomain.com/page-url" />
Use absolute URLs in canonical tags, never relative
Check for conflicting canonicals — the canonical URL should match the actual URL of the page (protocol, www/non-www, trailing slash all consistent)
Handle pagination correctly — paginated pages should either self-canonicalize or point to a view-all page, depending on your strategy

URL Structure and Redirects

Use clean, descriptive URLs — /services/web-design not /page?id=47&cat=3
Choose one URL format and enforce it — decide on www vs non-www, trailing slash vs no trailing slash, and redirect all variants to the canonical version
Set up 301 redirects from any old URLs if you're replacing an existing site — every inbound link and bookmark to the old site should reach the correct new page
Avoid redirect chains — every redirect should point directly to the final destination, never through intermediate URLs
Test all redirects — verify that they return 301 (permanent), not 302 (temporary)

SSL and Security

Install a valid SSL certificate and verify it covers all subdomains you use
Force HTTPS — all HTTP URLs should 301 redirect to their HTTPS equivalents
Check for mixed content — every resource on every page (images, scripts, stylesheets, fonts) must load over HTTPS
Verify the certificate chain is complete — incomplete chains cause warnings in some browsers and may affect crawling

On-Page SEO Elements

Every page has a unique title tag between 50 and 60 characters, containing the target keyword
Every page has a unique meta description between 120 and 160 characters
Every page has exactly one H1 tag that clearly describes the page content
Heading hierarchy is logical — H2s under H1, H3s under H2, no skipped levels
Images have descriptive alt text — not keyword-stuffed, but genuinely descriptive of the image content
Internal links use descriptive anchor text — "Learn about our web design process" not "click here"

Technical Foundation

Mobile responsiveness — test every page template on multiple device sizes; Google uses mobile-first indexing
Page speed — run each page template through a speed test; target Core Web Vitals thresholds (LCP under 2.5s, CLS under 0.1, INP under 200ms)
Structured data — implement relevant JSON-LD schema (Organization, LocalBusiness, Product, Article, FAQ) and validate with Google's Rich Results Test
Open Graph and Twitter Card tags — ensure social sharing displays correct titles, descriptions, and images
Custom 404 page — create a branded 404 page that helps users navigate back to useful content
Favicon and touch icons — small detail, but missing favicons look unprofessional in browser tabs and bookmarks

Launch Day Checklist

These checks should happen within hours of your site going live.

Index Verification

Remove any staging noindex tags — search your page source for <meta name="robots" content="noindex"> on every template; this is easy to miss if your CMS has a "discourage search engines" setting
Submit your sitemap to Google Search Console — go to Sitemaps in Search Console and add your sitemap URL
Submit your sitemap to Bing Webmaster Tools — Bing has a separate index and its own crawler
Request indexing for your most important pages — use the URL Inspection tool in Search Console to request indexing for your homepage and top landing pages
Verify DNS is resolving correctly — confirm that your domain points to the right server and that both www and non-www versions work as expected

Search Console Setup

Verify site ownership in Google Search Console using DNS verification (most reliable method)
Set your preferred domain — if you use the www version, make sure Search Console knows
Check the Coverage report — look for any pages already showing errors or exclusions
Submit any disavow file if you're relaunching a domain with a history of spammy backlinks
Enable email notifications for critical issues

Analytics Configuration

Verify Google Analytics tracking code is firing on every page — check real-time reports to confirm data is flowing
Set up goal tracking for key conversions — form submissions, purchases, sign-ups
Configure Google Tag Manager if you use it, and verify all tags are firing correctly
Set up event tracking for important interactions — downloads, video plays, outbound link clicks
Exclude internal traffic — filter out your own team's IP addresses so they don't skew data

Cross-Browser and Device Testing

Test in Chrome, Firefox, Safari, and Edge — rendering issues in any major browser affect real users
Test on iOS and Android devices — mobile rendering bugs are common and directly impact Google's evaluation
Verify forms work on all devices — submit every form from multiple browsers and confirm the data arrives
Check that JavaScript-dependent content renders — if your site relies on client-side rendering, verify that Googlebot can see the content (use Search Console's URL Inspection tool to check rendered HTML)

Post-Launch Checklist

The first 30 days after launch are critical. This is when you establish baselines and catch issues that only appear under real traffic.

First Week: Monitor and Fix

Check Search Console daily for crawl errors, indexing issues, and manual actions
Monitor server logs for unusual crawl patterns — is Googlebot hitting the right pages? Is it getting blocked anywhere?
Watch for 404 spikes — real users and search engines will find broken links that testing missed
Verify page speed under real load — staging environments often perform differently from production under actual traffic
Check that all redirects are working — especially if you migrated from an old site, verify that old URLs are landing on the correct new pages

First Month: Run Your First Full Audit

Once your site has been live for two to four weeks, run a comprehensive SEO audit. This is essential because:

Real-world crawling reveals issues testing didn't — search engines interact with your site differently than your QA team does
You establish a baseline — your first audit creates a benchmark against which all future audits will be compared
Early issues are cheapest to fix — catching a canonicalization problem in week three is far easier than unraveling it after six months of Google indexing the wrong URLs

AI SEO Scanner runs 255+ checks covering search indexability, Core Web Vitals, on-page SEO, structured data, and more. It gives you a complete picture of your site's health within minutes of your first crawl.

First Month: Content and Keyword Plan

Identify your initial keyword targets — use Search Console's Performance report to see which queries your site is already appearing for
Plan your first content updates — based on early ranking data, identify pages that are close to page one and could benefit from content improvements
Set up rank tracking for your primary keywords — this gives you a trend line to measure progress against
Review competitor rankings — see where competitors rank for your target terms and identify content gaps you can fill
Create a publishing calendar — new sites need consistent fresh content to build topical authority; plan at least one new piece per week for the first three months

Ongoing: Establish a Regular Audit Cadence

Run automated audits monthly at minimum — new content, plugin updates, and platform changes introduce issues continuously
Review Core Web Vitals quarterly — performance can degrade as you add features, scripts, and content
Re-audit after every major change — new sections, redesigns, CMS updates, and hosting migrations all warrant a fresh audit
Track historical trends — AI SEO Scanner stores audit history so you can see whether your site's SEO health is improving or declining over time

Common Launch Mistakes That Kill Rankings

Even experienced teams make these errors:

Forgetting to remove staging noindex tags — This single mistake can keep your entire site out of Google for weeks. Always search your rendered HTML for noindex directives after launch.

Launching without redirects from the old site — If you're replacing an existing site, every old URL needs a 301 redirect to its equivalent on the new site. Without this, you lose all the link equity and ranking authority the old pages accumulated.

Using placeholder content — Thin pages with "lorem ipsum" or "coming soon" content get indexed and evaluated by Google. If they rank poorly, that early signal can follow the URL even after you add real content.

Skipping mobile testing — Google indexes the mobile version of your site, not the desktop version. A site that looks great on desktop but breaks on mobile is functionally broken for SEO purposes.

Not setting up Search Console before launch — Search Console takes time to accumulate data. If you don't set it up until a month after launch, you've lost a month of crawl and indexing data that could have helped you diagnose early issues.

A new website launch is a fresh start. Every decision you make in the first few weeks shapes how search engines perceive your site for months to come. Use this checklist to make sure that first impression is a strong one.

Run your launch audit with AI SEO Scanner — catch every issue across 255+ checks before they become entrenched problems. Start for free, no credit card required.