Seo Hreflang
Audit content parity and localized SEO signals across language versions before or after hreflang rollout.
Overview
SEO Hreflang is an agent skill most often used in Launch (also Grow) that audits content parity and localized SEO across multi-language site versions.
Install
npx skills add https://github.com/agricidaniel/claude-seo --skill seo-hreflangWhat is this skill?
- Content parity matrix across page existence, sections, FAQ, images, charts, word count, and schema
- Severity tiers: High for missing pages, schema, and non-localized titles; Medium for structure and meta
- Section structure variance allowed ±1 H2/H3; FAQ variance ±2 items; word count ±30% of language ratio
- Requires localized title tags and meta descriptions—not English leftovers on locale URLs
- Reference loaded when auditing multi-language sites for equivalent value and SEO signals
- Content parity matrix with 9 comparison dimensions and defined variance rules (±1 section, ±2 FAQ, ±30% word count)
Adoption & trust: 2.1k installs on skills.sh; 8.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You run multiple language versions but are unsure whether each locale offers equivalent content, metadata, and structured data for SEO and users.
Who is it for?
Indie SaaS, content sites, and ecommerce with hreflang or planned locale expansion needing a repeatable audit script for agents.
Skip if: Single-language sites, greenfield copywriting without existing locale URLs, or teams that only need hreflang tag syntax without content equivalence.
When should I use this skill?
Load when auditing content parity across language versions of a site for equivalent value and SEO signals.
What do I get? / Deliverables
You get a structured parity matrix with severities per dimension so you can fix missing pages, localization gaps, and schema mismatches before search engines devalue alternate URLs.
- Parity matrix with severity per dimension
- Gap list for missing or mismatched locale pages
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch is the canonical shelf for international SEO and hreflang correctness when pages go live in multiple locales. SEO subphase covers hreflang, localized titles, schema, and equivalent page structure across languages.
Where it fits
Before go-live, verify every declared hreflang pair has a matching page, localized title, and JSON-LD type.
After translating a pricing FAQ, confirm question counts and images match the English canonical within ±2 items.
Compare prototype locale landers for section structure before committing to full site mirror.
How it compares
A checker-style SEO reference for cross-locale parity, not a keyword research or single-page meta generator skill.
Common Questions / FAQ
Who is seo-hreflang for?
Solo builders and small growth teams managing multilingual sites who want agent-guided hreflang and content parity audits.
When should I use seo-hreflang?
At Launch before indexing new locales, during Grow when adding languages or updating FAQs, and whenever you need to verify localized titles, schema, and section parity across versions.
Is seo-hreflang safe to install?
It is primarily a reference audit framework; review the Security Audits panel on this page and apply findings in your own repo without executing untrusted third-party scripts.
SKILL.md
READMESKILL.md - Seo Hreflang
MIT License - see repository root LICENSE file for complete terms. Copyright (c) 2026 AgriciDaniel https://github.com/AgriciDaniel/claude-seo # Content Parity Audit for Multi-Language Sites Load this reference when auditing content parity across language versions of a site. Content parity ensures all language versions provide equivalent value and SEO signals. Original concept: Chris Muller (Pro Hub Challenge) ## Content Parity Matrix For each page that exists in multiple languages, check: | Dimension | What to Compare | Acceptable Variance | Severity if Failing | |-----------|----------------|--------------------|--------------------| | Page existence | Does equivalent page exist in all declared languages? | 0% — all declared languages must have the page | High | | Section structure | Same number of H2/H3 sections? | ±1 section allowed | Medium | | FAQ items | Same number of FAQ questions? | ±2 items allowed | Medium | | Images | Same number of images with localized alt text? | Must match exactly | Medium | | Charts/SVGs | Charts present in all versions? | Must match exactly | Low | | Word count | Proportional to language expansion ratio? | ±30% of expected ratio | Low | | Schema markup | JSON-LD present and localized in all versions? | Must match type and key properties | High | | Title tag | Localized with target keyword in local language? | Must be localized, not English | High | | Meta description | Localized and within character limits? | Must be localized | Medium | ## Freshness Tracking Detect stale translations by comparing: 1. **File modification timestamps**: If EN version was updated after DE version, DE may be stale 2. **Frontmatter dates**: Compare `date_modified` or `lastmod` across language versions 3. **Content hash comparison**: If the source language content hash changed since last translation Freshness delta thresholds: - **Fresh**: Translated within 7 days of source update → OK - **Aging**: 8-30 days since source update → Low priority update - **Stale**: 31-90 days since source update → Medium priority update - **Outdated**: 90+ days since source update → High priority update ## Word Count Ratio Validation Expected word count ratios vs English source: | Target Language | Expected Ratio | Acceptable Range | |----------------|---------------|-----------------| | German (DE) | 1.25-1.35x | 1.10-1.50x | | French (FR) | 1.15-1.25x | 1.00-1.40x | | Spanish (ES) | 1.15-1.25x | 1.00-1.40x | | Japanese (JA) | 0.75-0.90x | 0.60-1.00x | | Chinese (ZH) | 0.70-0.80x | 0.55-0.95x | A German translation that is shorter than the English original likely has missing content. A Japanese translation that is longer than English likely has unnecessary padding. ## Cultural Adaptation Quality Gates Beyond direct translation, check for cultural markers that indicate proper localization: | Check | What to Look For | Severity | |-------|-----------------|----------| | Foreign brand references | US-specific brands on non-US pages (e.g., "Walmart" on de-DE) | Medium | | Foreign statistics | US-only data cited on localized pages (e.g., "80% of Americans") | Medium | | CTA aggressiveness | Aggressive CTAs on formal-culture pages (e.g., "BUY NOW!" on ja-JP) | Low | | Legal references | Wrong jurisdiction laws cited (e.g., CCPA on de-DE instead of DSGVO) | High | | Currency/unit mismatch | USD prices on EUR pages, imperial units on metric pages | High | | Untranslated elements | English text remaining in navigation, buttons, alt text, schema | Medium | ## Parity Score Calculation Score out of 100: - Page existence parity: 30 points - SEO element parity (title, meta, schema): 30 points - Content structure parity (sections, images, FAQ): 25 points - Freshness parity: 15 points Interpretation: - 90-100: Excellent parity across all language versions - 70-89: Good parity with minor gaps to address - 50-69: Significant parity issues affecting some language versions - Below 50: Major parity failures requiring immediate attent