Because they are the same page with the city name swapped. Google has a name for that pattern and treats it as spam. A location page ranks when it contains information that is genuinely different for that place, and it fails when the only difference is a word in the heading.
This is one of the most common requests we get. A business serves twelve cities, someone reads that location pages help local search, and the brief arrives asking for twelve pages. The brief is not wrong. The usual execution is.
Webflow makes the build itself straightforward, which is part of the trap. The CMS will happily generate two hundred pages from a spreadsheet in an afternoon. The hard part was never the building.
A location landing page is a page targeting people searching for your service in a specific place. It usually combines what you do, proof that you do it there, and a way to get in touch with that location. The goal is to rank for searches that pair your service with a place name.
The searches themselves are worth understanding. Someone typing a service plus a city name is far closer to buying than someone typing the service alone. That is why these pages are worth building even though they are harder to do well than most people expect.
They are not the same thing as a Google Business Profile listing, though the two work together. The profile handles the map results. The location page handles the organic result underneath, and it can carry far more detail than a listing allows.
Google penalizes thin ones. Its spam policies define doorway abuse as "when sites or pages are created to rank for specific, similar search queries", and one example given is "having multiple domain names or pages targeted at specific regions or cities that funnel users to one page". That is a direct description of the lazy version.
Read the second half of that example carefully, because it is the part that matters. The problem is pages that funnel users somewhere else. If your Bristol page tells a Bristol customer something useful and lets them contact the Bristol team, it is not a doorway. If it is a landing pad that pushes everyone to the same generic contact form, it is.
Google's scaled content abuse policy tightens this further. It defines the abuse as "when many pages are generated for the primary purpose of manipulating search rankings and not helping users", and specifically names using generative AI tools to produce many pages without adding value. Generating fifty city pages from a template and an AI paragraph is now named behavior in a published policy.
Our rule is simple and it has never let us down. If you cannot write three sentences about a location that would be false for any other location, do not build the page.
You create a Collection called Locations, add a field for every piece of information that varies, then design one Collection page template that pulls those fields in. Webflow generates a page per item automatically. The Webflow Way documentation confirms that when you create a CMS Collection, Webflow automatically creates a Collection template page for it.
Start with the fields, not the design. Ours usually include the city or region name, a short intro written specifically for that place, the local address and phone number where one exists, the team members who cover it, two or three projects delivered nearby, and any location-specific detail such as service area, opening hours, or regulations that differ.
Then build the template once. Webflow's documentation is clear that content is pulled dynamically from the CMS fields, and that editing the Collection page template updates the layout for every Collection page using it. That is the whole appeal. One design change propagates everywhere, so the pages stay consistent as the site evolves.
The discipline is in the fields. Every field you add is a promise that someone will fill it in honestly for every location. A field left empty on eight of twelve items is how a good system produces thin pages anyway.
Collection page URLs come from the item slug. Webflow's documentation states that URLs are automatically generated based on the Collection's slug, and that a slug is created from the item's name when you add it. It also advises updating that slug for brevity and clarity, which is worth doing every single time.
Decide your URL pattern before you add a single item, because changing it later means redirects. Something like a locations folder followed by the city name is clean and predictable. Webflow's own SEO guidance notes one constraint worth knowing up front: it does not currently support giving a Collection and a page folder the same slug, so a single directory cannot mix static and dynamic pages.
On the Collection page settings you can build the SEO title and meta description from CMS fields, so every location gets its own metadata without anyone writing it by hand. Set a pattern that reads naturally rather than one that stacks keywords. Our guide to Webflow page SEO settings covers the mechanics in full.
Do the same for image alt text, and keep it honest. Webflow's page-level SEO guidance recommends keeping alt text to a maximum of 125 characters and describing what matters about the image rather than stuffing keywords into it.
Specifics that only apply there. A named team, a real address, projects completed nearby, local pricing or regulations, travel times, and photographs actually taken in that place. Every one of those is something a competitor cannot copy and a template cannot generate.
Photographs are the most underrated item on that list. A stock image of a generic skyline tells a reader nothing. A photograph of your actual van outside an actual building in that city tells them you are really there, and it is the kind of signal that survives any algorithm change.
Reviews and testimonials from customers in that location do similar work. They are specific, they are hard to fake, and they answer the question the visitor is actually asking, which is whether you have done this for someone like them nearby. We cover the broader picture in our guide to local SEO for service businesses.
As many as you can fill honestly, and no more. For most businesses that is between three and twenty. If you genuinely operate in one hundred places with staff in each, one hundred pages is fine. If you operate from one office and serve a region, one page per real office plus a service area page is the honest structure.
The temptation is always to go wider. Someone points out that a competitor has three hundred city pages and asks why we are proposing eight. The answer is that the competitor's three hundred pages are mostly not ranking, and the ones that are would rank on eight good pages too.
Build a few properly, watch them in Search Console for a couple of months, and expand only where the data says there is demand. That approach applies to any templated page system, which we wrote about in our guide to programmatic SEO.
Two numbers matter. Webflow's pricing page puts the top site plan at up to 20,000 CMS items and 40 CMS Collections. The CMS itself requires the Premium site plan, listed at $25 a month billed yearly, since the Basic plan does not include a CMS at all.
For location pages those limits are effectively irrelevant. Nobody serving real places needs 20,000 of them. The collection limit is the one to watch on a large site, because forty collections goes faster than you expect once you have blog posts, categories, authors, case studies, team members, and services all modeled separately.
Plan the content model for the whole site before you build the Locations collection. Retrofitting a collection structure after launch is one of the more painful jobs in Webflow, and it is entirely avoidable with an hour of planning.
Redirect it, do not delete it. Deleting a Collection item removes the page and leaves anyone who linked to it hitting a 404. Set a 301 redirect from the old location URL to the nearest relevant page, which is usually the parent locations page or the office that took over the area.
Webflow's own SEO guidance makes the same point about URL changes generally, noting that implementing proper redirects is key to maintaining visibility when page URLs change. A closed location is exactly that situation, and it is the one people forget because the change feels like housekeeping rather than SEO.
Also update the Google Business Profile at the same time, and check your structured data. A LocalBusiness schema block still advertising an address you left is a small credibility problem that compounds quietly.
Yes, if you serve distinct places and can say something true and specific about each one. No, if you would be generating variations of a single page to catch extra searches, because Google has published a policy naming that exact pattern. The test is whether a real customer in that city would find the page useful.
The version that works is slower to build and much harder to copy. That is the point. A competitor can generate three hundred templated pages in a weekend, and they will still lose to eight pages carrying real photographs, real people, and real proof of work done nearby.
If you want help working out how many location pages your business can honestly support, or you have a set that is not performing, let's talk. We're happy to look at it with you at phoenix.studio.
Tell us where you want to go. We'll tell you how we'd get you there.