[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PRZ5YZHBMAKZDY2EBCBNMF":3,"skill-same:01M6PRZ5YZHBMAKZDY2EBCBNMF":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":14,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":6,"updatedAt":66,"install":67,"resources":79},"01M6PRZ5YZHBMAKZDY2EBCBNMF","seo-hreflang",null,"Hreflang and international SEO audit, validation, and generation. Detects common mistakes, validates language\u002Fregion codes, and generates correct hreflang implementations. Use when user says \"hreflang\", \"i18n SEO\", \"international SEO\", \"multi-language\", \"multi-region\", or \"language tags\".","headmktlucca-ui\u002Fneuroads-lp","headmktlucca-ui","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F247379838?v=4","01M6PDVAV6M1W96D1SR1PDF8CS","NeuroAds","01M6PDVAZ4P281GNDKD45CYTF5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-hreflang\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"seo","seo hreflang","international","mistakes","true","URL","multi-language","international seo","multi","codes","tags","generation","validation","i18n","language","use","common","correct","seo audit","audit","2026-11-10 10:12:30",false,"---\nname: seo-hreflang\ndescription: >\n  Hreflang and international SEO audit, validation, and generation. Detects\n  common mistakes, validates language\u002Fregion codes, and generates correct\n  hreflang implementations. Use when user says \"hreflang\", \"i18n SEO\",\n  \"international SEO\", \"multi-language\", \"multi-region\", or \"language tags\".\nuser-invocable: true\nargument-hint: \"[url]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  version: \"2.2.0\"\n  category: seo\n---\n\n# Hreflang & International SEO\n\nValidate existing hreflang implementations or generate correct hreflang tags\nfor multi-language and multi-region sites. Supports HTML, HTTP header, and\nXML sitemap implementations.\n\n## Validation Checks\n\n### 1. Self-Referencing Tags\n- Every page must include an hreflang tag pointing to itself\n- The self-referencing URL must exactly match the page's canonical URL\n- Missing self-referencing tags cause Google to ignore the entire hreflang set\n\n### 2. Return Tags\n- If page A links to page B with hreflang, page B must link back to page A\n- Every hreflang relationship must be bidirectional (A→B and B→A)\n- Missing return tags invalidate the hreflang signal for both pages\n- Check all language versions reference each other (full mesh)\n\n### 3. x-default Tag\n- Required: designates the fallback page for unmatched languages\u002Fregions\n- Typically points to the language selector page or English version\n- Only one x-default per set of alternates\n- Must also have return tags from all other language versions\n\n### 4. Language Code Validation\n- Must use ISO 639-1 two-letter codes (e.g., `en`, `fr`, `de`, `ja`)\n- Common errors:\n  - `eng` instead of `en` (ISO 639-2, not valid for hreflang)\n  - `jp` instead of `ja` (incorrect code for Japanese)\n  - `zh` without region qualifier (ambiguous; use `zh-Hans` or `zh-Hant`)\n\n### 5. Region Code Validation\n- Optional region qualifier uses ISO 3166-1 Alpha-2 (e.g., `en-US`, `en-GB`, `pt-BR`)\n- Format: `language-REGION` (lowercase language, uppercase region)\n- Common errors:\n  - `en-uk` instead of `en-GB` (UK is not a valid ISO 3166-1 code)\n  - `es-LA` (Latin America is not a country; use specific countries)\n  - Region without language prefix\n\n### 6. Canonical URL Alignment\n- Hreflang tags must only appear on canonical URLs\n- If a page has `rel=canonical` pointing elsewhere, hreflang on that page is ignored\n- The canonical URL and hreflang URL must match exactly (including trailing slashes)\n- Non-canonical pages should not be in any hreflang set\n\n### 7. Protocol Consistency\n- All URLs in an hreflang set must use the same protocol (HTTPS or HTTP)\n- Mixed HTTP\u002FHTTPS in hreflang sets causes validation failures\n- After HTTPS migration, update all hreflang tags to HTTPS\n\n### 8. Cross-Domain Support\n- Hreflang works across different domains (e.g., example.com and example.de)\n- Cross-domain hreflang requires return tags on both domains\n- Verify both domains are verified in Google Search Console\n- Sitemap-based implementation recommended for cross-domain setups\n\n## Common Mistakes\n\n| Issue | Severity | Fix |\n|-------|----------|-----|\n| Missing self-referencing tag | Critical | Add hreflang pointing to same page URL |\n| Missing return tags (A→B but no B→A) | Critical | Add matching return tags on all alternates |\n| Missing x-default | High | Add x-default pointing to fallback\u002Fselector page |\n| Invalid language code (e.g., `eng`) | High | Use ISO 639-1 two-letter codes |\n| Invalid region code (e.g., `en-uk`) | High | Use ISO 3166-1 Alpha-2 codes |\n| Hreflang on non-canonical URL | High | Move hreflang to canonical URL only |\n| HTTP\u002FHTTPS mismatch in URLs | Medium | Standardize all URLs to HTTPS |\n| Trailing slash inconsistency | Medium | Match canonical URL format exactly |\n| Hreflang in both HTML and sitemap | Low | Choose one method (sitemap preferred for large sites) |\n| Language without region when needed | Low | Add region qualifier for geo-targeted content |\n\n## Implementation Methods\n\n### Method 1: HTML Link Tags\nBest for: Sites with \u003C50 language\u002Fregion variants per page.\n\n```html\n\u003Clink rel=\"alternate\" hreflang=\"en-US\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n\u003Clink rel=\"alternate\" hreflang=\"en-GB\" href=\"https:\u002F\u002Fexample.co.uk\u002Fpage\" \u002F>\n\u003Clink rel=\"alternate\" hreflang=\"fr\" href=\"https:\u002F\u002Fexample.com\u002Ffr\u002Fpage\" \u002F>\n\u003Clink rel=\"alternate\" hreflang=\"x-default\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n```\n\nPlace in `\u003Chead>` section. Every page must include all alternates including itself.\n\n### Method 2: HTTP Headers\nBest for: Non-HTML files (PDFs, documents).\n\n```\nLink: \u003Chttps:\u002F\u002Fexample.com\u002Fpage>; rel=\"alternate\"; hreflang=\"en-US\",\n      \u003Chttps:\u002F\u002Fexample.com\u002Ffr\u002Fpage>; rel=\"alternate\"; hreflang=\"fr\",\n      \u003Chttps:\u002F\u002Fexample.com\u002Fpage>; rel=\"alternate\"; hreflang=\"x-default\"\n```\n\nSet via server configuration or CDN rules.\n\n### Method 3: XML Sitemap (Recommended for large sites)\nBest for: Sites with many language variants, cross-domain setups, or 50+ pages.\n\nSee Hreflang Sitemap Generation section below.\n\n### Method Comparison\n| Method | Best For | Pros | Cons |\n|--------|----------|------|------|\n| HTML link tags | Small sites (\u003C50 variants) | Easy to implement, visible in source | Bloats `\u003Chead>`, hard to maintain at scale |\n| HTTP headers | Non-HTML files | Works for PDFs, images | Complex server config, not visible in HTML |\n| XML sitemap | Large sites, cross-domain | Scalable, centralized management | Not visible on page, requires sitemap maintenance |\n\n## Hreflang Generation\n\n### Process\n1. **Detect languages**: Scan site for language indicators (URL path, subdomain, TLD, HTML lang attribute)\n2. **Map page equivalents**: Match corresponding pages across languages\u002Fregions\n3. **Validate language codes**: Verify all codes against ISO 639-1 and ISO 3166-1\n4. **Generate tags**: Create hreflang tags for each page including self-referencing\n5. **Verify return tags**: Confirm all relationships are bidirectional\n6. **Add x-default**: Set fallback for each page set\n7. **Output**: Generate implementation code (HTML, HTTP headers, or sitemap XML)\n\n## Hreflang Sitemap Generation\n\n### Sitemap with Hreflang\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\"?>\n\u003Curlset xmlns=\"http:\u002F\u002Fwww.sitemaps.org\u002Fschemas\u002Fsitemap\u002F0.9\"\n        xmlns:xhtml=\"http:\u002F\u002Fwww.w3.org\u002F1999\u002Fxhtml\">\n  \u003Curl>\n    \u003Cloc>https:\u002F\u002Fexample.com\u002Fpage\u003C\u002Floc>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"en-US\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"fr\" href=\"https:\u002F\u002Fexample.com\u002Ffr\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"de\" href=\"https:\u002F\u002Fexample.de\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"x-default\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n  \u003C\u002Furl>\n  \u003Curl>\n    \u003Cloc>https:\u002F\u002Fexample.com\u002Ffr\u002Fpage\u003C\u002Floc>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"en-US\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"fr\" href=\"https:\u002F\u002Fexample.com\u002Ffr\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"de\" href=\"https:\u002F\u002Fexample.de\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"x-default\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n  \u003C\u002Furl>\n\u003C\u002Furlset>\n```\n\nKey rules:\n- Include the `xmlns:xhtml` namespace declaration\n- Every `\u003Curl>` entry must include ALL language alternates (including itself)\n- Each alternate must appear as a separate `\u003Curl>` entry with its own full set\n- Split at 50,000 URLs per sitemap file\n\n## Output\n\n### Hreflang Validation Report\n\n#### Summary\n- Total pages scanned: XX\n- Language variants detected: XX\n- Issues found: XX (Critical: X, High: X, Medium: X, Low: X)\n\n#### Validation Results\n| Language | URL | Self-Ref | Return Tags | x-default | Status |\n|----------|-----|----------|-------------|-----------|--------|\n| en-US | https:\u002F\u002F... | ✅ | ✅ | ✅ | ✅ |\n| fr | https:\u002F\u002F... | ❌ | ⚠️ | ✅ | ❌ |\n| de | https:\u002F\u002F... | ✅ | ❌ | ✅ | ❌ |\n\n### Generated Hreflang Tags\n- HTML `\u003Clink>` tags (if HTML method chosen)\n- HTTP header values (if header method chosen)\n- `hreflang-sitemap.xml` (if sitemap method chosen)\n\n### Recommendations\n- Missing implementations to add\n- Incorrect codes to fix\n- Method migration suggestions (e.g., HTML to sitemap for scale)\n\n## Cultural Adaptation Assessment\n\nWhen analyzing a multi-language site, go beyond technical hreflang validation to assess\nwhether the content is culturally adapted for each target market.\n\nLoad `references\u002Fcultural-profiles.md` for pre-built profiles (DACH, Francophone, Hispanic, Japanese).\n\n**Assessment steps:**\n1. Identify all language versions and their target markets\n2. Load the relevant cultural profile(s)\n3. Check CTAs match cultural expectations (direct vs indirect)\n4. Check trust signals are locale-appropriate (certifications, legal pages)\n5. Check for foreign brand references on localized pages\n6. Check number\u002Fdate\u002Fcurrency formatting consistency\n7. Flag cultural adaptation issues as Medium severity\n\n**Output:** Cultural Adaptation Score per language version (0-100) with specific findings.\n\n## Content Parity Audit\n\n**Command:** `\u002Fseo hreflang audit \u003Cdirectory-or-url>`\n\nAudit content parity across all language versions of a site or local content directory.\n\nLoad `references\u002Fcontent-parity.md` for the full parity matrix and scoring methodology.\n\n**What it checks:**\n- Page existence across all declared languages\n- Section structure equivalence (H2\u002FH3 count)\n- SEO element parity (title, meta, schema localization)\n- Word count ratio validation (DE should be 25-35% longer than EN, JA 10-25% shorter)\n- Freshness tracking (stale translations detected via timestamps)\n- Cultural marker scanning (foreign brands, wrong legal references, untranslated elements)\n\n**Output:** Parity matrix table with per-page scores and prioritized action items.\n\n## Locale Format Validation\n\nLoad `references\u002Flocale-formats.md` for number, date, currency, address, and phone format\nreference tables per locale.\n\n**Checks:**\n- Number format consistency (e.g., \"1,000.00\" should be \"1.000,00\" on de-DE pages)\n- Date format matches locale expectations\n- Currency symbols and placement correct for target market\n- Phone numbers use international format with correct country code\n\n## Reference Files\n\nLoad on-demand as needed (do NOT load all at startup):\n- `references\u002Fcultural-profiles.md`: DACH, Francophone, Hispanic, Japanese cultural adaptation profiles\n- `references\u002Flocale-formats.md`: Number, date, currency, address, phone format tables per locale\n- `references\u002Fcontent-parity.md`: Content parity audit methodology and scoring\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess site structure. Suggest the user verify the URL and try again. |\n| No hreflang tags found | Report the absence. Check for other internationalization signals (subdirectories, subdomains, ccTLDs) and recommend the appropriate hreflang implementation method. |\n| Invalid language\u002Fregion codes detected | List each invalid code with the correct replacement. Provide a corrected hreflang tag set ready to implement. |\n| Cultural profile not available for language | Use the Default Profile checklist from cultural-profiles.md. Note that assessment is based on general guidelines, not a pre-built profile. |\n| Content parity directory empty | Report that no content files were found. Suggest verifying the directory path or providing a URL for live site analysis. |\n","# Hreflang & International SEO\n\nValidate existing hreflang implementations or generate correct hreflang tags\nfor multi-language and multi-region sites. Supports HTML, HTTP header, and\nXML sitemap implementations.\n\n## Validation Checks\n\n### 1. Self-Referencing Tags\n- Every page must include an hreflang tag pointing to itself\n- The self-referencing URL must exactly match the page's canonical URL\n- Missing self-referencing tags cause Google to ignore the entire hreflang set\n\n### 2. Return Tags\n- If page A links to page B with hreflang, page B must link back to page A\n- Every hreflang relationship must be bidirectional (A→B and B→A)\n- Missing return tags invalidate the hreflang signal for both pages\n- Check all language versions reference each other (full mesh)\n\n### 3. x-default Tag\n- Required: designates the fallback page for unmatched languages\u002Fregions\n- Typically points to the language selector page or English version\n- Only one x-default per set of alternates\n- Must also have return tags from all other language versions\n\n### 4. Language Code Validation\n- Must use ISO 639-1 two-letter codes (e.g., `en`, `fr`, `de`, `ja`)\n- Common errors:\n  - `eng` instead of `en` (ISO 639-2, not valid for hreflang)\n  - `jp` instead of `ja` (incorrect code for Japanese)\n  - `zh` without region qualifier (ambiguous; use `zh-Hans` or `zh-Hant`)\n\n### 5. Region Code Validation\n- Optional region qualifier uses ISO 3166-1 Alpha-2 (e.g., `en-US`, `en-GB`, `pt-BR`)\n- Format: `language-REGION` (lowercase language, uppercase region)\n- Common errors:\n  - `en-uk` instead of `en-GB` (UK is not a valid ISO 3166-1 code)\n  - `es-LA` (Latin America is not a country; use specific countries)\n  - Region without language prefix\n\n### 6. Canonical URL Alignment\n- Hreflang tags must only appear on canonical URLs\n- If a page has `rel=canonical` pointing elsewhere, hreflang on that page is ignored\n- The canonical URL and hreflang URL must match exactly (including trailing slashes)\n- Non-canonical pages should not be in any hreflang set\n\n### 7. Protocol Consistency\n- All URLs in an hreflang set must use the same protocol (HTTPS or HTTP)\n- Mixed HTTP\u002FHTTPS in hreflang sets causes validation failures\n- After HTTPS migration, update all hreflang tags to HTTPS\n\n### 8. Cross-Domain Support\n- Hreflang works across different domains (e.g., example.com and example.de)\n- Cross-domain hreflang requires return tags on both domains\n- Verify both domains are verified in Google Search Console\n- Sitemap-based implementation recommended for cross-domain setups\n\n## Common Mistakes\n\n| Issue | Severity | Fix |\n|-------|----------|-----|\n| Missing self-referencing tag | Critical | Add hreflang pointing to same page URL |\n| Missing return tags (A→B but no B→A) | Critical | Add matching return tags on all alternates |\n| Missing x-default | High | Add x-default pointing to fallback\u002Fselector page |\n| Invalid language code (e.g., `eng`) | High | Use ISO 639-1 two-letter codes |\n| Invalid region code (e.g., `en-uk`) | High | Use ISO 3166-1 Alpha-2 codes |\n| Hreflang on non-canonical URL | High | Move hreflang to canonical URL only |\n| HTTP\u002FHTTPS mismatch in URLs | Medium | Standardize all URLs to HTTPS |\n| Trailing slash inconsistency | Medium | Match canonical URL format exactly |\n| Hreflang in both HTML and sitemap | Low | Choose one method (sitemap preferred for large sites) |\n| Language without region when needed | Low | Add region qualifier for geo-targeted content |\n\n## Implementation Methods\n\n### Method 1: HTML Link Tags\nBest for: Sites with \u003C50 language\u002Fregion variants per page.\n\n```html\n\u003Clink rel=\"alternate\" hreflang=\"en-US\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n\u003Clink rel=\"alternate\" hreflang=\"en-GB\" href=\"https:\u002F\u002Fexample.co.uk\u002Fpage\" \u002F>\n\u003Clink rel=\"alternate\" hreflang=\"fr\" href=\"https:\u002F\u002Fexample.com\u002Ffr\u002Fpage\" \u002F>\n\u003Clink rel=\"alternate\" hreflang=\"x-default\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n```\n\nPlace in `\u003Chead>` section. Every page must include all alternates including itself.\n\n### Method 2: HTTP Headers\nBest for: Non-HTML files (PDFs, documents).\n\n```\nLink: \u003Chttps:\u002F\u002Fexample.com\u002Fpage>; rel=\"alternate\"; hreflang=\"en-US\",\n      \u003Chttps:\u002F\u002Fexample.com\u002Ffr\u002Fpage>; rel=\"alternate\"; hreflang=\"fr\",\n      \u003Chttps:\u002F\u002Fexample.com\u002Fpage>; rel=\"alternate\"; hreflang=\"x-default\"\n```\n\nSet via server configuration or CDN rules.\n\n### Method 3: XML Sitemap (Recommended for large sites)\nBest for: Sites with many language variants, cross-domain setups, or 50+ pages.\n\nSee Hreflang Sitemap Generation section below.\n\n### Method Comparison\n| Method | Best For | Pros | Cons |\n|--------|----------|------|------|\n| HTML link tags | Small sites (\u003C50 variants) | Easy to implement, visible in source | Bloats `\u003Chead>`, hard to maintain at scale |\n| HTTP headers | Non-HTML files | Works for PDFs, images | Complex server config, not visible in HTML |\n| XML sitemap | Large sites, cross-domain | Scalable, centralized management | Not visible on page, requires sitemap maintenance |\n\n## Hreflang Generation\n\n### Process\n1. **Detect languages**: Scan site for language indicators (URL path, subdomain, TLD, HTML lang attribute)\n2. **Map page equivalents**: Match corresponding pages across languages\u002Fregions\n3. **Validate language codes**: Verify all codes against ISO 639-1 and ISO 3166-1\n4. **Generate tags**: Create hreflang tags for each page including self-referencing\n5. **Verify return tags**: Confirm all relationships are bidirectional\n6. **Add x-default**: Set fallback for each page set\n7. **Output**: Generate implementation code (HTML, HTTP headers, or sitemap XML)\n\n## Hreflang Sitemap Generation\n\n### Sitemap with Hreflang\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\"?>\n\u003Curlset xmlns=\"http:\u002F\u002Fwww.sitemaps.org\u002Fschemas\u002Fsitemap\u002F0.9\"\n        xmlns:xhtml=\"http:\u002F\u002Fwww.w3.org\u002F1999\u002Fxhtml\">\n  \u003Curl>\n    \u003Cloc>https:\u002F\u002Fexample.com\u002Fpage\u003C\u002Floc>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"en-US\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"fr\" href=\"https:\u002F\u002Fexample.com\u002Ffr\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"de\" href=\"https:\u002F\u002Fexample.de\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"x-default\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n  \u003C\u002Furl>\n  \u003Curl>\n    \u003Cloc>https:\u002F\u002Fexample.com\u002Ffr\u002Fpage\u003C\u002Floc>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"en-US\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"fr\" href=\"https:\u002F\u002Fexample.com\u002Ffr\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"de\" href=\"https:\u002F\u002Fexample.de\u002Fpage\" \u002F>\n    \u003Cxhtml:link rel=\"alternate\" hreflang=\"x-default\" href=\"https:\u002F\u002Fexample.com\u002Fpage\" \u002F>\n  \u003C\u002Furl>\n\u003C\u002Furlset>\n```\n\nKey rules:\n- Include the `xmlns:xhtml` namespace declaration\n- Every `\u003Curl>` entry must include ALL language alternates (including itself)\n- Each alternate must appear as a separate `\u003Curl>` entry with its own full set\n- Split at 50,000 URLs per sitemap file\n\n## Output\n\n### Hreflang Validation Report\n\n#### Summary\n- Total pages scanned: XX\n- Language variants detected: XX\n- Issues found: XX (Critical: X, High: X, Medium: X, Low: X)\n\n#### Validation Results\n| Language | URL | Self-Ref | Return Tags | x-default | Status |\n|----------|-----|----------|-------------|-----------|--------|\n| en-US | https:\u002F\u002F... | ✅ | ✅ | ✅ | ✅ |\n| fr | https:\u002F\u002F... | ❌ | ⚠️ | ✅ | ❌ |\n| de | https:\u002F\u002F... | ✅ | ❌ | ✅ | ❌ |\n\n### Generated Hreflang Tags\n- HTML `\u003Clink>` tags (if HTML method chosen)\n- HTTP header values (if header method chosen)\n- `hreflang-sitemap.xml` (if sitemap method chosen)\n\n### Recommendations\n- Missing implementations to add\n- Incorrect codes to fix\n- Method migration suggestions (e.g., HTML to sitemap for scale)\n\n## Cultural Adaptation Assessment\n\nWhen analyzing a multi-language site, go beyond technical hreflang validation to assess\nwhether the content is culturally adapted for each target market.\n\nLoad `references\u002Fcultural-profiles.md` for pre-built profiles (DACH, Francophone, Hispanic, Japanese).\n\n**Assessment steps:**\n1. Identify all language versions and their target markets\n2. Load the relevant cultural profile(s)\n3. Check CTAs match cultural expectations (direct vs indirect)\n4. Check trust signals are locale-appropriate (certifications, legal pages)\n5. Check for foreign brand references on localized pages\n6. Check number\u002Fdate\u002Fcurrency formatting consistency\n7. Flag cultural adaptation issues as Medium severity\n\n**Output:** Cultural Adaptation Score per language version (0-100) with specific findings.\n\n## Content Parity Audit\n\n**Command:** `\u002Fseo hreflang audit \u003Cdirectory-or-url>`\n\nAudit content parity across all language versions of a site or local content directory.\n\nLoad `references\u002Fcontent-parity.md` for the full parity matrix and scoring methodology.\n\n**What it checks:**\n- Page existence across all declared languages\n- Section structure equivalence (H2\u002FH3 count)\n- SEO element parity (title, meta, schema localization)\n- Word count ratio validation (DE should be 25-35% longer than EN, JA 10-25% shorter)\n- Freshness tracking (stale translations detected via timestamps)\n- Cultural marker scanning (foreign brands, wrong legal references, untranslated elements)\n\n**Output:** Parity matrix table with per-page scores and prioritized action items.\n\n## Locale Format Validation\n\nLoad `references\u002Flocale-formats.md` for number, date, currency, address, and phone format\nreference tables per locale.\n\n**Checks:**\n- Number format consistency (e.g., \"1,000.00\" should be \"1.000,00\" on de-DE pages)\n- Date format matches locale expectations\n- Currency symbols and placement correct for target market\n- Phone numbers use international format with correct country code\n\n## Reference Files\n\nLoad on-demand as needed (do NOT load all at startup):\n- `references\u002Fcultural-profiles.md`: DACH, Francophone, Hispanic, Japanese cultural adaptation profiles\n- `references\u002Flocale-formats.md`: Number, date, currency, address, phone format tables per locale\n- `references\u002Fcontent-parity.md`: Content parity audit methodology and scoring\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess site structure. Suggest the user verify the URL and try again. |\n| No hreflang tags found | Report the absence. Check for other internationalization signals (subdirectories, subdomains, ccTLDs) and recommend the appropriate hreflang implementation method. |\n| Invalid language\u002Fregion codes detected | List each invalid code with the correct replacement. Provide a corrected hreflang tag set ready to implement. |\n| Cultural profile not available for language | Use the Default Profile checklist from cultural-profiles.md. Note that assessment is based on general guidelines, not a pre-built profile. |\n| Content parity directory empty | Report that no content files were found. Suggest verifying the directory path or providing a URL for live site analysis. |\n",{"name":5,"license":15,"metadata":54,"description":57,"argument-hint":58,"user-invocable":59},{"author":55,"version":56,"category":29},"AgriciDaniel","2.2.0","Hreflang and international SEO audit, validation, and generation. Detects common mistakes, validates language\u002Fregion codes, and generates correct hreflang implementations. Use when user says \"hreflang\", \"i18n SEO\", \"international SEO\", \"multi-language\", \"multi-region\", or \"language tags\".\n","[url]",true,"main","7a940b8e5af16c95e5c190a524421d32fc7445a9",".claude\u002Fskills\u002Fseo-hreflang","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui","https:\u002F\u002Fneuroads.com.br","2026-08-12 00:42:44",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":59},[69,72,75],{"tool":70,"command":71},"npx","npx skills add headmktlucca-ui\u002Fneuroads-lp --skill seo-hreflang",{"tool":73,"command":74},"bunx","bunx skills add headmktlucca-ui\u002Fneuroads-lp --skill seo-hreflang",{"tool":76,"command":77},"pnpm","pnpm dlx skills add headmktlucca-ui\u002Fneuroads-lp --skill seo-hreflang","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-hreflang\u002FSKILL.md",[80,86,92,96,100],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"LICENSE.txt","LICENSE","许可证",143,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-hreflang\u002FLICENSE.txt",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fcontent-parity.md","REFERENCE","参考文档",4129,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-hreflang\u002Freferences\u002Fcontent-parity.md",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fcultural-profiles.md",4942,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-hreflang\u002Freferences\u002Fcultural-profiles.md",{"path":97,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Flocale-formats.md",3521,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-hreflang\u002Freferences\u002Flocale-formats.md",{"path":101,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fmachine-translation-qa.md",2780,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-hreflang\u002Freferences\u002Fmachine-translation-qa.md",[105,128,153,179,196,229],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":117,"publishedAt":49},"01M6PTDCZTXTGSTX4RFK901YSZ","xunit-skill","Generates xUnit.net tests in C#. Covers Fact\u002FTheory, constructor injection, IClassFixture, and FluentAssertions. Use when user mentions \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal\", \"C# xUnit\". Triggers on: \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal C#\", \"xUnit.net\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxunit-skill\u002FSKILL.md",[111,114],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[118,119,120,121,122,44,123,124,125,126,127],"xunit","xunit skill","testing","injection","user","tests","triggers","unit","unit-testing","C#",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":136,"publishedAt":49},"01M6PTCB59ZTG5FTMWGPYEMMBP","xcuitest-skill","Generates XCUITest UI tests for iOS\u002FiPadOS apps in Swift. Apple's native testing framework for reliable, fast UI automation. Supports local simulators and TestMu AI cloud real devices. Use when user mentions \"XCUITest\", \"XCTest\", \"iOS UI test\", \"Swift test\", \"XCUIApplication\". Triggers on: \"XCUITest\", \"XCTest UI\", \"iOS UI test\", \"Swift UI test\", \"XCUIApplication\", \"TestMu\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxcuitest-skill\u002FSKILL.md",[134,135],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},[137,138,120,139,140,141,142,143,44,144,145,146,147,148,123,124,149,150,151,152],"xcuitest","xcuitest skill","automation","test","testing framework","ios","devices","mobile","mobile-testing","ui test","local","apple","apps","native","for","objective",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":163,"publishedAt":49},"01M6PTATMNTY9NF4J7KSR76YK6","world-builder","Create and manage generative game zones for Dorothy's Pokemon-style world. Use this skill when creating, updating, or designing game worlds via MCP tools.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworld-builder\u002FSKILL.md",[159,162],{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},[164,165,166,167,168,169,170,171,44,172,173,174,175,176,177,151,178],"builder","world","world builder","MCP","create","mcp tools","Tools","game","pokemon","manage","style","via","theme","zone","generative",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":187,"publishedAt":49},"01M6PT9Z92JTSQEHE1QR0NNW5F","webdriverio-skill","Generates WebdriverIO (WDIO) automation tests in JavaScript or TypeScript. Supports local and TestMu AI cloud. Use when user mentions \"WebdriverIO\", \"WDIO\", \"wdio.conf\", \"browser.url\", \"$\", \"$$\". Triggers on: \"WebdriverIO\", \"WDIO\", \"wdio\", \"browser.$\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebdriverio-skill\u002FSKILL.md",[185,186],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},[188,120,189,139,190,191,192,193,122,44,194,147,123,124,34,195],"webdriverio skill","typescript","javascript","browser","cloud","e2e","e2e-testing","conf",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":209,"publishedAt":49},"01M6PT9NVK36ZWCQ69YXK3FR4K","web-design-guidelines","Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb\u002FSKILL.md",[202,205,206],{"categoryNo":203,"categoryName":204,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":207,"categoryName":208,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,124,228],"design","web","guidelines","web design guidelines","web design","css","performance","components","web components","tasks","code","web performance","ui","platform design","html","responsive design","responsive","platform","implementing",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":237,"publishedAt":49},"01M6PT9A3JKRE3X34276F2FW5R","watchos-design-guidelines","Apple Human Interface Guidelines for Apple Watch. Use when building watchOS apps, complications, or workout features. Triggers on tasks involving Watch UI, Digital Crown, glanceable interfaces, or wrist-based interactions.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwatchos\u002FSKILL.md",[235,236],{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":207,"categoryName":208,"taxonomyType":26,"taxonomyTypeDesc":27},[210,212,238,219,222,44,239,240,148,227,241,124,149,242,151,243,244],"watchos design guidelines","workout","human","watch","interface","platform-design","features"]