All articles

Technical SEO checklist for a new website

Check the public URLs, crawl rules, internal links, and search signals that determine whether visitors can find the pages you launch.

A technical SEO checklist for a new website starts with public pages, crawlable links, and canonical URLs. Check what each page actually serves and keep a record of the result.

Start with a short list of URLs

Write down the homepage, the main pages that explain your offer, and the pages someone needs before taking action. Add the preferred HTTPS URL for each. If you have several pages that answer the same question, decide which one you want readers to land on before you review the redirects and sitemap.

Open the list in a private browser window. Check that each expected public URL loads without a login or a preview cookie. Review a few URLs that should have moved, too. A retired URL with a clear equivalent should redirect to that equivalent. Redirecting every old page to the homepage can make it harder for visitors to find what they were looking for.

Check discovery and indexing separately

Give important pages a path from the homepage or a relevant section of the site. Use ordinary links with descriptive anchor text. A landing page that exists in a sitemap but has no internal path is easy for an editor to forget the next time a section changes.

Check robots.txt, the page’s robots meta tag, and the response headers. A crawler needs to be able to fetch a page to see its noindex directive. A robots disallow rule blocks crawling and cannot reliably keep a known URL out of results. Review whether a preview environment left an indexing directive on the public version.

Make the canonical signals agree

Compare the preferred URL in your launch list with the URL returned by redirects, the page’s canonical link, and the sitemap entry. For example, if you want https://example.com/pricing/ to be the primary address, link to it internally and list that same address in the sitemap. Avoid pairing a canonical pointing to one URL with a sitemap entry pointing to a duplicate. Google treats these as signals and can select a different canonical. Google’s canonical URL guidance

Check what a reader gets

Read the page title, first heading, and opening paragraph together. They should describe the same page in terms a reader can recognize. On a product page, explain what the product does before adding claims or comparisons. On a guide, answer the main question early and use headings to organize the rest.

These basics also apply to Google’s AI features in Search. A page that is easy to crawl and useful to a reader is a better starting point than special markup added for the sake of visibility. Google’s guidance on AI features and websites

Keep a launch record

For each URL, record the HTTP status, canonical address, indexing directive, and one internal link that leads to it. Note the date and any exceptions. Repeat the check after deploying a redirect, changing a template, or switching hosting. Once enough Search Console data accumulates, use it to measure what readers found in search. How to read Search Console performance

Keep reading