Content Quality Audit (Originality, Accuracy, Reader Value)
This audit checks whether a page actually solves a reader's problem, adds meaningful value, supports its claims, and avoids repetitive filler. It treats SEO metadata as supporting infrastructure, not a substitute for useful content.
GPT / Claude / Gemini4 variables
Prompt
Audit this page for reader value and editorial quality.
Page URL or slug: {URL}
Intended reader and task: {AUDIENCE_AND_TASK}
Draft: {DRAFT}
Sources and related pages: {EVIDENCE_AND_RELATED_PAGES}
Evaluate:
- Does the page satisfy the stated reader task?
- What useful information or analysis is original to this page?
- Which claims need evidence, dates, caveats, or correction?
- Which sections are repetitive, vague, misleading, or unnecessary?
- Are examples specific enough to help someone act?
- Does the structure make the answer easy to find?
- Are internal links relevant and useful?
- Is the page materially stale, or is a date change unnecessary?
- Should the page be revised, merged, redirected, noindexed, or left alone?
For every finding include severity, evidence from the supplied draft, recommended change, and why it helps readers. Do not invent analytics, source checks, author credentials, reviews, or rankings.
Finish with a prioritized revision plan and a publish-readiness verdict.Quick brief
Purpose
Review a draft for usefulness and credibility before publishing.
Expected output
A prioritized audit with strengths, critical factual gaps, thin or redundant sections, originality opportunities, structural issues, metadata suggestions, internal-link candidates, and a publish/revise/merge recommendation.
Customize before copying
Replace these placeholders with your own context before you run the prompt.
{URL}{AUDIENCE_AND_TASK}{DRAFT}{EVIDENCE_AND_RELATED_PAGES}
Works well with
GPT
Claude
Gemini
Variations
Audit a batch of related URLs for overlap and consolidation opportunities.
Review a tool listing for unsupported features, stale prices, and missing limitations.
Run a pre-publication pass focused only on factual claims and sourcing.
What this prompt helps you do
This audit checks whether a page actually solves a reader's problem, adds meaningful value, supports its claims, and avoids repetitive filler. It treats SEO metadata as supporting infrastructure, not a substitute for useful content.
When to use it
Use on existing pages, AI-assisted drafts, product descriptions, tutorials, and articles due for a substantive review.
Decision context
The right outcome may be improve, merge, redirect, noindex, or leave unchanged. Do not rewrite a page solely to make it longer or to change its date. Assess the page's purpose and evidence first.
How it works
The audit scores reader-task completion, originality, accuracy, specificity, structure, sourcing, freshness, internal links, and page intent. Each finding includes evidence from the draft and a concrete recommended action.
Best practices
Supply the full draft, intended audience, page purpose, source list, and nearby pages. Ask reviewers to separate blocking factual issues from editorial improvements and optional polish.
Common mistakes
Do not reward word count, keyword density, fake author credentials, invented testimonials, or generic FAQs. Do not mark a fact as wrong unless the evidence supports that finding.
What you should expect back
A prioritized audit with strengths, critical factual gaps, thin or redundant sections, originality opportunities, structural issues, metadata suggestions, internal-link candidates, and a publish/revise/merge recommendation.
Limitations
A text-only audit cannot confirm real-world product experience, traffic performance, or whether a source is current unless supporting evidence is supplied.
Model notes
Provide the draft and relevant source material. Include analytics or Search Console evidence only if you want performance conclusions.
Real-world applications
Content operations, documentation maintenance, editorial QA, migration planning, and quality reviews for large content libraries.
How to tell if it worked
The revised page answers the intended question, has fewer unsupported claims, contributes something distinct, and gives readers a clear next step.
Where to go next
Combine with the source-grounded research brief and SEO content brief.
Appears in collections
Responsible SEO Editorial Workflow
A repeatable workflow for planning, researching, drafting, and maintaining useful search content.
Technical Documentation That Works
Tutorial and maintenance prompts for instructions people can follow, test, and recover from.
Software Buying and Comparison Toolkit
Evaluate software options with transparent criteria, verified evidence, and honest trade-offs.
Related prompts
SEO Content Brief (Search Intent to Editorial Plan)
Turn a topic into a useful, evidence-led brief before drafting.
SEO Competitor Content Gap and Differentiation Audit
Find content gaps worth addressing without copying competitors.
Product Review Brief (Balanced + Credible)
Write reviews that don't sound like paid ads.
Landing Page Copy Audit (Fix Confusing Text)
Improve website copy so users understand it in 5 seconds instead of leaving.
SEO Content Refresh Brief (Traffic Decay to Update Plan)
Turn aging pages into clear refresh plans that improve usefulness, depth, and ranking potential.
Topical Authority Cluster Planner (Pillar + Support Pages)
Turn a broad topic into a practical cluster strategy with pillar pages, support content, and internal-link logic.