Blog Locale Audit

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. Resolve the target directory inside the project root/current working directory. Reject symlinked directories and traversal outside the root, then scan blog content and group posts by language using:
   • Subdirectory names (en/, de/, fr/).
   • Frontmatter lang and translatedFrom fields.
   • hreflang-map.json if present.
2. Normalize detected language codes with the shared multilingual locale rules used by blog-translate, blog-localize, and blog-multilingual: ISO 639-1 language in lowercase, optional ISO 15924 script in title case, optional ISO 3166-1 Alpha-2 region in uppercase. Flag ambiguous language-only codes such as es, pt, and zh unless the content declares an explicit neutral mode.
3. Build a content matrix mapping which post exists in which languages. Use a stable translation-group key before comparing slugs: translationGroupId, sourceSlug, schema translationOfWork.url, or the IDs and URLs in hreflang-map.json. Fall back to normalized source slug only when no stable key exists.
4. 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:

Flag every significant deviation as an issue.

Phase 4: SEO Parity Audit

For every language version verify:

Phase 5: Hreflang Audit

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

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:

When available, store and compare sourceHash, source dateModified, translationHash, and Git mtime before relying only on translatedDate.

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 only inside the audited project root. Escape all dynamic filenames, titles, URLs, and issue text with html.escape(value, quote=True) before rendering HTML, and reject symlinked or outside-root report paths.

## 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 fixes1. [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

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>