Agent skill

Moai Ref SEO

by modu-ai in modu-ai/moai-adk

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…

Apache-2.0Auto-check passedMarketing & SEO

Install Moai Ref SEO

skills CLI
$ npx skills add modu-ai/moai-adk --skill moai-ref-seo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install modu-ai/moai-adk moai-ref-seo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/moai-ref-seo .claude/skills/moai-ref-seo && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
moai-ref-seo
GitHub stars
1.2k
Token cost
~3.3k tokens
SKILL.md length
1,687 words
Files
1
Skills in repo
48
Repo updated
First seen
Licence
Apache-2.0

At a glance

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…

  • Tasks that involve Schema markup
  • SKILL.md covers Target Agents, Core Principle, Document Semantics and Identity and Canonical Address, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Technical SEO

What it does

Moai Ref SEO is an agent skill from modu-ai/moai-adk. 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, visible focus…

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Schema markup, Technical SEO and UI design. The repository describes itself as: Agentic development harness for Claude Code — SPEC-driven plan/run/sync, TRUST 5 quality gates, model+effort routing, and Claude×GLM multi-LLM cost control. Single Go binary, 16… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Schema markup
  • Tasks that involve Technical SEO
  • Tasks that involve UI design

Example prompts

  • “/moai-ref-seo”

What it can do on your machine

Read from SKILL.md and the folder at commit 2aab5f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Moai Ref SEO loads about 3.3k tokens when it runs. Until then it costs about 227 tokens; SKILL.md has 1,687 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~227
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from modu-ai/moai-adk at commit 2aab5f7, republished under its Apache-2.0 licence (© modu-ai). 1,687 words, ~3,347 tokens.

Download SKILL.mdSave it as .claude/skills/moai-ref-seo/SKILL.md (or your agent's skills folder).
name
moai-ref-seo
description
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, visible focus indicators, and form-control labeling (accessibility owns those; delegated to the accessibility surface); generative-engine optimization, deliberately excluded as insufficiently settled; visual polish and interface detail (see moai-ref-ui-polish); API contract design (see moai-ref-api-patterns); security headers and hardening (see moai-ref-owasp-checklist and moai-ref-secops).
when_to_use
Use when a project emits pages that a search engine or an automated reader will fetch: choosing canonical addresses, writing per-page metadata, emitting…
user-invocable
false
metadata.version
1.0.0
metadata.category
domain
metadata.status
active
metadata.updated
2026-08-01
metadata.tags
seo, canonical, structured-data, json-ld, sitemap, robots, metadata, crawlability, reference
progressive_disclosure.enabled
true
progressive_disclosure.level1_tokens
100
progressive_disclosure.level2_tokens
3000

Search Visibility Reference

Target Agents

  • 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 instructions

Core Principle

A 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.

Document Semantics

The structure a parser reads before it reaches any content signal. Cheapest class of defect to introduce, and the cheapest to detect.

RuleHow to check itFailure it prevents
Exactly one h1 per documentCount h1 elements in the rendered output of each pageCompeting topic signals leave the subject ambiguous
No skipped heading levelWalk the heading sequence; each descent moves by at most one levelSection nesting a parser cannot reconstruct
Every image carries alt textEach image element has a non-empty alt attribute, or an empty one paired with an explicit decorative markerMeaning locked inside a binary the parser cannot open
Anchor text names its destinationRead each link's text with the surrounding sentence hidden, then ask where it goesInstruction-shaped link text carries no signal about the target
Fragment targets resolveFor each in-page fragment link, confirm a matching identifier exists in the same rendered outputNavigation 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.

Identity and Canonical Address

One resource, one address; everything else redirects to it.

DecisionRule
Which address is canonicalPick one form per resource and declare it. The declared value must equal the address actually served
Trailing-slash variantsChoose one form and redirect the other permanently. Serving both splits one resource across two addresses
Case, query parameters, tracking suffixesNormalize before serving. A parameter that does not change the response must not mint a second address
Parameterized routesBuild the declared value from the resolved parameters, never from a fixed string shared across the whole route
Retiring an addressRedirect permanently from the old form and update the declaration in the same change

A declaration pointing at an address that redirects, errors, or serves different content is worse than no declaration at all: it actively steers the reader away from the page it appears on.

Per-Page Metadata

FieldRuleRecurring defect
titleUnique per page, composed from a page-specific part plus a stable identifier for the siteThe scaffold's default survives to production on every route
meta descriptionUnique per page, written for a person reading a result snippetOne description copied everywhere, or prose that describes nothing
Indexing directiveSet a default for public pages, then narrow per page class. Authenticated areas and internal tools are excluded deliberately, not merely left unlinkedA private surface gets indexed because nothing declared otherwise
Social preview fieldsPresent and absolute. A relative address in a field a third party fetches resolves against the wrong hostA share card that renders blank off-site

Length budgets are a decision rule, not a constant: draft the text, observe where the consuming surface truncates it, then cut to what you observed. Placeholder detection belongs in the pre-ship check — scan the emitted output for the scaffold's own default strings and fail when one survives.

Structured Data

Serialized JSON-LD states what a page is. Its one hard constraint is correspondence with the visible page.

DecisionRule
Which types to emitDerive them from the page's actual role — an organization, a product, a piece of software, a place, an article. Emit the site-level type everywhere and the page-specific type only where it applies
Required fieldsEach type has a small mandatory core. Emit that core completely rather than emitting several types partially
Addresses inside the dataAbsolute, and resolving. Relative values are discarded without a warning
Several entities on one pageEmit one block holding all of them, give each a stable identifier, and cross-reference by identifier instead of nesting duplicate copies
PlacementKeep each type on the page it describes. A type repeated site-wide dilutes rather than reinforces

Mirroring rule — every claim in the serialized data needs a visible counterpart on the same page. A name, a description, a rating, or a question-and-answer pair that exists only in the markup is an assertion the reader cannot check, and it is now scored as a negative signal rather than a neutral one.

Entity Consistency

Structured data identifies an entity. Consistency is what makes that identity hold across independent sources.

SurfaceRequirement
Canonical nameOne spelling, one casing, one suffix — the same in the serialized data, the page copy, and the headings
Owned profile linksRestricted to accounts this entity itself administers, each confirmed to resolve rather than bounce to a sign-in wall
Contact detailsName, address, and contact number identical across the serialized data, the visible page, and any third-party listings
Omission over approximationA field with no accurate value is left out. A partial or invented one fragments the identity it was meant to establish

Formatting differences that read as trivial to a person are distinct values to a matcher. Fix one format per field and hold it everywhere the entity appears.

Host-Derived Crawl Artifacts

robots.txt and sitemap.xml are output the site serves, not files carried between environments.

ArtifactRule
robots.txtDerive the absolute addresses it contains from the incoming request's host, so every environment serves a correct description of itself
sitemap.xmlEnumerate the addresses actually served. An entry for a removed page spends crawl attempts and signals staleness
Staying in syncAdding or removing a route updates the enumeration in the same change. A hand-maintained list drifts within one iteration
Per-entry hintsFreshness and weighting hints attached to entries are advisory and widely discounted. Correctness of the address set matters far more than the hints on it

Hardcoding one environment's host into either artifact is the defect that keeps recurring, because it passes review while being correct in exactly one place.

Show full SKILL.md (615 more words)Show less

Delivery Chokepoints

ConcernRule
Response headersApply them at a single wrapping point every response passes through, error and redirect responses included. A header set only on the success path is missing exactly when a reader is most likely to be misled
Rendering modeTreat "what does a reader receive in the first response?" as a question the project answers explicitly. Content that appears only after client-side work is content a non-executing reader may never see
Redirect chainsOne hop to the canonical address. Each extra hop is another opportunity to lose the reader
Third-party originsConnection hints for origins the page depends on belong ahead of the resources that use them. Measure the effect on this project's own pages rather than assuming one
<!-- moai:evolvable-start id="rationalizations" -->

Common Rationalizations

RationalizationReality
"The framework already sets sensible metadata defaults"A default is identical on every route by construction. Uniqueness is the entire purpose of the field, so it cannot be inherited.
"Both address forms serve the same page, so it makes no difference"Two addresses serving one resource are two resources to a crawler. Which one survives is guessed unless a declaration and a redirect settle it deliberately.
"Serialized data may say more than the page shows — it is extra context"Data with no visible counterpart is an unverifiable claim, and it is scored as one.
"Heading structure and alt text belong to accessibility, not to indexing"They are the parse structure a machine uses to segment and describe a page. Sharing a mechanism with accessibility is not a reason to defer them.
"The address enumeration can be updated in a follow-up change"A list maintained apart from the routes drifts immediately and then silently. Deriving it from the routes is the only version that stays true.
"The staging host in the artifact is fine, we swap it at deploy"A hardcoded host is right in one environment and wrong in every other, including the one that gets indexed.
<!-- moai:evolvable-end -->
<!-- moai:evolvable-start id="red-flags" -->

Red Flags

  • Two or more h1 elements on one page, or a heading sequence that skips a level
  • A canonical declaration that does not match the address actually serving the page
  • The same title or meta description reused across more than one route
  • An image with no alt attribute, or alt text that repeats the file name
  • Link text that reads as an instruction instead of naming a destination
  • An in-page fragment link with no matching identifier in the rendered output
  • robots.txt or sitemap.xml carrying a hardcoded host instead of one derived from the request
  • Serialized JSON-LD asserting a name, description, or offer with no visible counterpart
  • A relative address in a field a third party fetches — a share-preview image, a structured-data logo
  • Response headers applied on the success path only, leaving redirect and error responses uncovered
<!-- moai:evolvable-end -->
<!-- moai:evolvable-start id="verification" -->

Verification

  • Every rendered page has exactly one h1 and a heading sequence with no skipped level — report the counts observed, not the intent
  • Each route's canonical declaration was fetched and returned that same page with no redirect in between
  • title and meta description were collected across all routes; no duplicates and no scaffold default strings remain
  • Every image element has an alt attribute, and decorative images are marked as such on purpose
  • Every in-page fragment link was resolved against the rendered output of the page carrying it
  • robots.txt and sitemap.xml were fetched from the deployed host and every address in them resolves — quote the address set observed
  • Serialized JSON-LD parses, its addresses are absolute, and each claim it makes has a visible counterpart quoted from the page
  • Response headers were observed on a success response, on a redirect response, and on an error response
<!-- moai:evolvable-end -->

© modu-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/moai-ref-seo of modu-ai/moai-adk.

Open the folder on GitHubat commit 2aab5f7

Compare with similar skills

Moai Ref SEO next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Moai Ref SEO compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Moai Ref SEO this skillmodu-ai/moai-adk1.2k—~3.3kAutomated safety check: PassApache-2.0
Universal SEO AnalysisAgriciDaniel/claude-seo19k—~4.9kAutomated safety check: PassMIT
Generative Engine Optimizationtech-leads-club/agent-skills7k—~2.5kAutomated safety check: PassMIT
SEO Geoericrisco/rsc-harness174—~2.8kAutomated safety check: PassMIT
SEO AI Optimizerluongnv89/skills131—~2.7kAutomated safety check: PassMIT
GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude11k—~2.8kAutomated safety check: NotesMIT

Similar skills

  • Universal SEO Analysis

    AgriciDaniel/claude-seo

    Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.

    19k GitHub stars~4.9k tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed
  • Generative Engine Optimization

    tech-leads-club/agent-skills

    Makes a page or site easier for AI answer engines to find, understand, trust and quote, using metadata, structured data, an llms.txt file and clear page structure.

    7k GitHub stars~2.5k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • SEO Geo

    ericrisco/rsc-harness

    A skill your agent uses when one existing page needs to rank in Google AND get cited by AI answer engines — auditing a URL for on-page SEO, structured-data JSON-LD, GEO citation levers, Core Web…

    174 GitHub stars~2.8k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • SEO AI Optimizer

    luongnv89/skills

    Audit and optimize websites for technical SEO, content SEO, and AI bot accessibility.

    131 GitHub stars~2.7k tokensUpdated today
    Marketing & SEOAuto-check passed
  • GEO-First SEO Audit Tool

    zubair-trabzada/geo-seo-claude

    Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.

    11k GitHub stars~2.8k tokensUpdated today
    Marketing & SEOAuto-check: notes
  • SEO Optimizer

    ailabs-393/ai-labs-claude-skills

    This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.

    454 GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed

More from modu-ai/moai-adk

All 48 skills in this repo
  • Builds hand-editable SVG diagrams from computed layout coordinates, lints the source and renders a 2x PNG, with rules for when mermaid is the better choice.

    1.2k GitHub stars~5.2k tokensUpdated today
    Auto-check: notes
  • MoAI Foundation Core

    modu-ai/moai-adk

    Reference for MoAI-ADK's core development principles: TRUST 5 quality gates, SPEC-first domain-driven workflow, agent delegation and token budgeting.

    1.2k GitHub stars~5k tokensUpdated today
    Auto-check passed
  • MoAI SPEC Workflow

    modu-ai/moai-adk

    Manages SPEC documents for MoAI-ADK development, with GEARS or EARS requirement notation, acceptance criteria and a link into the Plan-Run-Sync workflow.

    1.2k GitHub stars~5.1k tokensUpdated today
    Auto-check passed
  • MoAI TDD Workflow

    modu-ai/moai-adk

    Drives test-first development through the RED, GREEN, REFACTOR cycle, with a config switch that selects between TDD and a DDD workflow for existing code.

    1.2k GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • MoAI Worktree Management

    modu-ai/moai-adk

    Gives each SPEC its own Git worktree with a registry of active workspaces, base-branch sync and cleanup of merged ones, inside the MoAI-ADK workflow.

    1.2k GitHub stars~3.9k tokensUpdated today
    Auto-check passed
  • Watches a pull request's CI checks after creation, separates required from auxiliary failures, applies limited safe fixes and escalates anything semantic to you.

    1.2k GitHub stars~2.4k tokensUpdated today
    Auto-check: notes

Categories

Questions about Moai Ref SEO

What does Moai Ref SEO do?

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…. Moai Ref SEO is an agent skill from modu-ai/moai-adk.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.

When should I use Moai Ref SEO?

Moai Ref SEO fits situations like: tasks that involve Schema markup; tasks that involve Technical SEO; tasks that involve UI design.

How do I install Moai Ref SEO in Claude Code?

Run `npx skills add modu-ai/moai-adk --skill moai-ref-seo -a claude-code`. Or copy the skill folder (.claude/skills/moai-ref-seo in modu-ai/moai-adk) into .claude/skills/moai-ref-seo in your project. Claude Code loads it when a task matches its description.

How do I install Moai Ref SEO in Codex?

Run `npx skills add modu-ai/moai-adk --skill moai-ref-seo -a codex`. Or copy the skill folder (.claude/skills/moai-ref-seo in modu-ai/moai-adk) into .agents/skills/moai-ref-seo in your project. Codex loads it when a task matches its description.

Can I use Moai Ref SEO in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add modu-ai/moai-adk --skill moai-ref-seo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/moai-ref-seo, .gemini/skills/moai-ref-seo, .github/skills/moai-ref-seo and .opencode/skills/moai-ref-seo in your project.

What does Moai Ref SEO need to run?

SKILL.md names no scripts, command-line tools or credentials: Moai Ref SEO is instructions for the agent only.

Does Moai Ref SEO access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Moai Ref SEO safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Moai Ref SEO use?

Moai Ref SEO is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Moai Ref SEO use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Moai Ref SEO?

Skills that share tags, products or a category with Moai Ref SEO: Universal SEO Analysis (AgriciDaniel/claude-seo, 19k stars), Generative Engine Optimization (tech-leads-club/agent-skills, 7k stars), SEO Geo (ericrisco/rsc-harness, 174 stars) and SEO AI Optimizer (luongnv89/skills, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Moai Ref SEO?

modu-ai (a GitHub organization) maintains it in modu-ai/moai-adk, which has 1,232 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 9, 2026.

Source: modu-ai/moai-adk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.