Audit a Help Center Article for Gaps, Jargon and Outdated Steps
Paste a help center article and get a pass/fail checklist scorecard plus a line-by-line fix list ranked by customer impact, without a full rewrite.
You getScorecard, fix list and split recommendation
Prompt
You are a help center content lead who audits support articles before they are republished.
I will paste an existing help center article right after this message. Audit it for gaps, jargon and outdated steps. Do not rewrite the whole article. Give targeted fixes only.
Rules:
1. Score the article against this checklist, marking each item Pass, Partial or Fail with a one-line reason: one task per article, title names the task, numbered steps with one action each, UI labels written exactly and in bold, screenshots noted where a step is ambiguous, prerequisites listed first, last-verified date present, related articles linked.
2. Quote the exact line for every issue before the fix, so I can find it with Ctrl+F.
3. Flag any term a new customer would not know and give a plain replacement.
4. Mark steps that look outdated (old menu names, removed features, version numbers) as "Verify in product" instead of guessing the current UI.
5. Rank each fix: High (blocks the task), Medium (causes confusion), Low (polish).
Output format:
1. Scorecard: table with columns Check, Result, Reason, then a total out of 8.
2. Fix list: table with columns #, Quoted line, Problem, Fix, Priority.
3. Split recommendation: if the article covers more than one task, list proposed separate article titles.
4. Three quick wins to do today.
End by listing what you could not check without access to the live product.Example output
Tips and common edits
Why this works
- A fixed 8-point checklist gives a score you can compare across articles instead of a vague opinion.
- Quoting each line before the fix lets writers find and patch issues fast without rereading the whole article.
- "Verify in product" stops the model from inventing current menu names it cannot see.
Use before a quarterly help center review or after a product release. Copy the full article text, including the title and any update date, and paste it into ChatGPT, Claude or Gemini right after the prompt.
Common edits
- Add your own style-guide rules to the checklist, such as voice, tone or reading level.
- Paste several short articles at once and ask for one scorecard row per article.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Turn Feature Notes into a Step-by-Step Help Center How-To Guide
Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.
Find Help Center Gaps by Matching Support Tickets to Existing Articles
Get a ticket-to-article match table and a ranked list of new help articles to write, with ticket counts and deflection potential for each.
Turn Support Ticket Topics into a Help Center Category Structure and Article List
Groups your pasted ticket topics into 5-8 customer-language categories, flags duplicates and orphans, and ranks proposed article titles by ticket volume.
Write Help Article Titles and Meta Descriptions in Your Customers' Words
Get help article titles that start with the customer's task verb and meta descriptions within search length limits, each with a character count and the customer phrase it matches.
Turn a Resolved Support Ticket Thread into a Help Center Article
Paste a solved ticket thread and get a ready-to-publish help article with customer details removed, verb-first fix steps, and symptoms written the way customers search.
Write Chatbot Intent Answers with Trigger Phrases and Human Handoff Rules
Get a set of chatbot intents for your top support questions, each with customer-style trigger phrases, a short bot answer, and an exact rule for handing off to a human.