The Founder's Pre-Launch SEO Checklist: 20 Things to Do Before Going Live

Every founder shipping a website for the first time has a mental image of launch day: the site goes live, traffic starts arriving, and momentum builds from there. What actually happens for the majority of new sites is silence. The site is live, but Google hasn't discovered it, or has discovered it but hasn't indexed it, or has indexed it but placed it so far back in the results that no organic visitor ever finds it. Weeks pass. Nothing improves.

The gap between those two outcomes isn't luck. It's a set of pre-launch decisions that either give the site a fair chance of being discovered or quietly hobble it before the first real visitor arrives. Most of these decisions are boring, most of them take minutes rather than hours, and skipping them almost always shows up as flat organic performance for six months longer than it needed to.

This post is the checklist. Twenty specific items to close before you flip the switch on a new site, ordered by leverage. If you're two weeks from launch, this is what to work through.

Domain and hosting fundamentals

1. Confirm HTTPS is enforced on the primary domain. The site should serve exclusively over HTTPS, with HTTP requests 301-redirecting to HTTPS. Mixed content warnings, missing certificates, or optional HTTPS are all launch-day disqualifiers. Google downweights sites that lack proper TLS, and browsers increasingly refuse to display them.

2. Pick a canonical hostname and stick to it. Decide whether the primary is www.yoursite.com or yoursite.com, and ensure the non-canonical version 301-redirects to the chosen one. Failing to do this means Google indexes both versions, splits authority between them, and ranks neither well.

3. Configure your DNS with a proper TTL. A TTL of 300 seconds is fine for the launch period; long TTLs make it hard to fix problems quickly. Confirm A/AAAA records point at the right hosts and that MX records don't accidentally break email delivery from your domain.

4. Test the site's response time from at least three global regions. Use any free tool. Target under 500ms time-to-first-byte from your primary market. Slow sites don't just convert poorly — they get crawled less aggressively, which delays indexing.

Indexing infrastructure

5. Publish a sitemap.xml at the root of the site. The sitemap should list every URL you want indexed, with lastmod timestamps reflecting real modification dates. Do not include category pages, tag pages, or duplicate content — the sitemap is a curation, not a dump.

6. Publish a robots.txt at the root. At minimum, it should reference the sitemap location. If you have any pages or directories that should not be crawled, disallow them here. Do not use robots.txt to hide broken pages — those should be fixed or 410-marked, not just made invisible to crawlers.

7. Verify the site in Google Search Console. DNS verification is the most robust method. Once verified, submit the sitemap and check the Coverage report for anything unexpected.

8. Verify the site in Bing Webmaster Tools. Bing shares its index with a growing set of AI search systems. Skipping this used to be defensible; it isn't anymore.

9. Submit the sitemap to both search consoles. This accelerates discovery meaningfully for a fresh domain — the difference between "indexed in a week" and "indexed in six weeks."

On-page basics

10. Every page has a unique title tag under 60 characters. No template titles, no repeated titles across sections, no titles that just say your company name. Each title should describe what that specific page is about, in language a human would search for.

11. Every page has a unique meta description under 160 characters. Written for humans, not for crawlers. Descriptions are one of the single strongest levers for click-through rate from search results, and they carry over across every distribution channel that quotes the site.

12. Heading hierarchy is proper. One H1 per page, describing the page's primary topic. H2s for major sections. Don't skip levels. Don't use headings for visual styling — use them for structure.

13. Every image has an alt attribute. Not empty, not decorative — descriptive. Alt text is used by screen readers, drives image search traffic, and is factored into page-level topic understanding.

Mobile and Core Web Vitals

14. The site is fully responsive. Test at 375px width (small phone), 768px (tablet), and 1440px (desktop). No horizontal scrolling on mobile. Buttons that are tappable without zooming. Text that reads at default browser font size without pinch-to-read.

15. Largest Contentful Paint under 2.5 seconds. Run Lighthouse or PageSpeed Insights and confirm the primary landing pages pass. If they don't, the usual culprits are large hero images, uncompressed webfonts, or render-blocking third-party scripts.

16. Cumulative Layout Shift under 0.1. No content jumping around as the page loads. Set explicit dimensions on images, reserve space for ads and embeds, and load webfonts with font-display: swap plus preload.

Analytics and measurement

17. Analytics is installed and firing on every page. Whether you use Google Analytics, Plausible, or something else, confirm events land in the dashboard. Missing analytics on 15 percent of pages is a surprisingly common launch-day bug and it's costly to detect later.

18. Conversion events are defined before launch. What counts as a signup? A demo request? A trial start? Define these and fire the events from day one. Retroactive conversion tracking is always incomplete.

Directory pre-submissions

19. Submit to at least three quality directories in your niche. Doing this in the two weeks before launch means the listings go live around the same time as the site, giving you a starting backlink profile from real, curated sources rather than a lonely-domain-with-zero-backlinks profile that new sites usually have.

The final one

20. Have someone unfamiliar with the product visit the site and tell you what it does. Not a co-founder. Not an investor. Someone whose job requires them to make sense of unfamiliar things quickly. If they can't articulate what the site does within 30 seconds, the homepage needs a rewrite before launch — because search visitors will bounce even faster than that.

Two things that don't matter as much as you think

Two commonly-obsessed-over items that consistently underperform their reputation in the pre-launch phase:

Fancy schema markup. Basic Organization and WebSite schema is worth adding. Elaborate schema for content types you don't yet have (Product, Review, HowTo) is not — it's premature and often breaks silently when the underlying page structure changes. Add these when the pages exist and have stabilised.

Keyword-optimised URLs. Yes, /blog/how-to-improve-page-speed is better than /blog/2026-03-14. But the marginal value is small compared to actually having good content on the page. Don't spend a week debating URL structures. Pick a reasonable pattern, use it consistently, move on.

What to skip until after launch

A few items that founders often try to solve pre-launch but that make no sense until real users arrive:

Detailed heatmap and session recording tools. No traffic means no data. Install them after you have 100+ daily visitors.

Extensive A/B testing infrastructure. Same reason. Traffic first, tests later.

Comprehensive internal linking audit. This matters, but it matters after you have more than five real pages. On launch day, the internal link graph is small enough to evaluate by eye.

Backlink outreach beyond directories. Cold outreach to journalists, bloggers, or podcasters for a brand-new site with zero traffic and zero social proof converts terribly. Wait until you have some evidence of traction to reference.

The launch-day sequence

The morning of launch, in order:

1. Flip DNS to production.
2. Verify HTTPS works on all pages.
3. Confirm analytics is firing.
4. Re-submit sitemap in Search Console and hit "Request Indexing" on the homepage and top three landing pages.
5. Post about the launch in the places you already have an audience — even a small one. Signals of real traffic help indexing move faster.
6. Check the site from a private browser window as if you were a new visitor. Look for anything that would break the first impression.

None of this takes longer than an hour. All of it is skipped by roughly half of first-time launchers, and it visibly affects how the first three months of organic growth play out.

The deeper point

The pre-launch checklist isn't glamorous. Nothing on it produces a Twitter-thread-worthy screenshot. But launch day is one of only two or three moments in a site's life where these decisions compound directly into how Google treats the site going forward. A site launched with all twenty items in place will accumulate authority visibly faster than one launched with half of them broken — and the gap widens over time, not narrows.

If you're two weeks out, work through this list once, mark the items that need attention, and fix them. The specific fixes take an afternoon. The ranking advantage they buy is measured in months.