agentleFS
gaznilmuzammil12-proggaznilmuzammil12-prog/seo-skills-by-gaznil/skills/blog-locale-audit/SKILL.md

blog-locale-audit

Skill0 starsChanged 3 months agoMITView on GitHub

Audit a directory of multilingual blog content for completeness, consistency, hreflang correctness, meta-tag parity, and freshness. Builds a translation coverage matrix, flags stale translations, validates hreflang and schema, and emits a prioritized report with runnable fix commands. Use when user says "locale audit", "blog locale-audit", "check translations", "multilingual audit", "translation check", "hreflang check", "Uebersetzungen pruefen".

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If hreflang-tags.html, hreflang-sitemap.xml, or hreflang-map.json exists in the directory:

    line 93
  2. Very specific:

    If no hreflang files exist, report it as a critical gap and offer: "Run /blog multilingual <topic> --languages ...

    line 105
  3. Very specific:

    If seo-hreflang from claude-seo is installed, suggest running it for deeper validation.

    line 109

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Blog Locale Audit, Multilingual Quality Control

Audits a directory of multilingual blog content to ensure every language version is complete, consistent, correctly tagged, and SEO-optimized. Catches international content issues before they hurt rankings.

Adapted from claude-blog-multilingual by Chris Mueller (Pro Hub Challenge, March 2026). Original: https://github.com/Chriss54/multilingual-int

Workflow

Phase 1: Discovery

  1. Scan the target directory. Group blog posts by language using:
    • Subdirectory names (en/, de/, fr/).
    • Frontmatter lang and translatedFrom fields.
    • hreflang-map.json if present.
  2. Build a content matrix mapping which post exists in which languages.
  3. Detect the source language (most common translatedFrom target, or the sourceLanguage field in hreflang-map.json if present).

Phase 2: Completeness Audit

Show which translations are missing:

### Translation coverage matrix

| Post (EN) | DE | FR | ES | JA |
|-----------|----|----|----|----|
| how-to-avoid-ai-slop | ok | ok | missing | missing |
| content-marketing-2026 | ok | missing | ok | missing |

Coverage: 60% (6 of 10 expected translations present)
Missing: 4 translations needed

Phase 3: Content Parity Audit

For every post that exists in multiple languages:

CheckWhatSeverity
Section countSame number of H2 and H3 sectionsCritical
FAQ countSame number of FAQ itemsHigh
Image countSame number of imagesHigh
Chart countSame number of charts (SVG figures)High
Word count ratioWithin expected band for language pair (DE +20% to +30%, JA -20%, ES +10%)Medium
Link countSimilar internal and external link countsMedium
Citation capsule countSame number per H2 across versionsMedium
Frontmatter parityAll required fields present per versionHigh

Flag every significant deviation as an issue.

Phase 4: SEO Parity Audit

For every language version verify:

ElementCheckSeverity
Title tagPresent, correct length for the languageCritical
Meta descriptionPresent, correct length, contains a statCritical
lang attribute or frontmatter langPresent, valid ISO 639-1Critical
Schema inLanguageMatches langHigh
Schema translationOfWorkPoints to the source URLHigh
Alt textTranslated (no English alt in non-EN posts)High
SlugLocalized (no English slug in non-EN posts)Medium
TagsLocalizedMedium
KeywordsLocalizedMedium

Phase 5: Hreflang Audit

If hreflang-tags.html, hreflang-sitemap.xml, or hreflang-map.json exists in the directory:

CheckWhatSeverity
Self-referencingEach page references itselfCritical
Return tagsEvery relationship is bidirectionalCritical
x-defaultPresent, points to source languageCritical
Language codesValid ISO 639-1 (with optional region)High
URL consistencySame protocol, same trailing-slash conventionMedium
CompletenessEvery language version representedHigh

If no hreflang files exist, report it as a critical gap and offer: "Run /blog multilingual <topic> --languages ... to regenerate, or create hreflang-tags.html manually."

If seo-hreflang from claude-seo is installed, suggest running it for deeper validation.

Phase 6: Freshness Audit

For posts with translatedDate in frontmatter:

CheckWhatSeverity
Source updated after translationSource modified after translatedDateCritical
Translation older than 90 daysMay need refreshMedium
lastUpdated mismatch across versionsVersions out of syncMedium
File mtime newer than translatedDateContent changed without frontmatter updateWarning

Emit actionable commands per stale file:

3 translations are stale:
- de/ki-trends-2026.md (source updated 2 days ago)
  -> Run: /blog translate en/ai-trends-2026.md --to de
- fr/ki-trends-2026.md (source updated 2 days ago)
  -> Run: /blog translate en/ai-trends-2026.md --to fr
- es/tendencias-ia-2026.md (translation > 90 days old)
  -> Run: /blog translate en/ai-trends-2026.md --to es

Phase 7: Report

Output as markdown by default. If the user passes --html, also write the report to locale-audit-report.html with the same content.

## Multilingual content audit report

### Summary
- Posts audited: [N] across [N] languages
- Overall health: [score] / 100
- Critical issues: [N]
- Warnings: [N]

### Translation coverage
[Matrix from Phase 2]

### Issues found
#### Critical
- [Issue with file references]

#### Warnings
- [Issue with file references]

#### Passed
- [Checks that passed]

### Prioritized fixes
1. [Highest-impact action]
2. [...]

### Stale-translation alerts
[Runnable commands from Phase 6]

### Quick fixes
- Run `/blog translate <file> --to <missing-langs>` for [N] missing translations.
- Run `/blog multilingual` to regenerate hreflang assets.
- Run `/blog localize <file> --locale <code>` for weak cultural adaptations.

Error Handling

ScenarioAction
Empty directory"No blog posts found in [path]"
Only one language presentReport coverage, suggest target languages
No hreflang filesFlag as critical gap, offer regeneration
Unrecognized file formatSkip with a warning

Cross-References

  • Fill missing translations: /blog translate <file> --to <missing-codes>
  • Deepen weak adaptations: /blog localize <file> --locale <code>
  • Regenerate hreflang assets: /blog multilingual <topic> --languages <codes>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.