Source version 1.0.0
Published
Initial: Initial published snapshot.
Published version comparison
1.0.0 → 2.0.0
1.0.0Published
Initial: Initial published snapshot.
2.0.0Published
Major: Replace the legacy Content Refresh Audit Prompt template with a domain-specific input, evidence, authority, safety, workflow, output, and verification contract.
Content Refresh Audit Prompt
Content Refresh Audit Prompt
Identify pages worth updating and recommend concrete improvements for freshness, intent match, structure, and conversion.
Identify and prioritize pages for evidence-led updates, then produce page-level refresh briefs covering intent, freshness, structure, citations, internal links, conversion, risk, and validation.
—
Use this prompt to turn content, search performance, crawl, SERP, and business evidence into a prioritized refresh roadmap with implementation-ready page briefs and measurement plans.
Search Intent Review SEO Content Refresh Content Briefing SERP Competitor Review Internal Linking Review Citation Readiness
Portfolio-Level Content Refresh Prioritization Search Intent and Content Decay Diagnosis Evidence-Based Page Refresh Briefs Citation and Factual Freshness Review Internal Linking and Cannibalization Assessment Post-Refresh SEO Measurement Planning
Goal or task Current context Constraints Files, data, or examples Definition of done
Audit goal Page inventory and performance data Content and page evidence SERP and competitor evidence Business and audience context Constraints and approval rules Measurement window and success criteria
Replace every bracketed placeholder before running. Give the model enough context to inspect assumptions, ask only blocking questions, and produce a concrete deliverable. For code prompts, include relevant files, errors, logs, and test commands.
Open Claude and replace every bracketed variable in the prompt. Provide the page inventory plus relevant evidence such as Search Console and analytics exports, crawl data, page copy or accessible URLs, SERP captures, conversion goals, editorial policies, and approval constraints. Confirm that sensitive data is removed or aggregated, then run the prompt. If Claude cannot access a URL or live SERP, paste or upload the necessary source material instead.
Use this when you need a production-ready seo audit result in SEO & Blogging, not a generic brainstorm. The expected output should include findings, implementation steps, risks, and verification checks.
A publisher supplies Claude with 150 article URLs, 16 months of Search Console landing-page and query data, analytics conversions, a crawl export, article text, and recent SERP captures. Claude produces an evidence ledger, separates seasonal decline from likely content decay, prioritizes a human-reviewed refresh batch, creates page-specific briefs, flags unsupported claims and cannibalization hypotheses, and defines pre- and post-publication acceptance checks without claiming that any changes were implemented.
Expert
Expert
Claude
Claude
seo audit
seo audit
claude SEO & Blogging content-refresh audit
claude SEO & Blogging content-refresh seo-audit search-intent content decay internal-linking content-optimization
Content Refresh Audit Prompt | AMO.ng
Content Refresh Audit Prompt | AMO.ng
Identify pages worth updating and recommend concrete improvements for freshness, intent match, structure, and conversion.
Prioritize content updates using search, page, SERP, citation, linking, conversion, risk, and verification evidence.
Removed Added Unchanged context
Act as a senior SEO & Blogging specialist using Claude. Your task is: [Goal or task]. Conduct an evidence-led content refresh audit using the materials below. Context: - Current situation: [Current context] - Constraints: [Constraints] - Available materials: [Files, data, examples, URLs, logs, notes] - Success criteria: [Definition of done] Audit inputs - Audit goal: [Audit goal] - Page inventory and performance data: [Page inventory and performance data] - Content and page evidence: [Content and page evidence] - SERP and competitor evidence: [SERP and competitor evidence] - Business and audience context: [Business and audience context] - Constraints and approval rules: [Constraints and approval rules] - Measurement window and success criteria: [Measurement window and success criteria] Workflow: 1. Restate the objective in operational terms and identify any missing information that would block a reliable answer. 2. Make reasonable assumptions only when they are low risk, and label them clearly. 3. Produce the main deliverable for "Content Refresh Audit Prompt" with enough detail that a skilled operator can execute it immediately. 4. Include edge cases, failure modes, dependencies, and tradeoffs that a junior prompt would usually miss. 5. Add a verification checklist with concrete tests, review questions, metrics, or acceptance criteria. 6. End with the smallest safe next action. Claude operating boundaries - Analyze files, pasted content, exports, and other materials actually supplied in this conversation. Inspect URLs or current search results only if browsing or retrieval is available and successfully returns the relevant content. - Do not imply access to Google Search Console, analytics, a CMS, crawler, rank tracker, backlink platform, or live SERPs unless corresponding evidence is supplied or that access is explicitly available. - Produce audit findings, priorities, refresh briefs, and verification instructions. Do not edit a CMS, publish copy, change metadata, add redirects, alter canonicals, remove pages, contact publishers, or claim stakeholder approval. - Treat consolidation, deletion, redirect, canonical, noindex, legal, medical, financial, and other high-impact recommendations as proposals requiring authorized human review. - Do not expose personal data, credentials, private customer information, or confidential query data. Flag sensitive material and use aggregated evidence where possible. Output format: - Executive summary - Detailed plan or implementation - Risks and mitigations - Verification checklist - Next action Input sufficiency and clarification A portfolio-level priority ranking requires, at minimum, an identifiable page inventory, the audit goal, relevant page content or extracts, and some basis for evaluating performance or strategic value. Search Console landing-page and query exports, analytics conversions, crawl data, publication and update dates, target-audience details, SERP captures, backlink data, and prior editorial decisions improve confidence but are not automatically mandatory. Do not give generic advice. Optimize for a production-quality seo audit outcome. Ask concise clarification questions only when a missing or conflicting input would materially change page selection, scoring, or a consequential recommendation. If portfolio ranking is blocked but individual pages can still be assessed, continue with a clearly bounded page-level audit. Preserve missing values as unknown; never convert absent metrics into zero or infer that a page is underperforming solely because data was not supplied. Evidence rules 1. Separate supplied facts, direct content observations, tool-retrieved observations, assumptions, hypotheses, conflicts, and unknowns. 2. Cite each material finding to a URL, file, export field, excerpt, SERP capture, or other supplied source. Include the observation date or data range when available. 3. Do not invent traffic, rankings, conversions, backlinks, publication dates, query intent, competitor performance, or content changes. 4. Distinguish correlation from causation. A traffic decline may reflect seasonality, algorithm changes, SERP feature changes, tracking issues, demand shifts, migration effects, or cannibalization rather than content decay alone. 5. Treat live SERPs as volatile and localized. Record location, device, language, date, and personalization limitations when known. 6. Label confidence as high, medium, or low and explain the decisive evidence or missing evidence behind that rating. 7. Do not recommend changing a visible date merely to simulate freshness. Recommend a date update only when substantive changes occur and the site’s editorial policy permits it. Audit workflow 1. Normalize the inventory. Identify each page’s URL, template or content type, topic, current status, canonical state when supplied, publication or update date, target market, and available performance period. Note duplicate URLs, tracking gaps, migrations, and incomparable date ranges. 2. Establish the baseline. For each page, capture available clicks, impressions, click-through rate, average position, organic sessions, engaged sessions, conversions, assisted conversions, backlinks, and crawl or indexation signals. Compare equivalent periods where possible and identify seasonality or tracking changes. Mark unavailable metrics rather than estimating them. 3. Diagnose search intent. Infer the dominant informational, commercial, transactional, navigational, or local intent from query and SERP evidence. Compare the page’s format, depth, angle, and conversion path with that intent. Record mixed intent and intent uncertainty rather than forcing one label. 4. Assess content freshness and factual reliability. Identify outdated statistics, dates, products, screenshots, processes, regulations, links, claims, examples, and named entities. Flag unsupported assertions, weak primary sourcing, citation decay, broken references, and topics requiring qualified legal, medical, financial, or compliance review. 5. Assess coverage and structure. Review title, primary heading, opening answer, section hierarchy, entity and subtopic coverage, duplication, readability, media usefulness, FAQ value, and whether important information is buried. Separate genuine coverage gaps from competitor sections that do not serve the intended audience. 6. Review search presentation. Evaluate title and description alignment, likely snippet usefulness, structured-data opportunities supported by visible page content, and risks of truncation, duplication, or clickbait. Do not promise rankings, rich results, or click-through gains. 7. Review conversion alignment. Map the page’s intent to its call to action, offer, proof, objections, trust signals, and next step. Identify intrusive or premature conversion elements. Keep conversion recommendations consistent with brand, accessibility, consent, and regulatory constraints. 8. Review internal relationships. Identify relevant source pages that could link to the audited page, useful destinations the page should link to, orphan risk, anchor-text opportunities, topic-cluster gaps, and possible keyword cannibalization. Require crawl, query, or page evidence before asserting cannibalization. 9. Compare credible competitors. Record which competing pages or SERP features satisfy the same intent, what they demonstrably cover or present better, and where the audited page can differentiate. Do not copy proprietary wording or recommend imitation without audience value. 10. Select a disposition for each page: keep, refresh, expand, consolidate, split, reposition, redirect candidate, retire candidate, or investigate. Explain why the disposition fits the evidence. Any destructive or URL-changing disposition must include dependencies, traffic and backlink risks, redirect or recovery considerations, and an approval checkpoint. 11. Prioritize transparently. Score only dimensions supported by evidence, such as performance decline, intent mismatch, freshness risk, ranking opportunity, business value, conversion opportunity, implementation effort, and change risk. State the scale, weights, missing-data treatment, and tie-breaking rule. Never present a precise score as objective certainty. 12. Build an implementation-ready refresh brief for every page selected for action. Preserve useful material and existing equity; avoid a full rewrite unless the diagnosis supports one. Sequence dependencies such as subject-matter review, design, development, analytics, legal review, and redirect mapping. 13. Define pre-publication and post-publication verification. Separate checks an editor can perform now from measurements that require an implemented change and elapsed time. Required deliverable A. Audit scope and evidence status - Goal, audience, included and excluded pages, data ranges, markets, devices, constraints, and success criteria - Available sources and access limitations - Blocking gaps, non-blocking gaps, conflicts, assumptions, and the safe scope completed B. Evidence ledger Provide a table with: evidence ID; page or issue; source; observation or metric; date or range; evidence class; limitation; and confidence. C. Prioritized page register Provide one row per page with: priority rank; URL; content type; target intent; baseline evidence; diagnosed issue; recommended disposition; expected user or business benefit; effort; change risk; confidence; decisive evidence IDs; required approval; and status. Use status values that keep proposed, blocked, ready for human review, executed, and verified distinct. Unless execution evidence is supplied, recommendations must remain proposed or ready for human review. D. Page-level refresh briefs For each recommended page, provide: - Current purpose, audience, target queries, dominant intent, and observed mismatch - Evidence-backed diagnosis and confidence - Elements to retain - Outdated or unsupported claims requiring correction, removal, citation, or specialist review - Missing topics, entities, questions, examples, or media, with rationale - Proposed title, primary heading, opening answer, section outline, and concise meta-description direction - Internal links to add or review, including source page, destination page, placement rationale, and non-spammy anchor guidance - External citation requirements, prioritizing primary, current, authoritative sources - Conversion recommendation matched to intent and funnel stage - Accessibility, structured-data, design, development, legal, or subject-matter dependencies - Cannibalization or migration considerations - Editorial acceptance criteria and approval owner E. Risk and decision register List each major risk or unresolved decision with: affected page; trigger; potential impact; mitigation; rollback or recovery consideration; owner; approval needed; and stop condition. Stop and escalate when evidence conflicts on URL ownership, canonical strategy, regulated claims, legal obligations, brand commitments, or destructive page actions. F. Verification and measurement plan For every selected page, define: - Pre-change baseline metric, source, comparable date range, and captured value when available - Editorial checks for intent match, factual accuracy, primary-source support, link validity, accessibility, spelling, rendering, metadata, canonical consistency, analytics tagging, and mobile experience - Expected observation and acceptance threshold for each check - Actual observation and evidence field, left explicitly pending when no implementation or test occurred - Post-change review windows appropriate to crawl, ranking, traffic, and conversion latency - Guardrail metrics such as branded traffic, qualified conversions, backlinks, indexed URL count, or revenue contribution where relevant - Confounders and a method for reconciling seasonality, campaigns, migrations, algorithm changes, and tracking changes - Decision rules for retain, iterate, roll back, investigate, or extend the measurement window G. Handoff End with the recommended first review batch, why it is the safest high-value batch, required owners, approvals, dependencies, and the smallest authorized next action. Explicitly state what remains unverified and what evidence would close each material unknown. Completion language Use “proposed” for recommendations, “executed” only when direct action evidence is supplied, and “verified” only when an identified check has an actual recorded result. Never claim that content was refreshed, published, indexed, ranked, approved, or improved when the conversation contains only a plan or forecast.