localization-audit

Audit AEM Edge Delivery Services sites for content parity and hreflang SEO issues.

Updated May 14, 2026
One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill localization-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localization-audit
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/localization-audit
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill localization-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Localization gaps across multi-language AEM Edge Delivery Services sites cause broken user journeys and SEO issues, especially when pages exist in some locales but not others or when titles/descriptions stay in the source language. It also helps prevent incorrect locale routing by validating hreflang tags and reporting technical parity problems.

Core Features & Use Cases

  • Build a locale content matrix: Compares the primary locale page set against target locales using the query index (with sitemap fallback) to quantify content parity.
  • Identify missing translations with prioritization: Produces a prioritized remediation list that groups gaps by locale and urgency (critical to low).
  • Audit metadata completeness per language: Flags likely untranslated titles/descriptions and detects incomplete translations using content-length and heuristic checks, including image alt text considerations.
  • Validate hreflang implementation: Checks for missing alternate tags, missing self-reference and x-default, non-reciprocal hreflang links, invalid language codes, and hreflang links to 404 pages.

Quick Start

Run the localization-audit skill for your site URL to generate a locale completeness matrix, a prioritized missing-translation report, and a hreflang compliance checklist.

Frequently Asked Questions about localization-audit

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

FAQPage Schema
How do I find missing translations and content parity gaps in AEM Edge Delivery Services?

To find missing translations in AEM Edge Delivery Services, you can audit multi-language sites by building a locale content matrix from the query index or sitemap fallback to quantify content parity gaps and identify missing page variants across locales.

How do I validate hreflang tags and check for non-reciprocal links across locales?

Validating hreflang tags involves checking for missing alternate tags, missing self-reference and x-default entries, invalid language codes, non-reciprocal hreflang links, and hreflang links pointing to 404 pages to ensure correct locale routing.

What is the best way to detect untranslated metadata and image alt text by language?

Detecting untranslated metadata and image alt text requires auditing metadata completeness per language using content-length and heuristic checks to flag titles and descriptions that remain in the source language.

Can I use a sitemap fallback to audit locales if my AEM query index is incomplete?

Yes, you can use a sitemap fallback to build a locale content matrix and compare the primary locale page set against target locales when the AEM query index is incomplete or lacks sufficient data.

How do I generate a prioritized remediation report for missing page variants?

To generate a prioritized remediation report for missing page variants, compare metadata completeness across your locale matrix and group the identified content parity gaps by locale and urgency from critical to low.

Why does incorrect hreflang implementation cause SEO issues on multi-language sites?

Incorrect hreflang implementation causes SEO issues by preventing search engines from serving the correct language version to users, which happens when alternate tags, self-references, or reciprocal links are missing or point to 404 pages.