/seo-hreflang
Use when auditing or generating hreflang tags for i18n/multilingual SEO.
$ npx -y skills add fusengine/agents --skill seo-hreflang --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/seo-hreflang
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when auditing or generating hreflang tags for i18n/multilingual SEO.
SKILL.md
seo-hreflang.SKILL.mdname: seo-hreflang
description: Use when auditing or generating hreflang tags for i18n/multilingual SEO.
user-invocable: false
related-skills: seo, seo-technical, seo-sitemap
<objective> Audits or generates hreflang across all three implementation surfaces — HTML `<link>` tags, HTTP headers, and XML sitemap `<xhtml:link>` entries — validating self-referencing, return tags, x-default, and ISO 639-1 + ISO 3166-1 code correctness via `scripts/parse-hreflang.ts`. Lists the common mistakes: missing self-reference, missing return tags, invalid region codes (`en-UK` vs `en-GB`), HTTP/HTTPS mismatch between alternates, and trailing-slash inconsistency. </objective>
Hreflang / i18n SEO
Workflow
1. Detect hreflang tags (HTML `<link>`, HTTP header, or XML sitemap) 2. Run `scripts/parse-hreflang.ts` → validate 3. Check self-referencing, return tags, x-default 4. Verify language/region codes (ISO 639-1 + ISO 3166-1)
Common Mistakes
- ❌ Missing self-reference (`<link rel="alternate" hreflang="fr" href="/fr/">` from `/fr/`)
- ❌ Missing return tags (A → B but not B → A)
- ❌ Invalid codes (`en-UK` instead of `en-GB`)
- ❌ HTTP/HTTPS mismatch between alternates
- ❌ Mixing trailing slashes
Implementation Options
1. **HTML head**: `<link rel="alternate" hreflang="fr-FR" href="https://example.com/fr/">` 2. **HTTP Header**: `Link: <https://example.com/fr/>; rel="alternate"; hreflang="fr-FR"` 3. **XML Sitemap**: `<xhtml:link rel="alternate" hreflang="fr-FR" href="https://example.com/fr/"/>`
x-default
Required for international landing/locale selector pages:
<link rel="alternate" hreflang="x-default" href="https://example.com/">
Read more
name: seo-hreflang description: Use when auditing or generating hreflang tags for i18n/multilingual SEO. user-invocable: false related-skills: seo, seo-technical, seo-sitemap
<objective> Audits or generates hreflang across all three implementation surfaces — HTML `<link>` tags, HTTP headers, and XML sitemap `<xhtml:link>` entries — validating self-referencing, return tags, x-default, and ISO 639-1 + ISO 3166-1 code correctness via `scripts/parse-hreflang.ts`. Lists the common mistakes: missing self-reference, missing return tags, invalid region codes (`en-UK` vs `en-GB`), HTTP/HTTPS mismatch between alternates, and trailing-slash inconsistency. </objective>
Hreflang / i18n SEO
Workflow
1. Detect hreflang tags (HTML `<link>`, HTTP header, or XML sitemap) 2. Run `scripts/parse-hreflang.ts` → validate 3. Check self-referencing, return tags, x-default 4. Verify language/region codes (ISO 639-1 + ISO 3166-1)
Common Mistakes
- ❌ Missing self-reference (`<link rel="alternate" hreflang="fr" href="/fr/">` from `/fr/`)
- ❌ Missing return tags (A → B but not B → A)
- ❌ Invalid codes (`en-UK` instead of `en-GB`)
- ❌ HTTP/HTTPS mismatch between alternates
- ❌ Mixing trailing slashes
Implementation Options
1. **HTML head**: `<link rel="alternate" hreflang="fr-FR" href="https://example.com/fr/">` 2. **HTTP Header**: `Link: <https://example.com/fr/>; rel="alternate"; hreflang="fr-FR"` 3. **XML Sitemap**: `<xhtml:link rel="alternate" hreflang="fr-FR" href="https://example.com/fr/"/>`
x-default
Required for international landing/locale selector pages:
<link rel="alternate" hreflang="x-default" href="https://example.com/">
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill

