One Website, Many Cities: How to Build Local Pages Without Tripping Google's Doorway Page Rule

You serve Guelph, Kitchener-Waterloo, Cambridge, and maybe Toronto too. Someone on your team, or an agency you hired, suggests the obvious fix: build one page, copy it eleven times, and swap the city name at the top. More pages, more chances to rank, right?

Google disagrees, and it has a name for what you just built: a doorway page.

What is a doorway page, exactly?

Google’s own definition is a page created to rank for a specific search term that leads visitors to a less useful version of the same content elsewhere on the site. The pattern Google calls out by name includes pages that are “substantially similar to other pages” but target different geographic locations. That is precisely what happens when a city name is the only thing that changes.

This is not a new or obscure rule. Google published an update on doorway pages back in 2015, and the same principle sits inside its current spam policies today: pages built to capture search traffic without offering a visitor anything genuinely different are treated as manipulative, whatever the intent behind them was.

The practical risk is real. Sites that lean on this pattern can see the affected pages demoted in rankings, or removed from search results entirely if it rises to a manual action. For a small business that just spent money getting eleven city pages built, that is money spent making the site weaker, not stronger.

Why swapping the city name isn’t localization

The test Google is applying is simple: would this page still make sense if you changed the city name to a different one? If a paragraph reads “we proudly serve Guelph with fast, friendly service” and the exact same sentence works with “Cambridge” dropped in instead, it was never really about Guelph. It was boilerplate wearing a place name as a costume.

Real localization reads differently. It names the actual neighbourhoods, not just the city. It mentions a landmark, a specific area business owners in that town would recognize. It describes work done there, not work done generically “in the region.” None of that transfers cleanly to the next city on the list, and that is exactly the point.

What actually makes a local page unique

A handful of things separate a real local page from a doorway page:

• Specific coverage detail. Not “serving Kitchener-Waterloo” but the actual neighbourhoods, postal areas, or nearby towns you cover from that base, matched to what you actually told Google Business Profile.
• Real proof of work there. A project, a client story, or photos tied to that city. If you cannot point to anything you have actually done in a place, that is a sign you may not need a dedicated page for it yet.
• Locally relevant FAQs. Questions that only make sense for that market: permit rules that differ by municipality, drive times from your base, or services more in demand in that specific area.
• Its own metadata and internal links. A unique title tag, a unique meta description, and links to genuinely relevant content, not a copy-pasted block identical across every city page.
• Schema that matches reality. Structured data (Schema.org’s areaServed or LocalBusiness markup) that reflects what the page actually says, not a padded list of every town within two hours.

Our own local SEO guide for service-area businesses covers how this connects to your Google Business Profile settings. The two need to agree: what your profile claims about where you work and what your website proves should be the same story told twice, not two different ones.

How many city pages should you actually have?

Fewer than you think. The question is not “how many cities can I list” but “how many cities can I write a genuinely different, genuinely useful page for.” A business with a real, ongoing presence in three or four Ontario markets, say Guelph, Kitchener-Waterloo, and Cambridge, can usually build three or four strong pages. The same business trying to cover fifteen towns on its service list with the same effort ends up with fifteen thin pages instead, and thin, repetitive pages are exactly what draws Google’s doorway-page scrutiny in the first place.

Start with the cities where you have done real work and can prove it. Add a new city page only when you have enough there to say something true and specific. A shorter, honest list of local pages will outperform a padded one, both with Google and with the person actually reading the page before they call you.

Where should each page send visitors next?

A good local page does not deposit a visitor and vanish. It should route them into a relevant service page such as web design and development or digital marketing and SEO, and toward a way to act, such as reaching out directly on the contact page. Internal links between real pages, including links across your own city pages where it makes sense, are also part of what tells Google this is a connected site built for people, not a set of isolated landing pages built for search engines.

A quick self-check before you publish

Ask this about every local page on your site, existing or planned:

1. If I swapped the city name for a different one, would any sentence become false or nonsensical? If not, rewrite it.
2. Can I point to a specific project, client, or piece of proof tied to this exact place?
3. Does this page’s title, meta description, and FAQ content differ meaningfully from every other city page on the site?
4. Does this page match what my Google Business Profile actually says about my service area?
5. Would I be comfortable if a person from that town read this page and judged how well I actually know their area?

If any answer is no, that page needs work before it needs traffic. A handful of local pages built to genuinely earn their place will do more for an Ontario business than a full set built to game a search result, and they will hold up as Google keeps refining how it treats scaled, repetitive content. If you want a second set of eyes on the local pages you already have, or help building the ones you are missing, get in touch.