Pre-Launch Website SEO Audit: The Checklist You Need Before Going Live

# Pre-Launch Website SEO Audit: The Checklist You Need Before Going Live

You've spent weeks building your new website. The design looks great. The copy feels right. You're ready to go live.

Here's what most small business owners miss: the first few weeks after launch are when Google forms its initial impression of your site. If your technical SEO foundation has gaps — missing meta tags, broken links, slow pages, no structured data — you're starting with a handicap that can take months to overcome.

A pre-launch SEO audit catches these problems when they're cheapest to fix: before anyone sees them. It's the difference between a site that starts ranking within weeks and one that sits invisible on page five for months while you figure out what went wrong.

This guide walks you through what to check, why it matters, and how to do it without needing a developer on speed dial.

Why Pre-Launch SEO Matters

Google starts crawling and indexing your pages almost immediately after launch. According to Google's documentation on creating helpful content, search engines evaluate your site's overall quality signals from the start. If your site launches with duplicate title tags, missing descriptions, and no structured data, those are the signals Google records first.

Fixing SEO issues post-launch is possible, but slower — you're asking Google to re-evaluate something it already assessed. Google's crawl budget for new sites is limited, and every crawl spent discovering problems is a crawl not spent indexing your best content. A clean launch gives you a head start that compounds over time.

Here's what's at stake:

• Indexing delays. Pages with technical errors may not get indexed for weeks. For a new small business, that's weeks without appearing in local search results — weeks where potential customers find your competitors instead.
• Poor search snippets. Missing or duplicate meta descriptions mean Google writes its own snippet — often pulling random text from your page that doesn't convey what your business actually does.
• Lost local traffic. Without structured data, you won't appear in rich results for your area. When someone searches "bakery near me," the businesses with star ratings, hours, and addresses displayed directly in search results get the clicks.
• Speed penalties. Google's Core Web Vitals are a ranking factor. A slow site from day one starts behind faster competitors and has to work harder to catch up.
• Wasted ad spend. If you're planning to run Google Ads alongside your launch, sending paid traffic to a site with broken links, missing pages, or slow load times means you're paying for visitors who immediately leave.

The Pre-Launch SEO Audit Checklist

Work through these five sections in order — each one builds on the previous.

1. Crawlability and Indexing

Before worrying about keywords, make sure Google can actually find your pages. This is the foundation everything else depends on — a perfectly optimized page that Google can't crawl might as well not exist.

Check your robots.txt file. During development, many builders add Disallow: / to block all crawling. If that's still there at launch, Google won't index anything. This is one of the most common and most devastating pre-launch mistakes, and it's completely invisible unless you check for it.

• Visit yoursite.com/robots.txt in a browser
• Confirm it does NOT contain Disallow: /
• Verify your sitemap URL is listed: Sitemap: https://yoursite.com/sitemap.xml
• Check that you're not accidentally blocking CSS or JavaScript files — Google needs to render your pages to evaluate them

Verify your XML sitemap. Your sitemap tells Google which pages matter. Most CMS platforms generate one automatically, but they often include pages you don't want indexed — thank-you pages, internal search results, tag archives, or old drafts.

• Open your sitemap URL directly in a browser
• Confirm every listed URL returns a 200 status (not a 404 or redirect)
• Remove staging, test, or placeholder pages
• Verify the sitemap doesn't include URLs with query parameters that create duplicate content
• Make sure the sitemap is under 50MB and contains fewer than 50,000 URLs (Google's limits)

Check for noindex tags. Some page builders add during development. One leftover noindex tag on your homepage keeps it out of Google entirely. This can be especially tricky because the page looks perfectly normal in a browser — you'd never notice the tag without viewing the source.

• View page source on every key page (homepage, services, about, contact)
• Search for "noindex" — remove it before launch
• Also check HTTP response headers for X-Robots-Tag: noindex — some hosting platforms add this at the server level during staging

Set up Google Search Console. Before launch, verify your domain in Google Search Console. This lets you submit your sitemap directly, monitor indexing status, and receive alerts about crawl errors. You want this ready on day one, not scrambling to set it up after you notice your site isn't appearing in search results.

2. Meta Tags and On-Page Elements

This is where most pre-launch sites have the most issues — and where fixes have the most immediate impact on how your site appears in search results.

Title tags. Every page needs a unique, descriptive title tag under 60 characters. The title tag is the clickable blue link in search results, and it's one of the strongest on-page ranking signals Google uses.

Common problems:

• Every page has the same title ("Home | My Business")
• Titles are auto-generated placeholders ("Page 1", "Untitled")
• Titles are too long and get truncated in search results
• Titles stuff multiple keywords unnaturally ("Best Bakery Cakes Pastries Cookies Austin Texas")

Good title tag for a local bakery's services page:

> Custom Wedding Cakes & Pastries | Sunrise Bakery, Austin TX

Bad:

> Services

A strong title tag formula for small business pages: [Specific Service or Topic] | [Business Name], [Location]. This tells both Google and searchers exactly what the page is about and where the business is located.

Meta descriptions. These don't directly affect rankings, but they control what people see in search results. A compelling description increases click-through rate, which does affect rankings over time. Think of meta descriptions as free advertising copy — you get 120 to 155 characters to convince someone to click your result instead of the nine others on the page.

• Write a unique description for every page (120–155 characters)
• Include your primary keyword naturally
• Give a reason to click: what will the visitor get?
• Include a soft call to action ("See our menu," "Get a free quote," "Book today")

Canonical tags. Every page should have a tag pointing to its own URL. This prevents duplicate content issues when the same page is accessible through multiple URLs — for example, with and without trailing slashes, or with tracking parameters. If your site is accessible at both www.example.com and example.com, canonical tags tell Google which version to index.

Heading structure. Each page should have exactly one H1 tag. Use H2s and H3s to organize sections logically. Don't skip levels (going from H1 to H4). Screen readers and search engines both use heading hierarchy to understand page structure. A page with five H1 tags tells Google nothing about what the page is primarily about.

Image alt text. Every meaningful image needs descriptive alt text for image search visibility and accessibility. Use alt="" for purely decorative images. Alt text should describe the image content specifically — "custom three-tier wedding cake with white fondant and pink roses" is far more useful than "cake" or "image1."

Per-page mini-checklist:

• [ ] Unique title tag under 60 characters
• [ ] Unique meta description, 120–155 characters
• [ ] Canonical tag pointing to the correct URL
• [ ] One H1 tag per page
• [ ] Logical heading hierarchy (H1 → H2 → H3)
• [ ] Alt text on all content images
• [ ] No placeholder or "lorem ipsum" text remaining
• [ ] Open Graph tags for social sharing (og:title, og:description, og:image)

3. Performance and Core Web Vitals

Google uses three Core Web Vitals as ranking signals. These metrics measure real user experience, and they matter more than ever for ranking — especially on mobile, where most local searches happen.

Largest Contentful Paint (LCP): How fast your main content loads. Target: under 2.5 seconds. The most common cause of poor LCP on new sites is oversized hero images — a 4MB uncompressed PNG will destroy your load time. A single unoptimized image can be the difference between a 1.5-second and a 6-second page load.

Before launch:

• Compress all images (use WebP format when possible — it's typically 25–35% smaller than JPEG at equivalent quality)
• Set explicit width and height attributes on images to reserve layout space
• Use lazy loading for below-the-fold images with loading="lazy"
• Serve responsive images with srcset so mobile users don't download desktop-sized files
• Consider a CDN for static assets if your hosting doesn't include one

Cumulative Layout Shift (CLS): Whether your page jumps around while loading. Target: under 0.1. This happens when images load without reserved space, web fonts cause text to reflow, or ads and embeds inject themselves into the page after the initial render. Few things frustrate users more than trying to click a button that suddenly moves because a banner loaded above it.

Before launch:

• Always include width and height on tags
• Preload your web fonts with
• Use font-display: swap to show text immediately while fonts load
• Avoid injecting content above existing content after page load
• Set explicit dimensions on ad slots and embedded iframes

Interaction to Next Paint (INP): How quickly your page responds to clicks and taps. Target: under 200ms. Heavy JavaScript — especially third-party widgets — is usually the culprit. Every chat widget, analytics script, social media embed, and tracking pixel adds JavaScript that competes for the browser's attention.

Before launch:

• Defer non-essential JavaScript with defer or async attributes
• Audit third-party scripts (chat widgets, analytics, social embeds) — do you really need all of them at launch?
• Test on a real mobile device, not just your fast laptop — a mid-range Android phone shows you what most users actually experience
• Use the browser Performance tab to identify long tasks that block interactivity

Quick performance test process: Run Google's PageSpeed Insights on your staging URL. It tests both mobile and desktop and gives you specific, prioritized recommendations. Aim for a score above 90 on both. If you're below 50 on mobile, you have critical issues to fix before launch.

4. Structured Data

Structured data (schema markup) tells Google what your content is about in a machine-readable format. It powers rich results — enhanced search listings with star ratings, business hours, FAQ dropdowns, and more. Rich results take up more visual space in search results and get significantly higher click-through rates than standard blue links.

For most small business sites, you need at minimum:

LocalBusiness schema. This gives Google your business name, address, phone number, hours, and type. Without it, Google has to guess from your page text — and it doesn't always get it right. LocalBusiness schema is especially important for appearing in the Google Maps pack (the three local results that appear with a map for location-based searches).

{

"@context": "https://schema.org",

"@type": "LocalBusiness",

"name": "Sunrise Bakery",

"address": {

"@type": "PostalAddress",

"streetAddress": "1234 Main St",

"addressLocality": "Austin",

"addressRegion": "TX",

"postalCode": "78701"

},

"telephone": "+1-512-555-0199",

"openingHours": "Mo-Sa 07:00-18:00",

"url": "https://sunrisebakery.com",

"image": "https://sunrisebakery.com/images/storefront.jpg",

"priceRange": "$$"

}

Place this in a