Technical SEO Pre-Launch Checklist for a Website
A technical SEO pre-launch checklist for crawlability, indexing, URLs, metadata, schema, speed, tracking, and redirects.
A website launch is often remembered as the moment the domain changes or the publish button is opened, but the greatest risks sit in less visible details: staging still has noindex, the sitemap contains test URLs, internal links point to the old hostname, canonicals are wrong, forms do not record submissions, or redirects lose important pages. A technical SEO checklist helps verify the conditions that allow search engines and users to access, understand, and use the website.
Technical SEO does not replace useful content or business strategy. It creates the foundation for those parts to be discovered and presented correctly. Google’s technical SEO getting-started guidance covers crawling, indexing, URLs, sitemaps, redirects, and Search Console; none of these sections guarantees rankings automatically.
1. Lock down the environment and primary domain
List staging, preview, and production environments. Staging may need to block indexing, but before publication check that noindex, basic authentication, robots, and headers are no longer blocking the wrong things. Define the primary domain, www or non-www, HTTPS, locale, and trailing slash; every alternate version needs a redirect or canonical according to the decision. Check absolute URLs in the sitemap, Open Graph, hreflang when applicable, and email.
Open the website in a private window, on a phone, and on another network to confirm that users do not need internal permissions. Record the DNS switch date, owner, and error-reporting channel. Do not treat a local build as evidence that production is working correctly.
2. Check crawlability and indexability
Crawl a representative URL list: homepage, menu, services, catalogs, products, articles, contact, policies, the 404 page, and old URLs. Confirm a 200 status for real pages, 404 for pages that do not exist, 301 for permanently changed URLs, and no redirect loops. Google recommends crawlable links and access to the resources required by crawlers.
Review robots.txt: do not block CSS, JavaScript, images, or folders containing important pages; URLs that change state, such as cart, login, or internal search, need their own strategy. The sitemap should list only URLs you want indexed, use the primary domain, and contain no redirects, noindex pages, errors, or duplicates. A sitemap supports discovery; it is not an order forcing Google to index every URL.
3. Keep URLs and redirects stable
URLs should be readable, descriptive, and stable. Google’s URL structure guidance recommends avoiding fragments that change the content and requires URLs to follow standards. During a migration, create a table of old URL, new URL, change type, owner, and test status. Redirect directly in one step to an equivalent page; do not send every old URL to the homepage when the content is not equivalent.
Check canonicals for parameter URLs, product variants, paginated pages, and language versions. A canonical is a signal; it does not turn a page with the wrong content into the right page. If several URLs return the same content, choose the primary URL and update internal links, the sitemap, schema, and social sharing.
4. On-page elements and structured data
Every indexable page needs a unique title, a clear H1, a relevant meta description, headings in reading order, an opening paragraph that explains the topic, and internal links. Make sure titles are not taken from placeholders, old dates, incorrect product names, or another language. Forms and CTAs need copy, error states, and a testable thank-you page.
Add schema only when the data is visible on the page and the type matches the content. A product page may use Product; Organization, breadcrumbs, or article markup should be assessed in context. Google’s ecommerce data guidance notes that structured data helps search engines understand information, while an enhancement appearing depends on conditions and systems. Check that price, currency, inventory, reviews, return policies, and variants do not differ between the interface and markup.
5. Mobile, performance, and accessibility
Check the menu, typography, touch targets, forms, modals, information tables, and sticky CTAs on small screens. Do not hide primary content just because of a mobile layout. Labels, focus, tab order, contrast, alt text, and error messages need versions that work with a keyboard and screen reader.
Measure LCP, INP, and CLS on important templates, and look for causes instead of recording scores alone. Correctly sized images, sensible fonts and scripts, reserved media space, and limited widgets reduce risk. See Core Web Vitals and website image optimization to separate the workstreams. The Shopify performance guide notes that themes, apps, images, video, and third-party code all need review.
6. Links, tracking, and conversion flows
Crawl internal links and find 404s, links to staging, incorrect anchor text, orphan pages, or mobile pages missing paths. The internal linking guide helps organize the map before review. Confirm that menus, breadcrumbs, related-product links, CTAs, and policy links all lead to the right destinations.
Check analytics, Search Console, consent when applicable, and events for forms, calls, add-to-cart, checkout, purchases, and errors. Do not send sensitive data in URLs or events. Use test data, confirm the production environment, and disable test tags before publication. An event being recorded does not mean the business process handled it correctly; reconcile it with the email, CRM, inventory system, or recipient within the actual scope.
7. Launch-day verification sequence
- Capture the staging state and save the old URL list.
- Unlock production, the domain, and HTTPS after an owner is assigned.
- Check robots, noindex, canonicals, and the sitemap on the real domain.
- Test representative URLs, 404s, redirects, menus, forms, and checkout.
- Check titles, H1s, metadata, images, schema, and language content.
- Open the site on mobile, desktop, common browsers, and a slow network.
- Verify tracking, consent, confirmation emails, and error states.
- Submit or update the sitemap in Search Console when appropriate.
- Monitor logs, crawl errors, indexing, forms, and orders during the early period.
- Record changes and approvers so the cause can be traced.
After launch, do not change large groups of URLs, titles, and templates at the same time without a hypothesis. Check value-generating pages first, read data alongside user feedback, and fix errors with a clear impact. The Google crawling FAQ reminds us that a sitemap does not guarantee indexing or ranking; set expectations around observation, not promised dates.
The technical SEO pre-launch checklist can be included in the basic SEO for a new website process, the Website page, and the Marketing service. If the website sells products, add the ecommerce service to review the catalog, checkout, and policies as well.