Almost every service business in the Lower Mainland eventually asks the same question. We serve Vancouver, Burnaby, Richmond, Surrey, Coquitlam, North Vancouver, Langley and half a dozen more — should each one get its own page? The instinct is to say yes, because more pages feel like more coverage. The outcome is usually twenty near-identical pages, none of which rank, and a set of internal links spread so thin that the pages that could have ranked no longer do.
The better question is not "should we build a city page" but "does this city page deserve to be indexed". That reframing forces an evidence standard, and it produces a much smaller, much stronger set of pages.
Why Metro Vancouver makes this harder than it looks
Metro Vancouver is unusually compressed. A business in Mount Pleasant genuinely serves Burnaby and Richmond, and a customer in New Westminster does not perceive a trip to Vancouver as leaving their area. When the service radius overlaps this heavily, the honest differences between city pages shrink to almost nothing — which is exactly the condition that produces thin content.
Meanwhile, searcher behaviour is genuinely local. People do add municipality names to queries, and results do differ by city. So the demand is real. The mistake is assuming that real demand automatically justifies a separate indexable page for every name in the query set.
The seven-part indexability test
Score each proposed location page against these seven questions. Answer them with evidence you could show a sceptical colleague, not with intentions.
1. Is there a real operational tie to the area?
A physical address, a leased space, staff who live and work there, a vehicle fleet based there, or a licence to operate in that municipality. Genuine ties produce genuine content. "We drive there sometimes" is not a tie.
2. Can you name specifics only a local would know?
Bylaws, permit processes, building stock, neighbourhood names, traffic and access constraints, seasonal factors, the difference between working in a Richmond high-rise and a Langley acreage. If you cannot produce five specifics without inventing them, the page is not ready.
3. Do you have proof of work in that area?
Completed projects, named clients, before-and-after examples, reviews from customers in that city. Local proof is the single strongest differentiator between a page that deserves indexing and a template.
4. Does the service itself differ there?
Different pricing, response times, coverage limits, subcontracting arrangements, or scope. Where service differs, the page has an obvious reason to exist. Where it does not, the page has to earn its place on proof instead.
5. Is search intent for that city genuinely distinct?
Compare the results for your service in two municipalities. If the same pages rank in both with the same intent behind them, one page can serve both. If the results diverge — different competitors, different formats, different questions — that is a signal a separate page can be justified.
6. Can you keep the page maintained?
Every indexable page is an ongoing commitment: updated proof, refreshed examples, working links. Twenty pages nobody will revisit become twenty liabilities within a year.
7. Would you send a paying customer to it?
The blunt version of every other test. If you would be slightly embarrassed to send a prospect the URL, it is not an indexable asset.
Pages passing five or more of these are candidates to index. Three or four means hold and build evidence. Two or fewer means consolidate.
The index, consolidate, hold framework
Every proposed location page ends in one of three buckets, and each bucket has defined mechanics.
Index
The page has operational substance and local proof. Give it a self-referencing canonical, include it in the sitemap, link to it from the service page and any regional hub, and treat it as a first-class page with its own conversion path. If there is a real address, mark up the location properly; if there is not, describe the service area without claiming premises.
Consolidate
The page is a template with a place name. Merge whatever is genuinely useful into a stronger parent — either the core service page or a regional page covering the Lower Mainland — then 301 redirect the thin URL to the merged destination. Remove it from the sitemap and update internal links to point directly at the new target so no redirect chains form.
Hold
The page could deserve indexing once you finish two projects there and collect three reviews. Keep it noindex, keep it out of the sitemap, and put a date on the review. Holding is a legitimate decision; leaving a thin page indexed while you "get around to it" is not.
Avoiding the doorway problem
Google's search spam policies treat doorway pages — sets of similar pages built to capture many query variants while funnelling everyone to the same destination — as a violation. The risk with city pages is not the concept but the execution: mass-generated pages differing only by a variable.
Three practical rules keep you clear of it. First, no page should exist solely to hold a keyword; it should answer a question a local visitor actually has. Second, no page should be generated by substituting a place name into a fixed template. Third, if a page's only call to action is to send visitors somewhere else that does the real work, merge it into that destination.
What an indexable location page actually contains
- An opening that states plainly how you serve that municipality, including any limits.
- Service details specific to the area — access, timing, permits, local conditions.
- At least two pieces of local proof: a project, a review, a named client, or measurable outcomes.
- Practical logistics: coverage boundaries, response expectations, how to reach you.
- Two or three questions local customers genuinely ask, answered directly.
- Clear links up to the parent service page and across to the regional page.
- One conversion path that completes on the page rather than bouncing the visitor onward.
If a page cannot fill those sections with true, specific content, that is your answer about whether it deserves indexing.
A 30-day rollout
Week 1 — inventory. List every existing and proposed location page. Pull impressions, clicks and average position for each, plus indexing status. Note which are in the sitemap and which are linked internally.
Week 2 — score. Run the seven-part test on each page and assign index, consolidate or hold. Document the reasoning; you will be asked about it in three months.
Week 3 — consolidate. Merge and redirect the consolidate set. Update internal links to point at final destinations, remove redirected URLs from the sitemap, and confirm no chains.
Week 4 — strengthen. Rebuild the index set to the content checklist above, verify canonicals and structured data, then submit the updated sitemap and monitor indexing and query mix for the next four to six weeks.
Check your current location footprint
Before you decide anything, it helps to see how your existing pages are actually being treated — indexing, canonicals, thin-content signals and internal linking. A quick independent read gives you a baseline to argue from.
Where this fits
Location architecture is one of the highest-leverage decisions in local SEO, because it determines what the rest of your work is spread across. If you want a second opinion on which Metro Vancouver pages deserve to be indexed and which should be merged, that is the kind of decision we work through as an SEO company in Vancouver, and you can start with a free SEO audit of what you have now.
Fewer, stronger pages almost always beat broader, thinner coverage. The discipline is deciding that before you build twenty pages, not after.
