New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Hreflang and International SEO

by AgriciDaniel in AgriciDaniel/claude-seo

Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.

MITAuto-check passedMarketing & SEO

Install Hreflang and International SEO

skills CLI
$ npx skills add AgriciDaniel/claude-seo --skill seo-hreflang -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AgriciDaniel/claude-seo seo-hreflang --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-hreflang .claude/skills/seo-hreflang && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
seo-hreflang
GitHub stars
19k
Used in
5 other repos
Token cost
~3.4k tokens
SKILL.md length
1,522 words
Files
6 (incl. references)
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.

  • Works in 8 steps: Self-Referencing Tags → Return Tags → x-default Tag → …
  • Auditing hreflang tags on a multilingual site
  • SKILL.md covers Validation Checks, Common Mistakes, Implementation Methods and Hreflang Generation, plus 6 more sections
  • Reaches sitemaps.org and w3.org

What it does

Hreflang implementations are checked in a fixed order. Every page needs a self-referencing tag that exactly matches its canonical URL, return links must be reciprocal across all language versions, and a single x-default may point to a selector or fallback page with return tags from the other versions. The skill works with HTML, HTTP header and XML sitemap formats and can also generate correct tags.

Code validation requires ISO 639-1 language codes, optionally with an ISO 15924 script subtag such as zh-Hans or zh-Hant, and ISO 3166-1 Alpha-2 regions in a language-REGION pattern. It catches mistakes like eng for en, jp for ja, en-uk for en-GB, EU or UN used as regions, es-LA, and a region with no language, noting that a country code alone is invalid.

A geo-targeting heuristic ranks country-code domains above hreflang annotations, then server location and local signals. Reference notes cover content parity between versions, cultural profiles, locale formats and machine translation quality checks.

When your agent uses it

  • Auditing hreflang tags on a multilingual site
  • Generating hreflang markup for a new regional version
  • Finding missing return tags or a bad x-default
  • Checking language and region codes before launch

Example prompts

  • “Audit the hreflang tags on our English and French pages for missing return links.”
  • “Generate hreflang tags for our English, German and Brazilian Portuguese pages.”
  • “Is en-uk valid in hreflang, and what should we use instead?”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Self-Referencing Tags
  2. Return Tags
  3. x-default Tag
  4. Language Code Validation
  5. Region Code Validation
  6. Canonical URL Alignment
  7. Protocol Consistency
  8. Cross-Domain Support

What it can do on your machine

Read from SKILL.md and the folder at commit 4b99de2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are html and xml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • sitemaps.org
    • w3.org

    Also links to:

    • developers.google.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hreflang and International SEO loads about 3.4k tokens when it runs, and up to ~7.5k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 1,522 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AgriciDaniel/claude-seo at commit 4b99de2, republished under its MIT licence (© AgriciDaniel). 1,522 words, ~3,448 tokens.

Download SKILL.mdSave it as .claude/skills/seo-hreflang/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
seo-hreflang
description
Hreflang and international SEO audit, validation, and generation. Detects common mistakes, validates language/region codes, and generates correct hreflang implementations. Use when user says "hreflang", "i18n SEO", "international SEO", "multi-language", "multi-region", or "language tags".
user-invocable
true
argument-hint
[url]
license
MIT
metadata.author
AgriciDaniel
metadata.version
2.4.2
metadata.category
seo

Hreflang & International SEO

Validate existing hreflang implementations or generate correct hreflang tags for multi-language and multi-region sites. Supports HTML, HTTP header, and XML sitemap implementations.

Validation Checks

1. Self-Referencing Tags
  • Every page must include an hreflang tag pointing to itself
  • The self-referencing URL must exactly match the page's canonical URL
  • Missing self-referencing tags cause Google to ignore the entire hreflang set
2. Return Tags
  • If page A links to page B with hreflang, page B must link back to page A
  • Every hreflang relationship must be bidirectional (A→B and B→A)
  • Missing return tags invalidate the hreflang signal for both pages
  • Check all language versions reference each other (full mesh)
3. x-default Tag
  • Recommended when a selector/fallback URL exists: designates the fallback page for unmatched languages/regions
  • Typically points to the language selector page or English version
  • Only one x-default per set of alternates
  • Must also have return tags from all other language versions
4. Language Code Validation
  • Must use ISO 639-1 two-letter codes (e.g., en, fr, de, ja)
  • An optional ISO 15924 script subtag is the documented, official mechanism for script: zh-Hant (Traditional) / zh-Hans (Simplified). Script may combine with a region, e.g. zh-Hans-US is valid (language + script + region).
  • Common errors:
    • eng instead of en (ISO 639-2, not valid for hreflang)
    • jp instead of ja (incorrect code for Japanese)
    • zh is valid but ambiguous for script-specific pages; prefer zh-Hans or zh-Hant when targeting a script
5. Region Code Validation
  • Optional region qualifier uses ISO 3166-1 Alpha-2 (e.g., en-US, en-GB, pt-BR)
  • Format: language-REGION (lowercase language, uppercase region)
  • A country code alone is invalid, you cannot specify a region without a language (Google's own bad example is be, which is actually the Belarusian language code, not Belgium).
  • Common errors:
    • en-uk instead of en-GB (UK is not a valid ISO 3166-1 region code)
    • EU / UN as a region (not valid ISO 3166-1 values)
    • es-LA (Latin America is not a country; use specific countries)
    • Region without language prefix
5b. Geo-targeting signal hierarchy
  • Practical locale-signal heuristic: ccTLD > hreflang annotations > server location/IP > addresses/language/currency/Business Profile. Do not present this as a confirmed Google ranking order. hreflang is a hint, not a directive. Google ignores locational meta tags and HTML geotargeting attributes.
  • The Search Console International Targeting report and the manual country-targeting setting were removed in 2022, do not recommend setting country targeting in GSC; hreflang is the remaining lever.
5c. Region-specific Search units (EEA, South Africa, Türkiye)
  • Google documents Search experiences that exist only in certain regions (documentation added 2026-09-08; https://developers.google.com/search/docs/appearance/aggregator-features):
    • EEA only: aggregator units and supplier units (hotels, flights, ground transportation, products, and since 2026-09-18 local businesses), the ecosystem carousel, and job-site features.
    • Türkiye: places-site features (hotels, local businesses).
    • South Africa: a badge and refinement chip for travel, products, car hire, food delivery and ground transportation.
    • Structured data carousels in all three, with different query types. Eligibility and participation are documented per unit; they are not ranking signals.
  • When a site serves those regions with hreflang variants, note in the report whether the business is an aggregator or a direct supplier and point to the regional documentation, so the client is not surprised by a different result layout in those markets.
6. Canonical URL Alignment
  • Hreflang tags must only appear on canonical URLs
  • If a page has rel=canonical pointing elsewhere, hreflang on that page is ignored
  • The canonical URL and hreflang URL must match exactly (including trailing slashes)
  • Non-canonical pages should not be in any hreflang set
7. Protocol Consistency
  • All URLs in an hreflang set must use the same protocol (HTTPS or HTTP)
  • Mixed HTTP/HTTPS in hreflang sets causes validation failures
  • After HTTPS migration, update all hreflang tags to HTTPS
8. Cross-Domain Support
  • Hreflang works across different domains (e.g., example.com and example.de)
  • Cross-domain hreflang requires return tags on both domains
  • Use Google Search Console verification for monitoring or cross-site sitemap submission when needed
  • Sitemap-based implementation recommended for cross-domain setups

Common Mistakes

IssueSeverityFix
Missing self-referencing tagCriticalAdd hreflang pointing to same page URL
Missing return tags (A→B but no B→A)CriticalAdd matching return tags on all alternates
Missing x-default when fallback behavior is requiredMediumAdd x-default pointing to fallback/selector page
Invalid language code (e.g., eng)HighUse ISO 639-1 two-letter codes
Invalid region code (e.g., en-uk)HighUse ISO 3166-1 Alpha-2 codes
Hreflang on non-canonical URLHighMove hreflang to canonical URL only
HTTP/HTTPS mismatch in URLsMediumStandardize all URLs to HTTPS
Trailing slash inconsistencyMediumMatch canonical URL format exactly
Hreflang in both HTML and sitemapLowChoose one method (sitemap preferred for large sites)
Language without region when neededLowAdd region qualifier for geo-targeted content

Implementation Methods

Best for: Sites with <50 language/region variants per page.

html
<link rel="alternate" hreflang="en-US" href="https://example.com/page" />
<link rel="alternate" hreflang="en-GB" href="https://example.co.uk/page" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page" />

Place in <head> section. Every page must include all alternates including itself.

Method 2: HTTP Headers

Best for: Non-HTML files (PDFs, documents).

Link: <https://example.com/page>; rel="alternate"; hreflang="en-US",
      <https://example.com/fr/page>; rel="alternate"; hreflang="fr",
      <https://example.com/page>; rel="alternate"; hreflang="x-default"

Set via server configuration or CDN rules.

Best for: Sites with many language variants, cross-domain setups, or 50+ pages.

See Hreflang Sitemap Generation section below.

Method Comparison
MethodBest ForProsCons
HTML link tagsSmall sites (<50 variants)Easy to implement, visible in sourceBloats <head>, hard to maintain at scale
HTTP headersNon-HTML filesWorks for PDFs, imagesComplex server config, not visible in HTML
XML sitemapLarge sites, cross-domainScalable, centralized managementNot visible on page, requires sitemap maintenance

Hreflang Generation

Show full SKILL.md (626 more words)Show less
Process
  1. Detect languages: Scan site for language indicators (URL path, subdomain, TLD, HTML lang attribute)
  2. Map page equivalents: Match corresponding pages across languages/regions
  3. Validate language codes: Verify all codes against ISO 639-1 and ISO 3166-1
  4. Generate tags: Create hreflang tags for each page including self-referencing
  5. Verify return tags: Confirm all relationships are bidirectional
  6. Add x-default: Set fallback for each page set
  7. Output: Generate implementation code (HTML, HTTP headers, or sitemap XML)

Hreflang Sitemap Generation

Sitemap with Hreflang
xml
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <url>
    <loc>https://example.com/page</loc>
    <xhtml:link rel="alternate" hreflang="en-US" href="https://example.com/page" />
    <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />
    <xhtml:link rel="alternate" hreflang="de" href="https://example.de/page" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/page" />
  </url>
  <url>
    <loc>https://example.com/fr/page</loc>
    <xhtml:link rel="alternate" hreflang="en-US" href="https://example.com/page" />
    <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />
    <xhtml:link rel="alternate" hreflang="de" href="https://example.de/page" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/page" />
  </url>
</urlset>

Key rules:

  • Include the xmlns:xhtml namespace declaration
  • Every <url> entry must include ALL language alternates (including itself)
  • Each alternate must appear as a separate <url> entry with its own full set
  • Split at whichever comes first: 50,000 URLs or 50MB uncompressed per sitemap file

Output

Hreflang Validation Report
Summary
  • Total pages scanned: XX
  • Language variants detected: XX
  • Issues found: XX (Critical: X, High: X, Medium: X, Low: X)
Validation Results
LanguageURLSelf-RefReturn Tagsx-defaultStatus
en-UShttps://...✅✅✅✅
frhttps://...❌⚠️✅❌
dehttps://...✅❌✅❌
Generated Hreflang Tags
  • HTML <link> tags (if HTML method chosen)
  • HTTP header values (if header method chosen)
  • hreflang-sitemap.xml (if sitemap method chosen)
Recommendations
  • Missing implementations to add
  • Incorrect codes to fix
  • Method migration suggestions (e.g., HTML to sitemap for scale)

Cultural Adaptation Assessment

When analyzing a multi-language site, go beyond technical hreflang validation to assess whether the content is culturally adapted for each target market.

Load references/cultural-profiles.md for pre-built profiles (DACH, Francophone, Hispanic, Japanese).

Assessment steps:

  1. Identify all language versions and their target markets
  2. Load the relevant cultural profile(s)
  3. Check CTAs match cultural expectations (direct vs indirect)
  4. Check trust signals are locale-appropriate (certifications, legal pages)
  5. Check for foreign brand references on localized pages
  6. Check number/date/currency formatting consistency
  7. Flag cultural adaptation issues as Medium severity

Output: Cultural Adaptation Score per language version (0-100) with specific findings.

Content Parity Audit

Command: /seo hreflang audit <directory-or-url>

Audit content parity across all language versions of a site or local content directory.

Load references/content-parity.md for the full parity matrix and scoring methodology.

What it checks:

  • Page existence across all declared languages
  • Section structure equivalence (H2/H3 count)
  • SEO element parity (title, meta, schema localization)
  • Word count ratio validation (DE should be 25-35% longer than EN, JA 10-25% shorter)
  • Freshness tracking (stale translations detected via timestamps)
  • Cultural marker scanning (foreign brands, wrong legal references, untranslated elements)

Output: Parity matrix table with per-page scores and prioritized action items.

Locale Format Validation

Load references/locale-formats.md for number, date, currency, address, and phone format reference tables per locale.

Checks:

  • Number format consistency (e.g., "1,000.00" should be "1.000,00" on de-DE pages)
  • Date format matches locale expectations
  • Currency symbols and placement correct for target market
  • Phone numbers use international format with correct country code

Reference Files

Load on-demand as needed (do NOT load all at startup):

  • references/cultural-profiles.md: DACH, Francophone, Hispanic, Japanese cultural adaptation profiles
  • references/locale-formats.md: Number, date, currency, address, phone format tables per locale
  • references/content-parity.md: Content parity audit methodology and scoring
  • references/machine-translation-qa.md: Flags unreviewed machine translation, which Google's spam policy treats as scaled content abuse

Error Handling

ScenarioAction
URL unreachable (DNS failure, connection refused)Report the error clearly. Do not guess site structure. Suggest the user verify the URL and try again.
No hreflang tags foundReport the absence. Check for other internationalization signals (subdirectories, subdomains, ccTLDs) and recommend the appropriate hreflang implementation method.
Invalid language/region codes detectedList each invalid code with the correct replacement. Provide a corrected hreflang tag set ready to implement.
Cultural profile not available for languageUse the Default Profile checklist from cultural-profiles.md. Note that assessment is based on general guidelines, not a pre-built profile.
Content parity directory emptyReport that no content files were found. Suggest verifying the directory path or providing a URL for live site analysis.

© AgriciDaniel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/seo-hreflang of AgriciDaniel/claude-seo.

  • SKILL.md
  • LICENSE.txt
  • references/content-parity.md
  • references/cultural-profiles.md
  • references/locale-formats.md
  • references/machine-translation-qa.md

Open the folder on GitHubat commit 4b99de2

Used in 7 other repositories

We found 20 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in AgriciDaniel/claude-seo, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Hreflang and International SEO next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hreflang and International SEO compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hreflang and International SEO this skillAgriciDaniel/claude-seo19k5 repos~3.4kAutomated safety check: PassMIT
GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude11k—~2.8kAutomated safety check: NotesMIT
SEO Optimizerailabs-393/ai-labs-claude-skills4551 repos~3.2kAutomated safety check: PassMIT
SEO and GEO Auditdageno-agents/seo-geo-audit176—~2kAutomated safety check: PassMIT
SEO Coachakseolabs-seo/seo-coach146—~2.8kAutomated safety check: PassNone
E2E SEO Assistantirinabuht12-oss/marketing-skills4.1k—~1.9kAutomated safety check: PassNone

Similar skills

  • GEO-First SEO Audit Tool

    zubair-trabzada/geo-seo-claude

    Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.

    11k GitHub stars~2.8k tokensUpdated yesterday
    Marketing & SEOAuto-check: notes

  • SEO Optimizer

    ailabs-393/ai-labs-claude-skills

    This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.

    455 GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed

  • SEO and GEO Audit

    dageno-agents/seo-geo-audit

    Runs one prioritized audit that combines technical SEO, content quality, trust signals, entity clarity and AI search readiness for a page, site or domain.

    176 GitHub stars~2k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • SEO Coach

    akseolabs-seo/seo-coach

    Beginner-first SEO coaching for people who want to learn by doing one safe, verifiable step at a time.

    146 GitHub stars~2.8k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • E2E SEO Assistant

    irinabuht12-oss/marketing-skills

    Full SEO workflow covering technical audits, content gaps, backlink opportunities, on-page fixes, and content briefs.

    4.1k GitHub stars~1.9k tokensUpdated 17 days ago
    Marketing & SEOAuto-check passed

  • SEO Audit

    andrew-yangy/gru-ai

    Full website SEO audit with parallel subagent delegation. An agent skill from andrew-yangy/gru-ai.

    155 GitHub stars~731 tokensUpdated 7 mo ago
    Marketing & SEOAuto-check passed

More from AgriciDaniel/claude-seo

All 33 skills in this repo

  • Google SEO APIs

    AgriciDaniel/claude-seo

    Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.

    19k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed

  • SEO Keyword Clustering

    AgriciDaniel/claude-seo

    Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.

    19k GitHub starsUsed in 2 repos~3.3k tokens
    Auto-check passed

  • SEO Content Brief Generator

    AgriciDaniel/claude-seo

    Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.

    19k GitHub starsUsed in 2 repos~2.6k tokens
    Auto-check passed

  • FLOW SEO Framework

    AgriciDaniel/claude-seo

    Brings the FLOW framework's stage-specific SEO prompts into the agent, from keyword discovery through backlinks, on-page work and conversion to local SEO, loaded on demand.

    19k GitHub starsUsed in 2 repos~1.4k tokens
    Auto-check passed

  • SEO Image Generator

    AgriciDaniel/claude-seo

    Generates Open Graph previews, blog hero images, product photos and infographics for SEO use through Gemini image tools and the banana extension.

    19k GitHub starsUsed in 2 repos~2.1k tokens
    Auto-check passed

  • SEO Drift Monitor

    AgriciDaniel/claude-seo

    Captures baselines of a page's SEO-critical elements, compares later snapshots against them and flags regressions by severity, like version control for on-page SEO.

    19k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

Categories

Questions about Hreflang and International SEO

What does Hreflang and International SEO do?

Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes. Hreflang implementations are checked in a fixed order. Every page needs a self-referencing tag that exactly matches its canonical URL, return links must be reciprocal across all language versions, and a single x-default may point to a selector or fallback page with return tags from the other versions.

When should I use Hreflang and International SEO?

Hreflang and International SEO fits situations like: auditing hreflang tags on a multilingual site; generating hreflang markup for a new regional version; finding missing return tags or a bad x-default; checking language and region codes before launch.

How do I install Hreflang and International SEO in Claude Code?

Run `npx skills add AgriciDaniel/claude-seo --skill seo-hreflang -a claude-code`. Or copy the skill folder (skills/seo-hreflang in AgriciDaniel/claude-seo) into .claude/skills/seo-hreflang in your project. Claude Code loads it when a task matches its description.

How do I install Hreflang and International SEO in Codex?

Run `npx skills add AgriciDaniel/claude-seo --skill seo-hreflang -a codex`. Or copy the skill folder (skills/seo-hreflang in AgriciDaniel/claude-seo) into .agents/skills/seo-hreflang in your project. Codex loads it when a task matches its description.

Can I use Hreflang and International SEO in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgriciDaniel/claude-seo --skill seo-hreflang -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-hreflang, .gemini/skills/seo-hreflang, .github/skills/seo-hreflang and .opencode/skills/seo-hreflang in your project.

What does Hreflang and International SEO need to run?

SKILL.md names no scripts, command-line tools or credentials: Hreflang and International SEO is instructions for the agent only.

Does Hreflang and International SEO access the network?

SKILL.md names 3 domains. In commands or code: sitemaps.org and w3.org; the agent is likely to contact these when it follows the instructions. As links in the text: developers.google.com. This is read from the text; nothing was executed.

Is Hreflang and International SEO safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Hreflang and International SEO use?

Hreflang and International SEO is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hreflang and International SEO use?

About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4k tokens, read only when the agent opens those files.

What are the alternatives to Hreflang and International SEO?

Skills that share tags, products or a category with Hreflang and International SEO: GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars), SEO Optimizer (ailabs-393/ai-labs-claude-skills, 455 stars), SEO and GEO Audit (dageno-agents/seo-geo-audit, 176 stars) and SEO Coach (akseolabs-seo/seo-coach, 146 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hreflang and International SEO?

AgriciDaniel (a GitHub user) maintains it in AgriciDaniel/claude-seo, which has 18,627 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 4, 2026.

Source: AgriciDaniel/claude-seo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.