Website & Development
Technical SEO Checklist for a New Website (Before You Go Live)
Copy for AI
Handle technical SEO during the build, before a new website goes live.
The foundations you set now are the most expensive to change after launch.
The verdict: this technical SEO checklist comes down to four checks. Make the site indexable, lock in the URL structure, give every page clean headings and fill in the meta fields page by page.
Do that before launch and you start with a clean base instead of a list of repairs.
Here’s the checklist to tick off during the build:
This is deliberately a foundations checklist for a site under construction.
Want a deeper, developer-focused list on speed, redirects and structured data? Read our technical SEO checklist for developers.
To 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 the choices you make early.
Your URL structure, your navigation and your information architecture are hard to change later. Changing them turns into a small SEO site migration.
That means three jobs:
- Redirects: every old URL needs a new home
- Internal links: every link to an old URL needs updating
- Waiting: and hoping you don’t lose rankings
You avoid that whole problem by doing it right once, during the build.
The first impression counts
There’s 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 decides how smoothly they pick up the rest.
A site that goes live clean, fast and logically structured gets indexed faster and more completely. A site full of technical noise doesn’t.
What we steer on
At Customer Impact we build conversion-focused B2B sites.
We steer on one question: will search engines soon 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?
Remove the staging noindex, open robots.txt for production and submit a clean sitemap.
Indexability is the first hurdle. It’s also the mistake that most often goes unnoticed: a brand-new site that ends up entirely on noindex, because the staging setting travelled through to production.
Without indexing, even your best content ranks nowhere.
The indexability checklist
Tick this off before you go live:
- Remove the staging
noindex. Check this at page level and in your CMS settings. - Shield staging with a password, not with
robots.txtalone. Google says robots.txt isn’t a mechanism for keeping a page out of Google: a blocked URL can still be indexed if others link to it. - Set your production
robots.txtcorrectly. Leave the site fully crawlable, including the CSS and JavaScript files Google needs to render the page. - Set a
canonicaltag per page. It points to the definitive URL, so the same content doesn’t compete via several URLs. More in our guide to the canonical tag. - Generate an XML sitemap. Include only indexable, canonical URLs and submit it in Google Search Console as soon as the site is live.
What a clean production robots.txt looks like
A production robots.txt can be very short. Here’s ours:
Our own robots.txt, October 2026: one rule for all crawlers, plus the line that points to the sitemap.
No staging blocks, no leftover Disallow: /. That’s the state you want on launch day.
Disallow vs noindex
Pay close attention to the difference between Disallow in robots.txt (don’t crawl) and noindex (don’t index).
They look alike but do something different. The wrong choice keeps pages out of the search results by accident.
Watch out: don’t combine them on the same URL.
A noindex only works if Google can crawl the page. Google’s own docs say the page must not be blocked by robots.txt, or the crawler never sees the rule.
For non-HTML files such as PDFs, the X-Robots-Tag header does the same job as a meta noindex.
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, with every important page a few clicks from the homepage.
That structure decides how smoothly Google crawls your site and how easily visitors find their way. It’s the choice you least want to change afterwards, so take the time now.
The structure checklist
Concretely, during the build:
- Short, descriptive URL slugs. Base them on the topic, not on internal IDs or dates.
/services/website-development/says more than/page?id=42. - A logical hierarchy. Group pages in categories and subpages, so the URL reflects the place in the site.
- Three clicks at most. Keep important pages within three clicks of the homepage, with service and contact pages in the navigation.
- Internal links planned now. Every important page deserves at least one link from relevant content.
Google’s URL structure guidance backs this up. It recommends readable words over long ID numbers, and hyphens over underscores between words.
It also warns that complex URLs with many parameters can cause problems for crawlers.
Avoid orphan pages
A page without internal links stays almost invisible to Google.
Those are orphan pages, and new sites create them easily when a page is published but never linked.
Lock it in early
Your navigation is more than a menu. It’s where crawlability and ease of use come together.
Read more in website navigation and in the SEO side of your site architecture.
Best moment: your wireframes, before any code is written.
How do you organise your headings and content hierarchy?
With one <h1> per page for the main topic, then a logical build-up in <h2> and <h3>.
Headings aren’t there to make text bigger. They tell search engines, and increasingly AI search systems, how your content is put together.
The heading checklist
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 looks. - Headings that answer the reader’s question instead of vague labels.
- Semantic HTML elements (
<nav>,<main>,<article>) instead of a sea of<div>s.
For example, an <h2> that reads “What does onboarding cost?” tells Google more than one that reads “Pricing”.
Who owns the headings?
The content of headings is content work. The tags themselves are dev work.
On a new build, those two easily get mixed up.
Agree on it explicitly: 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 Open Graph fields for social sharing.
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.
Google’s title link guidance names it directly. It advises against “repeated or boilerplate text in <title> elements”.
The meta checklist
Per page, arrange four things:
- A unique, descriptive
title. Put the topic first. Google sets no character limit, but it truncates long titles to fit the screen. Our wiki on the title tag covers the details. - A
meta description. It summarises the page and invites a click. Google sometimes rewrites it, but a good one raises your chance of a tidy display. See our guide to the meta description. - Meaningful
alttext on images. It helps accessibility and image SEO. - Open Graph and social fields. A shared link then shows a correct title and image instead of a bare URL.
Want to see how a title and description look in Google before launch? The SERP snippet preview shows it.
Keep the fields reachable
Set up your CMS so the editorial team can fill in these fields per page without a developer.
Otherwise, after launch, titles quickly go empty or duplicate.
What else do you set up technically before traffic has to come to the site?
The baseline conditions: speed, mobile, security and accurate structured data.
These don’t 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 between slow and fast, not between fast and perfect.
Here’s what field data looks like for a live site, in this case ours:
PageSpeed Insights field data for customerimpact.be on mobile, October 2026. LCP passes at 1.9 s; CLS at 0.13 still needs work.
A brand-new site has no field data yet. Until it does, test the lab score with our website speed test.
Mobile
Google uses the mobile version of your content for indexing and ranking.
So check that all content, metadata and structured data are present on mobile too, not only on desktop. More in our guide to mobile-first indexing.
Security
Deliver the whole site over HTTPS with a valid certificate.
Make sure no mixed-content warnings remain.
Structured data
Only add schema markup that honestly describes the content, such as Organization or BreadcrumbList.
Don’t invent markup for content that isn’t there. Check the result in a validator before launch:
The Schema Markup Validator on our own English homepage, October 2026. Each detected type should match what the page visibly says.
Accessibility
An accessible site is often also more crawlable.
Avoid the well-known accessibility mistakes already in your templates.
Migrating from an old site?
Then a layer is added: redirects from old to new URLs, so the authority you’ve built up doesn’t fall away.
How to tackle that is in website migration without ranking loss and in our 301 redirect plan. Check each redirect with the redirect checker.
After launch: watch the crawl
In the first weeks, Search Console’s Crawl Stats show how Google meets the new site:
Crawl Stats in our own Search Console for customerimpact.be, October 2026. The breakdown by response shows requests that hit a 301 or a 404.
A spike in 404s right after launch usually means a missed redirect or a broken internal link.
The short summary
Technical SEO for a new website comes down to four foundations you lock in during the build:
- Indexability: no staging
noindex, a clean robots.txt and sitemap. - Structure: a logical URL and navigation structure.
- Headings: a clean heading hierarchy on every page.
- Meta fields: unique titles and descriptions, page by page.
The baseline conditions, speed, mobile, HTTPS and honest structured data, finish it off.
Work through this checklist before you go live. You start with a clean base instead of a list of expensive repairs.
Keep steering on the pages that bring clients and revenue, not on vanity numbers. For the launch day itself, our website launch checklist covers the non-SEO tasks.
Building on Webflow? Also work through our Webflow SEO checklist for the platform-specific settings.
Want us to build your new site on a technically correct base made for leads? Look at our website development service, or discuss your project with us.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.