Technical SEO Checklist for a New Website

A wooden block that says seo on it

A new website can look finished and still be invisible to search engines because of one overlooked setting. This checklist covers the technical points to verify before and just after launch. It is written for a small site and can be completed in an hour or two. For the concepts behind it, read Technical SEO Basics: Crawling, Indexing and Ranking Explained.

How to use this checklist

Work through it once on the staging site before launch and again on the live site in the first week. Mark each item as done, not applicable, or needs action, and assign an owner to anything open.

1. Access for search engines

  • The option that discourages search engines from indexing the site is switched off on the live site.
  • robots.txt does not contain Disallow: / and does not block CSS, JavaScript or image folders. See How to Create a Robots.txt File Without Blocking Important Pages.
  • No important page carries a noindex tag by mistake.
  • Coming-soon or maintenance mode is off.
  • Staging and test copies are password-protected or set to noindex, so they do not compete with the live site.

2. One address for every page

  • The site loads over HTTPS with a valid certificate.
  • http redirects to https with a single 301 redirect.
  • Either www or non-www is chosen, and the other redirects to it.
  • Addresses with and without a trailing slash resolve to one version.
  • Each page has a canonical tag pointing to its own preferred address.
  • No mixed-content warnings appear in the browser.

3. Structure and addresses

  • URLs are short, readable and lowercase, with words separated by hyphens.
  • The permalink structure is final before launch.
  • Every important page can be reached within a few clicks from the homepage.
  • The main navigation uses ordinary links that work without JavaScript.
  • No page is an orphan; each has at least one internal link pointing to it.
  • Breadcrumbs are present where the site has several levels.

4. Sitemap

  • An XML sitemap exists and loads without error.
  • It lists only indexable pages that return 200.
  • It is referenced in robots.txt.
  • It has been submitted in Google Search Console and Bing Webmaster Tools. See How to Create and Submit an XML Sitemap.

5. Page-level basics

  • Every page has a unique title tag that describes its content.
  • Every page has a unique meta description.
  • Each page has exactly one H1, and headings follow a logical order.
  • Meaningful images have alt text.
  • Each page has substantial content of its own. Empty or placeholder pages are removed or set to noindex.
  • The language of the page is declared in the HTML.

6. Status codes and redirects

  • Working pages return 200.
  • Missing pages return 404, and the 404 page is helpful.
  • If the site replaces an older one, every old address redirects with a 301 to its closest new equivalent. See How to Set Up 301 Redirects When URLs Change.
  • There are no redirect chains or loops.
  • A crawl of the site finds no broken internal links.

7. Mobile and performance

  • Pages are readable and usable on a phone without zooming.
  • Content and links present on desktop are also present on mobile.
  • Images are compressed and sized appropriately.
  • Page caching is active.
  • Key pages have been tested in PageSpeed Insights and the main issues addressed. See Website Performance Basics.
  • No intrusive pop-up covers the content on arrival.

8. Structured data

  • Organization or local business markup is present on the homepage or contact page, where relevant.
  • Articles, products and breadcrumbs use the appropriate markup, usually through the SEO plugin or shop system.
  • The markup passes Google’s Rich Results Test without errors.
  • Structured data describes only what is visible on the page.

9. International and multilingual sites

  • Each language version has its own URL.
  • hreflang annotations link the language versions to each other, and each version references itself.
  • Visitors are not redirected automatically by location in a way that prevents search engines from reaching all versions.

10. Measurement

In the first weeks after launch

  • Inspect the homepage and a few key pages with the URL inspection tool.
  • Check the Page indexing report weekly for unexpected exclusions.
  • Watch for not-found errors and add redirects where needed.
  • Confirm the sitemap status remains Success.
  • Review Core Web Vitals once field data is available.

The five checks that prevent most disasters

If you have only ten minutes, check these:

  1. The discourage search engines option is off.
  2. robots.txt does not block the site.
  3. The homepage has no noindex tag.
  4. All versions of the address redirect to one HTTPS address.
  5. The sitemap is submitted and readable.

Next step

Technical health makes content findable. To plan the content itself, continue with SEO for a New Website: A Practical Beginner’s Checklist.