Website launch checklist
Dan Counsell · Founder of Realmac SoftwareUpdated
We’ve made RapidWeaver, a website builder for Mac, since 2004. Each guide works with any tool, then shows how in RapidWeaver Elements.
Work through this list in order, then do the last section again on the live site. It works for any website, whatever you built it with.
Content
- A first-time visitor can tell who the site is for and what it offers within a few seconds.
- Each important page has one clear next step, such as Contact us or Book now.
- Every page is proofread: spelling, dates, prices, opening hours, phone numbers.
- No placeholder text or images are left.
- Pages that aren’t ready are hidden.
- The menu labels are clear, and the logo links to the home page.
- The footer has your contact details and links to legal pages.
Legal and privacy
- A privacy policy says what data you collect, why, and who sees it.
- Terms are published if you sell, take bookings or have accounts.
- Cookie consent is set up if you use tracking that needs it.
- Forms only ask for what you need.
This is a prompt, not legal advice. Rules differ by country.
Search and sharing
- Every page has its own title and meta description.
- Each page has one H1, with H2s and H3s in order.
- Addresses are short and readable, such as
/about/. - A social sharing image is set, and links look right when shared.
- A favicon shows in browser tabs. See what is a favicon.
sitemap.xmllists your public pages. See how to create a sitemap.robots.txtdoesn’t block the site.- A friendly 404 page links back to useful pages.
- Old addresses redirect to new ones if this replaces an old site. See .htaccess redirects.
Accessibility
- Meaningful images have alt text; decorative ones have empty alt text.
- Text has enough contrast against its background.
- Every link, button and form works with the keyboard alone.
- Form fields have visible labels.
- No sound plays on its own.
More in how to make a website accessible.
Speed and images
- Images are resized and compressed, ideally as WebP.
- Unused large files are removed.
- Key pages score well in PageSpeed Insights.
- Nothing jumps around as the page loads.
Forms and features
- Every form sends, and the message arrives where it should.
- The thank-you message or page makes sense.
- Videos, maps and galleries load on a phone.
- Payment buttons work, tested with a real small purchase or the provider’s test mode.
Hosting and publishing
- HTTPS is on, and
http://redirects tohttps://. wwwand the plain domain both work, and one redirects to the other.- You have a backup of the site and the project file.
- Analytics is installed and recording visits. See our Google Analytics guide.
After launch
- Visit the live site in a private window, on a laptop and on a phone.
- Click through every page once more.
- Add the site to Google Search Console and submit the sitemap. See how to get your website on Google.
- Send a test form from the live site.
- Tell people. Update your email signature and social profiles.
Let AI do the first pass in RapidWeaver Elements
In RapidWeaver Elements, the AI Assistant or a connected AI tool such as Claude can work through this list with you. It can look through your pages for missing titles, descriptions and alt text, uneven headings and broken links, and fix many of them. Try a prompt like this:
Review the open Elements project against a website launch checklist. Show which checks pass, list anything that needs attention, and fix the safe issues. Ask before changing legal wording, tracking, domains or publishing.
AI can’t replace every check. Test forms and analytics on the live site yourself, and look at it on a real phone. The full list is in the Elements manual.
Questions about launching a website
How long does it take to launch a website?
The launch itself takes an hour or so once the site is built. Allow a day for the checks, and a few hours for a new domain to work everywhere.
Should I launch quietly first?
Yes, if you can. Publish, check everything on the live site, fix what you find, then tell people.
What should I do in the first week after launch?
Check Search Console for errors, look at your analytics to see which pages people visit, and fix anything visitors tell you about.