Book a Call

Why Most Service Business Websites Don't Rank on Google (And How to Fix It)

TL;DR: Service business websites usually fail to rank for one of nine reasons, and almost none of them are about "needing more content". The real killers are: a broken canonical setup, missing or wrong schema, slow Core Web Vitals, thin city pages, no internal linking, a weak Google Business Profile, JavaScript-rendered content Google cannot see, duplicate page templates, and missing review signals. Fix the technical foundation first, then write more, or you are pouring content into a leaky bucket.

Want more local customers to find your business? Review your service and town pages, Google profile and quote path. See what we would improve for your trade and service area. Local SEO for contractors.

Key takeaways

  • A wrong canonical can consolidate pages under another URL. Check Google's selected canonical before assuming a page needs more content.
  • JavaScript-rendered sites require an extra rendering step. Inspect what Google actually sees rather than assuming a framework causes a fixed traffic loss.
  • Page experience matters, but Google prioritizes relevant content even when experience is imperfect. There is no published 75-point PageSpeed ranking filter.
  • Your Google Business Profile is how you appear in the "near me" map results. A perfect website with a weak GBP still loses there.
  • "Write more content" is the most common, and least useful, advice given to service businesses with ranking problems.

Table of contents

How to tell if you actually have a ranking problem

Before assuming Google hates you, check the data:

  1. Search Console → Performance. Sort by impressions, not clicks. Impressions show that a result was displayed, but zero clicks can reflect position, intent or presentation. Zero impressions for a query do not prove the page is absent from the index; inspect the URL separately.
  2. Search Console → Indexing → Pages. Compare "Indexed" count vs your sitemap count. Check the reasons for excluded URLs. Redirects, duplicates and intentionally excluded pages mean the sitemap and indexed counts need context.
  3. site:yourdomain.com in Google. Quick way to see what Google has. Use it as a rough spot-check, not a complete index count; URL Inspection is the better diagnostic for an individual page.

Now, the nine real reasons.

Reason 1: Your canonical tags are broken

This is the silent killer. If every page on your site has a <link rel="canonical" href="https://yoursite.com/" /> pointing back to the homepage, Google treats every URL as a duplicate and consolidates them. Your blog post, your city page, your service page, all collapsed into one.

For a single-page application, inspect both the initial HTML and rendered page. A template that points every route at the homepage can conflict with the intended page-specific canonical.

How to check:

  1. Open any non-homepage URL on your site.
  2. View page source (Ctrl+U / Cmd+U).
  3. Search for canonical.
  4. The href should match the URL you are on. Not the homepage.

How to fix:

  • Static HTML sites: Edit each page's <head> to set the correct canonical.
  • WordPress: Yoast or Rank Math auto-handles this. Make sure neither is set to "canonical to homepage" by accident.
  • SPAs (React, Vue): Pre-render each route to static HTML at build time, with the correct canonical baked in. Google's JavaScript guidance recommends consistent canonical signals between initial and rendered HTML; do not change an existing canonical to a different URL during rendering.

For the SPA fix specifically, see the next section.


Want a website built right the first time? Our website design service ships custom service business sites at $2,499 one time, or $297 a month with all the fundamentals, accurate schema, service and city pages, quote forms and performance-conscious implementation. Or book a free strategy call.


Reason 2: Your site is a JavaScript SPA with no pre-rendering

If your site is built in React, Vue, or any other client-side framework without server-side rendering or pre-rendering, Google has to execute JavaScript to see your content. Google can do this, but:

  • Rendering adds a step. Google says the queue may take seconds or longer; it does not give a fixed days-or-weeks delay.
  • Failed scripts, blocked resources or rendering errors can prevent content from being seen. Inspect the tested HTML and screenshot.
  • It is the wrong default for an SEO-focused site

How to check:

  1. Go to Google Search Console.
  2. Use the URL Inspection tool on a blog post or service page.
  3. Click "Test Live URL" → "View Tested Page" → "Screenshot".
  4. If the screenshot is blank or shows a loading spinner, Googlebot can not render your content reliably.

How to fix:

Three options, in order of effort:

  1. Pre-render at build time. A small script that visits every URL during your deploy and saves the rendered HTML. Tools: vite-plugin-prerender, react-snap, puppeteer + a custom script. We use pre-rendering on this site. The effort depends on the routing, data and interactive features involved.
  2. Static site generation (SSG). Migrate to a framework that pre-builds every page: Astro, Next.js with output: 'export', Gatsby. Bigger change, better long-term.
  3. Server-side rendering (SSR). Next.js or Remix with SSR. Best for dynamic content, more infrastructure complexity.

For a service business site that does not change minute-by-minute, option 1 (pre-render at build time) is usually the right answer.

Reason 3: Missing or wrong schema markup

Schema is how you tell Google what your page is, not just what it says. For local service businesses, two schema types are non-negotiable:

LocalBusiness schema, on every page that represents your business:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Your Business Name",
  "image": "https://yoursite.com/photo.jpg",
  "telephone": "+1-555-555-5555",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "Phoenix",
    "addressRegion": "AZ",
    "postalCode": "85001",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 33.4484,
    "longitude": -112.0740
  },
  "url": "https://yoursite.com",
  "priceRange": "$$",
  "openingHours": "Mo-Fr 09:00-17:00"
}

Service schema, on each service page:

{
  "@context": "https://schema.org",
  "@type": "Service",
  "serviceType": "Artificial Turf Cleaning",
  "provider": { "@type": "LocalBusiness", "name": "Your Business Name" },
  "areaServed": { "@type": "City", "name": "Phoenix" },
  "description": "Professional artificial turf cleaning..."
}

How to check: Run any page through Google's Rich Results Test. It will tell you exactly what schema it found and what is missing.

Most common mistakes:

  • Choosing a type that misrepresents the business or inventing locations
  • Expecting review stars for self-serving LocalBusiness reviews: Google makes these ineligible, including third-party widgets
  • priceRange left as the default placeholder
  • Schema present on the homepage only, missing from service and city pages

Reason 4: Slow Core Web Vitals on mobile

Core Web Vitals measures loading, interaction and visual stability. Assess field data at the 75th percentile, separately for mobile and desktop:

Metric "Good" "Needs improvement" "Poor"
LCP ≤ 2.5s > 2.5 to 4.0s > 4.0s
INP ≤ 200ms > 200 to 500ms > 500ms
CLS ≤ 0.1 > 0.1 to 0.25 > 0.25

Google uses these metrics, but does not publish that penalty formula. Fix poor experiences for visitors and evaluate actual search results separately.

How to check:

  1. Go to PageSpeed Insights.
  2. Test your homepage and a service page and a blog post.
  3. Look at the mobile scores, not desktop. Check desktop too; prioritize the devices your customers use.

The usual fixes:

  • LCP > 2.5s: Hero image is too large. Compress to WebP, max 200KB. Lazy-load below-the-fold images.
  • INP > 200ms: Too much JavaScript on the main thread. Defer third-party scripts (chat widgets, analytics).
  • CLS > 0.1: Images or ads without explicit width/height attributes, causing layout shift as they load.

Estimate the work after diagnosing the bottleneck. Image fixes can be small; changes to a rendering system or third-party scripts may take more work.

Reason 5: Thin or templated city pages

City pages are the highest-ROI SEO move for service businesses if you do them right. Near-identical pages made mainly for search traffic can violate Google's spam policies.

The wrong way:

/service-area/phoenix
/service-area/scottsdale
/service-area/tempe

Each page has the same template with the city name swapped. 300 words. No real local content. No photos. No specific service details.

Google sees these as doorway pages and either ignores them or actively penalizes the whole site.

The right way:

Each city page needs:

  • Original information specific to that city; Google has no preferred word count
  • A real local photo (not stock)
  • City-specific service notes (e.g., "Phoenix's intense UV cycle means we recommend quarterly cleaning vs the standard biannual")
  • Neighborhood callouts (e.g., "We service Arcadia, Biltmore, Paradise Valley...")
  • Genuine local reviews if you have them, displayed for visitors without a promise of review-star snippets
  • Driving directions or map embed for the closest service area

Start with your top 3 to 5 cities. Prove the model. Then expand.

For the playbook on how to make city pages work with useful local information, see our local SEO for service businesses page.

Reason 6: Zero internal linking strategy

Most service business sites have a navigation menu and that is it for internal linking. Google uses internal links to:

  1. Discover pages (you have to link to them to get them crawled)
  2. Pass authority between pages (the "link juice" model is still real)
  3. Understand topical relationships (which pages support which)

The minimum internal linking structure for a service business:

  • Every blog post links to at least 1 service page and 2 other related blog posts
  • Every service page links to the relevant city pages and 2 supporting blog posts
  • Every city page links to the relevant service pages and the contact page
  • The homepage links to all top-level service pages and the top 5 blog posts

This sounds tedious. It is. It is also one of the highest-ROI SEO actions you can take, and almost no service business does it well.

Reason 7: A weak Google Business Profile

For "near me" searches and the local 3-pack, your Google Business Profile is the listing Google shows. Its reviews matter too: in Whitespark's 2026 ranking factors report, the biggest shift was the growing weight of review and behavioral signals. If your GBP is weak, website work alone will not close the gap.

GBP non-negotiables:

  • Primary category set exactly right (not "Marketing Agency" if you are an SEO agency, specificity matters)
  • Secondary categories accurate: use the fewest needed for the core business
  • Services list populated with every service you offer
  • Genuine current photos that show the work you do
  • Posts published weekly (the Posts feature is underused, works like a mini-blog inside GBP)
  • Reviews answered within 24 hours (yes, even the 5-stars)
  • Real customer questions answered, with a website FAQ for recurring questions
  • Booking link added if you have one

Use genuine project photos and accurate service-area details. A Maps screenshot or geotagging routine is not a supported shortcut to a higher local position.

For the full GBP playbook, see turf cleaning Google Business Profile, the framework applies to any local service.

Reason 8: Duplicate title tags and meta descriptions

Every page needs a unique <title> and <meta name="description">. Most service business sites do not have this, they have either the same title on every page, or templated titles like "Service - Company Name" that look identical to Google.

How to check: In Google Search Console → Pages → Indexed. Click into any page and look at the title shown. Are 10 of your pages showing the same title? You have a duplicate title problem.

The fix:

  • Each page's title: [Primary Keyword] | [Modifier] | [Brand], e.g., Turf Cleaning Phoenix | Same-Week Service | TTM
  • Each page's description: 150 to 160 characters, unique, includes the primary keyword and a benefit/CTA

If you have 30+ pages and writing all those is daunting, batch it. One afternoon with a spreadsheet and you are done.

Reason 9: No review velocity signal

Google says more reviews and positive ratings can help local ranking. It does not provide a count-and-recency formula that determines which of two businesses will rank higher.

The fix:

  • Send a review request to every customer within 24 hours of job completion
  • Use a tool that makes leaving a review one tap (NiceJob, Birdeye, or even a custom QR code)
  • Invite honest feedback consistently, without staff quotas or rating targets.
  • Respond to every review within 24 hours. Include positive reviews; replies show readers how you handle feedback.

If you are doing 8+ jobs a week and getting 0 reviews, you do not have a Google problem, you have an asking problem. Fix the asking first; reviews are one of the signals Google uses to rank local businesses.

The 30-day fix-everything plan

If you do nothing else, do these in this order:

Week 1: Audit + foundations

  • Run Search Console → check indexed count vs sitemap count
  • Check canonical tags on 10 random pages
  • Run PageSpeed Insights on mobile for 3 pages
  • Audit GBP completeness (categories, services, photos)
  • Pull a list of all current page titles + descriptions

Week 2: Technical fixes

  • Fix canonical tags (or pre-render if SPA)
  • Add LocalBusiness schema to every page
  • Add Service schema to each service page
  • Compress all hero images to <200KB WebP
  • Defer non-critical JavaScript

Week 3: Content fixes

  • Rewrite duplicate titles and descriptions
  • Audit top city pages and add genuinely missing local information
  • Add internal links (every blog → service + 2 blog; every service → cities + blogs)

Week 4: GBP + reviews

  • Fully populate GBP (categories, services, photos)
  • Set up weekly photo upload routine
  • Set up review request automation
  • Resubmit sitemap in Search Console

Use URL Inspection to check fixed pages and request recrawling where appropriate. Record subsequent indexing and visibility changes; completing this work does not guarantee a ranking deadline.

Frequently asked questions

My sitemap has 57 pages but Google only indexes 49. Why? Most likely a canonical issue or a JavaScript rendering issue. Check the canonical tag on a non-indexed page first, if it points to the homepage, that is your culprit. Treat the numbers in this question as an example, not this site's current index count.

How long until rankings improve after I fix all this? Indexing changes can be assessed after Google recrawls and processes the fixed pages. Ranking changes have no fixed timetable; compare your priority pages and qualified inquiries with their baseline.

Should I disavow bad backlinks? For 99% of service businesses, no. Google's algorithm is good enough now to ignore spammy links automatically. Disavow only if you have evidence of a manual penalty or a clear negative SEO attack.

What about AI-generated content for SEO? Google's scaled-content policy applies to low-value content made primarily to manipulate rankings, whether produced by people, automation or both. Publish useful, accurate answers and genuine work rather than pages made merely to capture variants of a query.

Is local SEO worth it if I run a lot of paid ads? Yes. Paid stops the day you stop paying; local SEO keeps working after the work is done. Run both: the site and Business Profile can continue helping customers find your information, and ads add volume when you want to grow or open a new market.

How much do I budget for SEO if I do it right? $300 to $1,500/month for a single-location service business. Most of that goes to content production and link/citation building. The technical foundation is mostly one-time work, done right once, you only revisit it when Google changes the rules.


Want us to audit your site and fix the technical foundation? Our local SEO service starts with a free technical audit, we tell you exactly which of these 9 issues you have, prioritized by impact. Or book a free strategy call and we will walk it through live.

Related reading: