A Practical Technical SEO Checklist for a New Website

A new website can look finished and still be difficult for search engines to crawl, understand or index. A launch review should therefore begin with technical access and URL consistency before anyone starts polishing keyword density or chasing a score.

This checklist is designed for a practical pre-launch or post-launch review. It does not assume that every page should be indexed, and it does not treat an XML sitemap as a substitute for crawlable navigation.

1. Confirm what should be public and indexable

List the pages that are meant to appear in search and the areas that should remain private. Remove staging-wide blocks from the production site only after launch, and protect genuinely private content with authentication rather than relying on robots.txt as an access-control system.

• Check the final page returns the expected HTTP status.
• Review any noindex directives on pages intended for search.
• Confirm robots rules do not accidentally block resources needed to render important pages.
• Keep account, admin and confidential areas behind proper access controls.

2. Choose one canonical URL for each page

Decide which URL represents each piece of content, then make internal links, canonical hints and redirects support that choice. Google documents canonicalization as a way to signal the representative URL among duplicates or near-duplicates; it is not a guarantee that a specific URL will always be selected. See Google Search Central’s canonicalization guidance.

Review these consistency points

• HTTPS versus HTTP.
• Preferred hostname format.
• Trailing-slash conventions.
• Uppercase versus lowercase paths where the server treats them differently.
• Tracking parameters and duplicate filter URLs.

Redirect retired URLs directly to the closest relevant replacement. Test the response rather than assuming the redirect rule works, and avoid unnecessary redirect chains.

3. Make important pages discoverable through links

An XML sitemap can help discovery, but important pages should also be reachable through useful navigation and contextual links. Google recommends crawlable links with an <a> element and a resolvable href. Its current guidance is available in crawlable link best practices.

Review main navigation, breadcrumbs, category hubs and contextual links. If you want a structured way to map relevant source pages to a target, EseoGen’s Internal Link Mapper can rank user-supplied page topics by lexical overlap. Treat that as a prioritization aid, not as proof that a link should be added.

4. Check titles, descriptions and visible headings

Every important page should explain its purpose quickly. Review the WordPress title, visible main heading and supporting headings for consistency. A meta description can help present the page clearly in search, but search engines may choose a different snippet for a specific query.

EseoGen’s SERP Preview Tool is useful for visual editing, but its preview is intentionally simplified and does not query live rankings. Use it to spot awkward wording, not to predict exactly how Google will display a result.

5. Validate structured data against visible facts

If the site uses JSON-LD, verify that the type matches the page and that properties reflect information a visitor can actually verify. Do not invent ratings, prices, authors, addresses or availability merely because a schema generator offers those fields.

Also inspect the final rendered source so that theme or plugin output does not duplicate or contradict your markup.

6. Review mobile usability and real performance data

A desktop-only check can miss layout shifts, oversized controls and interaction problems. Test representative pages on smaller screens, with real navigation and forms.

For performance, distinguish measured values from a promise of ranking improvement. EseoGen’s Core Web Vitals Input Assessment classifies user-entered LCP, INP and CLS values against stored thresholds and reminds you to confirm current official guidance. It does not run a live performance test.

7. Run a final launch pass

• Open a sample of key URLs in a fresh browser session.
• Test redirects and canonical destinations.
• Follow navigation and contextual links.
• Check the XML sitemap contains the intended canonical URLs.
• Review titles, snippets, structured data and mobile rendering.
• Record issues with an owner and a retest date.

For related browser-based checks and planning utilities, browse the EseoGen SEO and marketing tools library. The useful mindset is to verify observable conditions first, then use tools to organize the review—not to replace judgment with a single score.