blog-locale-audit

Audits multilingual blog content for translation coverage, hreflang correctness, and SEO parity.

1|Updated Dec 24, 2021
One-click install
npx skills add https://github.com/arthur-fontaine/arthurfontaine.fr --skill blog-locale-audit-arthur-fontaine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blog-locale-audit
Source: https://github.com/arthur-fontaine/arthurfontaine.fr/tree/main/.agents/skills/blog-locale-audit
Command: npx skills add https://github.com/arthur-fontaine/arthurfontaine.fr --skill blog-locale-audit-arthur-fontaine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multilingual blogs drift out of sync: translations go missing, hreflang tags break, meta tags stay untranslated, and stale localized versions keep ranking after the source post changes. This Skill audits an entire directory of localized blog content and surfaces every gap with prioritized, runnable fixes. ## Core Features & Use Cases - Translation Coverage Matrix: Groups posts by language and translation-group keys, then reports which language versions are missing and the overall coverage percentage. - Content and SEO Parity Checks: Compares section counts, FAQ counts, images, word-count ratios, titles, meta descriptions, canonical URLs, schema inLanguage, alt text, and slugs across language versions. - Hreflang and Freshness Validation: Verifies self-referencing and bidirectional hreflang tags, x-default, valid BCP 47 codes, and flags stale translations using translatedDate, source hashes, and Git mtimes. - Use Case: You maintain a blog in English, German, French, and Japanese. Run the audit to discover that two German posts are stale after a source update, one French post is missing, and the hreflang map lacks x-default, then follow the emitted fix commands. ## Quick Start Ask the assistant to run a locale audit on your blog content directory, for example by saying: audit the translations in my blog folder for missing languages, hreflang errors, and stale localized posts.

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 the audit on your content directory and it builds a translation coverage matrix grouping posts by language subdirectories, frontmatter lang fields, and translation-group keys. The report lists every missing language version and the overall coverage percentage.

How to validate hreflang tags for a multilingual blog?▼

The audit checks hreflang-tags.html, hreflang-sitemap.xml, or hreflang-map.json for self-referencing tags, bidirectional return links, canonical consistency, x-default presence, and valid Google-compatible language codes. Missing hreflang files are flagged as a critical gap.

Can it detect stale translations after the source post changes?▼

Yes. The freshness audit compares translatedDate frontmatter against source modification dates, stored source and translation hashes, and Git or file mtimes. Stale files are reported with runnable retranslation commands for each affected language.

What content differences between language versions does it flag?▼

It compares H2/H3 section counts, FAQ counts, image and chart counts, word-count ratios adjusted per language pair, link counts, and frontmatter field parity. Each deviation is classified by severity from critical to medium.

Does the audit support HTML report output?▼

Yes. Passing the --html flag writes a locale-audit-report.html file inside the audited project root, with all dynamic filenames, titles, and URLs escaped before rendering. The default output is a markdown report in the conversation.