Pre-Launch SEO Checklist For A Website Rebuild

A website rebuild can look ready before it is ready for search. The design is approved. The CMS works. The homepage feels polished. The forms submit. Everyone wants the launch date to hold.

That is exactly when the SEO checklist matters most.

Pre-launch SEO is not a box-ticking exercise for the end of a project. It is the quality control layer that protects visibility, content value, measurement, and lead flow before DNS changes or deployment pressure make every issue louder.

The checklist below is built for serious marketing sites where organic search, paid campaigns, referrals, and conversion paths all matter. It is not meant to slow the launch. It is meant to prevent avoidable damage.

Crawl Staging Before Launch

Start with a full crawl of the staging site while there is still time to fix structural problems. Do not wait until the live domain is switched over.

The staging crawl should answer basic questions:

• Are important pages reachable through links?
• Are there accidental 404s or 500s?
• Are staging URLs exposed in links, canonicals, metadata, or sitemaps?
• Are pages returning the expected status codes?
• Are important templates rendering unique titles, descriptions, headings, and canonical URLs?
• Are noindex rules correct for staging and ready to change for production?
• Are internal links pointing to final production paths?

This is also the moment to compare the new crawl against the old site inventory. Which valuable pages are missing? Which old URLs now have new destinations? Which pages were intentionally removed? Which new pages should be indexed?

Google's site move guidance recommends preparing the new site and testing thoroughly before moving URLs. The practical value is simple: a crawl turns a visual approval into a technical review.

For a website modernization, this crawl often reveals useful project decisions. Maybe the new information architecture is cleaner, but a high-performing resource disappeared. Maybe the new design is stronger, but article templates lost structured metadata. Those are fixable before launch and expensive after launch.

Verify Metadata And Indexation Signals

A rebuild often changes templates. Template changes can quietly change search signals across hundreds of pages.

Review the pages and templates that matter most:

• Homepage
• Service pages
• Articles and insights
• Case studies
• Location pages
• Product or solution pages
• Landing pages
• Resource downloads
• Legal and trust pages

Check title tags, meta descriptions, heading structure, canonical URLs, robots meta tags, Open Graph metadata, schema, breadcrumb output, and sitemap inclusion. The old site may not have been perfect, but the team should know what changed and why.

Pay special attention to canonical tags. Staging domains, preview URLs, duplicate slugs, trailing slash differences, and CMS preview routes can all create confusing canonical output. A page that looks correct in the browser may still tell search engines the wrong preferred URL.

Also review noindex behavior. Staging should usually be protected from indexing. Production pages that should rank should not inherit staging noindex tags. This sounds basic, but it is a common launch risk because noindex rules are often added early and forgotten.

Structured data deserves a template-level check. If the old site used a plugin to output article schema, organization schema, breadcrumbs, or FAQ markup, the new build needs an intentional replacement or a documented reason to remove it.

Protect Redirects And Internal Links

Redirect planning should be complete before launch day. Last-minute redirect maps tend to miss valuable edge cases.

For every important old URL, decide whether to:

1. Keep the same URL.
2. Redirect to an equivalent page.
3. Merge into a stronger related page.
4. Create a new destination.
5. Return a true 404 or 410.

Then test the implementation. A spreadsheet does not protect SEO until the server, host, framework, CDN, or CMS actually returns the correct response.

Check for:

• 301 or 308 status codes for permanent moves
• No redirect chains
• No redirect loops
• Correct handling of trailing slashes
• Correct handling of uppercase paths if relevant
• Query parameter behavior for campaign URLs
• Redirects for PDFs and other linked assets
• Old subdomain or protocol variants when applicable

Internal links need their own review. The new site should link directly to canonical URLs, not to old URLs that rely on redirects. Redirects protect external and historical traffic. They should not become a permanent substitute for clean internal linking.

Test Performance, Forms, And Tracking Together

Launch SEO is not only crawlability. Search visibility is connected to page experience, conversion paths, and measurement.

Performance checks should include real templates, not just the homepage. Test pages with large images, forms, embedded media, long content, third-party scripts, and interactive sections. Google's Largest Contentful Paint guidance is a useful reminder that lab scores are not the whole story. Real user experience and field data matter after launch.

Before launch, check:

• Largest visible content loads quickly on key templates
• Images have stable dimensions and useful alt text
• Layout does not shift as fonts, images, or embeds load
• Navigation is usable on mobile
• Consent tools do not block critical content
• Third-party scripts are intentional and documented
• Forms submit successfully
• Form validation is clear
• CRM records receive source, campaign, and page context
• Analytics events fire once, not twice
• Conversion goals match leadership reporting expectations

A rebuild is a common time to lose tracking because the old site collected events through plugins, tag manager snippets, embedded forms, and theme code. The new site may be cleaner, but it must still preserve the metrics the business uses.

Prepare Search Console And Launch-Day Monitoring

Before launch, confirm that the team has access to the tools needed for diagnosis.

At minimum, prepare:

• Google Search Console properties
• XML sitemap location
• Analytics real-time reporting
• Tag manager access if used
• Form and CRM admin access
• Hosting logs or error monitoring
• Redirect rule ownership
• A rollback plan for critical launch issues

Define what blocks launch. A missing meta description should not stop a launch. Production pages inheriting noindex tags should. A low-priority broken image can be scheduled. Broken lead forms cannot.

Also define who is watching what. Search Console data can lag. Analytics can show immediate traffic and conversion behavior. Logs can reveal 404s and redirect mistakes quickly. Forms and CRM systems can confirm whether leads are still flowing.

This ownership keeps launch day from becoming a room full of people refreshing different dashboards without a shared standard.

A Practical Pre-Launch Checklist

Use this final checklist when the site is close to launch:

• Crawl the old site and staging site.
• Confirm all high-value URLs are preserved, redirected, merged, or intentionally retired.
• Test redirects for top organic, paid, referral, and backlink URLs.
• Verify title tags, meta descriptions, headings, canonicals, schema, and index rules.
• Confirm production pages are not blocked by robots.txt or noindex tags.
• Generate and review the XML sitemap.
• Remove staging URLs from internal links, metadata, canonicals, and sitemaps.
• Test key templates on mobile and desktop.
• Run performance checks on representative pages.
• Submit forms and verify CRM attribution.
• Confirm analytics and conversion events.
• Review paid campaign landing URLs.
• Prepare Search Console, sitemap submission, monitoring, and rollback steps.

The best rebuild launches feel calm because the hard questions were answered before the switch. A good modernization partner treats SEO launch readiness as part of the build, not a final favor at the end.

The checklist does not need to be complex. It needs to be real, owned, and finished before the new site starts carrying the business.