The Thin Content Repair Manual

What Is Thin Content?

Thin content is not defined by word count alone. A 200-word product description can be complete. A 2,000-word guide can be thin. Thinness is about value density: the ratio of useful information to total page real estate.

A page is thin if it meets any of these criteria:

• Low unique body text: Under 300 words of unique content after removing navigation, headers, footers, and boilerplate.
• High boilerplate ratio: Over 50% of the page is repeated content (navigation, footers, sidebars, disclaimers, CTAs).
• No original insight: The page restates common knowledge without adding analysis, examples, data, or expert perspective.
• Unanswered core question: The page raises a question the reader came for but does not answer it.
• Doorway page: The page exists primarily to rank for a keyword and redirect or funnel users elsewhere.
• Auto-generated: The page was programmatically generated without human review or editorial oversight.

The Diagnosis Framework

Before repairing thin content, you must diagnose why it is thin. The same symptom (low word count) can have different causes. The wrong diagnosis leads to the wrong fix.

Step 1: Measure Unique Body Text

Strip navigation, headers, footers, sidebars, and repeated boilerplate. Count only the unique content in the main content area. Use these thresholds:

Step 2: Calculate Boilerplate Ratio

Boilerplate is content that appears on multiple pages: navigation, footers, sidebars, cookie notices, standard disclaimers, repeated CTAs. Calculate:

Boilerplate Ratio = (Total Words - Unique Body Words) / Total Words

A ratio over 0.5 (50%) signals that the page is more navigation than content. This is common on product pages and category pages. It is fixable by expanding the unique content, not by removing necessary navigation.

Step 3: Assess Originality

Originality is not about being first. It is about adding value beyond what is already available. Ask:

• Does this page include original examples, case studies, or data?
• Does it offer expert analysis or perspective not found elsewhere?
• Does it answer a question that competing pages leave unanswered?
• Would a reader bookmark this page instead of the top-ranking alternative?

If all answers are no, the page lacks originality even if it meets word count targets.

Step 4: Check for Unanswered Questions

Read the page from a reader's perspective. Write down every question that comes to mind. Then check: does the page answer each question? If the core question (the one the reader came with) is unanswered or deferred to another page, the content is thin.

The Decision Tree

Once you have diagnosed the thinness, use this decision tree to determine the repair strategy. Start at the top and follow the path.

Repair Strategies

Each branch of the decision tree leads to a repair strategy. Use the strategies below to execute the repair.

Expand Small Topics

Some topics are inherently small: a single feature, a narrow FAQ, a specific error message. These do not need 2,000 words. But they do need to meet the minimum for their page type.

How to expand:

1. Add context: Why does this feature exist? What problem does it solve? Who benefits most?
2. Add examples: Show the feature in use. Include before/after, input/output, or step-by-step.
3. Add related information: What should the reader know next? What are common mistakes? What are the limitations?
4. Add proof: Screenshots, data, testimonials, case studies that support the claims.

Example: A 100-word FAQ answer becomes 250 words by adding context (why this matters), an example (concrete scenario), and a related link (where to learn more).

Consolidate a Series

When you have many thin pages that are part of a logical series (product variants, location pages, category pages), consolidation is often better than expansion. One strong page beats ten weak pages.

How to consolidate:

1. Identify the parent topic: What broader topic encompasses all the thin pages?
2. Create a comprehensive parent page: Cover the parent topic with enough depth to be authoritative.
3. Include variant information as sections: Each former page becomes a section or subsection of the parent.
4. 301 redirect old URLs to the parent: Pass link equity and signal the change to search engines.
5. Use anchors for direct access: If users need to jump to a specific variant, use URL anchors (e.g., /products/#variant-a).

Example: Ten thin location pages (50 words each) become one "Service Areas" page (800 words) with a section for each location. The old URLs redirect to the parent page with anchors.

Expand Existing Pages

Pages with traffic or inbound links deserve expansion. These pages have already earned attention. The goal is to make them worthy of that attention.

How to expand:

1. Audit competing pages: Find the top 3-5 ranking pages for the same topic. List what they cover that you do not.
2. Add missing subtopics: For each gap, add a section or paragraph. Do not fluff. Add genuine value.
3. Add original elements: Examples, data, screenshots, diagrams, case studies, expert quotes. Things competitors do not have.
4. Update outdated information: If the page is over 6 months old, check for stale stats, broken links, or outdated advice.
5. Add internal links: Link to related pages on your site. This signals depth and helps readers explore further.

Target: Aim for 2x the current word count as a first pass. If the page is under 500 words, target 1,000+. If it is 500-800, target 1,500+.

Merge and Redirect

Some pages should not exist as standalone pages. They are too narrow, too similar, or too low-value. Merging them into a broader page is better than expanding them artificially.

When to Merge

• Subtopic pages: A page about a single feature, a narrow aspect, or a specific subtopic that logically belongs to a broader guide.
• Duplicate variants: Multiple pages that differ only in minor ways (color, size, location) without unique content.
• Overlapping guides: Two or more guides that cover the same topic from slightly different angles.
• Orphan pages: Pages with no internal links pointing to them and no clear place in the site hierarchy.

How to Merge

1. Identify the target page: Which page will absorb the content? Choose the one with the most traffic, links, or logical fit.
2. Extract unique content: Copy the unique body text from the source page. Do not copy boilerplate, navigation, or repeated elements.
3. Integrate into the target: Add the content as a new section or subsection. Rewrite transitions to match the target's voice.
4. Set up 301 redirects: Redirect the source URL to the target URL (or to a specific anchor on the target URL).
5. Update internal links: Any page linking to the source should now link to the target.
6. Update the sitemap: Remove the source URL. Ensure the target URL is listed.

Redirect Best Practices

• Use 301 (permanent) redirects: This passes link equity and signals to search engines that the page has permanently moved.
• Redirect to the most relevant page: Do not redirect all thin pages to the homepage. Redirect to the page that best matches the original intent.
• Use anchors when appropriate: If the merged content is a section of a larger page, redirect to the anchor (e.g., /guide/#section-name).
• Test redirects: Verify that each redirect works and lands on the expected content.

When to Delete

Not all thin content should be repaired. Some pages should be deleted. Deletion is the right choice when repair would be more costly than removal.

When to Delete

• No unique purpose: The page does not serve a reader need that is not already met elsewhere on the site.
• No traffic or links: The page has no organic traffic, no inbound links, and no internal links pointing to it.
• Outdated beyond repair: The information is so outdated that updating would require rewriting the entire page.
• Low-value programmatic content: Auto-generated tag pages, date archives, author pages with no unique content.
• Legal or compliance risk: The page makes claims that cannot be substantiated or violates policies.

How to Delete Properly

1. Check for traffic and links: Use analytics and backlink tools to confirm the page has no value.
2. Return 410 (Gone) or 404 (Not Found): Do not redirect if there is no relevant target. A 410 signals that the page is intentionally removed.
3. Remove from sitemap: Ensure the deleted URL is not listed in sitemap.xml.
4. Update internal links: Remove or update any links pointing to the deleted page.
5. Monitor for 404 errors: Watch server logs or Search Console for 404s from external links. If significant traffic appears, consider redirecting to a relevant page.

When to Noindex Instead

Sometimes you want to keep a page accessible but remove it from search results. Use noindex when:

• The page is useful for users who have the URL but not valuable for search traffic.
• The page is temporary or transitional.
• The page is a filtered or sorted variant of a canonical page.

Add this meta tag to the page:

<meta name="robots" content="noindex, follow">

Prevention

The best thin content strategy is prevention. Use these practices to avoid creating thin content in the first place.

Pre-Publication Checklist

• [ ] Page meets minimum word count for its type
• [ ] Boilerplate ratio is under 50%
• [ ] Page includes at least one original element (example, data, insight, case study)
• [ ] Core reader question is answered on the page
• [ ] Page has a clear place in the site hierarchy
• [ ] Internal links point to and from the page
• [ ] Author and last-updated date are visible

Content Planning

• Outline before writing: List all subtopics before drafting. Ensure the outline is substantial enough to meet word count targets.
• Assign ownership: Every page should have an owner responsible for keeping it updated and complete.
• Set review cadence: Guides and cornerstones should be reviewed every 6 months. Product pages every 3 months. Blog posts annually.

Ongoing Monitoring

• Quarterly content audits: Review all pages for thinness using the diagnosis framework.
• Track performance: Pages with declining traffic or high bounce rates may need expansion or consolidation.
• Monitor Search Console: Look for "indexed, not submitted in sitemap" or "discovered, not indexed" statuses that may indicate thin content.

The Audit Workflow

Use this workflow to audit your existing content for thinness. Budget 2-3 hours for a small site (under 50 pages) or 1-2 days for a medium site (50-200 pages).

Step 1: Inventory All Pages

Export all URLs from your sitemap.xml. Add any known URLs not in the sitemap. Create a spreadsheet with columns for: URL, page type, word count, unique words, boilerplate ratio, traffic (last 30 days), inbound links, and disposition.

Step 2: Measure Each Page

For each URL:

1. Categorize the page type (homepage, product, guide, blog, landing, local, category).
2. Count total words and unique body words (strip navigation, footer, boilerplate).
3. Calculate boilerplate ratio.
4. Note traffic and inbound links (use analytics and backlink tools).
5. Assess originality (yes/no): does it include original examples, data, or insight?

Step 3: Apply the Decision Tree

For each page that fails the thresholds, apply the decision tree and record the disposition: Expand, Merge, Delete, or Noindex.

Step 4: Execute Repairs

Start with high-traffic pages. Expand or merge the top 10-20% first. Then work through the rest. Delete or noindex pages that have no traffic and no strategic value.

Step 5: Verify and Monitor

After repairs, verify that redirects work, sitemaps are updated, and internal links are fixed. Monitor Search Console and analytics for changes in indexing and traffic over the next 4-8 weeks.

Related Resources