What does this skill do, and when should you use it?
This is the standalone hreflang and international SEO skill in the Claude SEO repository. It focuses on multilingual and multi-region websites, checking self-references, return tags, x-default, language and region codes, canonical alignment, protocol consistency, and cross-domain relationships. It can generate HTML, HTTP header, or XML sitemap implementations. Additional reference files support cultural adaptation, content parity, and locale-format analysis when needed.
Reads a site URL or content directory, detects language versions and page equivalents, validates hreflang tags and ISO 639-1/ISO 3166-1 codes, and checks canonical URLs, protocols, trailing slashes, bidirectional links, and x-default. It produces HTML link tags, HTTP header values, or hreflang XML sitemaps with the required xhtml namespace, plus severity-based findings and recommendations. On demand, it loads cultural-profiles.md, locale-formats.md, and content-parity.md for cultural adaptation, number/date/currency formatting, and multilingual content-parity audits.
- An international SEO consultant audits a multilingual site for missing self-referencing tags and incomplete return links.
- A team migrating to HTTPS needs to identify mixed-protocol hreflang URLs and canonical mismatches.
- A large cross-domain site wants to move from page-level HTML tags to centrally maintained XML sitemaps.
- A content team compares translated pages for title, metadata, structure, word-count, freshness, and localization parity.
How do you install this skill?
- Do not treat x-default as universally mandatory for every hreflang set; verify the current official search-engine guidance before implementation.
- The skill does not clearly document network boundaries, redirect/SSRF protection, authenticated-page handling, or sensitive-data handling for URL fetching.
- Parity, cultural adaptation, and machine-translation checks depend on additional references and live-fetch capabilities; none were executed in this static review.
- Chinese coverage is limited mainly to locale-format data and lacks a Chinese cultural profile; mainland-China language, legal, and reachability assumptions require separate validation.
- Network access
- Local filesystem
Install the complete AgriciDaniel/claude-seo repository, which includes this skill. For Claude Code 1.0.33+, run /plugin marketplace add AgriciDaniel/claude-seo, then /plugin install claude-seo@agricidaniel-claude-seo. Alternatively, run git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git followed by bash claude-seo/install.sh. The source does not document a standalone installation procedure for skills/seo-hreflang/.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/seo-hreflang" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
In Claude Code, run /seo hreflang <url> for an audit or generation workflow. For content parity, use /seo hreflang audit <directory-or-url>. You can also provide a URL and ask for an hreflang, international SEO, multilingual, or multi-region analysis.
What are this skill's strengths and limitations?
- Covers HTML, HTTP header, and XML sitemap implementations.
- Checks self-references, return links, x-default, code validity, canonical URLs, protocols, and cross-domain setup.
- Generates implementation-ready tags, headers, or sitemap XML with severity-based reporting.
- Provides extension paths for cultural adaptation, content parity, and locale formatting.
- Cultural, content-parity, and locale-format analysis depends on additional reference files whose contents are not included here.
- The source provides no separate test-count or independent platform-coverage evidence for this skill.
- Cross-domain validation requires both domains to be verified in Google Search Console; the skill does not document that verification process.
- When a URL is unreachable, it reports the error instead of inferring the site's structure.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| International SEO Hreflang Auditor this page | 51 · Use with care | ★ 19k | 23d ago | MIT |
| Sitemap Inspector & Builder | 50 · Use with care | ★ 19k | 23d ago | MIT |
| SEO Audit (Basic) Skill | 57 · Use with care | ★ 765 | 4mo ago | MIT |
| Multilingual Blog Publisher | 55 · Use with care | ★ 2.4k | 13d ago | MIT |
| Full-Site SEO Audit | 53 · Use with care | ★ 19k | 23d ago | MIT |
Choose the implementation method by scale and file type: HTML link tags suit pages with fewer than 50 language or region variants; HTTP headers suit non-HTML files such as PDFs; XML sitemaps suit large sites, cross-domain setups, or sites with 50+ pages. The source recommends sitemap-based implementation for large sites.
How did FollowSkills review this skill?
The skill is primarily for auditing, validation, and code generation, with no evident malware, credential theft, or destructive default. However, it does not disclose URL-fetching data flows, network permissions, cross-domain risks, user confirmation, or rollback boundaries, so 8 points are deducted.
It provides validation rules, a generation workflow, output templates, and several abnormal-input responses. It lacks path-specific scripts, tests, or reproducible key-path evidence, and some rules such as treating x-default as required are over-absolute; the score is therefore constrained by static calibration and reduced.
Triggers, URL input, HTML/HTTP-header/XML-sitemap outputs, and international-SEO scenarios are reasonably clear. Non-fit boundaries, runtime assumptions, Chinese cultural coverage, and mainland-China reachability are under-specified, while some functions depend on fetching URLs or loading additional references, so 7 points are deducted.
The skill has useful metadata, readable sections, progressive on-demand references, examples, error handling, and MIT licensing. It lacks an independent changelog, explicit maintenance ownership, dependency/install notes, and a clear update path, so 6 points are deducted.
The checklist, generation process, templates, and report format can directly support basic hreflang work. However, some normative statements may produce incorrect recommendations, cultural and parity scoring depend on unshown runtime capabilities, and no representative path-specific output is verified; the score is reduced and capped by static calibration.
The document contains concrete checks, examples, reference materials, and some external-source pointers. It has no path-specific test suite, revision-pinned execution evidence, or systematic corroboration across sources, so 6 points are deducted and the score remains within the static ceiling.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →