Pre-Launch Website Checklist: Prevent Costly SEO Mistakes

Launching a new website involves more than publishing pages and checking whether the design looks right. A site can appear finished while still containing broken links, incorrect redirects, indexing problems, slow-loading pages, and technical errors that affect search visibility and user experience.

Finding these problems before launch is usually easier than fixing them after visitors, search engines, and other websites begin interacting with the site. A pre-launch website audit helps identify problems early, verify that essential features work as expected, and establish a reliable starting point for future improvements.

Whether you're launching a new business website, redesigning an existing site, or migrating to a different platform, this checklist covers the technical, on-page, performance, security, and usability checks to complete before going live.

1. Check Your Website's Crawlability and Indexability

Search engines need to discover and crawl your website's pages before they can consider them for indexing. A website that looks complete to visitors may still contain technical restrictions that prevent search engines from accessing important content.

Before launch, review your robots.txt file, indexing directives, XML sitemap, and internal links.

Review the robots.txt file

Confirm that your robots.txt file does not accidentally block important sections of the website. Development environments often use broad directives such as Disallow: / to prevent crawling before launch. Make sure any temporary restrictions are removed or adjusted before production.

Check indexing directives

Inspect page-level robots meta tags and X-Robots-Tag HTTP headers. Make sure important pages do not contain unintended noindex directives, and that canonical tags point to the intended URLs.

Validate your XML sitemap

Include the canonical URLs of pages that should be indexed. Remove staging URLs, redirected pages, broken URLs, and pages intentionally excluded from search results. Check that the sitemap is accessible and referenced correctly in robots.txt.

• Check robots.txt for accidental sitewide blocking.
• Remove unintended noindex directives from important pages.
• Verify canonical tags point to the correct URLs.
• Generate an XML sitemap containing indexable canonical URLs.
• Check that the sitemap returns a successful HTTP response.
• Confirm important pages are accessible to search engine crawlers.
• Remove staging and development URLs from production discovery.
• Verify that important pages can be reached through internal links.

For additional checks, see the XML Sitemap Errors: Common Problems and Fixes article and the guide to finding and fixing noindex issues.

2. Test URLs, HTTP Status Codes, and Redirects

One of the most common launch problems is publishing a website with URLs that return unexpected status codes. A page may return a 404 error, redirect to an outdated location, or load successfully while returning an incorrect HTTP status.

Crawl your website and review the status codes for all important URLs. Pay particular attention to pages that have been migrated from an existing site.

Redirects to test

• Redirect HTTP versions to HTTPS.
• Choose one preferred hostname, such as www.example.com or example.com, and redirect the alternative.
• Redirect old URLs to their appropriate new destinations during a redesign or migration.
• Avoid redirect chains and loops.
• Check that redirected URLs do not remain in internal navigation, XML sitemaps, or canonical tags.
• Confirm that important pages do not unexpectedly redirect to the homepage.

If the website already has broken internal links, use the broken link audit guide to identify and resolve them. You can also review how to find and fix broken internal links.

3. Review Every Page's On-Page SEO

A website can be technically accessible but still launch with missing titles, duplicate metadata, poorly structured headings, or incomplete content. These problems can make it harder for search engines and visitors to understand what each page offers.

Review the most important pages individually, then use a website crawler to identify patterns across the entire site.

• Write a unique, descriptive title tag for every important page.
• Add a relevant meta description to key pages.
• Use one clear primary H1 heading per page where appropriate.
• Organize content with logical H2 and H3 headings.
• Check for duplicate or missing title tags and meta descriptions.
• Use descriptive, readable URLs.
• Add descriptive alt text to meaningful images.
• Check that internal links use relevant anchor text.
• Ensure the page content matches its intended search topic.
• Verify canonical URLs and language or regional tags, if applicable.

Pay attention to page titles and descriptions

Page titles should clearly describe the page and distinguish it from other pages on the site. Meta descriptions should summarize the page accurately and provide a useful preview for potential visitors. Avoid filling either field with repetitive keywords.

For a new website, start with a spreadsheet that records each URL, its intended topic, title tag, meta description, H1, canonical URL, and indexing status. This gives the team a reference when checking pages before and after launch.

Related reading: Missing Title Tags: Causes and How to Fix Them, Duplicate Title Tags, and Missing Meta Descriptions.

4. Find and Fix Broken Internal Links

Broken internal links can lead visitors to missing pages and prevent search engines from following important paths through your website. These issues often appear when menus, buttons, or content links are copied from a development environment or when URLs change during a redesign.

Check links in:

• Main navigation and dropdown menus
• Footer menus and breadcrumbs
• Blog posts and other editorial content
• Product and service pages
• Calls to action and buttons
• Related-content sections
• Image links and downloadable resources

Do not only count broken URLs. Identify which pages link to them and whether those links are important to navigation or content discovery.

Example only: These are illustrative URLs and not actual crawl results.

If a destination no longer exists, determine whether a replacement page is available. Update the internal link directly rather than relying on a redirect for every visitor.

5. Check Website Speed and Core Web Vitals

A slow website can frustrate visitors, particularly on mobile devices or slower internet connections. Performance testing before launch can reveal oversized images, excessive scripts, render-blocking resources, and server response problems while there is still time to address them.

Review performance on representative pages, including the homepage, landing pages, blog articles, and any pages with interactive features.

Largest Contentful Paint (LCP)

LCP measures how quickly the largest visible content element appears. A good target is 2.5 seconds or less.

Interaction to Next Paint (INP)

INP measures how responsive the page is to user interactions. A good target is 200 milliseconds or less.

Cumulative Layout Shift (CLS)

CLS measures unexpected visual movement while a page loads. A good target is 0.1 or less.

These are Google's Core Web Vitals thresholds. Field data from real users is the best way to evaluate actual visitor experience, but a website that has not launched yet may not have enough field data. Use lab testing as an initial diagnostic, then monitor real-user performance after launch.

• Test key pages using PageSpeed Insights or Lighthouse.
• Test representative pages on mobile and desktop.
• Compress large images and use appropriate image formats.
• Set image dimensions to help prevent layout shifts.
• Review third-party scripts, tracking codes, and embedded widgets.
• Minimize unnecessary JavaScript and CSS.
• Check caching and compression settings.
• Confirm that fonts load efficiently and do not cause major layout shifts.
• Test pages over a typical mobile connection.
• Review server response times and hosting capacity.

6. Test Mobile Responsiveness and User Experience

A website that works well on a desktop monitor may be difficult to navigate on a phone. Test how the site behaves at different screen sizes, including small mobile devices and tablets.

Pay attention to more than whether the page fits on the screen. Visitors should be able to read content, tap buttons, navigate menus, and complete important tasks without unnecessary effort.

• Check that the layout adapts to different screen widths without horizontal scrolling.
• Confirm that navigation menus open and close correctly on touchscreens.
• Make buttons and links easy to tap without accidentally selecting nearby elements.
• Check font sizes, line spacing, and contrast on smaller screens.
• Ensure that forms can be completed using a mobile keyboard.
• Confirm that pop-ups, banners, and cookie notices do not obscure essential content.
• Verify that images, tables, and embedded media fit within the viewport.
• Test the full user journey, including sign-up, contact, checkout, or booking where applicable.

7. Test Forms, Buttons, and Other Interactive Features

A website launch can be disrupted by small functional issues that are easy to miss during visual reviews. A contact form may look correct but fail to send messages. A call-to-action button may point to an outdated page, or a registration flow may stop at the final step.

Test every interactive feature that visitors will rely on.

• Submit contact forms and verify that messages arrive.
• Test newsletter subscriptions and confirmation emails.
• Check registration, login, and password reset flows if applicable.
• Verify that buttons and calls to action lead to the correct destinations.
• Test search boxes and site navigation.
• Confirm that payment and checkout processes work, if applicable.
• Check file downloads and document links.
• Verify that error messages and validation work on forms.
• Test confirmation pages and automated email notifications.
• Check that interactive elements work on mobile and desktop.

For forms that collect personal information, also verify that submissions are handled securely, that the privacy notice is accessible, and that the correct team receives the information.

8. Verify HTTPS, Security, and Privacy Settings

Before launch, ensure that visitors can access the website securely and that sensitive information is protected. An active HTTPS certificate is essential, but it is only one part of a secure production setup.

• Confirm that the HTTPS certificate is valid and covers the required hostnames.
• Redirect HTTP requests to HTTPS.
• Check for mixed-content warnings caused by HTTP images, scripts, stylesheets, or other resources.
• Confirm that administrator accounts use strong authentication.
• Review access permissions for hosting, CMS, domain registrar, and analytics accounts.
• Remove unused test accounts, temporary credentials, and development tools.
• Check that production environment variables and API keys are not exposed in public code.
• Verify that backups are configured and that restoration procedures are documented.
• Review privacy policies, cookie notices, and consent requirements applicable to your site.
• Confirm that security-related headers and server configurations are appropriate for your application.

For websites that accept payments or handle sensitive personal information, involve the appropriate technical and compliance specialists before launch.

9. Set Up Analytics and Search Monitoring

A website launch is the beginning of measurement, not the end of development. Without reliable analytics and search monitoring, it can be difficult to determine whether visitors are reaching the right pages, whether important events are being recorded, or whether technical issues appear after launch.

• Install and test your chosen analytics platform.
• Verify that page views are recorded on important pages.
• Configure conversion events for relevant actions, such as form submissions, purchases, and sign-ups.
• Check that analytics does not record duplicate page views or events.
• Set up Google Search Console and verify ownership of the production domain.
• Submit the XML sitemap in Search Console.
• Confirm that important pages can be inspected using the URL Inspection tool.
• Configure uptime monitoring for critical pages and services.
• Make sure the team responsible for the site can access analytics and monitoring reports.

If the website is replacing an existing site, preserve access to historical analytics and search performance data. This helps distinguish launch-related changes from longer-term trends.

10. Prepare for Website Migration and URL Changes

If the launch involves a redesign, a new CMS, a domain change, or a different URL structure, migration checks deserve particular attention. Even a visually successful redesign can lose search visibility if important URLs are removed, redirects are incomplete, or content is unintentionally changed.

Start with a list of existing URLs and map them to their intended destinations on the new website.

Illustrative migration plan, not actual website URLs.

Migration checklist

1. Crawl the existing website and export its URLs.
2. Identify pages that receive organic traffic, backlinks, or important internal links.
3. Map old URLs to relevant new pages.
4. Configure permanent redirects for pages that have moved.
5. Preserve important content, metadata, and structured data where appropriate.
6. Update internal links to use the new URLs directly.
7. Check canonical tags, XML sitemaps, and robots directives on the new site.
8. Crawl the new production site and test the migration rules.
9. Monitor indexing, traffic, errors, and important conversions after launch.

Avoid redirecting every removed page to the homepage. Where a genuinely relevant replacement does not exist, a proper not-found or removal response may be more appropriate.

11. Validate Structured Data and Social Sharing

Structured data can help search engines interpret certain types of content and may make eligible pages qualify for enhanced search appearances. Social metadata helps control how pages appear when shared on supported platforms.

Neither guarantees a particular search appearance or social engagement, but incorrect markup can lead to confusing previews or missed opportunities.

• Validate relevant structured data using Google's Rich Results Test.
• Check that structured data reflects visible page content.
• Verify business details, product information, or article metadata where applicable.
• Remove outdated or duplicated structured data.
• Confirm that Open Graph titles, descriptions, and images are correct.
• Test social-sharing previews for important landing pages and articles.
• Ensure that social images load successfully and use appropriate dimensions.
• Confirm that page URLs in metadata use the correct production domain.

For example, a blog article should have accurate article information, while a product page should describe the actual product being offered. Avoid adding markup for information that is not present on the page.

12. Review Content, Images, and Legal Pages

Before publishing, check that all public-facing content is complete and appropriate for the production environment. Placeholder copy, missing images, incorrect contact information, and unfinished pages can undermine visitor confidence even when the technical setup is sound.

• Remove placeholder text, sample products, and demonstration content.
• Check spelling, grammar, factual accuracy, and consistency across pages.
• Verify business names, addresses, phone numbers, and contact details.
• Confirm that all important images load and display correctly.
• Replace low-quality, missing, or outdated graphics.
• Check that downloadable files are accessible and current.
• Verify copyright notices and appropriate image or content permissions.
• Publish the necessary privacy policy, terms of service, and other applicable legal notices.
• Review cookie consent and data collection disclosures where required.
• Confirm that all important pages have clear calls to action.

If a website has multiple contributors, assign a person to approve the final content rather than relying on an informal last-minute review.

13. Complete a Final Production Crawl

After the main fixes are completed, run another full crawl against the production website. A staging crawl can reveal problems before launch, but the production crawl checks the actual live environment and can catch issues introduced during deployment.

Use the final crawl to verify:

• Important URLs return the expected status codes.
• Internal links do not lead to broken or unintended destinations.
• Pages have appropriate title tags, meta descriptions, and headings.
• Canonical tags point to the intended production URLs.
• Indexable pages are not accidentally blocked.
• XML sitemap entries are valid and consistent with the site's canonical URLs.
• Images and other important resources are accessible.
• Redirects work correctly and do not form loops or unnecessary chains.
• Important pages can be reached through internal links.

Suggested issue priorities

Priority depends on the website's purpose, affected pages, and business impact. Address blockers first, then work through the remaining issues according to their potential impact.

14. Monitor the Website After Launch

A pre-launch audit reduces the risk of avoidable problems, but it cannot guarantee that a website will remain error-free. Live traffic, search engine crawling, third-party services, and production configurations can reveal issues that did not appear during testing.

Plan a post-launch review immediately after deployment and continue monitoring throughout the first few weeks.

Keep a record of the initial crawl, issue list, fixes, and post-launch results. This creates a baseline for subsequent audits and makes it easier to identify regressions when the website changes.

Complete Pre-Launch Website Audit Checklist

Use this summary to check that all major audit categories have been reviewed. Each category should be marked complete only after the relevant checks have been performed and necessary corrections verified.

• Crawlability and indexing verified.
• HTTP status codes and redirects tested.
• On-page SEO reviewed.
• Internal links checked.
• Website performance tested.
• Mobile responsiveness reviewed.
• Forms and interactive features tested.
• HTTPS, security, and privacy reviewed.
• Analytics and search monitoring configured.
• Migration and URL changes validated, if applicable.
• Structured data and social sharing checked.
• Content, images, and legal pages reviewed.
• Final production crawl completed.
• Post-launch monitoring schedule prepared.

Related Technical SEO Resources

Continue preparing your website for launch with these SiteAuditLint articles covering common technical SEO issues and ways to resolve them.

Final Thoughts

A successful website launch depends on more than design and content. Crawlability, indexability, redirects, performance, mobile usability, security, and functional testing all contribute to how reliably a website serves visitors and how well search engines can discover its pages.

The most effective approach is to audit early, document problems, fix them according to their impact, and run a final crawl against the actual production environment. After launch, continue monitoring the site and use the initial audit as a baseline for future technical improvements.

For a repeatable process, use a website crawler such as SiteAuditLint to identify technical issues across your pages, review the results, and compare subsequent crawls to track changes over time. A consistent audit routine helps catch problems before they become larger maintenance or search visibility issues.

Frequently Asked Questions