What is the SEO AEO content quality auditor agent skill?

Runs a dual SEO + AEO audit on any landing page or blog post. It stands out by giving search and SEO workflows a defined shape, so the agent asks for better context and returns a more usable result.

What inputs does SEO AEO content quality auditor need?

Context for search and SEO workflows: your goals, audience, constraints, and any source material the skill asks for.

What does SEO AEO content quality auditor output?

A ready-to-use result for search and SEO workflows: the analysis, copy, or recommendations the agent produces.

SEO AEO content quality auditor

Quick answer

01What is it?: Runs a dual SEO + AEO audit on any landing page or blog post. It stands out by giving search and SEO workflows a defined shape, so the agent asks for better context and returns a more usable result.
02Inputs: Context for search and SEO workflows: your goals, audience, constraints, and any source material the skill asks for.
03Output: A ready-to-use result for search and SEO workflows: the analysis, copy, or recommendations the agent produces.

Add this skill

Paste-ready

Install as a package

Installs this one skill package for your coding agent, including any supporting files that skill ships with — not every skill in the repository. Read the tutorial.

Terminal

$ npx skills add sickn33/antigravity-awesome-skills --skill seo-aeo-content-quality-auditor

Use in Profound

Copy this file into a new Profound Skill. That's it, nothing else to install.

Copy and create in Profound

SKILL.md

SEO-AEO Content Quality Auditor

Overview

Runs a dual SEO + AEO audit on any landing page or blog post. Produces an overall score, SEO score, AEO score, and readability score — each out of 100 — with severity-ranked issue lists (Critical / Warning / Polish), exact fix instructions for every issue, and projected scores after all fixes are applied.

Part of the SEO-AEO Engine (https://github.com/mrprewsh/seo-aeo-engine).

When to Use This Skill

Use when auditing a landing page or blog post before publishing
Use after the blog-writer or landing-page-writer skill outputs content
Use when diagnosing why existing content is underperforming in search
Use when you need a scored, actionable SEO and AEO report

How It Works

Step 1: Run SEO Checks

Verify keyword density, H1/H2/H3 structure, meta elements, word count, sentence length, and paragraph density. Flag every issue with its severity.

Step 2: Run AEO Checks

Check for TL;DR block, definition sentence, FAQ section (minimum 4 entries), bullet and numbered lists, comparison table, and extractable direct answers. Score each signal as found or missing.

Step 3: Run Readability Checks

Check passive voice ratio, transition word presence, wall-of-text paragraphs, subheading frequency, and reading level.

Step 4: Score and Prioritise

Calculate three scores out of 100. Sort all issues into Critical (fix before publishing), Important (fix soon), and Polish (optional improvements). Generate projected scores after all fixes are applied.

Scoring System

Score	Status	Label
85–100	✅ Pass	Strong
70–84	⚠️ Warn	Acceptable
50–69	🔶 Weak	Needs work
0–49	❌ Fail	Do not publish

Examples

Example: Audit Summary

Overall Score: 84/100 ⚠️ Acceptable SEO Score: 88/100 ✅ Pass AEO Score: 74/100 ⚠️ Acceptable Readability: 91/100 ✅ Pass Verdict: Strong SEO foundation. AEO needs a TL;DR block and one more FAQ entry before publishing. 🔴 Critical (fix before publishing):

AEO: No TL;DR block found Fix: Add a 2–3 sentence direct-answer block in a blockquote immediately after the H1.

🟡 Important (fix soon): 2. AEO: FAQ has 3 entries — minimum is 4 Fix: Add one more FAQ entry using a secondary keyword as the question. Projected score after fixes: 93/100 ✅

Best Practices

✅ Do: Fix all Critical issues before publishing — they block AEO extraction
✅ Do: Use the projected score to prioritise which fixes to make first
✅ Do: Run the audit on both the landing page and blog post in the same session
❌ Don't: Publish content scoring below 50/100 overall
❌ Don't: Ignore AEO warnings — they directly affect AI engine citation probability

Common Pitfalls

Problem: SEO score is high but AEO score is low Solution: Traditional SEO tools miss AEO signals entirely. Run the AEO checklist separately and treat it as equally important.
Problem: Fix list is long and overwhelming Solution: Work through Critical issues only first, re-run the audit, then tackle Important issues.

Related Skills

@seo-aeo-blog-writer — produces the content this skill audits
@seo-aeo-landing-page-writer — produces landing pages this skill audits
@seo-aeo-schema-generator — uses audit output to determine schema priorities

Additional Resources

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Common questions

How do I install SEO AEO content quality auditor in Cursor, Claude Code, or Codex?

Run npx skills add sickn33/antigravity-awesome-skills --skill seo-aeo-content-quality-auditor in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only SEO AEO content quality auditor, not every skill in the repository.

Where does SEO AEO content quality auditor come from and what license is it under?

SEO AEO content quality auditor comes from the sickn33/antigravity-awesome-skills repository on GitHub. That repository has 42.1K GitHub stars. The skill is published under the MIT license.

Prefer plain text? Read the SEO AEO content quality auditor guide as markdown.