The launch-day mistakes that cost the most
Leaving search engines blocked. Staging sites are rightly hidden from Google with a noindex tag, a "Discourage search engines" tick box in WordPress, or a robots.txt that disallows everything. Forget to switch it off and the new site quietly drops out of Google over the following weeks. It is the single most common launch mistake, and the checker tests for all three.
Links still pointing at staging. Images, internal links and canonical tags that still use the staging address work fine for you and break for everyone else, or tell Google the staging site is the real one.
No redirects from the old site. If URLs have changed, every old page needs a 301 to its replacement, set up before the switch. The redirect map generator builds the list.
Tracking that never arrives. Analytics left on a test property, a consent banner that blocks everything, or a Tag Manager container nobody published. You only notice a month later, when there's no data to report.
Questions agencies ask
The essentials: search engines can index it (no noindex or robots.txt block left from staging), it redirects to HTTPS, there are no links to the staging address, redirects from the old URLs are in place, forms send email, analytics is recording, backups and monitoring are running, and the content is signed off. The checklist above covers all of it, and tests the technical parts automatically.
Make sure nothing is still blocking search engines from staging, and redirect every old URL that changed to its new page with a 301. Then submit the sitemap in Search Console and watch the coverage report for the first couple of weeks.
It adds a noindex instruction to every page. Useful on staging, disastrous if it's still ticked when the site goes live. It's under Settings, Reading. The checker spots it as a noindex on the homepage.
The switch itself can take minutes if DNS TTLs were lowered the day before. Allow a few hours for checks and fixes, and keep an eye on Search Console, analytics and the order emails for the first week.
Yes, in your browser, separately for each site you check. Nothing is stored on this server beyond a few minutes of caching for the automatic checks.
Yes. I do launch-day support for agencies, especially on WooCommerce and Laravel builds: migrations, DNS, redirects, tracking, and fixing whatever turns up.
Launching something complicated?
I help agencies get WooCommerce and Laravel builds over the line: launch-day support, migrations, redirects, tracking and the fixes that turn up in the first week, so your team isn't up at midnight.
- White-label, under your brand, or alongside your team
- Laravel, WordPress, WooCommerce, integrations and tracking
- Inherited and half-finished sites taken over and stabilised
- UK based, straight to the developer, no account managers