Short answer: Fix thin content in Search Console by using the Manual Actions and Performance reports to identify low-quality pages. Then improve, merge, or remove them—focusing on adding unique value, better depth, and proper formatting.
Key takeaways
- Thin content lacks substance or unique value for users.
- Search Console flags it via manual actions or low impressions.
- Fix it by expanding, merging, or deleting pages.
- Use the Performance report to find underperforming pages.
- Redirect or consolidate thin content after improvement.
What you will find here
- What Does Thin Content Mean in Search Console?
- Find Thin Content with Search Console Reports
- Deeper Dive: Use the Page Indexing Report
- Assess Which Pages to Fix, Merge, or Remove
- How to Decide Between Merge and Remove
- Fix Thin Content: A Step-by-Step Plan
- Avoid Common Mistakes When Fixing Thin Content
- Monitor Progress After Fixes
You open Search Console and see a manual action for thin content. Or maybe your best pages have been slipping. Thin content is a ranking killer. But it’s also fixable. Here’s how to find it and turn it around.

What Does Thin Content Mean in Search Console?
Google’s thin content penalty targets pages that don’t add real value. Auto-generated pages, scraped content, or short, shallow articles all qualify. In Search Console, you’ll see it as a Manual Action under the Manual Actions report. If you have no manual actions, thin content may still hurt you in the algorithm.
The fix? Audit your site. Identify patterns. Then improve or remove low-quality pages.
Find Thin Content with Search Console Reports
You don’t have to guess. Use these Search Console reports to spot thin content.
The Manual Actions Report
Go to Security & Manual Actions > Manual Actions. If you see “Thin content” or “Low-quality content,” the affected pages are listed. Click them to see the specific issue.
The Performance Report
Under Performance, set a filter for pages with low impressions (e.g., fewer than 50 in 3 months) and low CTR. These often correlate with thin content. Another method: sort by position and look for pages ranking 30–50+ with no clicks—they likely need improvement.
Combine both reports to prioritize: pages with a manual action are urgent; pages with no impressions need attention before they become a problem.
Deeper Dive: Use the Page Indexing Report

In Search Console, the Page Indexing report (under Index) shows you which pages are indexed and which are not. Thin content that Google chose not to index often appears here. Look for pages with status “Discovered – currently not indexed” or “Crawled – currently not indexed.” These may have been evaluated as low-quality. Click into the example URLs to see patterns. If a category of page (like tag pages or outdated blog posts) is consistently non-indexed, those are prime candidates for thin content. Address them before they drag down your site’s overall reputation.
Assess Which Pages to Fix, Merge, or Remove
Not every thin page deserves the same treatment. Use this guide:
| Page Type | Action | Example |
|---|---|---|
| Thin, but has potential | Expand with unique detail, examples, data | A 100-word product description |
| Several thin pages on same topic | Merge into one comprehensive guide | Multiple shallow blog posts about the same keyword |
| No traffic, no value, no backlinks | Delete or noindex | A placeholder page that never got content |
| Scraped or auto-generated | Rewrite from scratch or remove | Pages copied from other sites |
Be honest about what you can improve. If you can’t write 500+ words of original value, it’s better to remove and redirect.
How to Decide Between Merge and Remove
When two or more pages cover the same topic, merging is usually better than deleting with no redirect. Merging preserves any link equity. To merge, choose the page with the strongest backlink profile or highest traffic. Rewrite it to include the best from all other pages. Then set up 301 redirects from the merged pages to the surviving one. But if a page has zero traffic, zero backlinks, and no useful content, removing it (with a redirect to a relevant parent page) is cleaner. Use tools like a backlink checker to see which pages have external links. Pages with links are worth saving.
Fix Thin Content: A Step-by-Step Plan
Once you’ve identified the thin pages, here’s how to fix them:
- Bulk up the content. Add at least 300–500 words of original information: step-by-step instructions, examples, screenshots, or expert tips. Aim to cover the topic more deeply than any competing page.
- Improve formatting. Use subheadings, bullet points, and images to make it scannable. A well-structured page can earn better dwell time.
- Add internal links. Link to relevant pages on your site. This signals depth and helps Search Console understand your site’s structure. For example, you can reference how to use Search Console to optimize content.
- Review duplicate or similar content. If you have multiple pages about the same thing, merge them. Use 301 redirects from the removed URLs to the single surviving page.
- Submit for review. Once you’ve made changes, if the issue was a manual action, go back to Manual Actions and click “Request Review.” Write a concise summary of what you fixed.
Remember: thin content fixes take time to reflect in rankings. Expect 2–4 weeks after changes, especially if you requested a review.
Avoid Common Mistakes When Fixing Thin Content
Many site owners make things worse. Avoid these pitfalls:
- Padding with fluff. Don’t just add irrelevant text to hit a word count. That’s still thin content.
- Ignoring user intent. If users want a quick answer, a 2000-word essay might be ignored. Match intent first.
- Noindexing instead of improving. Noindexing a thin page hides it from Google but wastes any authority it had. Improve or redirect instead.
- Forgetting related issues. Thin content often overlaps with duplicate content. Check for both simultaneously.
Also, don’t confuse thin content with low word count alone. A 100-word FAQ page that directly answers a question can be valuable. Judge by the reader’s experience.
Monitor Progress After Fixes
After making changes, track your progress in Search Console. Check the Performance report for the affected pages. Look for gradual increases in impressions and clicks. If you requested a manual action review, monitor the Manual Actions report for the status change.
You can also compare your site’s analytics with Search Console data. For deeper insight, see our guide on Search Console vs Google Analytics when diagnosing content performance.
Consistency matters. Schedule a quarterly content audit using Search Console to catch thin content before it becomes a penalty.
Frequently asked questions
What is considered thin content by Google?
Thin content refers to pages that provide little to no added value to users. Examples include auto-generated text, scraped content, doorway pages, and very short articles that don’t cover the topic adequately. Google’s search quality guidelines define it as low-quality pages that lack substance.
How do I find thin content on my site?
Use Google Search Console’s Manual Actions report to spot penalties. Also, filter the Performance report for pages with very low impressions and clicks. Tools like a site crawl can reveal extremely short pages or those with high bounce rates.
Can I recover from a thin content manual action?
Yes. Identify the affected pages, either improve them with original content, merge them with other pages, or remove them. After fixing all issues, request a review in Search Console with a detailed explanation of the changes you made.
Should I delete thin content or improve it?
Improve it if the page has potential or external backlinks. If it’s beyond repair—like scraped content—remove it and 301 redirect the URL to a relevant, high-quality page. Deleting without redirecting can waste existing ranking signals.
How long does it take for thin content fixes to work?
It depends. Algorithmic devaluation can take weeks to lift. If you had a manual action, Google typically reviews and resolves requests within a few weeks. Monitor your Search Console reports for changes over 2–4 weeks after fixes.