How to Fix Thin Service and Product Pages (Under 500 Words)
Your service and product pages are the ones that earn revenue, but many are a headline, a photo and two short paragraphs. This guide shows you how to find every money page under 500 words, add useful buyer information to each one, and confirm that the new content is in the page HTML where crawlers can read it.

Why it matters
Thin money pages give Google and AI assistants little to match against specific queries such as "waterproof hiking boot for wide feet" or "emergency plumber pricing Leeds," so they rank for fewer long-tail terms and are rarely quoted in AI answers. Buyers who can't find specs, pricing context or answers to their objections leave for a competitor or contact you with questions the page should have answered. The audit flags the site when 40% or more of its service/product pages have fewer than 500 words, so fixing the worst pages first changes the result quickly.
What you need
Step-by-step fix
List every service and product page with its word count
Crawl the site and export word counts for the URLs that sell something: /services/, /products/, /product/, /shop/ and individual offering pages. In Screaming Frog, run the crawl, open the Internal tab, filter to HTML, and sort by the Word Count column, then export. For a single page, paste the snippet below into the browser console (F12 > Console) to count the words in the main content area.
(document.querySelector('main') || document.body).innerText.trim().split(/\s+/).filter(Boolean).lengthPrioritise pages by revenue and search demand
Mark every page under 500 words. Then sort that list by revenue, conversions or Search Console impressions (Performance > Search results > Pages tab). Fix the highest-value pages first.
Because the check fails when 40% or more of money pages are thin, also consider merging or noindexing near-duplicate variants (for example, colour-only product pages) instead of padding each one.
Build a reusable content outline for money pages
Use one consistent outline so every page gets the same kind of depth. A strong outline covers:
- What it is and who it's for (2-3 short paragraphs)
- Specifications or what's included (table or list)
- Use cases or scenarios with concrete examples
- Process, delivery or setup steps
- Pricing factors (what affects cost, even if you don't publish a price)
- Comparison with alternatives or your other tiers
- FAQs from real sales and support questions
Each section should answer a question a buyer actually asks. Don't add filler to reach a word count.
Add a specs table and use-case section
Put specifications in a real HTML table rather than an image so search engines and AI tools can read and quote the values. Follow it with 2-4 use cases that name a situation, the problem and the result. Use specific numbers, materials, dimensions, turnaround times and standards.
<section id="specs">
<h2>Specifications</h2>
<table>
<tr><th scope="row">Material</th><td>Full-grain leather, Gore-Tex lining</td></tr>
<tr><th scope="row">Weight</th><td>540 g per boot (UK 9)</td></tr>
<tr><th scope="row">Widths</th><td>Standard, Wide (2E)</td></tr>
<tr><th scope="row">Warranty</th><td>2 years</td></tr>
</table>
</section>
<section id="use-cases">
<h2>Who the Example Co Ridge Boot suits</h2>
<h3>Multi-day hikes on wet ground</h3>
<p>The sealed lining kept feet dry in our 6-hour stream-crossing test...</p>
</section>Add a comparison and an FAQ section
A comparison helps buyers choose and gives search engines content for "X vs Y" queries. Compare your tiers, models or your service against the common alternative. Then add 5-8 FAQs with direct 40-80 word answers.
Native <details> elements keep the page tidy while keeping the text in the HTML.
<section id="compare">
<h2>Repair vs full replacement</h2>
<table>
<thead><tr><th></th><th>Repair</th><th>Replacement</th></tr></thead>
<tbody>
<tr><th scope="row">Typical cost</th><td>£300-£1,200</td><td>£5,000-£12,000</td></tr>
<tr><th scope="row">Time on site</th><td>1 day</td><td>3-5 days</td></tr>
<tr><th scope="row">Best when</th><td>Damage under 30% of roof</td><td>Widespread leaks, roof over 25 years old</td></tr>
</tbody>
</table>
</section>
<section id="faq">
<h2>Roof repair FAQs</h2>
<details>
<summary>Can you repair a roof in the rain?</summary>
<p>We can fit temporary tarping in light rain to stop water getting in...</p>
</details>
</section>Make sure the new content is in the server HTML
Content loaded by JavaScript after the page renders, inside iframes, or only in images may not be counted or indexed reliably. Right-click the page, choose View Page Source (not Inspect), and search (Ctrl+F / Cmd+F) for a sentence from your new FAQ. If it isn't in the source, move it into the template or CMS field that renders on the server.
Tabs and accordions are fine as long as the text is in the source.
curl -s https://example.com/services/roof-repair | grep -c "Can you repair a roof in the rain"
Re-crawl and confirm the word counts
Re-run your crawler on the money-page list and check that each updated page now shows 500+ words, ideally 600+ to allow for template text. Calculate the share of money pages still under 500 words; it needs to be below 40% to pass, and as close to zero as you can get. In Search Console, use URL Inspection > Request indexing for your most important updated pages, then run the audit again.
Platform-specific notes
WordPress / WooCommerce
Edit the main product content in Products > All Products > Edit, in the large description editor, not the Product short description box, which many themes show only beside the price. Some themes put the description in a tab; that's fine because tabs are in the HTML. For services, add Table, Details and Heading blocks in the block editor.
Shopify
Edit Products > [product] > Description. For specs shared across products, create product metafields (Settings > Custom data > Products) and connect them to a block in Online Store > Themes > Customize > Product template. Content from review or FAQ apps loaded by JavaScript may not appear in the page source, so check View Page Source after adding it.
Wix
In the Editor, add text, a Table and a FAQ element to the service or product page. On Wix Stores, use Store Products > [product] > Info sections for specs and care details. Confirm that these render in the published page source.
Webflow
Add Rich Text fields for Specs, Use cases and FAQs to the Products or Services CMS Collection, bind them to elements on the Collection template page, and publish. Then every item can be filled in from the CMS without changing the design.
Next.js / headless
Render the new sections with server components, getStaticProps or SSR so they are in the initial HTML. Content fetched client-side in useEffect will not appear in View Page Source, and crawlers may miss it.
Check that it worked
✅ How to verify
- Re-crawl with Screaming Frog or Sitebulb and confirm every updated money page shows 500+ words in the Word Count column, with fewer than 40% of money pages still below 500.
- Open View Page Source on three updated pages and search for a sentence from the new FAQ and specs sections to confirm they are server-rendered.
- Use Search Console URL Inspection > View crawled page > HTML to confirm Google sees the new sections.
- Re-run the audit and check that the content-depth check passes.
⚠️ Common mistakes
- Padding pages with generic boilerplate or the same paragraph on every product, which creates duplicate content instead of depth.
- Putting specs, comparisons or FAQs in images, PDFs or JavaScript-only widgets that crawlers don't count.
- Expanding only the top 3 pages while dozens of thin variant or location pages keep the failing share above 40%.
- Hiding the CTA or price below hundreds of new words. Keep the buying action near the top and put depth below it.
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
How many words should a product or service page have?
There's no ranking word count, but under 500 words rarely covers specs, use cases, pricing factors and common questions. Most well-built money pages land between 600 and 1,500 words. Write until the main buyer questions are answered, then stop.
Do words in tabs or accordions count for SEO?
Yes, if the text is in the HTML when the page loads. Google indexes content in tabs and accordions on mobile-first indexing. Content loaded only after a click through JavaScript is less reliable.
Will longer product pages hurt conversions?
Not if the price, key benefit and CTA stay above the fold and the extra depth sits below in scannable sections. Specs, comparisons and FAQs usually reduce pre-sale questions and returns.
Should I add FAQ schema to service pages?
You can add FAQPage markup, but Google shows FAQ rich results only for a limited set of authoritative government and health sites. The visible FAQ content is what helps rankings and AI answers, so prioritise writing good answers.
How to Build a Pillar and Cluster Content Structure
How to Fix Missing Cited Sources and Statistics in Articles
How to Fix Pages Missing Their Top Google Query in Title or H1
How to Add Author Bios and Expert Profile Pages to Your Site
How to Fix Content Gaps: Rank for Topics You're Missing
How to Fix E-E-A-T: Show First-Hand Experience in Content