heading-optimizer

Audit AEM Edge Delivery Services heading hierarchies and generate optimized H1–H6 recommendations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you detect and fix weak, inconsistent, or structurally incorrect heading usage across AEM Edge Delivery Services (EDS) pages so your content aligns with search intent and remains accessible.

Core Features & Use Cases

  • Headings inventory (H1–H6): Extracts all headings from EDS pages via .plain.html, including section and block context, so you can see the real outline authors created.
  • SEO-focused evaluation: Flags issues like missing/duplicate H1s, generic headings (e.g., “Overview”), keyword mismatch, overly long/short H1s, and mismatched intent.
  • Hierarchy & consistency checking: Detects skipped levels, empty headings, and cross-page duplication or naming inconsistencies, then recommends safer replacements.

Use Case: Standardize blog post and landing page heading patterns after noticing multiple pages share the same generic H1 (e.g., “Overview”) and several pages skip levels (H1 → H3), which harms both search clarity and accessibility.

Quick Start

Run the heading-optimizer on your target EDS pages by providing the page paths (or your query index) and ask it to return a heading audit with before/after optimized suggestions for each impacted page.

Frequently Asked Questions about heading-optimizer

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

FAQPage Schema
How do I audit heading hierarchy and SEO issues on AEM Edge Delivery Services pages?

You can audit multiple EDS pages simultaneously by providing specific page paths or leveraging the `/query-index.json` file for site-wide inventory. This allows the tool to extract headings across pages and check for cross-page duplication or naming inconsistencies.

What is the best way to fix generic or duplicate H1 tags across my website?

This Skill handles single-page or site-wide reviews by extracting H1–H6 from `.plain.html` and using `/query-index.json` for inventory. It analyzes heading context within sections and blocks to generate actionable, optimized heading recommendations for each page.

Can I check for skipped heading levels and empty headings in my structured content?

Yes, this Skill detects skipped heading levels and empty headings by extracting the full H1–H6 outline from your `.plain.html` pages. It evaluates the structure to ensure content consistency and accessibility compliance across your site.

Does the heading audit work with content authored in Google Docs or Word?

Yes, the audit generates per-page optimized heading recommendations designed for authors to apply directly in Google Docs or Word. It provides before-and-after suggestions based on the extracted `.plain.html` structure.

Why do my EDS pages have weak H2–H6 phrasing and how do I optimize them?

Weak H2–H6 phrasing typically stems from generic text lacking keyword alignment. This Skill analyzes heading context within sections and blocks to flag weak phrasing and recommends stronger, SEO-optimized replacements for on-page optimization.