Thin Content and Content Ratio

Screpy provides two related filters: Thin Content for pages with fewer than 300 words and Low Content Ratio when visible text represents less than 10% of the analyzed page content. Both are diagnostic thresholds, not universal search-engine quality rules.

Separate quantity from usefulness

Word count measures volume, not whether a page solves its visitor's task. A concise contact page, calculator, product selector, or login screen can be complete with little text. A 2,000-word article can still be unhelpful if it is repetitive, outdated, or written for keywords rather than people.

Content ratio asks a different question: how much of the page is meaningful text compared with shared navigation, markup, scripts, styling, and other surrounding material. A low ratio can reveal heavy templates or sparse main content, but modern applications can legitimately contain substantial interface code.

Analyze the filtered set

1. Label each URL by purpose and page type.
2. Compare like with like: product pages against products, not articles.
3. Inspect the main content rendered to a visitor.
4. Check whether important information is hidden behind client-side rendering, tabs, authentication, or failed requests.
5. Review queries and conversions to understand what users expect.
6. Group repeated findings by template and content field.

Ask whether the page provides unique information, satisfies its intended query, and deserves a separate indexable URL. Do not add filler merely to cross 300 words.

Decide the right action

• Expand a valuable page when essential questions, evidence, specifications, or comparisons are missing.
• Consolidate overlapping pages when several thin URLs serve the same intent.
• Improve templates when navigation and repeated blocks overwhelm the main content.
• Keep concise pages concise when they complete a clear task.
• Exclude or remove low-value generated URL spaces when they have no independent purpose.

Example decision

A product template produces 600 pages with 120 words. The pages contain unique specifications, price, availability, images, and purchase actions, and they match specific product searches. Do not expand all of them to 300 words. Improve only products missing decision-critical details. By contrast, 80 location pages differing only by city name require consolidation or substantial unique local value.

Verify the work

Publish the change and run a new crawl. Confirm main content is present in the fetched output, ratios changed for the intended templates, and no new duplicate pages were created. Measure search and conversion outcomes over a comparable period rather than declaring success from word count alone.

Evaluate usefulness before word count

Thin Content and Low Content Ratio are review signals. Neither defines a universal minimum word count. A concise calculator, contact page, glossary entry, or product specification can satisfy its purpose with little prose. A long page can still be unhelpful when it repeats generic text.

Review the main content against the page's intent:

• Does it answer the question or complete the task?
• Is important information unique to this URL?
• Is the content visible in rendered HTML?
• Is navigation or boilerplate dominating the page?
• Does another URL serve the same intent better?

Choose the right action

Add content only when readers need missing explanation, evidence, examples, comparisons, or next steps. Consolidate overlapping pages when each is too narrow to stand alone. Remove or noindex pages that have no search purpose and no user value, but avoid mass actions based only on a threshold.

For programmatic or faceted pages, inspect several template states. Empty categories, unavailable products, and unfiltered listings often create low-ratio patterns that need product or indexing rules rather than more paragraphs.

Interpreting change

If Thin Content falls after expansion, confirm engagement and clarity did not suffer. If it falls because pages were consolidated, expect total page count to decrease and redirects to increase temporarily. A rising count after publishing may simply reflect new short-form page types.

Google explicitly states that it has no preferred word count in its people-first content guidance. Use Screpy to find candidates, then improve the experience rather than chasing length.

Related guidance

Return to the Pages overview to compare content signals across the crawl. Google's spam policies clarify why adding large amounts of low-value text is not a valid response to a thin-content finding.