Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →modu-ai/moai-ref-seo
Search-visibility and crawlability reference for web output: canonical URL discipline, per-page title and meta description uniqueness, robots.txt and sitemap.xml as host-derived artifacts, JSON-LD structured data with entity consistency, and the document-semantics rules that decide whether a machine can read a page at all. Agent-extending skill that amplifies web-output implementation and pre-ship review with production-grade indexing and structured-data patterns. NOT for: keyboard operability,
Passed 21 of 22 test cases with the skill, and 19 of 22 without it.
3 fixed18 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am preparing our web application for release and need a pre-ship search indexing review on our rendered pages, metadata output, and server response configs. Please analyze our HTML structure, canonical links, social tags, JSON-LD blocks, and host artifacts like sitemap and robots settings. Present your findings as a structured audit report divided by category, detailing pass/fail results for each route, identified search visibility issues, and prioritized remediation steps for our engineering team.
| Checked | Without skill | With skill |
|---|---|---|
| requires JSON-LD claims to have a visible counterpart on the page | Missed | Passed |
The instructions your model reads when the skill loads.
manager-develop — applies these rules while implementing pages, routes, and serialized metadata output/moai review — pre-ship indexing review surface; equivalently available as a per-spawn Agent(general-purpose) with web-output review instructionsA page is indexed on what a machine can fetch and parse, not on what a person sees once everything has finished loading. Two failures dominate everything below: the same content reachable at more than one address, and a claim asserted in serialized data that nothing on the page corroborates. Every rule here is a specialization of one of those two.
Figures that engines publish and then quietly revise — truncation widths, ranking weights, crawl allowances — are deliberately absent. Where a limit matters, this reference gives the decision rule and the measurement to take, so the guidance outlives the figure.
The structure a parser reads before it reaches any content signal. Cheapest class of defect to introduce, and the cheapest to detect.
| Rule | How to check it | Failure it prevents |
|---|---|---|
Exactly one h1 per document | Count h1 elements in the rendered output of each page | Competing topic signals leave the subject ambiguous |
| No skipped heading level | Walk the heading sequence; each descent moves by at most one level | Section nesting a parser cannot reconstruct |
Every image carries alt text | Each image element has a non-empty alt attribute, or an empty one paired with an explicit decorative marker | Meaning locked inside a binary the parser cannot open |
| Anchor text names its destination | Read each link's text with the surrounding sentence hidden, then ask where it goes | Instruction-shaped link text carries no signal about the target |
| Fragment targets resolve | For each in-page fragment link, confirm a matching identifier exists in the same rendered output | Navigation that silently lands nowhere |
Derive alt text from what the image depicts, never from its file name. Where an
image genuinely adds nothing a reader needs, mark it decorative on purpose instead
of inventing a description for it.
One resource, one address; everything else redirects to it.
test cases passed, vs 19 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.