A homeowner in Provo has a water heater leaking into her basement. She searches "water heater repair provo," taps a plumber she recognizes, and lands on a page about plumbing across all of Utah County. It lists a dozen services and twenty cities. Water heaters get one bullet point. She goes back and calls the next company.
That plumber did show up, and Search Console even recorded the click. But Google sent a ready-to-hire searcher to a broad page, and the page built for her, a Provo water heater repair page, never got the chance to do its job.
We see this often on Utah service and ecommerce sites, and it is frequently misdiagnosed. Here is how we catch it and decide what to do.
Ranking, the page Google picks and the page that converts are different things
Most SEO reports blur three separate questions:
- Does the site rank? Is any URL from your domain appearing for the search?
- Which URL did Google choose? For each query, Google picks the page on your site it considers the best answer, and that choice can change week to week.
- Did that page convert? Did the visitor call, book, request a quote or buy?
A site can win the first question and lose the other two.
Sometimes the broad page deserves to win. If someone searches "plumber utah county" and you serve fifteen cities there, a strong county page is the right answer. Someone searching "how long does a water heater last" wants an explanation, not a booking form. Before calling anything the wrong page, define the right page for that specific intent.
An illustrative example: an Orem plumber that also serves Provo
This example is invented for teaching. The URLs are not real pages, and nothing below comes from a real Search Console account.
Picture a plumbing company based in Orem that does a lot of work in Provo. Its site has three relevant pages:
/services/water-heater-repair, the core service page/provo/water-heater-repair, a Provo-specific service page/utah-county/plumbing, a broad regional page
Provo water heater calls are flat even though the company "ranks." In Search Console, the query "water heater repair provo" shows impressions, but nearly all of them are attributed to /utah-county/plumbing. The Provo page barely appears. That is a pattern worth investigating, not yet a diagnosis.
How to catch it in Google Search Console
Google's Search Console getting-started guide points site owners to the Performance report for this kind of question. Here is the workflow we use.
Step 1: Set up a fair comparison
Open Performance > Search results, keep the search type on Web, and pick a date range you can repeat. We look at the last three months for the pattern and the last 28 days for the current state. If your business is seasonal, as water heaters, HVAC, roofing and holiday lighting all are, compare against the same period last year too. Filter the country to the United States if only Utah customers matter, and check desktop and mobile separately.
Step 2: Filter one exact commercial query
Add a query filter for the precise phrase, such as "water heater repair provo." Broad "contains" filters mix intents, so add close variants one at a time afterward.
Step 3: Switch to the Pages tab
With the query filter on, click Pages to see which URLs earned impressions and clicks. If several appear, Google has been rotating them; change the date range to see whether that is new.
Step 4: Compare the page to the intent, then to your leads
Ask honestly whether each URL would satisfy that searcher, then check form fills, calls and booked jobs by landing page. Search Console shows where searchers landed, not whether they became customers.
Step 5: Reverse the filter
Clear the query, add a page filter for the intended URL, and open Queries. If the Provo page earns impressions mostly for broad or unrelated terms, Google may not understand its purpose. Repeat for the county page to see which specific service-and-city searches it absorbs.
Step 6: Don't overread average position
Average position blends every impression, query and device in your filter, using your site's topmost position each time. A page shown fourth to some searchers and fortieth to others averages to a number that describes neither. Rely more on impressions and clicks per URL over time.
Step 7: Inspect both URLs
Run each URL through URL Inspection. Confirm the intended page is indexed, then check the Google-selected canonical. If Google chose a different canonical for your Provo page, Search Console reports that traffic under the canonical URL, which can look like the wrong page ranking when Google is really treating the two as one. Google's canonicalization troubleshooting guide explains why a different canonical gets chosen.
For larger sites, the Search Console API can return query and page pairs together, listing every city search that lands on a non-city URL.
What the findings might look like
Fictional example rows for illustration only. No real data or metrics are shown.
| Query | Page shown by GSC | Intended page | Diagnosis | Check next |
|---|---|---|---|---|
| water heater repair provo | /utah-county/plumbing | /provo/water-heater-repair | Possible overlap; Provo page may be thin or poorly linked | URL Inspection, internal links |
| plumber utah county | /utah-county/plumbing | /utah-county/plumbing | Working as intended | Leave it alone |
| tankless water heater lifespan | /blog/tankless-guide | /blog/tankless-guide | Informational search, correct page | Guide links to the service page |
| water heater repair orem | /services/water-heater-repair | Undecided | Does Orem need its own page? | Demand, leads, real service footprint |
Three problems that look alike
A wrong page in Search Console usually means one of three different situations, each with a different fix.
1. True duplicates that Google has grouped together
Two URLs carry essentially the same content, such as a Provo page that copies the county page with the city name swapped, or a parameter or trailing-slash version of a URL. Google groups duplicates and picks one canonical. Google's guidance on consolidating duplicate URLs applies here: redirects and rel="canonical" are strong signals, sitemaps are weaker, and Google does not recommend noindex for choosing which duplicate becomes canonical. Notice the word signals. A canonical tag is a hint for duplicate content, not a switch that tells Google which page to rank.
2. Two indexable pages with overlapping intent
Both pages are unique and indexed, and both could plausibly answer the search. The county page mentions water heaters and Provo, while the Provo page is thin, rarely linked or unclear about what makes it different. The fix is giving each page a clearer job, not pointing a canonical from one unique page to another.
3. Google chose a page that arguably answers better
Sometimes the county page really is more useful, with reviews, photos and an FAQ the Provo page lacks. Or the search is ambiguous, or brand searches and sitelinks show several of your URLs at once without anything being broken. None of these is a penalty, and none calls for a redirect.
A decision tree for choosing the fix
Work through these questions in order and stop at the first one that explains what you see.
- Does the intended page exist, and is it indexed? If not, nothing else matters yet.
- Is something technical in the way? Check for a 200 status, robots.txt rules, a stray
noindex, the declared canonical, and whether key content only appears after JavaScript runs. Our technical SEO reviews start here, because rewriting cannot help a page Google cannot read properly. - Does the page actually answer the search? A Provo water heater page should cover repair versus replacement, gas and electric units, how quickly you can get there and how to book. A template with the city name dropped in usually does not.
- Does it overlap with another page? List every URL that touches the topic: service, city, county, blog post or ecommerce guide. Decide which one owns which intent. This is where a deliberate content strategy earns its keep.
- Is it linked from the logical places? The Provo page should be linked from the water heater service page and the Provo section of the county page, with descriptive anchor text.
- Does demand justify a standalone page? If few people search that city and service together and you do little work there, a strong service page with a clear service-area section may be the better answer.
Then choose one outcome:
- Consolidate and redirect when two pages genuinely serve the same purpose and one is clearly stronger. Move useful content first, then add a 301.
- Differentiate and strengthen when both pages have a real job. Rebuild the weaker page around its intent and fix internal links.
- Leave it alone when Google's choice serves searchers well and leads are coming in.
Two warnings. Do not rewrite core service pages just to make a blog architecture diagram look tidy; service pages are where people hire you. And do not redirect every related page into one master page without evidence, or you can erase years of earned relevance in an afternoon.
Service footprint, Google Maps and city pages
Utah's high-intent markets sit close together: Lehi, Orem and Provo in Utah County; Sandy, Draper and South Jordan in the south Salt Lake Valley; St. George, Washington and Hurricane in Washington County. One business can legitimately serve all of them without having an office in each, and the website should not suggest otherwise.
Google describes local Maps results as based mainly on relevance, distance and prominence, tied closely to your real Business Profile. Organic results depend more on what each page says. A city page can earn organic visibility in a city you truly serve, but it will not create a Maps presence where you have no location, and implying an office you do not have damages trust. Our local SEO work keeps those tracks separate on purpose.
We follow the same rule. Utah SEO Experts works from the Salt Lake area and St. George, and our Utah County SEO and Provo SEO pages describe the businesses we serve there, not an office we do not have.
Clients we support show why this monitoring matters on multi-market sites. Parley's Plumbing, Heating & Air Conditioning, based in Orem, publishes service pages such as water heater repair alongside city pages for Provo, Lehi and other Utah County communities. Northridge Roofing & Exteriors has regional pages for Northern and Southern Utah plus city pages from Sandy and Draper to St. George and Hurricane. These are examples of structures that need query-to-page checks, not sites with a wrong-page problem.
The ecommerce version: category intent versus product intent
Utah stores selling nationwide face the same issue with different page types. Another illustrative example, a Shopify store selling off-road lighting:
- A collection page for LED whip lights
- A buying guide on choosing whip length
- A product page for one specific four-foot whip pair
Someone searching "best led whip lights for utv" is comparing options, so the collection or guide should win. Someone searching the exact product name and length is ready to buy, and landing on the guide adds a step that can cost the sale. If the guide absorbs exact product searches, or one product absorbs broad category searches, that is the same wrong-page pattern.
The fix follows the plumber's logic: the collection owns category intent with useful filters and comparisons, the guide stays educational and links to the collection, and each product page is specific enough (model, size, compatibility, what is in the box) that Google has no reason to substitute something broader.
Stores we support show these layers in practice. Holt Anatomical organizes Shopify collections by body system, such as brain models, and publishes a separate guide on choosing models by curriculum. Gorilla Whips separates its broad LED whips collection from product-family collections for pairs and singles. Again, these are structural examples, not reports of a problem. Our ecommerce SEO work starts by mapping which layer should own which kind of search.
Measuring whether the change worked
The goal is not a green audit score but the right page earning the right searches and producing leads. Before changing anything, record:
- A baseline query-and-page table for the searches you care about, over both three months and 28 days.
- Organic qualified leads by landing page, from forms, call tracking or your CRM.
- Clicks by destination URL for the affected group of pages, not just sitewide totals.
Afterward, compare like with like: same search type, same country and device filters, same period length and, where possible, the same season. Google's guide to debugging search traffic drops recommends the same discipline: compare against a similar period and look for patterns in the pages affected.
Expect a delay while Google recrawls the pages. We usually read signals after two to six weeks, but there is no guaranteed timeline. Watch whether the Google-selected page for your target searches shifts, whether older searches the previous page earned still land somewhere sensible, and whether qualified leads increase. If you consolidated pages, confirm the redirected URL's old searches moved to the destination instead of disappearing.
Make it a routine, not a one-time audit
If your site has many service, city and county pages, or a large catalog, this check belongs on a recurring schedule. It is a core part of how we approach SEO for Utah businesses: find where searchers and pages are mismatched, fix the cause, and measure leads instead of rankings alone.
If you suspect Google is sending your best customers to the wrong page, book a consultation and we will walk through your query and page data with you.

