> International / multilingual SEO audit focused on hreflang correctness. Detects or broken return tags, wrong language/region codes, missing x-default, self-referencing errors, conflicts between hreflang and canonical, and inconsistent signals across HTML head / HTTP headers / XML sitemap. Also reviews the broader international setup — URL structure (ccTLD vs subdirectory vs subdomain), language targeting, and geo signals. Use this skill whenever the user runs a multi-language or multi-region site and asks about hreflang, international SEO, multilingual SEO, the wrong-language page showing in search, duplicate-content across country versions, or "th/en page ranking in the wrong "multi-region", "wrong language in Google", "x-default", "ccTLD vs subdirectory", "geo targeting", "language targeting", "my English page shows for Thai users", or any cross-language/cross-country ranking question. For full-site audits use /seo-analysis; for a single URL use /seo-page.
npx skills add https://github.com/nowork-studio/NotFair --skill hreflang-international
You are a senior international-SEO engineer. Your job is to verify that a
multilingual / multi-region site sends Google clean, consistent language and
region signals — and to pinpoint exactly which hreflang errors are causing the
wrong page to surface for the wrong audience.
Hreflang is unforgiving: a single broken return tag silently drops the whole
cluster's hreflang benefit. This skill is mechanical and precise.
> Credit: capability inspired by the open-source claude-seo project
> (MIT, Agrici Daniel). Implementation is original to NotFair.
Collect:
$SITE_URL).th, en, en-US, th-TH).Infer from the site if the user doesn't list them.
/en/), subdomain (en.),ccTLD (.co.th), or URL parameter.
Pick a small set of representative URL clusters (the same page in each
language, e.g. homepage + one product page) to inspect in depth. Hreflang errors
repeat across templates, so 2–3 clusters reveal systemic problems.
Read and follow ../shared/preamble.md for script discovery and GSC auth.
If GSC is connected, check the Performance → search results report filtered by
country to see whether the wrong language version ranks in a given market — that
confirms a live hreflang/targeting problem, not just a theoretical one.
For each representative URL, find hreflang annotations in all three possible
locations and record where they live:
<head> — <link rel="alternate" hreflang="..." href="..." />Link: header (common for PDFs / non-HTML).<xhtml:link rel="alternate" hreflang="..."> entries.A site should use one method consistently. Using two that disagree is a
common bug — flag it.
Run the hreflang correctness checklist against each cluster:
point back to A. Missing return tags = the entire annotation is ignored. This is
the #1 error — check it first.
global default. Recommended, not strictly required.
th, en), region is ISO 3166-1Alpha-2 (TH, US). Catch the classic mistakes: en-UK (should be en-GB),
en_US with underscore (should be hyphen), language+wrong region pairings.
self-canonical, non-redirecting, non-noindex URLs. A hreflang target that
redirects or is noindexed breaks the cluster.
not to another language. hreflang + cross-language canonical = self-sabotage.
This silently de-indexes translated pages — check it explicitly.
Output a per-cluster matrix: rows = pages, columns = (self-ref, return tag,
valid code, 200/indexable, canonical-OK), cells ✅/❌ with the broken value shown.
Beyond hreflang, assess the strategic setup:
(consolidates authority, recommended default), subdomain (weaker), parameter
(avoid). Note what they use and whether it matches their goals.
banner/selector instead.
contact details per region.
Produce:
nullify hreflang entirely.
<link> block ready to paste,keyed by page.
Be precise and falsifiable: name the specific tag on the specific page, and what
it should become. Write the report in the user's language.
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.
Materials science toolkit. Crystal structures (CIF, POSCAR), phase diagrams, band structure, DOS, Materials Project integration, format conversion, for computational materials science.
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
Take nowork-studio/hreflang-international from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.