How to launch your website the right way

Your site is live. Now make sure it's finished, findable, shareable and measurable — then tell people about it.

Launching is not the finish line. A site that nobody can find, that previews as a blank grey box on social, and that has no analytics wired up is a site that launched into a void.

This journey covers the things worth doing in the verge of your site goes live. Some of them are technical, and we can verify those for you against a monitored URL. The other are about getting in front of humans — you do those yourself, and mark them complete when they're done.

Work top to bottom. The order matters: the site should be finished before anyone sees it, the social preview tags need to be live before you post the link anywhere, the sitemap needs to exist before you can submit it, and you want to know the site holds up under load before you send a crowd at it.

Steps

Open a step to read it

1
Confirm the site is actually finished: Lorem Ipsum
Verifies with Lorem Ipsum Auditor
The cheapest win on any launch checklist is checking whether the thing you're about to promote is done. Placeholder copy survives more launches than anyone wants to admit — it hides in footers, empty states, error messages and the third card in a grid nobody scrolled to. Search engines index it, and the first stranger to visit will find it before you do.
2
Confirm the site is actually finished: 404 page
Verifies with Not Found Auditor
A 404 page that returns HTTP 200 with the words "page not found" printed on it tells search engines every broken URL on your site is a real page worth indexing. That's a soft 404, and it quietly pollutes your index for months. Make missing pages return an actual 404 status, and put something useful on them — a search box, a link home, your main navigation.
3
Set up basic SEO: page title
Verifies with Page Title Auditor
Your title tag is the headline in every search result, the label on every browser tab, and the fallback text when someone bookmarks you. Aim for 15–70 characters: long enough to say what the page is, short enough that Google doesn't truncate it. Write it for a human deciding whether to click, put the distinctive part first, and give every page its own — a site where fifty pages share one title is a site search engines can't tell apart.
4
Set up basic SEO: meta description
Verifies with Meta Description Length Auditor
The meta description is the pitch underneath your title in search results. Google doesn't rank on it, but it decides click-through, which is the part you actually feel. Aim for 150–160 characters, describe what someone gets from the page rather than restating the title, and skip keyword stuffing — if it reads like it was written for a crawler, it gets rewritten by one.
5
Add Open Graph tags
Verifies with OpenGraph Auditor
Open Graph is what LinkedIn, Facebook, Slack, Discord and most chat apps read when someone pastes your URL. Without it they fall back to scraping whatever text they find first, which is usually your nav bar. Set og:title, og:description, og:type, og:url and an absolute og:image URL at 1200×630.
6
Add a Twitter Card
Verifies with Twitter Card Auditor
X/Twitter uses its own namespace. twitter:card and twitter:title are mandatory; if you pick summary_large_image you also need twitter:image. Add twitter:image:alt while you're in there — it's the difference between an accessible preview and a decorative one.
7
Add JSON-LD structured data
Verifies with Schema Entities Auditor
Structured data tells search engines and AI crawlers what your page is, not just what it says. Start with the schema types that actually match your site — Organization and WebSite on the homepage, then Product, SoftwareApplication, Article or FAQPage where they apply. JSON-LD in a
8
Install Google Analytics
Verifies with Google Analytics Auditor
You cannot tell whether the launch worked without a baseline. Install gtag.js with a valid G-XXXXXXXXXX measurement ID in the , and make sure the ID in the script src matches the one in your config call — mismatched IDs are the most common silent failure. If you run Google Tag Manager instead, the GTM auditor checks the container ID, dataLayer init and noscript fallback.
9
Publish a sitemap.xml
Verifies with Sitemap Auditor
A sitemap is how search engines find the pages nothing links to yet — which, on a brand new site, is most of them. Generate it at build time so it stays current, keep lastmod dates honest, and add a Sitemap: line to your robots.txt so crawlers find it without being told.
10
Submit your sitemap to search engines
Publishing a sitemap makes it discoverable. Submitting it makes it urgent. Verify your domain in Google Search Console and Bing Webmaster Tools, then submit the sitemap URL in each. Bing's submission also feeds DuckDuckGo and, increasingly, AI answer engines. Come back to Search Console in a week to see what actually got indexed.
11
Make sure you can survive the traffic spike
Verifies with Cache AuditorVerifies with CDN Coverage AuditorVerifies with Time To First Byte Auditor
A front-page Hacker News post is a load test you never scheduled, and it arrives all at once. Check this before you post, not after: that HTML and static assets carry sane cache headers, that your assets are actually served from a CDN rather than your origin, that time to first byte is under 800ms, and that the console isn't throwing errors that only appear on a cold cache. Everything here is cheap to fix on a Tuesday afternoon and impossible to fix while you're on the front page.
12
Post on Hacker News
Submit to news.ycombinator.com — use the Show HN: prefix if you built the thing yourself. Weekday mornings US Eastern get the most eyes. Post a plain, specific title with no marketing language, then add a first comment explaining what you built and why. Stay in the thread and answer everything.
13
Post on Reddit
Find the two or three subreddits where your users already are, and read their self-promotion rules before you post anything. A post that explains a problem you hit and what you built to solve it survives; a post that reads like a press release gets removed. r/SideProject, r/webdev and r/SaaS are broad starting points, but niche subreddits convert far better.
14
Post on TabNews (Brazil)
If you're building for a Brazilian audience, TabNews is where the developer community talks. Write it in Portuguese, lead with the technical story rather than the pitch, and be ready to defend your design decisions — the audience is sharp and reads the code.
15
Submit to directories
Directory listings are slow-burn: a little referral traffic, and backlinks that help search engines take your domain seriously. Work through the general ones (Product Hunt, BetaList, Indie Hackers, AlternativeTo, SaaSHub, Dofollow.Tools) plus any directory specific to your niche. Keep a list of what you submitted where — most take days to approve and some never do.

Create an account, add your site as a monitored URL and work through these steps on it.