How to Fix Thin Content: Expand or Merge Pages Under 300 Words
Thin content means indexable pages that carry fewer than 300 words of real text, such as stub product pages, near-empty tag archives, one-paragraph service pages and placeholder posts. This guide shows you how to find every flagged URL and decide whether to expand, merge or noindex it. You will then apply the fix on your platform and confirm that the share of thin pages on your site has dropped.

Why it matters
Google's helpful-content signals are applied across the whole site. A large share of low-value pages can pull down rankings for your good pages too, and it wastes crawl budget on URLs that will never rank. AI answer engines like Google AI Overviews, ChatGPT search and Perplexity quote pages that answer a question in detail, so a 120-word page rarely gets cited.
Visitors also leave quickly when a page has no specifics, and that cuts conversions. Our audit scores this check by the proportion of crawled pages under 300 words, so a few short utility pages are tolerated but a site-wide pattern is not.
What you need
Step-by-step fix
Export every page under 300 words
Start from the URLs flagged in the audit. To get word counts for the whole site, crawl it in Screaming Frog. Then open Content > Word Count, or sort the Internal > HTML tab by the Word Count column and export everything below 300.
Add three columns from Search Console (Performance > Pages, last 12 months): clicks, impressions and backlinks. These numbers drive your decision in the next step.
curl -s https://example.com/services/roof-repair | sed -e 's/<script[^>]*>.*<\/script>//g' -e 's/<[^>]*>//g' | wc -w
Triage each URL: expand, merge, noindex or keep
Give every thin URL one action:
- Expand: the page targets a real search intent and has impressions or a commercial purpose.
- Merge: several pages cover the same topic, such as city variants, near-duplicate posts or one product per color.
- Noindex: the page must exist for users but has no search value, such as tag archives, internal search results, thank-you pages or login pages.
- Keep: short by nature and useful, such as a contact page. A few of these are fine.
- Delete (410): the page is outdated, has no traffic and has no backlinks.
Rule out content the crawler cannot see
Some pages look full in a browser but are thin in the HTML. The common causes are text injected by client-side JavaScript, text loaded inside iframes, text shown only after clicking a tab that fetches it over AJAX, or text baked into images. View the page with view-source: or curl and confirm your body copy is in the raw HTML.
If it is missing, render it server-side or statically before you write anything new.
curl -s https://example.com/products/oak-desk | grep -c "solid oak"
Expand pages with original, specific detail
Add content that only you can provide, not filler to reach a number. Useful material includes:
- specs, dimensions and materials
- pricing ranges and lead times
- step-by-step process
- real customer questions from support tickets
- comparisons with alternatives
- original photos with captions
- author or reviewer details
Structure it with descriptive H2s and a short FAQ that answers the queries Search Console shows for that URL. Aim for whatever fully answers the intent; 300 words is a floor, not a target.
<h2>How long does a roof repair take?</h2> <p>Most patch repairs by Example Co take 3-5 hours. Full section replacements over 20 m² usually take 1-2 days, weather permitting.</p> <h2>What affects the price?</h2> <ul> <li>Roof pitch and access (scaffolding adds €400-€900)</li> <li>Material: concrete tile, slate or EPDM</li> <li>Extent of underlying batten or deck damage</li> </ul>
Merge overlapping pages with 301 redirects
Pick the strongest URL in each group as the target. This is usually the one with the most traffic or backlinks. Move the unique facts from the weaker pages into it, then 301-redirect each weaker URL to the target.
Update internal links and your XML sitemap so they point straight to the target and not through the redirect.
# Nginx (inside the server block)
location = /roof-repair-leeds { return 301 /services/roof-repair; }
location = /roof-repair-bradford { return 301 /services/roof-repair; }
# Apache (.htaccess)
Redirect 301 /roof-repair-leeds /services/roof-repair
Redirect 301 /roof-repair-bradford /services/roof-repairNoindex or remove pages that should not rank
For thin pages users still need, add a robots meta tag and keep the page crawlable. txt, or Google cannot see the noindex. Remove these URLs from your XML sitemap.
For pages you delete outright, return a 410 or 404 status rather than a 200 'not found' page.
<meta name="robots" content="noindex, follow">
Re-crawl and confirm the thin-page ratio dropped
Re-run the audit and recrawl with Screaming Frog. Check three things:
- expanded pages now show 300+ words
- merged URLs return 301 to the right target
- noindexed pages show the noindex directive
In Search Console, use URL Inspection > Request indexing on the key expanded pages. Then watch Indexing > Pages over the next 2-6 weeks.
curl -sI https://example.com/roof-repair-leeds | grep -iE "^(HTTP|location)"
Platform-specific notes
WordPress
Edit pages in the block editor. For redirects, use Rank Math **Redirections** or the free Redirection plugin (**Tools > Redirection**). To noindex thin archives, go to Yoast **Settings > Categories & tags** (or **Settings > Advanced > Author archives**), or in Rank Math **Titles & Meta > Tags**, and set 'Show in search results' to off. For a single post, use the SEO panel's **Advanced** tab.
Shopify
Expand product and collection descriptions in **Products** or **Collections**, or add metafield-driven sections in the theme editor. Create redirects at **Online Store > Navigation > View URL redirects**, or bulk-import them as CSV. Shopify has no noindex toggle, so add `{% if template contains 'search' %}<meta name="robots" content="noindex">{% endif %}` (or a similar condition) to `theme.liquid`.
Wix
Add text in the Editor, keeping it as real text and not text inside images. Add redirects at **Dashboard > Settings > SEO > URL Redirect Manager** (location can vary by Wix version). Noindex a page via **Pages > ⋯ > SEO basics > Let search engines index this page**, switched off.
Webflow
Expand CMS items through Collection fields bound to the template. A rich-text field avoids the problem of every item sharing the same short template. Add redirects in **Site settings > Publishing > 301 redirects**. For noindex, add the robots meta tag in **Page settings > Custom code > Inside <head>**, and switch off **Sitemap indexing** for that page.
Next.js
Make sure body copy is server-rendered (App Router server components, or SSG/SSR), not fetched client-side after load. Add redirects in `next.config.js` with `redirects()` and `permanent: true`. For noindex, export `metadata = { robots: { index: false, follow: true } }` from the route.
Check that it worked
✅ How to verify
- Re-run the audit and confirm the number and percentage of pages under 300 words has dropped, with any remaining flags limited to intentional utility pages.
- Run curl -sI on each merged URL and confirm it returns a single-hop 301 to the correct target.
- Use Search Console URL Inspection > View crawled page to confirm the new text appears in the HTML Google rendered.
- After 2-6 weeks, check Search Console Indexing > Pages: noindexed URLs should appear under 'Excluded by noindex tag', and expanded pages should stay indexed.
⚠️ Common mistakes
- Padding pages with generic intros, repeated boilerplate or AI-spun text to pass 300 words. It clears the count but stays low-value and can be flagged as scaled content.
- Blocking thin pages in robots.txt instead of using noindex, which stops Google from ever seeing the noindex directive.
- Redirecting merged or deleted pages to the homepage instead of the closest relevant page.
- Loading the main text with client-side JavaScript or inside images, so crawlers still see a near-empty page.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Is 300 words a Google requirement?
No. Google has no minimum word count. The 300-word line is a practical threshold: pages below it rarely have enough substance to satisfy a query. A short page that fully answers its intent can rank. A site where many indexable pages are this short usually signals low value.
Should I delete thin content or improve it?
Improve pages that target a real search intent or already get impressions. Merge near-duplicates into one stronger page with 301 redirects. Noindex pages users need but searchers do not. Delete only pages with no traffic, no backlinks and no purpose, returning 410 or 404.
Do product pages and tag pages count as thin content?
Yes, if they are indexable and mostly empty. A product page with only a title, price and one-line manufacturer description is thin. Add specs, use cases, sizing, shipping details and reviews. Tag archives with one or two posts are usually best noindexed or consolidated into categories.
How long until fixing thin content improves rankings?
Individual expanded pages can move within days of being recrawled. Site-wide quality improvements usually take several weeks to a few months to show, as Google re-evaluates the site over multiple crawls and core updates.
How to Fix Duplicate Content Across Pages on Your Website
How to Fix Missing Video Entries in Your XML Sitemap
How to Fix Content Freshness: Dates, Updates & Last-Modified
How to Fix Heavy YouTube and Vimeo Embeds with Facades
How to Fix a Low Readability Score (Flesch Reading Ease)