- Home
- Skills
- Writing & Content
- Blog On Page SEO Quality Auditor
Works with the AI Agents you already use
Blog On Page SEO Quality Auditor
An evidence-led SEO auditor that identifies content gaps, intent mismatches, and prioritized on-page improvements.
$9.99
Blog On Page SEO Quality Auditor
Example session with this skill installed
Audit this blog post draft about 'Choosing a JavaScript Framework': [Article Text: Selecting a framework is hard. React is popular. Vue is easy. Angular is for big teams. Use one today.]
- Read your context and instructions
- Compiled the blog on page
I have audited the provided text for 'Choosing a JavaScript Framework'. The audit focuses on content-based intent and topical completeness based on the supplied draft.
SEO Quality Audit Report
1. Scope and Limitations
Audit performed on raw text only. HTML structure, metadata, page speed, and live SERP competition were not inspected.
2. Executive Summary
The article is currently a high-level summary that lacks the depth required for a 'Choosing' intent. It identifies frameworks but provides no decision criteria or technical trade-offs.
3. Prioritized Corrections Table
| ID | Priority | Evidence | Issue | Suggested Action | Rationale | Effort |
|---|---|---|---|---|---|---|
| 001 | Critical | "Use one today." | No decision framework. | Add a comparison table of features. | Reader cannot choose based on text. | High |
| 002 | High | "React is popular." | Surface-level claim. | Define 'popular' (NPM trends, jobs). | Adds authority and evidence. | Medium |
| 003 | Medium | "Angular is for big teams." | Jargon/Generalization. | Explain why (TypeScript, DI, CLI). | Clarifies 'why' for the reader. | Medium |
4. Suggested Revisions
Current Heading Structure:
- Selecting a framework is hard (H1)
Recommended Heading Structure:
- Choosing a JavaScript Framework in 2024: A Developer's Guide (H1)
- Key Factors for Selection: Performance vs. Developer Experience (H2)
- React: The Ecosystem Powerhouse (H2)
- Vue: The Progressive Favorite (H2)
- Angular: The Enterprise Standard (H2)
- Comparison: Bundle Size and Learning Curve (H2)
Content Gaps:
- No mention of Svelte or Next.js/Nuxt.js meta-frameworks.
- Missing discussion on community support and long-term maintenance.
- Lack of a "Which should you choose?" summary conclusion.
Next steps
- Expand the individual framework sections with specific pros/cons.
- Insert an internal link to your 'Intro to JavaScript' article in the first paragraph.
- Provide the meta description for review once the new sections are drafted.
Connects securely to your tools. The creator never sees your data.
About this skill
Auditing content for SEO often results in generic advice or rigid adherence to character counts that ignore the reader. This skill provides an evidence-led audit of existing blog articles to improve clarity, intent alignment, and topical completeness without promising hollow ranking outcomes.
What it does
- Evidence-led auditing finds specific passages that weaken an article's authority or clarity.
- Intent mapping compares the article's promise against the actual answers provided to the reader.
- Structural analysis reviews H1-H3 hierarchies for logical flow and descriptive value.
- Link discovery identifies internal linking opportunities with descriptive anchor text suggestions.
- Gap detection highlights missing decision criteria, definitions, or follow-up questions.
- Action prioritization ranks fixes by impact and effort, from critical omissions to minor polish.
How it works
- Supply the content via a URL or full article text, including any known target topics or reader profiles.
- Review the scope to see which elements were inspected and which require more data, like Search Console or SERP notes.
- Analyze the report to see technical metadata reviews, heading fixes, and readability gaps.
- Implement changes using the prioritized table that separates observable evidence from assumptions.
Frameworks & tools
This skill works with any Markdown or HTML-based content. It focuses on linguistic patterns, information architecture, and search intent alignment rather than specific CMS-bound plugins.
Why this beats prompting it yourself
Standard prompts often produce "SEO fluff" like arbitrary keyword density rules. This skill enforces a strict priority system and demands evidence for every claim, ensuring you get actionable content improvements rather than generic advice.
Use cases
- Audit high-traffic posts that have started losing engagement or relevance.
- Review new drafts against a content brief to ensure all requirements are met.
- Optimize older archives for internal linking and topical completeness.
- Screen guest posts for jargon, unsupported claims, or weak transitions.
Known limitations
Cannot inspect page speed, server-side indexability, or live rankings unless Search Console or third-party tool data is manually provided. Character counts are approximate guidance only.
Cannot verify live indexability, page speed, or rankings without manual data input. Intent analysis is content-based only if live SERP data is not provided.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 22 days ago