blog-locale-audit

Audit multilingual blog directories for translation coverage, hreflang correctness, and content parity.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/captaindevv/SEO-ajaypipes --skill blog-locale-audit-captaindevv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blog-locale-audit
Source: https://github.com/captaindevv/SEO-ajaypipes/tree/main/skills/blog-locale-audit
Command: npx skills add https://github.com/captaindevv/SEO-ajaypipes --skill blog-locale-audit-captaindevv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multilingual blogs drift out of sync: translations go missing, hreflang tags break, meta tags diverge, and stale translations linger after the source post is updated. This Skill audits an entire localized content directory and surfaces every gap with a prioritized, actionable report. ## Core Features & Use Cases - Translation Coverage Matrix: Groups posts by language via subdirectories, frontmatter fields, or hreflang-map.json, then shows exactly which translations are missing. - Content & SEO Parity Checks: Compares section counts, FAQ items, images, word-count ratios, title tags, meta descriptions, schema inLanguage, alt text, and slugs across language versions. - Hreflang & Freshness Validation: Verifies self-referencing tags, bidirectional return links, x-default, and flags translations whose source was updated after the translatedDate. - Use Case: You run a blog published in English, German, French, Spanish, and Japanese. Point the Skill at your content directory to get a health score, a list of critical issues, and runnable fix commands like /blog translate en/post.md --to de. ## Quick Start Run a locale audit on my blog content directory at ./content and show me the coverage matrix and critical issues.

Frequently Asked Questions about blog-locale-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which blog translations are missing?▼

Run a locale audit on your content directory. The Skill groups posts by language using subdirectories, frontmatter lang fields, or hreflang-map.json, then builds a coverage matrix showing which translations exist and which are missing per post.

How to validate hreflang tags across multilingual pages?▼

The audit checks hreflang-tags.html, hreflang-sitemap.xml, or hreflang-map.json for self-referencing tags, bidirectional return links, a correct x-default, valid ISO 639-1 codes, and URL consistency. Missing hreflang files are flagged as a critical gap.

Can I detect stale translations after updating the source post?▼

Yes. The freshness audit compares each translation's translatedDate frontmatter field against the source post's modification date. If the source changed after translation, it flags the file as critical and emits a runnable retranslate command.

What content parity checks run across language versions?▼

The audit compares H2/H3 section counts, FAQ items, image and chart counts, word-count ratios adjusted per language pair, link counts, and frontmatter field presence. Significant deviations are flagged with severity levels from critical to medium.

Does the locale audit work if my blog has only one language?▼

It still runs but reports that only one language is present, shows current coverage, and suggests target languages. The full parity and hreflang checks require at least two language versions of the same posts.