QA Scoring: Score Thin Content Fixes Before Publish Review
SEO Slots
| Slot | Value |
|---|---|
| seo_title | Content QA Scoring for Thin Page Rewrites |
| meta_description | Score rewritten pages with a practical QA rubric for reader value, intent fit, differentiation, evidence, links, CTA, and technical readiness. |
| slug | qa-scoring |
| primary_query | content QA scorecard |
| secondary_queries | content QA scorecard, content QA scorecard checklist, content QA scorecard template |
| search_intent | operational checklist |
| canonical_path | /resources/content-thinness-lab/qa-scoring/ |
| og_title | Content QA Scoring for Thin Page Rewrites |
| og_description | Score rewritten pages with a practical QA rubric for reader value, intent fit, differentiation, evidence, links, CTA, and technical readiness. |
Search Intent
operational checklist. The article must answer the reader's operational question before any commercial route appears.
Reader Artifact
Reusable checklist, table, or runbook from the article body. This artifact is the reason the article can be saved, cited, or reused by an operator.
Internal Links
- Hub: /resources/content-thinness-lab/
- Related article: /resources/content-thinness-lab/thin-page-symptoms/
- Related article: /resources/content-thinness-lab/overlap-map/
- Related article: /resources/content-thinness-lab/rewrite-matrix/
- Related article: /resources/content-thinness-lab/content-briefs/
- Tool/service route: /services/diagnostic-sprint/
Structured Data
Recommended schema: Article, BreadcrumbList. Keep BreadcrumbList aligned with /resources/content-thinness-lab/qa-scoring/. Do not add Product, Offer, Review, Rating, or FAQPage schema for this wave unless a later approved public page visibly supports it.
CTA Route
Primary route: /services/diagnostic-sprint/.
CTA label: Use the related checklist or diagnostic route.
CTA family: diagnostic_sprint.
Use this route only after the article artifact has clarified the next operational step. Public forms, accounts, and payments are intentionally not part of this resource page.
The CTA stays measured and specific, with no public payment or account route on this page.
Measurement
| Event | Name |
|---|---|
| event_view_article | view_article_content_thinness_lab_qa_scoring |
| event_click_artifact | click_artifact_content_thinness_lab_qa_scoring |
| event_click_cta | click_cta_content_thinness_lab_qa_scoring |
| utm_policy | No UTM on internal links; campaign UTMs only during approved external distribution. |
Public-Preflight NG Items
- Fake client proof, fake metrics, fake awards, or guaranteed outcomes.
- Public account, form, payment, repo, domain, or outreach route before checks pass.
- Unapproved cross-brand, unrelated monetization, or off-topic trust route.
- Unsupported claims about SEO, ranking, revenue, or tool behavior.
- Machine-like slug, broken internal link, missing schema plan, or missing measurement slot.The final question is not "does the rewritten page sound better?" The final question is "does it pass a repeatable publish-readiness score without hiding unresolved risk?"
This scorecard gives content teams a practical gate for rewritten pages.
QA Scorecard
Score each category from 0 to 5.
| Category | 0 | 3 | 5 |
|---|---|---|---|
| Reader value | No reusable artifact or decision support | Useful explanation but weak artifact | Strong artifact that can be reused |
| Intent fit | Mixed or wrong intent | Mostly aligned with small drift | Title, intro, outline, artifact, and CTA match one intent |
| Differentiation | Duplicates sibling page | Some unique sections but overlap remains | Unique job, artifact, and route are clear |
| Evidence | Unsupported claims or invented specificity | Claims mostly qualified but thin examples | Claims are supported, qualified, or removed |
| Rewrite action | Random editing | Action chosen but acceptance criteria weak | Matrix action and acceptance criteria are explicit |
| Internal links | No hub or sibling links | Links exist but route is weak | Hub, three siblings, artifact route, and service route are useful |
| CTA fit | Hard sell or unrelated route | CTA is relevant but too early or vague | CTA follows artifact and matches reader task |
| Technical readiness | Missing canonical, schema, or measurement | Most slots present with small issues | Canonical, schema, breadcrumbs, metadata, and events are clean |
| Operational readiness | No owner or rollback note | Owner known but monitoring weak | Owner, measurement, and rollback trigger are documented |
| Brand boundary | Fake proof, private labels, or route mixing | Minor wording risk | Clean B2B, no fake proof, no route contamination |
Maximum score: 50.
Publish Thresholds
| Score | Status | Action |
|---|---|---|
| 45-50 | PM review candidate | Send to publish QA checklist |
| 38-44 | Revision candidate | Fix weak categories and rescore |
| 30-37 | Rewrite needed | Return to rewrite matrix |
| 0-29 | Hold | Rebuild brief or revisit overlap map |
Zero-score blockers:
- Reader value;
- Intent fit;
- Differentiation;
- Evidence;
- Technical readiness;
- Brand boundary.
Any zero in these categories blocks publish review even if the total score is high.
Example Score
| Category | Score | Note |
|---|---|---|
| Reader value | 5 | Includes a concrete rewrite matrix |
| Intent fit | 5 | Query, title, artifact, and CTA align |
| Differentiation | 4 | Slight overlap with brief article but unique action-owner fields |
| Evidence | 4 | No invented metrics; could add one more example |
| Rewrite action | 5 | Action types and acceptance criteria are clear |
| Internal links | 5 | Hub, siblings, tool, and service route included |
| CTA fit | 4 | Relevant route; final copy needs approval before launch |
| Technical readiness | 5 | Canonical, schema, and measurement slots present |
| Operational readiness | 4 | Owner role and threshold present; monitoring owner needs final assignment |
| Brand boundary | 5 | Clean B2B and no fake proof |
| Total | 46 | PM review candidate |
Review Workflow
Score the page independently from the draft owner.
Mark every category with a score and short note.
Apply zero-score blockers.
Return failed pages to the rewrite matrix or content brief.
Send passed pages to the pack publish QA checklist.
Record measurement events and rollback trigger before any public approval request.
QA Notes Template
| Field | Required value |
|---|---|
| URL | Canonical path |
| Score date | Local review date |
| Reviewer role | Content lead, SEO owner, or marketing engineer |
| Total score | 0-50 |
| Blockers | Category and reason |
| Fix owner | Role |
| Required next action | Brief, rewrite, technical fix, PM review, or hold |
| Measurement events checked | Yes or no |
| CTA route checked | Yes or no |
| Publish approval status | Local review only |
Optional CTA
If a batch has repeated low scores, use the content diagnostic placeholder to find the shared cause before rewriting more pages. Teams with accepted scorecards can route implementation work into an Implementation Sprint. The scorecard improves review discipline; it does not guarantee search, revenue, or approval outcomes.