EnlightenIt — Free on-page SEO readiness checker and guides for webmasters.

On-Page SEO Checklist for New Websites | EnlightenIT

A new website can look finished while remaining difficult for search engines to understand. Launch pressure tends to focus attention on design, forms and final copy, leaving SEO checks until after pages are already live. A better approach is to make on-page SEO part of the release process, so each important URL launches with a clear purpose, crawlable content and a sensible place within the wider site.

Give every indexable page a distinct purpose

List the pages intended to appear in search and state what each one is meant to satisfy. Service pages, product categories, location pages and guides should not exist merely because a website template provided a slot for them.

Check for overlap before launch. If two pages would answer the same searcher's need with substantially the same information, combine or differentiate them now. Preventing duplication is easier than untangling it after search engines have discovered both versions.

Write unique titles and main headings

Each important page needs an HTML title that describes its subject accurately. The visible H1 should also make the primary purpose clear, although it does not need to repeat the title word for word.

Avoid templates that produce identical or near-identical titles across large sections. Add location, service or category terms only where they genuinely describe the destination. Readability matters because titles also help people choose search results.

Prepare useful meta descriptions

Write concise descriptions for priority pages that explain what visitors will find. Search engines may choose different snippet text, but a well-written meta description still gives them an appropriate candidate and improves publishing quality.

Do not use the field as a keyword list. Make the wording specific to the page and consistent with the promise made by the title and visible content.

Check URLs, canonicals and indexability

Use concise, stable URLs where practical and confirm that the preferred versions are internally linked. Review canonical tags so they point to the intended URLs and remove development noindex directives before launch.

Check robots configuration carefully. Blocking the wrong path can prevent important content from being crawled, while leaving staging or duplicate areas exposed can create unnecessary URLs for search systems to process.

Build internal links into the architecture

Important pages should not depend on an XML sitemap for discovery. Connect them through navigation and contextual links that reflect how subjects and customer journeys relate.

Use descriptive anchor text and make sure new articles or supporting resources link towards relevant core pages. At launch, crawl the site to identify orphaned pages and broken internal links before they become established problems.

Optimise images and page performance

Resize and compress images appropriately rather than uploading unnecessarily large source files. Provide dimensions where useful to reduce layout movement and use lazy loading selectively for resources that are not needed immediately.

Review scripts, fonts and third-party widgets across representative templates. Performance problems often come from components repeated on every page, so fixing one template can improve much of the new website at once.

Make mobile usability part of sign-off

Test real journeys on small screens: navigation, reading, forms, checkout or enquiry actions. Check that text remains legible, controls are easy to use and overlays do not obstruct essential content.

Mobile testing should include pages with unusual content such as tables, long headings and embedded media. A homepage that behaves correctly does not prove that every template is ready.

Prepare measurement and post-launch checks

Configure the appropriate analytics and Google Search Console access so the team can observe what happens after launch. Submit or make available an accurate XML sitemap and inspect priority URLs once the live site is accessible.

Then crawl the production website rather than assuming the release matches staging. Check status codes, redirects, metadata, canonicals and internal links. A new website's SEO foundation is strongest when launch is treated as the beginning of monitoring rather than the end of the project. Clear page purpose, sound technical signals and disciplined publishing make future optimisation much easier.

Frequently Asked Questions

What is the first on-page task for a new site?

Give every page a unique, descriptive title tag and a single clear H1. These two basics have an outsized effect and are quick to get right.

Do I need a sitemap for a small new site?

Yes. A sitemap helps Google discover your pages quickly, which matters most when a site is new and has few inbound links.

What is the most common new-site mistake?

Leaving a site-wide noindex tag on after moving from staging to live, which keeps the whole site out of search until it is removed.