[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CT12R4B5ESP0T03341EPTD":3,"skill-same:01M7CT12R4B5ESP0T03341EPTD":76},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":38,"updatedAt":39,"install":40,"resources":52},"01M7CT12R4B5ESP0T03341EPTD","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\".","peterish8\u002Fprats-skill-atlas","peterish8","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F181628466?v=4","01M7CHQAPN6X8D29E2Q8DW4BYF","Prathick Dhanes R","01M7CHQAQ7T42E6D8HH3CZH342",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-hreflang\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-hreflang\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.4\"\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- Recommended when a selector\u002Ffallback URL exists: 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- An **optional ISO 15924 script subtag** is the documented, official mechanism\n  for script: `zh-Hant` (Traditional) \u002F `zh-Hans` (Simplified). Script may\n  combine with a region, e.g. `zh-Hans-US` is valid (language + script + region).\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` is valid but ambiguous for script-specific pages; prefer `zh-Hans` or `zh-Hant` when targeting a script\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- A **country code alone is invalid**, you cannot specify a region without a\n  language (Google's own bad example is `be`, which is actually the Belarusian\n  *language* code, not Belgium).\n- Common errors:\n  - `en-uk` instead of `en-GB` (UK is not a valid ISO 3166-1 region code)\n  - `EU` \u002F `UN` as a region (not valid ISO 3166-1 values)\n  - `es-LA` (Latin America is not a country; use specific countries)\n  - Region without language prefix\n\n### 5b. Geo-targeting signal hierarchy\n- Practical locale-signal heuristic: **ccTLD > hreflang annotations >\n  server location\u002FIP > addresses\u002Flanguage\u002Fcurrency\u002FBusiness Profile**. Do not\n  present this as a confirmed Google ranking order. hreflang is a\n  **hint, not a directive**. Google **ignores** locational meta tags and\n  HTML geotargeting attributes.\n- The Search Console **International Targeting report and the manual\n  country-targeting setting were removed in 2022**, do **not** recommend setting\n  country targeting in GSC; hreflang is the remaining lever.\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- Use Google Search Console verification for monitoring or cross-site sitemap submission when needed\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 when fallback behavior is required | Medium | 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 whichever comes first: 50,000 URLs or 50MB uncompressed 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- Recommended when a selector\u002Ffallback URL exists: 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- An **optional ISO 15924 script subtag** is the documented, official mechanism\n  for script: `zh-Hant` (Traditional) \u002F `zh-Hans` (Simplified). Script may\n  combine with a region, e.g. `zh-Hans-US` is valid (language + script + region).\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` is valid but ambiguous for script-specific pages; prefer `zh-Hans` or `zh-Hant` when targeting a script\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- A **country code alone is invalid**, you cannot specify a region without a\n  language (Google's own bad example is `be`, which is actually the Belarusian\n  *language* code, not Belgium).\n- Common errors:\n  - `en-uk` instead of `en-GB` (UK is not a valid ISO 3166-1 region code)\n  - `EU` \u002F `UN` as a region (not valid ISO 3166-1 values)\n  - `es-LA` (Latin America is not a country; use specific countries)\n  - Region without language prefix\n\n### 5b. Geo-targeting signal hierarchy\n- Practical locale-signal heuristic: **ccTLD > hreflang annotations >\n  server location\u002FIP > addresses\u002Flanguage\u002Fcurrency\u002FBusiness Profile**. Do not\n  present this as a confirmed Google ranking order. hreflang is a\n  **hint, not a directive**. Google **ignores** locational meta tags and\n  HTML geotargeting attributes.\n- The Search Console **International Targeting report and the manual\n  country-targeting setting were removed in 2022**, do **not** recommend setting\n  country targeting in GSC; hreflang is the remaining lever.\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- Use Google Search Console verification for monitoring or cross-site sitemap submission when needed\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 when fallback behavior is required | Medium | 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 whichever comes first: 50,000 URLs or 50MB uncompressed 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":25,"description":29,"argument-hint":30,"user-invocable":31},{"author":26,"version":27,"category":28},"AgriciDaniel","2.2.4","seo","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","f1bcf88a052c2ccbb297666b33fb820cfd94ac71",".codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-hreflang",0,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas","https:\u002F\u002Fgithub.com\u002Fpeterish8","Building real-world products with clean UI, smart architecture, and privacy in mind. Frontend-focused, full-stack curious.","2026-10-15 19:02:31",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":31},[42,45,48],{"tool":43,"command":44},"npx","npx skills add peterish8\u002Fprats-skill-atlas --skill seo-hreflang",{"tool":46,"command":47},"bunx","bunx skills add peterish8\u002Fprats-skill-atlas --skill seo-hreflang",{"tool":49,"command":50},"pnpm","pnpm dlx skills add peterish8\u002Fprats-skill-atlas --skill seo-hreflang","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-hreflang\u002FSKILL.md",[53,58,64,68,72],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",143,{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fcontent-parity.md","REFERENCE","参考文档",4129,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-hreflang\u002Freferences\u002Fcontent-parity.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fcultural-profiles.md",4942,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-hreflang\u002Freferences\u002Fcultural-profiles.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Flocale-formats.md",3521,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-hreflang\u002Freferences\u002Flocale-formats.md",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fmachine-translation-qa.md",3381,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-hreflang\u002Freferences\u002Fmachine-translation-qa.md",[77,86,94,102,109,117],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":20},"01M7CTAZW9MHV3RWH2ZEKDQXG9","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftools-utilities\u002Fgeneral-purpose\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftools-utilities\u002Fgeneral-purpose\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":20},"01M7CT8MG7NB1JR67XYZ9EWW3B","seo-audit","Full website SEO audit with parallel subagent delegation. Crawls up to 500 pages, detects business type, delegates to up to 15 specialists (8 always + 7 conditional), generates health score. Use when user says audit, full SEO check, analyze my site, or website health check.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fseo-audit\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fseo-audit\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":20},"01M7CT87F6GQ0WAD393PKPAGGX","playwright","Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fplaywright\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7CT809RF90MG98MYEA97D8Z","gsap-performance","Official GSAP skill for performance — prefer transforms, avoid layout thrashing, will-change, batching. Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fgsap-performance\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":20},"01M7CT7Q4VD995JHZMQQFBZZV9","firecrawl-seo-audit","Audit a website's SEO with Firecrawl. Use when the user asks for an SEO audit, metadata and heading review, sitemap\u002Fsite-structure analysis, keyword opportunities, competitor SERP comparison, or prioritized search optimization recommendations.","ISC","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Ffirecrawl-seo-audit\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":20},"01M7CT7JRJFC5RAKJBAP0VS1CV","firecrawl-qa","QA test a live website with Firecrawl browser and scrape evidence. Use when the user wants exploratory QA, form testing, navigation\u002Flink checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Ffirecrawl-qa\u002FSKILL.md",[],[]]