Skip to content
Technical specialists

Launch QA

Pre-launch and go-live checks

Is anything going to stop this site being indexed when it goes live?

A fast, verifiable pass over the gatekeepers that most often stop a new site being indexed, run against the production URL: staging noindex and robots blocks, auth walls, preview hosts in canonicals and sitemaps, redirects, soft 404s, share images, analytics and crawlers blocked at the CDN. Results are split into launch blockers and fix-this-week.

install/copy-paste/launch-qa.md ↗

Paste into Claude Code, Cursor, Codex or any agent that can open a link. If yours cannot, use Copy full text.

Reach for it when you say

  • “We launch tomorrow”
  • “Pre-launch SEO check”
  • “We just deployed”
  • “What will stop this ranking?”

Installed as a skill, it triggers on requests like these by itself.

How it works
  1. Step 01Pin the targets: the production host and one URL per key template
  2. Step 02Run the checks in ladder order, each with an exact command
  3. Step 03Classify each result as a launch blocker or fix-this-week
  4. Step 04Report the scorecard, then what to check on launch day and in the first week
Use it

Three modes, three ways in

Run it in audit mode first: it records findings and changes nothing. Then fix applies only the findings you approve, and re-check re-tests them later. Switch modes on the prompt above.

  1. 01Paste the link promptOne line that points your agent at the skill on GitHub. Nothing to install, always the latest version.
  2. 02Paste the full textFor agents that cannot open links. The skill is self-contained, so this works in any chat.
  3. 03Install the packInstalled as skills, it triggers by itself when you describe the problem, and can hand work to the other skills.
Install guides →

Questions about this skill?

Ask me on LinkedIn, or open an issue on GitHub if something is wrong or missing.