Reach
Indexation and rendering
Can a crawler reach the URL and see its content in the served HTML?
The foundation, and where AI-built sites fail most often. It fetches real pages and checks the raw HTML before any JavaScript runs, then the gatekeepers: status codes, HTTPS, stray noindex, robots.txt and sitemaps. If content only exists after JavaScript, it moves it into the server response.
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
- “Google can't find my site”
- “Is my site crawlable?”
- “SSR or CSR?”
- “Pages not indexed”
Installed as a skill, it triggers on requests like these by itself.
- Step 01Diagnose: identify the stack, fetch a real URL and read the served HTML, check the gatekeepers
- Step 02Fix: move content into the server response, then robots, sitemap, status and HTTPS
- Step 03Verify by re-fetching the served output, never by trusting the edit
- Step 04Report what was wrong, what changed and how it was verified
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.
- 01Paste the link promptOne line that points your agent at the skill on GitHub. Nothing to install, always the latest version.
- 02Paste the full textFor agents that cannot open links. The skill is self-contained, so this works in any chat.
- 03Install the packInstalled as skills, it triggers by itself when you describe the problem, and can hand work to the other skills.
Questions about this skill?
Ask me on LinkedIn, or open an issue on GitHub if something is wrong or missing.