Launch mistakes
Launch mistakes that surface after a client site goes live
The build is done, the date is public, and a week later the client finds a noindex tag, a form posting to staging or a page full of lorem ipsum. Each page below covers one of these mistakes: what it is, how it slips through on an agency launch, how to spot it yourself in a minute or two, and exactly what Launch Ready's scan checks and does not check.
Last reviewed
Eight mistakes to check before handoff
A noindex tag left on
The live site tells search engines not to index it, usually because a staging setting came along.
robots.txt still blocking the site
A staging Disallow: / rule is still in the live robots.txt, so crawlers are told to stay away.
A form still posting to staging
The form's action still points at a staging or local address, so the first enquiries go nowhere useful.
Analytics that never fired
The tracking tag is missing, waiting for consent that never comes, or installed twice.
Staging and localhost links left in
Links, canonical tags or redirects still send visitors to staging, a preview build or a developer's machine.
Placeholder text on a live site
Lorem ipsum, “coming soon” sections or test labels that were meant to be replaced before launch.
Broken links and missing assets
Internal links that return errors, and images, scripts or stylesheets that fail to load on the live site.
Mixed content and SSL errors
An untrusted certificate, pages still served over HTTP, or files loaded over HTTP on secure pages.
Beyond these eight
The free 72-item website launch checklist covers the rest of a launch, and marks each item as Scan check, Partly checked or Manual. How we scan explains what the crawler fetches, renders and stores. Launch Ready does not submit forms or run functional tests, and the launch decision stays with your team.
Check your next client site before handoff
Add the staging or live URL, read the fix list, and send the client a report when it is ready.