Rewrite Matrix: Choose the Right Fix for Thin Pages
SEO Slots
| Slot | Value |
|---|---|
| seo_title | Rewrite Matrix for Thin Content Fixes |
| meta_description | Use a rewrite matrix to choose whether a thin page needs expansion, consolidation, differentiation, evidence, internal links, or a new brief. |
| slug | rewrite-matrix |
| primary_query | content rewrite matrix |
| secondary_queries | content rewrite matrix, content rewrite matrix checklist, content rewrite matrix template |
| search_intent | operational checklist |
| canonical_path | /resources/content-thinness-lab/rewrite-matrix/ |
| og_title | Rewrite Matrix for Thin Content Fixes |
| og_description | Use a rewrite matrix to choose whether a thin page needs expansion, consolidation, differentiation, evidence, internal links, or a new brief. |
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/content-briefs/
- Related article: /resources/content-thinness-lab/qa-scoring/
- Tool/service route: /services/diagnostic-sprint/
Structured Data
Recommended schema: Article, BreadcrumbList. Keep BreadcrumbList aligned with /resources/content-thinness-lab/rewrite-matrix/. 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_rewrite_matrix |
| event_click_artifact | click_artifact_content_thinness_lab_rewrite_matrix |
| event_click_cta | click_cta_content_thinness_lab_rewrite_matrix |
| 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.Once a page is diagnosed as thin, the tempting move is to "add more content." That is often the wrong fix. A page may need evidence, differentiation, consolidation, a new brief, cleaner internal links, or removal from the search landing-page plan.
A rewrite matrix makes the fix explicit.
Rewrite Matrix
| Diagnosed issue | Do not do this | Better action | Owner decision | Acceptance criteria |
|---|---|---|---|---|
| Missing reader artifact | Add generic paragraphs | Add a checklist, rubric, matrix, or template tied to the query | Content lead | Artifact can be reused without reading the whole article |
| Intent mismatch | Keep title and patch body | Rebuild outline around the primary query | Editor | H1, intro, headings, artifact, and CTA answer one intent |
| Overlap with sibling | Rewrite both pages separately | Choose keep, merge, differentiate, noindex, or retire | SEO owner | Overlap map records unique job for each URL |
| Unsupported claims | Add confident wording | Replace with evidence, remove claim, or add verification note | Reviewer | No claim requires hidden proof or invented metrics |
| Weak internal route | Add many links | Add hub, three siblings, artifact route, and relevant service route | Content ops | Links help the reader continue the diagnostic sequence |
| CTA mismatch | Make CTA louder | Move CTA after artifact and align to diagnostic or implementation route | Growth owner | CTA extends the article's task and avoids pressure |
| Template contamination | Edit article copy only | Check metadata, canonical, schema, breadcrumbs, and tracking | Marketing engineer | Technical slot passes before PM review |
| Repeated thinness after rewrite | Ask for another draft | Build a stronger content brief with evidence and acceptance fields | Content lead | Brief prevents the same failure pattern |
Action Types
Expand
Use when the page has a unique intent but lacks examples, decision criteria, or proof. Expansion should add usable structure, not filler.
Required output:
- new artifact section;
- at least one concrete example;
- updated internal links;
- QA score after rewrite.
Differentiate
Use when pages overlap but both deserve to exist. Differentiation must change the reader job, artifact, and CTA route.
Required output:
- unique title promise;
- unique artifact;
- unique internal links;
- overlap map note explaining why both pages remain.
Merge
Use when two pages solve the same task and one page can become the stronger canonical destination.
Required output:
- chosen target URL;
- sections to preserve;
- redirect or internal link update plan;
- rollback note.
Noindex
Use when a page is useful for existing users but should not be a search landing page.
Required output:
- reason for noindex;
- internal route retention decision;
- measurement note;
- owner approval.
Retire
Use when the page has no unique user job, no evidence, no route, and no consolidation value.
Required output:
- replacement destination or archive note;
- internal link cleanup list;
- measurement watch list;
- owner approval.
Rewrite Queue Template
| URL | Issue | Action | Owner | Acceptance criterion | Measurement event | Status |
|---|---|---|---|---|---|---|
| /resources/example/page-a/ | Missing artifact | Expand | Content lead | Adds decision matrix and example | view_article_example_page_a | Ready for brief |
| /resources/example/page-b/ | High overlap | Merge | SEO owner | Target selected and sibling links updated | click_artifact_example_page_b | Needs owner decision |
| /resources/example/page-c/ | CTA mismatch | Rewrite route | Growth owner | CTA follows artifact and uses approved placeholder | click_cta_example_page_c | Ready for QA |
Acceptance Criteria Checklist
- The page has one primary intent.
- The artifact solves a real operator task.
- The page's unique job is clear in the overlap map.
- Claims are either supported, qualified, or removed.
- Internal links include hub and siblings.
- CTA appears after value and matches the task.
- Measurement events are named.
- Publish QA score meets the threshold.
Optional CTA
If the matrix produces a multi-page fix queue, an Implementation Sprint can turn the accepted actions into briefs, rewrites, technical checks, and final QA. The placeholder route is a planning path only; public forms, payments, and publishing remain approval-gated.