Content QA: Check Counting Rules, Repetition and the Published Draft
Use a seven-word sample, a keyword denominator check and a revision comparison to verify a draft without treating word count as a quality score.
Start with the destination’s actual acceptance rules. A word target, a character cap and a requirement to explain a procedure are different checks. Keep the source draft so a mechanical cleanup cannot silently remove a useful qualification.
Tools in this guide
1. Establish what the counter measures
Paste “Ready for release. Review the rollback plan.” into Word Counter. This simple English sample has seven space-separated words. Confirm the word result, then inspect character counts separately; punctuation and spaces affect those counts.
For Chinese, emoji, combining marks or hyphenated terms, compare with the destination editor. Different tools may count code units, code points or segmented words. When a publisher rejects a field, its own measured limit is the relevant acceptance check.
Ready for release. Review the rollback plan.2. Interpret a frequency percentage before changing prose
In Keyword Density Checker, enter “API api tools to go 中文”. With the tool’s current filtering, the retained tokens are api, api and tools: api is 2/3, or 66.67%. The percentage is not two occurrences divided by every visible word or character.
Use the result to locate repeated phrases, then read the paragraph. An API name may need repetition for clarity; removing it just to reduce a percentage can make the explanation less precise. There is no universal keyword-density target that proves useful content.
API api tools to go 中文
api: 2 / 3 = 66.67%
tools: 1 / 3 = 33.33%3. Check whether every section answers a concrete question
For a procedure, look for the required input, the operation, the expected output and one failure condition. A section that only says “use the tool and check the result” lacks an acceptance criterion even if it has many words.
For example, replace “validate the export” with “confirm two rows, keep 00123 as text, and compare the note containing a comma with the source”. These are observable checks, not extra filler.
4. Compare the final artifact with the approved source
Use Text Diff on the original and revised draft. Review removed warnings, changed numbers and renamed fields before accepting cosmetic edits. Then preview the Markdown, especially tables, code blocks and headings.
Paste the final version into its destination and recheck any hard field limit there. Record the rule used, the final count and the substantive checks completed. A passing count does not replace fact-checking, working examples or a useful answer.