Publishing a new corporate website without technical SEO verification is like opening a store before checking that visitors can find the entrance. If search crawlers and answer systems cannot reliably fetch, parse, or understand priority pages, those pages may be harder to discover or index.
Use this operational checklist across pre-launch QA and launch day to verify that your digital platform is accessible, indexable, and ready for search discovery.
Quick answer: what should be checked before a website launch?
A new-website launch should expose crawlable, indexable HTML for every priority page; return the intended status codes; use one canonical URL per page; publish accurate titles, descriptions, headings, image alternatives, and structured data; include only canonical 200 URLs in the sitemap; and keep analytics and conversion tracking testable. Validate both before launch and immediately after DNS or hosting changes.
Choose the right technical SEO checklist
| Project stage | Best-fit guide | Focus |
|---|---|---|
| New website | This launch checklist | Crawlability, indexability, robots.txt, canonicals, sitemap, metadata, mobile checks, and analytics handoff |
| Existing-site redesign or migration | Technical redesign SEO QA | Legacy URL inventory, redirect mapping, staging controls, canonical preservation, and cutover testing |
| Redesign planning and content decisions | Website redesign SEO checklist | Content preservation, URL decisions, navigation, and visibility measurement |
For platform-specific implementation, see WordPress & Webflow development.
Example: a practical pre-launch QA pass
For a small marketing site, export the final route list, crawl the production candidate, and record each URL's status, canonical, robots directive, title, H1, structured-data types, and internal-link discoverability. Then test one representative page on mobile and desktop, submit only canonical 200 URLs in the sitemap, and repeat the same checks after DNS or hosting cutover. This example is a validation sequence—not a promise that every launch will index immediately.
For implementation support, see Search Engine & AI Visibility Services or contact Autonexa AI.
A simple pass/fail sheet makes handoff clearer: record the URL, expected status, final status, canonical target, indexability directive, title, H1, structured-data types, mobile/desktop result, and one discovered internal link. Assign an owner to every failure and rerun the sheet after DNS or hosting changes. This keeps launch QA evidence separate from later ranking or indexing outcomes.
Phase 1: Crawlability and Indexing Architecture
For a deeper implementation guide, see Autonexa AI’s SEO, AEO and GEO service and the website redesign SEO checklist.
- Robots.txt Directives: Verify that
/robots.txtallows indexing on public routes (Allow: /) and correctly references your production sitemap address. Ensure modern AI bots (such asOAI-SearchBotandGPTBot) are explicitly configured. - XML Sitemap Verification: Confirm that your
/sitemap.xmlcontains only canonical, indexable URLs with HTTP 200 statuses. Exclude administrative routes, staging domains, and redirect targets. - Meta Robots & HTTP Headers: Audit production templates to ensure accidental
noindexornofollowdirectives carried over from staging environments are completely removed. - Absolute Canonical Tags: Verify every public page possesses a self-referencing canonical link tag (
<link rel="canonical" href="https://autonexaai.tech/..." />) to prevent query-string duplicate content penalties.
Phase 2: On-Page Semantic Hierarchy & Metadata
- Single H1 Rule: Ensure each page contains exactly one primary
<h1>tag that reflects its core topic, followed by logically nested<h2>and<h3>tags. - Title Tags & Meta Descriptions: Craft unique, descriptive title tags (50–60 characters) and actionable meta descriptions (140–160 characters) for every key landing page and blog post.
- Open Graph & Twitter Cards: Test that social sharing cards display accurate images, titles, and descriptions using tools like LinkedIn Post Inspector and Twitter Card Validator.
- Descriptive Image Alt Text: Ensure all informative imagery includes contextual alt text for screen readers and image search algorithms. Purely decorative elements should include empty alt attributes (
alt="").
Phase 3: JavaScript Rendering & Mobile Usability
Modern web frameworks (React, Next.js, Vite) provide fluid user interactions, but requires careful attention to client-side rendering:
[Browser Request] ──> [HTML Delivered] ──> [DOM Rendered] ──> [Content Crawlable]
- Rendered DOM Inspection: Use Google's URL Inspection Tool to confirm that primary headings, body copy, and navigation links appear in the rendered HTML output.
- Mobile-First Responsive Layout: Verify that touch targets are at least 48x48px, fonts scale comfortably without horizontal scrolling, and interactive dropdowns function flawlessly on mobile Safari and Chrome.
- Clean URL Architecture: Enforce lowercase, hyphenated slugs with consistent trailing slash policies. Avoid session IDs or tracking parameters in canonical internal links.
Phase 4: Telemetry, Verification, and Post-Launch Checks
- Google Search Console Verification: Verify domain ownership via DNS TXT records or HTML meta verification tags.
- Analytics & Conversion Telemetry: Verify Google Analytics 4 (
gtag.js) triggers accurately across page views, form submissions, and high-intent button clicks. - Sitemap Submission: Manually submit your sitemap inside Search Console to accelerate crawl discovery.
- 404 Handling: Test that non-existent paths return a clean, user-friendly 404 page with clear navigational links back to primary services.
Build a crawlable, measurable website launch
Autonexa AI helps teams review crawlability, metadata, structured data, responsive delivery, and analytics as part of a launch-readiness engagement. Search visibility and AI citations depend on external systems and are not guaranteed.
Schedule a Launch Readiness Audit → or discover our Search Engine & AI Visibility Services.