Launching a website is not the moment you flip a switch. It’s a structured process — and the difference between a launch done well and one done poorly is the difference between a website that performs from day one and one that spends months being corrected because pre-launch checks weren’t made.
Whether you’re building your first website or rebuilding an existing one, this checklist covers the critical steps to verify before any website goes live.
Technical Checks
SSL certificate active. The site should load on HTTPS on every page. Check the padlock in the browser address bar and confirm there are no mixed content warnings (HTTP elements loading on an HTTPS page).
All pages returning correct HTTP status codes. Every page should return a 200 (OK) status. Run the site through a crawler (Screaming Frog free version covers up to 500 URLs) to identify any pages returning 404 errors, 301 redirects, or other unexpected status codes.
Redirects from old URLs (for rebuilt sites). If the new site uses different URLs from the old one, 301 redirects should be in place for every old URL — directing both visitors and Google to the correct new page and preserving ranking authority.
Page speed verified on mobile. Run the homepage and key service pages through Google PageSpeed Insights on mobile and confirm scores are above 50, ideally above 80. Any score below 50 should be investigated before launch.
Contact form tested. Submit a test enquiry and confirm it arrives in the correct inbox. Check that the confirmation email or redirect works correctly.
All links checked. Internal links should point to live pages. External links should open in a new tab and go to the intended destination. No orphan pages should exist (pages with no internal links pointing to them).
SEO Checks
Title tags and meta descriptions set for every page. Check each page in Yoast or Rank Math to confirm title tags and meta descriptions are present, unique, and optimised for the page’s target keyword.
H1 headings confirmed on every page. Every page should have exactly one H1 — the primary heading — that includes the page’s target keyword naturally.
XML sitemap submitted to Google Search Console. The XML sitemap (typically at yoursite.com/sitemap.xml) should be submitted to Google Search Console to accelerate indexing of all pages.
Google Search Console ownership verified. The site should be claimed and verified in Google Search Console before or immediately after launch.
Google Analytics 4 tag confirmed live. Check the GA4 Realtime report while viewing the site to confirm the tracking tag is firing correctly.
Schema markup validated. Run key pages through Google’s Rich Results Test to confirm structured data is correctly implemented and error-free.
Robots.txt not blocking indexing. Check your robots.txt file (yoursite.com/robots.txt) to confirm Google is not being blocked from crawling your pages. Staging environments often have robots.txt set to block all crawlers — this must be updated on launch.
Content and UX Checks
All placeholder content removed. Lorem ipsum text, test images, and temporary content should be replaced with final content before launch.
Mobile experience tested on a real device. View every key page on a real mobile phone, not just a desktop browser emulator. Test navigation, scroll, tap targets, and the contact pathway.
Accessibility basics checked. All images should have alt text. Colour contrast should meet WCAG AA standards. Navigation should be keyboard-accessible.
A proper launch process is built into every project managed by a web designer on the Mornington Peninsula who takes technical quality seriously. Browse our portfolio to see live examples of well-launched local business websites, or get in touch to discuss your upcoming launch.
Frequently Asked Questions
How long does the website launch process take?
For a thorough pre-launch check of a five to fifteen page local business website, allow one to two days. The checklist above can be worked through systematically by an experienced practitioner in a few hours, but resolving any issues identified adds time. Rushing the launch to hit an arbitrary date is one of the most common sources of post-launch problems.
What happens if I find problems after the website has launched?
Fix them as quickly as possible. Most post-launch issues — a broken redirect, a missing meta description, an unlinked page — are fixable within minutes. The priority is identifying them quickly through Google Search Console monitoring and your own post-launch review rather than discovering them weeks later.
Should I tell Google when I launch a new website?
Submitting your XML sitemap to Google Search Console is the most direct way to notify Google of a new or updated site. Google will discover and crawl your pages independently, but sitemap submission accelerates the process — particularly for new domains or significantly restructured sites.
How quickly will a new website start ranking in Google after launch?
New pages typically begin appearing in Google’s index within days to weeks of launch for sites with active crawling. Meaningful ranking positions for competitive terms take longer — typically three to six months for a new site with proper SEO foundations, and faster for established domains with existing authority being rebuilt.
