Technical SEO for a new website: the launch checklist
The technical work that must be complete before a website launches if it is to be found: indexing, metadata, structured data, performance, redirects and measurement.
Why the technical foundation comes first
Search visibility is often discussed in terms of content and links, and both matter. Neither is effective on a website that search engines cannot crawl, index and understand. The technical foundation is the work that makes everything subsequent possible, and it is far easier to establish at launch than to retrofit once a site is live and indexed incorrectly. The following checklist covers the items that should be complete before a new website is made public.
Crawling and indexing
Confirm that the site is not blocked from indexing: the robots file should allow the pages that should be found and exclude only those that should not, such as administrative or duplicate pages. Confirm that no page carries a noindex directive by accident, a common leftover from staging. Generate a sitemap listing every indexable page with its last-modified date, reference it from the robots file, and submit it in Search Console once the site is live.
Addresses and canonicals
Each page should be reachable at one address only. Choose between www and non-www, and between trailing slash and none, and redirect the alternatives permanently. Every page should declare a canonical address pointing to itself, so that any duplicate, such as a page reached with tracking parameters, is attributed to the original. Where the site serves more than one language or region, declare the relationship between versions with language annotations.
Redirects from a previous website
When a new website replaces an existing one, its search standing must be carried across. List every address on the old site that receives traffic or carries links, map each to its closest equivalent on the new site, and implement permanent redirects before launch. Content that performed on the old site should be retained or improved rather than removed. Monitor Search Console for missed addresses in the weeks after launch.
Metadata
Every page requires a unique title and description. The title should state the page's subject and the organisation, in that order, within the length shown in search results. The description should summarise the page for a person deciding whether to click, not restate the title. Metadata should be written for the search results page, where it competes for attention, rather than filled in as an afterthought.
Heading structure
Each page should have a single main heading stating its subject, followed by subheadings that address the questions a visitor would ask, in a hierarchy that reflects the structure of the content. Headings should be real headings in the markup, not styled paragraphs, so that search engines and assistive technology can read the structure. Images that carry meaning should have descriptive alternative text.
Structured data
Structured data describes the organisation and its content in a format search engines can use for rich results. At minimum, a business website should describe the organisation, its services, its navigation through breadcrumbs, and, where applicable, its articles, products and frequently asked questions. The markup should be validated before launch and must reflect what is actually on the page; markup that describes content the page does not contain is treated as spam.
Performance
Search engines assess page experience through Core Web Vitals: loading speed, interactivity and visual stability. Before launch, serve images at the size the screen requests in modern formats, limit and preload fonts, restrict scripts to those each page requires, and ensure the layout does not shift as content loads. Test on a mid-range mobile device over a throttled connection, which is where most visitors will be.
Security and accessibility
The site should be served over HTTPS with a monitored certificate, and every insecure address should redirect to its secure equivalent. Accessibility fundamentals, sufficient colour contrast, keyboard operability, descriptive labels and support for reduced motion, are both a legal consideration in many jurisdictions and a signal of quality to search engines.
Measurement
Verify the site in Search Console and connect Analytics before launch, so that data is collected from the first day. Define the events that matter to the business, such as form submissions or bookings, and exclude internal traffic. Without measurement, the effect of any subsequent work cannot be assessed.
Common launch mistakes
The failures we encounter most often on newly launched websites are straightforward: a noindex directive carried over from the staging environment, so that the site is invisible for weeks; redirects from the previous site omitted, so that established search standing is lost; duplicate addresses left unresolved, so that pages compete with themselves; metadata copied from a template, so that every page carries the same title; and measurement connected after launch, so that the first weeks of data are missing. Each item on the checklist above exists because of a failure of this kind.
After launch
The foundation must be maintained as the site changes. Pages are added and removed, templates are updated, components are replaced, and each change can affect visibility. Ongoing technical monitoring, whether under a maintenance plan or a continuing SEO programme, identifies these effects within the month rather than through declining traffic later. Our SEO setup covers every item on this checklist; Ongoing SEO continues the work as a monthly programme.
Using the checklist
The checklist is most effective when worked through in the week before launch, with each item verified on the live domain rather than on a staging environment, since several items, including redirects, canonicals and Search Console verification, can only be confirmed in production. A short written record of the checks, kept with the project documentation, makes the next audit considerably faster.