content-audit

Audit Adobe Edge Delivery Services pages for content quality, SEO, accessibility, and performance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Content teams need a reliable way to review Adobe Edge Delivery Services (EDS) pages across content structure, metadata/SEO, accessibility, performance patterns, and EDS-specific best practices.

Core Features & Use Cases

  • Prioritized, actionable fix list: produces concrete remediation steps rather than vague recommendations.
  • EDS-aware page parsing: fetches the published page plus the .plain.html variant, and also inspects header/footer fragments used by EDS.
  • Multi-domain audit coverage: checks content structure (headings/sections/blocks), metadata (title/description/OG/robots/canonical), SEO and AI discoverability, accessibility requirements (alt text, headings, link text, contrast), and EDS performance rules (LCP budget, E-L-D phases, font loading, and head.html constraints).

Quick Start

Use the content-audit skill to audit a single published EDS URL you provide by fetching its .plain.html variant and generating a prioritized remediation report with specific fixes.

Frequently Asked Questions about content-audit

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

FAQPage Schema
How do I audit an Adobe Edge Delivery Services page for SEO and accessibility issues?▼

You can audit an EDS page by fetching its published URL and the `.plain.html` variant to check content structure, metadata, accessibility, and EDS best practices, producing a prioritized fix list for SEO and quality gaps.

Why does my EDS page have low Lighthouse and Core Web Vitals scores?▼

Low Lighthouse and CWV scores on EDS pages often stem from LCP budget violations, improper loading-phase execution, or head.html constraints, which a content audit investigates by analyzing published and `.plain.html` page representations.

What EDS-specific best practices should I check before launching a page?▼

Before launching an EDS page, check H1 and heading hierarchy rules, metadata and Open Graph tag presence, canonical tags, robots directives, and EDS-specific performance loading-phase and LCP budgeting heuristics.

Does the content audit check the header and footer fragments used by EDS?▼

Yes, the EDS content audit inspects header and footer fragments alongside the published page and the `.plain.html` variant to ensure comprehensive metadata, accessibility, and best-practice compliance coverage.

What is the best way to fix content quality gaps on an Adobe Edge Delivery Services site?▼

The best way to fix EDS content quality gaps is to run a multi-domain audit that parses both published and `.plain.html` page representations, producing a prioritized and actionable list of concrete remediation steps.