Thin Page Symptoms: A Diagnostic Table for Weak Content
SEO Slots
| Slot | Value |
|---|---|
| seo_title | Thin Page Symptoms for Content Diagnostics |
| meta_description | Diagnose thin pages with a practical symptom table covering reader value, intent fit, overlap, evidence, internal links, and CTA readiness. |
| slug | thin-page-symptoms |
| primary_query | thin page symptoms |
| secondary_queries | thin page symptoms, thin page symptoms checklist, thin page symptoms template |
| search_intent | troubleshooting |
| canonical_path | /resources/content-thinness-lab/thin-page-symptoms/ |
| og_title | Thin Page Symptoms for Content Diagnostics |
| og_description | Diagnose thin pages with a practical symptom table covering reader value, intent fit, overlap, evidence, internal links, and CTA readiness. |
Search Intent
troubleshooting. 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/overlap-map/
- Related article: /resources/content-thinness-lab/rewrite-matrix/
- 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/thin-page-symptoms/. 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_thin_page_symptoms |
| event_click_artifact | click_artifact_content_thinness_lab_thin_page_symptoms |
| event_click_cta | click_cta_content_thinness_lab_thin_page_symptoms |
| 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.Thin content is not just a short article. A long page can be thin when it repeats common knowledge, answers the wrong intent, overlaps another page, lacks proof, or sends the reader into a confusing route. The first job is not rewriting. The first job is diagnosis.
Use this guide when a page has weak impressions, low engagement, no clear next step, or a pattern of near-duplicate content across the site.
What Makes a Page Thin
A page is thin when the reader cannot complete the task implied by the title and search intent. Length is only one clue.
Thinness often appears in five layers:
| Layer | What fails | Example signal |
|---|---|---|
| Reader value | The page does not help a real operator decide or act | Generic advice, no examples, no criteria |
| Intent fit | The page answers a neighboring query instead of the target query | Title promises diagnosis, body gives definitions |
| Differentiation | The page overlaps too heavily with siblings | Multiple pages share the same outline and claims |
| Evidence | Claims are unsupported or too broad | "Improves performance" with no source or method |
| Route | The page has no useful next step | Internal links and CTA are unrelated to the problem |
Thinness Symptom Decision Table
| Symptom | Likely cause | Evidence to check | Severity | First action |
|---|---|---|---|---|
| The page can be summarized in one generic paragraph | No practitioner artifact | Headings, examples, tables, templates, screenshots, decision criteria | High | Add a checklist, matrix, workflow, or example before polishing copy |
| Several pages share the same H2 pattern | Topic overlap or template cloning | Compare H1, H2, title tags, intros, internal links | High | Build an overlap map before rewriting |
| Search intent says "checklist" but the page gives a definition | Intent mismatch | Query, title, SERP pattern, body sections, artifact | High | Rewrite around the task promised by the query |
| The page has facts but no decision support | Weak usefulness layer | Tables, thresholds, examples, next actions | Medium | Add a decision table or rubric |
| The page uses broad benefit claims | Unsupported evidence | Claims, numbers, tool behavior, case claims, dates | Medium | Replace broad claims with observable checks or remove them |
| The CTA appears before the useful artifact | Funnel-first structure | CTA position, intro, section order, scroll depth | Medium | Move CTA after the artifact and make it optional |
| The page has no internal path to related content | Orphan or weak cluster | Hub link, sibling links, breadcrumbs, sitemap entry | Medium | Add hub and sibling links with clean route-relative paths |
| The page is useful but targets two unrelated intents | Mixed intent | Search query, H1, sections, CTA, related links | Medium | Split, refocus, or choose one primary intent |
| The page reads like a replacement for another page | Cannibalization risk | Ranking queries, title similarity, shared examples, backlinks | High | Map overlap and choose merge, differentiation, or canonical strategy |
| The page has no owner or rollback note | Operational thinness | Publish ticket, change log, page owner, monitoring plan | Medium | Add owner, measurement events, and rollback action |
Three-Minute Triage
Read the title, meta description, H1, first two sections, artifact, internal links, and CTA.
Mark the first visible symptom from the table.
Check whether the symptom is isolated or repeated across a cluster.
If repeated, stop single-page editing and build an overlap map.
If isolated, choose one rewrite action and define acceptance criteria.
This prevents a common mistake: improving sentence quality while leaving the page structurally thin.
Severity Rules
| Severity | Meaning | Allowed next action |
|---|---|---|
| Low | Page has one weak section but clear intent and artifact | Edit section, add example, keep URL |
| Medium | Page has useful parts but weak artifact, links, or evidence | Rewrite with matrix and QA score |
| High | Page overlaps siblings, misses intent, or lacks unique value | Map cluster before rewriting |
| Critical | Page creates trust, claim, or route risk | Hold from publication review until owner decision |
Common Diagnosis Mistakes
Mistake: Treating Word Count as the Main Test
Word count can reveal a risk, but it does not prove thinness. A concise page with a clear decision table can outperform a long page that repeats vague advice.
Mistake: Rewriting Before Mapping Overlap
If five pages have the same promise, editing one page may make the cluster worse. Use the overlap map before choosing which page should own which intent.
Mistake: Adding a CTA to Create Value
A CTA is not reader value. The page should stand on its own as a diagnostic asset, then offer a next step for teams that need help applying it.
Diagnostic Output
For each URL, record:
| Field | Example value |
|---|---|
| URL | /resources/example-cluster/page-a/ |
| Primary symptom | H2 overlap with sibling pages |
| Severity | High |
| Evidence | Same outline appears on three pages |
| First action | Build overlap map |
| Owner decision needed | Merge Page A and Page B, differentiate Page C |
| Next artifact | Overlap map |
Optional CTA
After you classify the symptoms, use the D01 content thinness diagnostic placeholder to group pages by severity and first action. Teams with a large batch can route the output into a content diagnostic review and then an Implementation Sprint. No ranking, traffic, or indexation outcome is guaranteed; the value is a cleaner decision path.