SEO for franchises is the practice of ranking one brand across many independently operated locations, so the system captures both national brand demand and local “near me” intent. Unlike single-site local SEO, where one owner controls every decision, franchise SEO is constrained by a contract — the franchise agreement decides who may change what, and no amount of keyword research overrides it.
That contractual layer is why franchise SEO programmes stall. The tactics are not hard. The permissions are.
Google documents exactly three factors behind local pack rankings — relevance, distance and prominence (Google Search Central, 2026) — and a franchisee controls meaningful input to only two of them. Ahrefs’ study of 1.9 billion keywords found 94.74% get ten or fewer searches a month (Ahrefs, 2024), which is why a 200-unit system cannot be built on head terms and has to be built on the long tail of city-level queries instead. Semrush put zero-click searches at 58.5% of all US Google queries (Semrush, 2024), so for a franchise the Google Business Profile is increasingly the destination, not the doorway.
Why franchise websites don’t rank
Every franchise SEO audit I run turns up the same finding, and it is never the one the client expects. They expect thin content. What they have is self-competition.
Here is the mechanism. Corporate builds /locations/dallas/ as a regional landing page because it targets “dallas” nicely. Three franchisees operate in the Dallas metro, each with their own page. Google sees four pages from one domain answering the same query, picks the strongest — almost always the corporate one, because it sits closer to the homepage and absorbs internal links — and suppresses the other three.
The franchisees are not invisible because they did bad SEO. They are invisible because corporate outranked them with a page that has no phone number, no booking button and no local staff.
You can test this in thirty seconds. Search site:yourbrand.com "your city" in Google. If more than one of your own URLs comes back targeting that city’s core service query, you have cannibalisation, and it is suppressing revenue for whichever franchisee lost. I have found systems where sixty per cent of units were being outranked by their own head office.
The second failure mode is the template. Franchisors hand every franchisee the same approved boilerplate to protect brand voice, the franchisee swaps the city name, and Google gets 200 near-identical pages. That is not a duplicate content penalty — no such penalty exists — but it is a relevance problem. Google selects one page to represent the cluster and quietly ignores the rest.
SEO for franchises is a governance problem
Here is the part the guides skip. In a franchise system, nobody has unilateral authority over the website.
The franchisor owns the domain and the brand. The franchisee owns the local business, funds the national marketing pool, and often owns the Google Business Profile outright — which matters enormously, because when that franchisee leaves the system they can take the profile, the reviews and the ranking history with them. I have seen a departing franchisee’s profile keep ranking for the brand in their city for months, pointing at their new competing business.
So before any technical work, three questions need contractual answers:
1. Who owns the location page? The URL lives on the franchisor’s domain, so legally the franchisor does. But the franchisee paid for the local content and the photos. Decide what happens to that page on termination — most agreements are silent, and silence means a dispute at the worst moment.
2. Who owns the Google Business Profile? This should be the franchisor as primary owner, with the franchisee as manager. That way a unit transfer does not cost the brand its review history. Getting this wrong is the single most expensive franchise SEO mistake, because reviews cannot be transferred between profiles.
3. What does the national marketing fund actually buy? Franchisees contribute to a pooled fund, then frequently get billed again by a local agency for work the fund already covers. Publish the line: fund pays for domain, architecture, template, schema, national links. Franchisee pays for local content production and review generation. Anything ambiguous becomes a grievance.
In my experience auditing multi-location systems, roughly half the “SEO problems” I am hired to fix turn out to be unresolved versions of those three questions. You cannot optimise your way out of a permissions deadlock, and a technical SEO engagement that ignores the contract will deliver recommendations nobody is authorised to implement.
The architecture decision: subfolders, not separate sites
Should each franchise location have its own website? Almost never. The instinct is understandable — franchisees want control — but it splits your authority across dozens of weak domains instead of compounding it on one.
Use brand.com/locations/city/ as subfolders on the brand domain. Every local link a franchisee earns strengthens the whole system, and every brand-level link lifts every location. This is the same subdomain versus subfolder trade-off that applies to any segmented site, except the stakes are higher because you are multiplying it by your unit count.
Then separate the two page types by job, which is what actually kills the cannibalisation:
- Regional index pages (
/locations/texas/,/locations/dallas/) list the units in that area with name, address and a link. No phone number, no booking CTA, no service copy. They exist to route, not to convert. - Unit pages (
/locations/dallas-uptown/) carry the full service content, the local detail, the phone number and the CTA. These are the pages that should rank for “service + city.”
The moment a regional index page starts carrying conversion elements and service copy, it becomes a competitor to the unit pages beneath it. Keep it thin on purpose. This is deliberate internal linking strategy, not an accident of the CMS.
A framework for scaling location pages without duplication
Writing genuinely unique content for 200 locations is not realistic, and pretending otherwise is why franchise content programmes collapse in month two. The workable approach is to fix the ratio: keep the shared template shared, and make the differentiated portion genuinely local.
- Audit for self-competition first. Run
site:brand.com "city"for your twenty largest markets and record every URL that returns. Any market with more than one competing URL goes on the fix list before you write a single new word. There is no point adding content to a page Google has already decided to ignore. - Define the fixed template. Roughly 60% of each location page — service descriptions, brand positioning, trust signals, schema scaffolding — is shared and should stay shared. Trying to rewrite this per location produces worse copy, not better rankings.
- Define the mandatory local block. The remaining 40% is non-negotiable per unit: staff names and photos, the specific neighbourhoods served, directions from a local landmark, opening hours including local holidays, and at least three location-specific reviews. Make it a form the franchisee fills in, not a blank page they never touch.
- Set
areaServedin schema per unit. Define the postcodes or neighbourhoods each location actually covers using LocalBusiness schema. This is the clearest signal you can send about which unit serves which territory, and it directly reduces sister-location conflict. - Assign one primary query per page. One unit page targets one “service + city or neighbourhood” query. Write it down in a keyword map, one row per URL. If two rows share a target, one of them is wrong.
- Gate publication on the local block. No unit page goes live with the local 40% empty. A page published as template-only will get indexed as thin, and reindexing it later after you fill it in takes far longer than waiting a week to launch it properly.
That sequence works because it treats the shared portion as a feature rather than a liability. The differentiation carries the local relevance; the template carries the brand consistency the franchisor is contractually obliged to protect.
Google Business Profiles are the real storefront
For a franchise, the profile matters more than the page. Most local searches now resolve inside Google’s interface — directions, calls, hours, reviews — without a click to the website at all.
That reframes what the SEO programme is for. At scale you need three things the single-location playbook does not require. First, bulk management with real account hierarchy, so corporate can see all units while a franchisee sees only their own. Second, NAP consistency enforced centrally rather than trusted to each unit, because a single inconsistent phone number across directories degrades that unit’s prominence signal. Third, review velocity as an operational metric per location, not a marketing afterthought — a unit that stops collecting reviews visibly loses local pack position within a quarter.
The franchisee genuinely does own this layer. They take the photos, they ask for the reviews, they update hours when they close for a local holiday. Corporate cannot do it for them, which is why franchise SEO without franchisee participation is a programme that only works on paper. A local SEO foundation is the prerequisite, not an add-on.
What franchise SEO actually costs
Published market rates put fully managed local SEO at roughly 500 to 2,000 USD per location per month, with single-territory programmes commonly quoted at 1,500 to 3,500 USD and competitive metros above that. Those numbers are real but they are also the least interesting part of the budget conversation.
The question that determines whether the programme survives is the split. A franchisee paying into a national marketing fund and then receiving a separate invoice for location page content will, correctly, ask what the fund was for. Multiply that across fifty units and you have a system-wide trust problem that ends the programme regardless of results.
Publish the boundary before you spend anything:
- Fund covers: domain, hosting, site architecture, page templates, schema, technical maintenance, national link building, reporting infrastructure.
- Franchisee covers: local content production, photography, review generation, community sponsorships and local link building in their own market.
If you are building the budget case internally, the same logic applies as in any SEO ROI measurement exercise — except the unit of measurement is revenue per location, not sitewide sessions. A programme that lifts twelve units and does nothing for the other forty is a failed programme even if aggregate traffic rose.
Measuring a franchise programme without lying to yourself
Aggregate traffic is the most misleading metric in multi-location SEO. Total organic sessions can climb 30% while two thirds of your franchisees see nothing, because the growth concentrated in the markets that were already strong.
Report per location or do not report. The four numbers that matter per unit are local pack position for the primary query, Google Business Profile actions (calls, directions, website clicks), unit page organic entrances, and review count and velocity. Roll them up for the board, but never let the roll-up be the only view, because it hides exactly the failures the franchisees will raise at the next convention.
Track distribution too: how many units improved, how many stayed flat, how many declined. That single distribution chart does more to keep a franchise SEO programme funded than any traffic graph, because it answers the question every franchisee is actually asking, which is whether the money did anything for them specifically. Set this up properly in your SEO KPIs and reporting framework from the start — retrofitting per-location reporting a year in is painful.
SEO for franchises rewards systems that settle ownership before they settle keywords. Fix the governance, fix the architecture, then optimise — in that order, because the other order produces recommendations nobody has the authority to ship. Automotive dealer groups face the same governance challenge at larger scale: a group of 20 dealerships needs per-location GBP management, per-location review velocity, and distinct location pages — the same requirements as a retail franchise but with the added technical challenge of sold-vehicle URL management at every site. The full picture is in the automotive SEO guide.
Restaurant groups face the same location-page problem, covered in SEO for restaurants.
Running a fitness business? The same local logic applies to memberships and classes: see SEO for gyms.
Frequently Asked Questions
How does SEO work for franchise and multi-location businesses?
Franchise SEO runs on two layers that have to be governed separately: a national layer the franchisor owns, and a local layer each franchisee feeds. The franchisor owns the domain, the URL architecture, the schema and the brand-level links. The franchisee owns the Google Business Profile, the reviews, the local detail and the community links. It fails when both layers try to rank for the same city query, because Google picks one page and suppresses the rest.
How much does SEO cost for a franchise?
Published market rates run roughly 500 to 2,000 USD per location per month for fully managed local SEO, with single-territory programmes often quoted at 1,500 to 3,500 USD and competitive metros higher. The more useful question is what the national marketing fund covers versus what the franchisee pays on top, because a franchisee billed separately for work the fund already pays for is the most common dispute in these systems.
Who should manage SEO in a franchise system?
The franchisor should manage everything that is shared and the franchisee everything that is local, with the split written into the franchise agreement rather than agreed informally. Shared means the domain, the site architecture, the template, the schema and national link building. Local means the Google Business Profile, reviews, photos, staff and community involvement. Systems where franchisees run their own separate websites almost always end up competing against their own brand.
Why don’t franchise websites rank?
Usually because the brand is competing against itself, not because the content is bad. Hundreds of location pages built from one template with only the city name swapped get treated as thin duplicates, and the corporate page for a region frequently outranks the individual location page it was built to feed. Run a site: query for your own brand and target city — if several of your own URLs appear, that is the problem.
Should each franchise location have its own website?
No, in almost every case. Separate domains split your link equity across dozens of weak sites instead of compounding it on one strong one, and they make NAP consistency and schema governance nearly impossible to enforce. Location pages as subfolders on the brand domain, in the form brand.com/locations/city/, is the structure that consolidates authority while still letting each unit rank locally.
If your multi-location system is competing against itself and you need the diagnosis before the tactics, that is what an SEO audit is for. Sources worth reading directly: Google’s local ranking factors documentation, Google Search Central on duplicate content, and schema.org’s LocalBusiness type for the areaServed property.
