Skip to content
Search Experts

Home services case study

Turning a Plumbing Website Into a Search Architecture Built Around Real Customer Demand

Plumbing customers do not search for one broad service. They search for specific problems: drain cleaning, water heater repair, leak repair, sewer problems, emergency plumbing.

They also search within the cities and service areas where they need help.

This case study shows how we approached a plumbing website that needed stronger alignment between its services, geographic markets and internal-link architecture. The client is not identified; naming and figures follow explicit approval and verified data.

Discuss a situation like this

Demand path

  1. Customer need
  2. Service intent
  3. Location
  4. Right landing page

Service demand

  • Drain cleaning
  • Water heaters
  • Leak repair
  • Sewer
  • Emergency
Written by
The Search Experts team
Reviewed by
Search Experts search strategy review
Published
Updated

This work was performed by members of the team behind Search Experts prior to the launch of the Search Experts brand. Search experience dates to 2009; SearchExperts.ai itself does not.

The client is not identified. Names, screenshots and figures are published only with explicit written approval and verified source data.

The challenge

The Website Did Not Fully Reflect How Customers Searched

The business offered multiple plumbing services across multiple markets, but the site architecture did not clearly translate those real-world capabilities into a search structure.

Typical issues in this kind of environment can include:

  • Major services competing for attention on broad pages
  • Insufficient depth around high-value services
  • Location pages disconnected from service authority
  • Internal links that fail to reinforce the most important commercial pages
  • City targeting that becomes repetitive instead of useful
  • Unclear hierarchy between company, services and markets

What we found

Search Demand Was More Specific Than the Existing Architecture

Customer intent determines architecture. Each query implies a service, sometimes a location, and always a page that should exist to answer it.

Intent chain

  1. Customer need
  2. Service intent
  3. Location
  4. Right landing page
  • “drain cleaning”Drain Cleaning service page
  • “water heater replacement”Water Heater Services page
  • “plumber in [market]”Legitimate local-market page
  • “sewer line camera inspection”Sewer service page
Customer intent determines architecture. The page a searcher deserves to land on is decided before a single URL is created.

The strategy

Build Around Services First. Geography Second.

  1. Define the core commercial services the business actually sells.
  2. Give meaningful high-value services clear page ownership.
  3. Build legitimate local-market pages only where real service presence justified them.
  4. Connect location pages back into the primary service hierarchy.
  5. Improve internal linking so authority is not trapped in isolated city pages.
  6. Reduce unnecessary keyword duplication and cannibalization.
This mirrors the approach documented in local SEO and content SEO.

Architecture

Plumbing company

Services

  • Drain cleaning
  • Water heaters
  • Leak repair
  • Sewer
  • Emergency plumbing

Markets

  • Primary market
  • Secondary market
  • Additional service areas

Contextual connections

  • Drain cleaningPrimary market
  • Water heatersSecondary market
  • Emergency plumbingPrimary market
  • SewerAdditional service areas
Service and location reinforce each other without creating dozens of duplicate pages.

Implementation

What Changed

Only work that has been confirmed is described. Where an item is not listed, it should not be assumed to have been performed.
Observation
High-value services were described inside broad pages rather than owning a destination of their own.
Decision
Give each commercially meaningful service a single page responsible for that intent.
Implementation
Service pages were created or reorganized so that one URL owns one service, with titles and H1s written to the intent behind the query.
Result
Awaiting verified data before publication.
Observation
Location pages sat apart from the service hierarchy and repeated similar copy.
Decision
Keep local pages only where the business genuinely serves the market, and tie each one back to the service pages.
Implementation
Local pages were restructured and linked into the service hierarchy instead of standing alone.
Result
Awaiting verified data before publication.
Observation
Internal links pointed mostly at the homepage and the contact page, leaving commercial pages under-supported.
Decision
Route internal authority towards the pages the business actually needs to rank.
Implementation
Internal linking and navigation were revised so service and market pages reinforce each other.
Result
Awaiting verified data before publication.
Observation
Several URLs targeted overlapping variations of the same service query.
Decision
Consolidate overlapping intent rather than maintaining competing pages.
Implementation
Duplicate targeting was reduced and supporting content pointed at the owning page.
Result
Awaiting verified data before publication.

Sequence

How the Engagement Progressed

Dates are published only where they have been confirmed. The sequence matters because it separates deliberate strategy from coincidental movement.

  1. Baseline

    Existing URLs, coverage and internal-link structure recorded.

  2. Audit

    Service demand and market presence compared against the site.

  3. Architecture

    Service ownership and legitimate market pages defined.

  4. Implementation

    Pages created, restructured and reconnected.

  5. Search response

    Crawling, indexation and query mapping monitored.

  6. Measurement

    Verified reporting prepared against the recorded baseline.

Exact dates are published once confirmed against the client's reporting records.

Results

What Happened After Implementation

This section publishes only verified figures, each with its source system and comparison period.

The evidence

Verified performance data is being prepared for publication.

This case study documents the diagnosis, the decisions and the implementation. Results are published only once the underlying figures have been exported from the measurement system, checked against a matching baseline period and approved for release by the client.

Lessons

What Other Businesses Can Learn

These generalize from the case. They are not a promise that another business will see the same outcome.

  1. Service clarity precedes geographic reach

    A market page borrows its credibility from the service pages behind it. Build those first and local pages have something to reinforce.

  2. Page count is not a strategy

    More location pages usually means more internal competition. Coverage should follow real service presence, not a spreadsheet of city names.

  3. Internal links decide where authority lands

    If commercial pages are not linked from the pages that earn attention, they stay invisible regardless of how well they are written.

  4. Query specificity should be visible in the structure

    When someone searches for a distinct job with distinct pricing, they should land on a page that only discusses that job.

Case study FAQs

Because near-duplicate city pages compete with each other and rarely earn the local relevance they are meant to capture. A location page works when there is genuine service presence behind it and specific information a searcher in that market actually needs.

Bring Us a Situation Like This One.

Describe your market and current architecture, and we will walk through how we would diagnose it.

Contact Search Experts