SEO9 min read

The Technical SEO Checklist Every Founder Should Run Before Launching a Website

Technical SEO is the work that makes a website findable, crawlable, and understandable to search engines — completely separate from the words on the page or the links pointing at it. It's the plumbing: sitemaps, robots.txt, HTTPS, canonical tags, structured data, page speed, indexing. Get it wrong on launch day and it doesn't matter how good your copy is or how many backlinks you eventually earn, because Google may never properly see the site in the first place.

This is the checklist we run before every launch, written so you can hand it directly to your developer without needing to know what any of it means first. Most of these items take minutes to fix and months to notice if you don't.

What technical SEO actually is, and what it isn't

People use "SEO" as one catch-all term, which causes most of the confusion. In reality there are three distinct disciplines, and technical SEO is the one that has to work before the other two matter at all.

Content SEO — the words themselves: what keywords you target, how the page answers a search intent, how it's structured for readers.
Off-page SEO / link building — the reputation signals other sites send to yours, mainly backlinks and mentions.
Technical SEO — whether a search engine can find your pages, crawl them, render them correctly, and index them at all.

Here's the part founders miss: you can write the best page on the internet about your product, and if a misconfigured robots.txt file tells Google not to crawl it, that page is invisible. Technical SEO doesn't make your content rank higher on its own — it's the precondition for ranking at all. Think of it as the difference between writing a great book and making sure it's actually on the shelf, spine facing out, in a store people walk into.

The launch-day disaster almost nobody checks for

The single most common technical SEO failure on new websites is also the easiest to prevent: a robots.txt file left over from staging that blocks the entire site from being crawled. Development environments are usually set to "noindex, nofollow" on purpose, so search engines don't index a half-built site full of placeholder text. Teams flip that setting when they go live — except when they forget, and the exact same block that protected the staging site quietly ships to production.

The result is a website that looks completely normal to every human visitor and is functionally invisible to Google. It can sit like that for weeks before anyone notices, because nothing about the site itself looks broken. The only symptom is silence: no organic traffic, no impressions in Search Console, no indexed pages. This single check — opening yoursite.com/robots.txt and confirming it isn't disallowing everything — takes ten seconds and prevents one of the most expensive mistakes a launch can make.

A website can be visually perfect and completely invisible to Google at the same time. Technical SEO is the difference between the two.

The pre-launch and post-launch checklist

Run through this with your developer before you announce the launch, and again a few days after it goes live. Each item is something you can verify yourself, even without a technical background.

01
Confirm robots.txt isn't blocking the whole site
Visit yoursite.com/robots.txt directly. It should not contain a blanket "Disallow: /" line unless you genuinely intend to keep the entire site out of search results. This single file has caused more launch-day SEO disasters than any other item on this list.
02
Generate and submit an XML sitemap
An XML sitemap is a file, usually at yoursite.com/sitemap.xml, listing every page you want indexed. Submit it directly inside Google Search Console so Google has an explicit map of your site rather than relying on it to discover pages by chance.
03
Verify ownership and monitor Google Search Console
Search Console is Google's free tool for seeing exactly how your site is being crawled and indexed, including any errors it hits along the way. Set it up before launch, not after — you want visibility from day one, not a blind spot during the first weeks that matter most.
04
Check that important pages are actually being indexed
Search site:yoursite.com in Google, or use the URL Inspection tool in Search Console, to confirm your key pages show up. A page can exist, load fine, and still not be in Google's index — indexing is a separate step from simply being online.
05
Set canonical tags to prevent duplicate content issues
A canonical tag tells search engines which version of a page is the "real" one when the same content is reachable through multiple URLs — with and without a trailing slash, with tracking parameters, on both http and https. Without it, search engines may split ranking signals across duplicates instead of consolidating them onto one page.
06
Confirm HTTPS is properly installed sitewide
Every page should load under https, with no mixed-content warnings and no lingering http version still reachable without a redirect. HTTPS has been a baseline ranking and trust signal for years, and browsers now actively flag http sites as not secure to visitors.
07
Test mobile-friendliness on a real phone
Google indexes and ranks primarily using the mobile version of your site, not desktop. Load every key page on an actual phone and check that text is readable, buttons are tappable, and nothing overflows the screen, rather than trusting a browser window resized on a laptop.
08
Check basic page speed on your key pages
Run your homepage and two or three other important pages through Google PageSpeed Insights. You're not chasing a perfect score on day one, but a page that takes many seconds to become usable will quietly cost you both rankings and visitors before you've had a chance to earn either.
09
Add schema.org structured data to relevant pages
Structured data is a standardized code format that tells search engines specifically what a page represents — a business, a product, an article, a review — which makes it eligible for enhanced results like star ratings, FAQ dropdowns, or business info panels in search.
10
Write unique title tags and meta descriptions for every page
Every page needs its own title tag and meta description — not a template repeated sitewide, and not left blank for Google to guess at. These are frequently the exact text shown in search results, so a missing or duplicated one is a missed opportunity on every single page it affects.
11
Add descriptive alt text to every meaningful image
Alt text describes an image in words so search engines — and screen readers, for visually impaired visitors — can understand what it shows. "Handmade leather boots on a wooden table" is useful; "IMG_4021.jpg" is not, and it's the default your images will keep if nobody replaces it.

Why URL structure and broken links matter more than founders expect

URLs are one of the few pieces of technical SEO a visitor actually reads, which makes them worth getting right from the start rather than restructuring later. A clean URL like yoursite.com/services/web-design tells both a person and a search engine exactly what the page is about at a glance. A URL like yoursite.com/page?id=4827&ref=nav tells neither of them anything, and it's far harder to change later without breaking every link that already points to it.

Broken internal links cause a quieter version of the same problem. Every link on your site that points to a page which no longer exists sends both visitors and search engine crawlers into a dead end. A properly configured 404 page — one that's styled, helpful, and offers a way back to the site — softens the visitor experience. But the real fix is finding and correcting the broken links themselves, because a crawler that keeps hitting dead ends on your site learns to trust it a little less each time, and a visitor who hits one gives up a lot faster than that.

How to verify all of this yourself, without a developer in the room

You don't need to take anyone's word for whether this checklist actually got done. A handful of free, official tools will show you directly.

Google Search Console — sitemap submission status, indexing coverage, mobile usability issues, and crawl errors, all in one dashboard.
Google's Rich Results Test — paste in a URL to see whether your structured data is valid and which rich result types it qualifies for.
Google PageSpeed Insights — a free speed and Core Web Vitals report for any single URL.
A simple browser check of yoursite.com/robots.txt and yoursite.com/sitemap.xml — both should load, and neither should look like it was left over from staging.

Technical SEO is a launch requirement, not a post-launch upsell

The pattern we see most often is a site that launches beautifully, gets shared around, gets a small spike of direct traffic — and then plateaus, because it was never properly set up to be found by search in the first place. By the time someone notices, three months of compounding search visibility are already gone, and there's no way to get them back. Retroactively fixing a robots.txt block or submitting a sitemap late doesn't undo that lost window; it just starts the clock from wherever you are now.

This is exactly why we treat technical SEO as part of the build itself at Serenity Labs, not a separate line item sold back to clients after launch. Every site we ship leaves with its sitemap submitted, its robots.txt verified, its canonical tags set, and its structured data in place — because a website that Google can't properly read isn't finished, no matter how good it looks.