Technical SEO Checklist for a New Website (Before You Go Live)

A new website is the ideal moment to get technical SEO right straight away, because the foundations you set during the build are the most expensive to change after launch. The short answer: make sure your site can be indexed, lock in a logical URL and navigation structure, give every page a clean heading hierarchy and fill in your meta fields page by page. Do that before you go live and you start with a clean base instead of a list of repairs. In this article you work through the SEO checklist you tick off during the build.

This is deliberately a foundations checklist for a site under construction. If you want a deeper, developer-focused list covering speed optimisation, redirects and structured data in detail, read our technical SEO checklist for developers. If you want to periodically review the health of an existing site later, a technical website audit goes broader than SEO alone. This page is part of the wider guide to building a B2B website.

Why do you handle technical SEO during the build and not afterwards?

Because the most expensive mistakes are exactly the choices you make early: your URL structure, your navigation and your information architecture. Changing those afterwards means setting up redirects, revising internal links and hoping you do not lose rankings. You avoid that whole problem by doing it right once during the build.

There is also a question of sequence. A new site has no authority yet, no backlinks and no history with Google. The first impression search engines get of your site determines how smoothly they pick up the rest. A site that goes live clean, fast and logically structured is indexed faster and more completely than a site full of technical noise.

At Customer Impact we build conversion-focused B2B sites, and we steer on the question that matters: will search engines soon be able to find the pages that bring you enquiries and revenue? Not on vanity numbers like the count of indexed pages. That focus starts during the build, not at the first report three months later.

How do you make sure your new site can even be indexed at all?

Indexability is the first hurdle, and also the mistake that most often goes unnoticed: a brand-new site that ends up entirely on noindex by accident because the staging setting travelled through to production. Without indexing, even your best content ranks nowhere.

Tick this off before you go live:

• Remove the noindex setting you had on the staging environment during the build. Check this at page level and in your CMS settings.
• Set your robots.txt correctly: block your staging environment, but leave the production site fully crawlable, including the CSS and JavaScript files Google needs to render the page.
• Set a canonical tag per page that points to the definitive URL, so the same content does not compete via multiple URLs.
• Generate an XML sitemap with only indexable, canonical URLs and submit it through Google Search Console as soon as the site is live.

Pay close attention to the difference between Disallow in robots.txt (do not crawl) and noindex (do not index). They look alike but do something different, and the wrong choice keeps pages out of the search results unintentionally. Test every rule before you set it live.

Which URL and site structure do you lock in before you go live?

A logical, shallow structure in which every important page is reachable in a few clicks, because that structure determines how smoothly Google crawls your site and how easily visitors find their way. This is the choice you least want to change afterwards, so take the time for it now.

Concretely, during the build:

• Choose short, descriptive URL slugs based on the topic of the page, not on internal IDs or dates. /services/website-development/ says more than /page?id=42.
• Group your pages in a logical hierarchy of categories and subpages, so the URL reflects the place in the site.
• Keep important pages within three clicks of the homepage and make sure your service and contact pages are reachable from the navigation.
• Decide now how you place your internal links: every important page deserves at least one link from relevant content, otherwise it stays almost invisible to Google.

In all of this, your navigation is more than a menu, it is where crawlability and ease of use come together. You can read more about it in website navigation and in the SEO side of your site architecture. Preferably lock in these choices as early as your wireframes, before a single line of code is written.

How do you organise your headings and content hierarchy?

With one <h1> per page for the main topic, followed by a logical build-up in <h2> and <h3>. Headings are not meant to make text bigger, they tell search engines (and increasingly AI search systems) how your content is put together.

Keep it simple and consistent:

• One <h1> per page that names the topic, not several.
• A clean <h2>/<h3> hierarchy that follows the logic of the page, without skipping levels for the sake of appearance.
• Headings that answer the reader’s question instead of vague labels, so both people and search engines grasp the structure.
• Semantic HTML elements (<nav>, <main>, <article>) instead of a sea of <div>s, so your structure is readable in the code as well.

The content of those headings is content work, the tags themselves are dev work. On a new build project those two easily get mixed up. So agree explicitly on who guards the heading structure in the template and who delivers the copy, otherwise it falls between two stools.

Which meta fields do you fill in per page before launch?

A unique title and meta description per page, plus the Open Graph fields for how your links look on social media. One template for the whole site is a common mistake on new websites: dozens of pages then share the same title and compete with each other.

Per page you arrange:

• A unique, descriptive title that puts the topic of the page up front and stays within the usual length so it is not truncated in the search results.
• A meta description that summarises the page and invites a click. Google sometimes rewrites it, but a good description increases your chance of a tidy display.
• Meaningful alt text on images, for both accessibility and image SEO.
• Open Graph and social fields, so a shared link shows a correct title and image instead of a bare URL.

Set up your CMS so the editorial team can fill in these fields per page without a developer. A site where no one can reach the meta fields quickly slips, after launch, into empty or duplicate titles.

What else do you set up technically before traffic has to come to the site?

The baseline conditions that finish the foundations: speed, mobile, security and honest structured data. These do not have to be perfect on day one, but they must be in order before you really pull in traffic.

• Speed: compress images in modern formats, limit render-blocking scripts and measure with Core Web Vitals instead of by feel. The biggest gain is in the difference between slow and fast, not between fast and perfect.
• Mobile: Google assesses your site based on the mobile version, so check that all content, metadata and structured data are present on mobile too, not only on desktop.
• Security: deliver the whole site over HTTPS with a valid certificate and make sure no mixed-content warnings remain.
• Structured data: only add schema markup that honestly describes the content, such as Organization or BreadcrumbList. Do not invent markup for content that is not there.
• Accessibility: an accessible site is often also more crawlable. Avoid the well-known accessibility mistakes already in your templates.

Are you migrating from an existing site to a new one? Then a layer is added: redirects from old to new URLs, so the authority you have built up does not fall away. How to tackle that without ranking loss, you can read in website migration without ranking loss.

The short summary

Technical SEO for a new website comes down to four foundations you lock in during the build: make sure the site can be indexed (no staging noindex, a clean robots.txt and sitemap), lock in a logical URL and navigation structure, give every page a clean heading hierarchy and fill in your meta fields page by page. The baseline conditions, speed, mobile, HTTPS and honest structured data, finish it off. Work through this checklist before you go live and you start with a clean base instead of a list of expensive repairs. And keep steering on the pages that bring clients and revenue, not on vanity numbers.

Are you building specifically on Webflow? Then additionally work through our Webflow SEO checklist for the platform-specific settings. Do you want us to build your new site straight away on a technically correct base that is made for leads? Take a look at our website development service or discuss your project with us.

Book your free intake