Website Launch Readiness Checker
Catch the technical issues commonly missed before a website goes live
- HTTPS and redirects
- Browser support signals
- Indexing blockers
About Website Launch Readiness Checker
Enter a website address to check the homepage, its redirects, HTTPS and certificate, browser support signals, security headers, robots.txt, sitemap, page metadata, forms, third-party services, page weight and basic accessibility signals. Browser support compares the responses different browsers receive and looks up the HTML and CSS features the page uses in caniuse data; it does not render the page in real browsers. Each finding shows the evidence and what to do next, and a readiness score sums up the checks performed. It is a passive check: forms are never submitted and nothing is stored. Requires a free account; each scan uses one check from your daily allowance.
A practical pre-launch check
The checker requests your homepage the way a browser would, follows up to five redirects, then reads robots.txt, confirms that a sitemap can be loaded, tries the HTTP version of the site, and checks a small sample of the links and images on the page. Everything else comes from the homepage response itself. It needs a free account, and each scan uses one check from your daily allowance.
- Availability: status code, final URL, redirect chain, HTTPS, the HTTP-to-HTTPS redirect, certificate expiry, the www and non-www host, and whether missing pages return 404.
- Browser support: whether Chrome, Firefox, Safari and iPhone identities receive the same response, which modern HTML and CSS features the page uses and where caniuse data shows gaps, plus doctype, character encoding and obsolete technology.
- Indexing: noindex directives, robots.txt blocks, title, description, canonical URL, sitemap and sharing tags.
- Security headers: HSTS, Content-Security-Policy, framing protection and related headers, read against OWASP guidance.
- Content, forms, third-party services, page weight and accessibility basics such as alt text, labels and the page language.
How to read the score
Each check is weighted by how much it matters for launch. A pass earns its full weight, a warning half and a failure nothing. Checks that could not be completed are left out of the score and listed separately, and a potential launch blocker keeps the score below 50.
The score summarises the checks performed. It is not a measure of search ranking, security, accessibility compliance or how a launch will go.
What this check can’t see
Only the homepage HTML and up to three of its own stylesheets are read, so content added by JavaScript after the page loads, pages deeper in the site and anything behind a login are not checked. JavaScript features are not analysed for browser support. Forms are listed but never submitted, and nothing about the scanned page is stored.
Further reading
Questions people ask
- Why does my staging site fail the indexing checks?
- Staging sites usually block search engines on purpose with noindex or robots.txt. That is fine before launch; run the check again on the production domain and make sure the blocks are gone there.
- Does it test my site in real browsers?
- No. It compares the responses different browser identities receive and looks up the features found in your HTML and CSS in caniuse data (CC BY 4.0). It cannot show how the page looks or behaves, so check it yourself in the browsers your visitors use. Brave, Opera and other Chromium browsers usually follow Chrome.
- Does a sitemap pass mean Google has it?
- No. The check confirms a sitemap can be loaded. Whether it has been submitted and processed can only be seen in your own Google Search Console account.
- Will the scan submit my forms or change anything?
- No. The scan only reads pages. Linked pages and images are checked with lightweight HEAD requests, and links that look like sign-out or delete actions are skipped.