Pre-Writing Analysis
1. What most Nashville businesses get wrong: The assumption that having a page is better than not having a page. Nashville businesses create location pages for 50 suburbs with 100 words each, service pages that say nothing beyond “we offer this service,” and blog posts that exist just to publish something. Thin pages don’t just fail to rank; they hurt site-wide quality signals.
2. The underlying mechanism: Google’s helpful content system evaluates site-wide content quality. A site with 100 pages where 60 are thin signals low overall quality, dragging down even the good pages. Thin content isn’t neutral; it’s negative. Fewer quality pages outperform many thin pages.
3. The differentiating Nashville angle: Nashville’s multi-location businesses are thin content factories. Creating pages for Nashville, Franklin, Brentwood, Murfreesboro, Mount Juliet, Hendersonville, Gallatin, Lebanon, Smyrna, and La Vergne with template content produces 10 thin pages. Each hurts the site. Better to have 3 strong regional pages than 10 thin location pages.
Thin content is any page that doesn’t provide sufficient value to justify its existence. The test isn’t word count; it’s whether a user would be satisfied if this was the only result for their query. Most Nashville location and service pages fail this test.
Minimum Content Standards
Establishing content standards for Nashville pages:
Service pages:
Minimum: 500 words of substantive content
Should include:
- What the service is and who needs it
- How the service process works
- Nashville-specific considerations
- Pricing transparency (range or factors)
- Why choose your company for this service
- FAQ section (3-5 questions minimum)
- Clear CTA
Test: Would this page satisfy someone searching “[service] Nashville” if it were the only result?
Location pages:
Minimum: 400 words of unique content per location
Should include:
- Location-specific information (not just address)
- Why you serve this area
- Local team member or point of contact
- Location-specific testimonial or case study
- Service area details for that location
- Location-specific contact method
Test: Is this page meaningfully different from other location pages?
Blog posts:
Minimum: 800 words for standard posts, 1,500+ for guides
Should include:
- Substantive information not easily found elsewhere
- Nashville-specific angle or data
- Actionable takeaways
- Supporting evidence or examples
Test: Would someone share this post because it’s genuinely useful?
Category pages:
Minimum: 150 words of introductory content
Should include:
- Category description
- What users will find
- Navigation guidance
Test: Does this provide context beyond just a list of links?
Thin Page Identification
Finding thin content on Nashville sites:
Method 1: Crawl analysis
Use Screaming Frog or similar:
- Filter pages by word count < 300
- Review pages with low content-to-HTML ratio
- Check pages with minimal unique text
Method 2: Analytics thin page signals
High bounce rate + low time on page + low pages/session often indicates thin content.
Sort by bounce rate descending, investigate top bouncers.
Method 3: Search Console performance
Pages with impressions but no clicks may have thin content (not compelling in SERP).
Pages with clicks but poor engagement may be thin (users leave quickly).
Method 4: Manual audit
For Nashville local businesses, manually review:
- All location pages
- All service pages
- Oldest blog posts
- Any template-generated pages
Thin content red flags:
- Word count under 300
- Template content with only location/service swapped
- No images or media
- No internal links out
- No external validation (links, citations)
- Written for search engines, not users
- Duplicates content from other pages
- No Nashville-specific information
- Generic content applicable to any city
- Missing key information users need
Content Enhancement
Improving thin pages:
Enhancement approach for service pages:
Current thin page:
“We offer plumbing services in Nashville. Our plumbers are experienced and professional. Contact us for all your plumbing needs. We serve Davidson County and surrounding areas.”
(50 words, zero value)
Enhanced version:
Expand to 600+ words including:
- Specific services offered (list with brief descriptions)
- Nashville plumbing challenges (older homes, hard water, specific issues)
- Service process (what to expect)
- Pricing structure (transparency)
- Team credentials
- Nashville-specific FAQ
- Recent Nashville project examples
- Clear contact pathway
Enhancement approach for location pages:
Current thin page:
“ABC Plumbing serves Franklin, Tennessee. Contact us for plumbing services in Franklin. We’re your local Franklin plumber.”
(25 words, zero value)
Enhanced version:
Expand to 500+ words including:
- Why Franklin has specific plumbing needs (new construction vs older areas)
- Franklin neighborhoods served
- Team member who covers Franklin
- Franklin customer testimonials
- Response times to Franklin
- Franklin-specific services (well water in rural areas, etc.)
- Local partnerships or community involvement
- Franklin office hours or service area map
Enhancement approach for blog posts:
Current thin post:
“5 Signs You Need a Plumber” with 5 bullet points and 200 words total.
Enhanced version:
Expand to 1,000+ words including:
- Each sign explained in detail
- Nashville-specific context for each sign
- When it’s DIY vs professional
- Cost implications
- Prevention tips
- Local examples or case studies
- Related resources
When enhancement isn’t worth it:
Sometimes thin pages should be removed rather than enhanced:
- Topic already covered better elsewhere on site
- No search demand for the topic
- Page serves no user need
- Cost of enhancement exceeds value
Location Page Solutions
Preventing thin location pages:
Option 1: Reduce location page count
Instead of 15 thin location pages:
- Nashville/Davidson County (comprehensive)
- Williamson County (Franklin, Brentwood, Nolensville)
- Rutherford County (Murfreesboro, Smyrna, La Vergne)
3 substantial regional pages instead of 15 thin city pages.
Option 2: Hub and spoke model
Main location page (Nashville) is comprehensive.
Sub-location pages are shorter but link to main for shared information.
Nashville page: 1,500 words covering full service
East Nashville page: 500 words unique + “See our full Nashville services” link
Option 3: Unique content requirements
Before creating location page, require:
- Minimum 400 words unique content
- Location-specific testimonial
- Location-specific case study or project
- Local team member photo/bio
- Location-specific FAQ (3+ questions)
If requirements can’t be met, don’t create the page.
Option 4: Programmatic with manual enhancement
Start with programmatic template for initial page structure.
Require manual unique content addition before indexing.
Keep pages noindexed until unique content threshold met.
Nashville location page checklist:
☐ Unique opening paragraph about this specific location
☐ Why we serve [Location] specifically
☐ Local team member or primary contact
☐ At least one testimonial from [Location] customer
☐ Location-specific challenge or consideration
☐ Response time or coverage specifics for [Location]
☐ Local landmark or neighborhood references
☐ Minimum 400 total words
☐ Not duplicate of any other location page content
Service Page Depth
Preventing thin service pages:
Service page content requirements:
Every Nashville service page needs:
- Service definition (100 words)
What is this service? Who needs it?
- Nashville context (150 words)
Why Nashville properties need this service.
Local factors (climate, housing stock, regulations).
- Service process (200 words)
Step-by-step what happens.
Timeline expectations.
What customer should prepare.
- Pricing section (100 words)
Price range or pricing factors.
What affects cost.
Free estimate offer.
- Why us section (150 words)
Differentiators for this service.
Credentials relevant to this service.
Nashville experience.
- FAQ section (200 words)
3-5 questions specific to this service.
Structured for featured snippets.
- Social proof (100 words)
Testimonials related to this service.
Case study reference if available.
- CTA section (50 words)
Clear next step.
Multiple contact options.
Total: 1,000+ words of substantive, structured content.
Service page template trap:
Many Nashville businesses use identical templates:
“[Service] is an important service for Nashville homeowners. At [Company], we provide professional [service] to the Nashville area. Contact us for your [service] needs.”
This produces 10 service pages with 95% identical content and 5% variable replacement.
Solution: Require unique content for each service:
- Different opening angle
- Different Nashville context
- Service-specific FAQ (not generic)
- Service-specific testimonials
- Unique value proposition per service
Quality Thresholds
Publishing standards for Nashville content:
Pre-publish checklist:
Content quality:
☐ Minimum word count met for page type
☐ Nashville-specific information included
☐ Not duplicate of existing content
☐ Provides value beyond what competitors offer
☐ Answers likely user questions
☐ Includes supporting evidence/examples
Technical quality:
☐ Unique title tag
☐ Unique meta description
☐ Header structure (H1, H2s)
☐ Internal links to and from relevant pages
☐ Images with alt text
☐ Schema markup where appropriate
User experience:
☐ Clear navigation path
☐ Mobile-friendly formatting
☐ Readable text (appropriate length paragraphs)
☐ Clear CTA
Gate before indexing:
Consider keeping new pages noindexed until quality review:
- Create page (noindex by default)
- Quality review against checklist
- If passes, remove noindex
- If fails, enhance before indexing
This prevents thin pages from ever entering Google’s index.
Ongoing quality maintenance:
- Quarterly audit of lowest-performing pages
- Annual full content audit
- Remove or enhance pages that don’t meet standards
- Track thin page ratio (thin pages / total pages)
Goal: Zero thin pages. Every indexed page should pass quality threshold.