moai-ref-seo

Reviews web pages for canonical URLs, metadata uniqueness, JSON-LD structured data, and crawlability.

1.2k|222|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/modu-ai/moai-adk --skill moai-ref-seo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-ref-seo
Source: https://github.com/modu-ai/moai-adk/tree/main/internal/template/templates/.claude/skills/moai-ref-seo
Command: npx skills add https://github.com/modu-ai/moai-adk --skill moai-ref-seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pages often ship with duplicate titles, conflicting canonical addresses, hardcoded hosts in robots.txt, and structured data that contradicts visible content, causing search engines to misindex or ignore them. This Skill provides a decision-rule reference for auditing and fixing search visibility and crawlability defects before deployment.

Core Features & Use Cases

  • Canonical and Identity Rules: Enforces one address per resource with redirect discipline, trailing-slash normalization, and parameter handling.
  • Metadata and Structured Data Auditing: Checks per-page title and meta description uniqueness, JSON-LD type selection, absolute addresses, and the mirroring rule that every serialized claim has a visible counterpart.
  • Crawl Artifact Generation: Guides host-derived robots.txt and sitemap.xml output so every environment serves a correct description of itself.
  • Use Case: Before shipping a marketing site, run a pre-ship review that fetches each route's canonical declaration, collects titles across all routes to detect duplicates, and validates that JSON-LD entity names match the visible page copy.

Quick Start

Ask the agent to audit the rendered pages of the site for canonical URL consistency, duplicate titles and meta descriptions, JSON-LD claims without visible counterparts, and host-derived robots.txt and sitemap.xml correctness.

Frequently Asked Questions about moai-ref-seo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a website for SEO issues before launch?

Fetch each route's canonical declaration and confirm it returns the same page without redirects, collect titles and meta descriptions across all routes to detect duplicates, and validate that JSON-LD parses with absolute addresses and visible counterparts for every claim.

How to set canonical URLs correctly for a website?

Pick one address form per resource, declare it, and redirect all variants permanently to it. The declared value must equal the address actually served, and parameterized routes must build the declaration from resolved parameters rather than a fixed string.

Why does duplicate title and meta description hurt indexing?

A default or copied value is identical on every route by construction, while uniqueness is the entire purpose of these fields. Duplicate metadata leaves pages indistinguishable in search results and signals scaffold defaults surviving to production.

Should robots.txt and sitemap.xml be hardcoded per environment?

No. Derive the absolute addresses in robots.txt from the incoming request's host and enumerate only routes actually served in sitemap.xml. A hardcoded host is correct in exactly one environment and wrong everywhere else, including the one that gets indexed.

What are the limits of JSON-LD structured data for SEO?

Every claim in serialized data needs a visible counterpart on the same page; assertions existing only in markup are scored as negative signals. Relative addresses are discarded, and repeating a page-specific type site-wide dilutes rather than reinforces it.