<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Lead PPC</title>
	<atom:link href="https://leadppc.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://leadppc.com/</link>
	<description>Franchise FSO + PPC</description>
	<lastBuildDate>Mon, 16 Nov 2026 22:25:30 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://leadppc.com/wp-content/uploads/2024/10/cropped-Lead-Lion-Logo-32x32.png</url>
	<title>Lead PPC</title>
	<link>https://leadppc.com/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Multi-Unit Franchise Ad Copy Compliance: RSAs That Pass Brand Review Without Killing CTR</title>
		<link>https://leadppc.com/franchise/multi-unit-franchise-ad-copy-compliance/</link>
					<comments>https://leadppc.com/franchise/multi-unit-franchise-ad-copy-compliance/#respond</comments>
		
		<dc:creator><![CDATA[Grant James]]></dc:creator>
		<pubDate>Mon, 16 Nov 2026 22:14:41 +0000</pubDate>
				<category><![CDATA[Franchise]]></category>
		<guid isPermaLink="false">https://leadppc.com/?p=4436</guid>

					<description><![CDATA[<p>Multi-Unit Franchise Ad Copy Compliance: RSAs That Pass Brand Review Without Killing CTR Multi-unit franchise ad copy compliance: RSAs that pass brand review without killing CTR. Key Takeaways Brand and legal usually flag unapproved claims, offers, trademarks, pricing, earnings-adjacent language, and location copy that implies rights you do not have—not “interesting headlines.” Build an approved [...]</p>
<p>The post <a href="https://leadppc.com/franchise/multi-unit-franchise-ad-copy-compliance/">Multi-Unit Franchise Ad Copy Compliance: RSAs That Pass Brand Review Without Killing CTR</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>Multi-Unit Franchise Ad Copy Compliance: RSAs That Pass Brand Review Without Killing CTR</h1>
<div class="wp-caption alignnone" style="width: 1290px;">
<p><img fetchpriority="high" decoding="async" src="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-ad-copy-compliance-featured.jpg" alt="Multi-unit franchise ad copy compliance: responsive search ads that pass brand review" width="1280" height="720" /></p>
<p class="wp-caption-text">Multi-unit franchise ad copy compliance: RSAs that pass brand review without killing CTR.</p>
</div>
<p><!-- HERO --></p>
<div class="key-takeaways" style="border: 1px solid #d9d9d9; border-left: 4px solid #1e73be; background: #f7f9fc; padding: 16px 20px; margin: 24px 0;">
<p><strong>Key Takeaways</strong></p>
<ul>
<li>Brand and legal usually flag unapproved claims, offers, trademarks, pricing, earnings-adjacent language, and location copy that implies rights you do not have—not “interesting headlines.”</li>
<li>Build an approved asset library first, then assemble RSAs from that library. Pin only what must always appear, and pin 2–3 distinct compliant variants per pinned position so CTR is not stuck on one line.</li>
<li>Put a review SLA in writing (who reviews, turnaround, what “approved” means). Waiting on informal Slack approvals is how launches miss opening weekends.</li>
<li>Location-specific copy can coexist with national rules if city/ZIP lines stay factual, territory-true, and free of inventing rankings or guarantees corporate did not clear.</li>
<li>Test under compliance by rotating approved variants—not by sneaking unapproved claims into “temporary” assets. Disapproved or paused assets should never re-enter via a different ad group name.</li>
<li>When creative ownership changes mid-cycle (new agency, new unit, resale), freeze the approved library, re-map pins, and re-submit only what changed so you do not reset brand trust.</li>
</ul>
</div>
<p>Responsive search ads fail franchise brand review for predictable reasons: a headline corporate never cleared, a local offer that conflicts with national pricing, or a pin that makes the only compliant line the weakest one. Multi-unit operators feel it hardest because every unit wants “our” angle while brand wants one voice.</p>
<p>This is the operator guide to RSA copy that clears brand and legal without sandbagging click-through rate. Your franchise agreement, brand book, and co-op creative rules still win any conflict with general PPC advice. Google’s RSA features (pins, campaign-level text assets, Ad Strength guidance, text disclaimers) change over time—confirm current behavior in Google Ads Help before you rebuild an account around a single tactic.</p>
<figure style="margin: 28px 0;"><video style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" title="Multi-unit franchise ad copy compliance in 25 seconds" poster="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-ad-copy-compliance-video-poster.jpg" preload="metadata" muted="" controls="controls" width="1280" height="720"><source src="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-ad-copy-compliance-video.mp4" type="video/mp4" /></video><figcaption style="font-size: 14px; color: #5c687c; text-align: center; margin-top: 8px;">Multi-unit franchise ad copy compliance: the key points in 25 seconds.</figcaption></figure>
<h2>What Brand and Legal Usually Flag in RSA Assets</h2>
<p>Brand and legal flag claims, offers, and trademark uses that are unapproved, misleading, or out of sync with the FDD / advertising rules—not merely “short headlines.” If an asset cannot stand alone in any combination, it should not be in the RSA.</p>
<p>Common rejection triggers for multi-unit Search ads:</p>
<ul>
<li><strong>Unapproved value claims:</strong> “#1 in town,” “guaranteed results,” medical/financial outcomes, or anything that sounds like an earnings claim for the franchisee business.</li>
<li><strong>Offer and price drift:</strong> local discounts, financing teaser rates, or bundle language that national marketing did not clear for that market.</li>
<li><strong>Trademark misuse:</strong> altered logos in image assets, wrong legal entity names, or competitor-comparative headlines the brand forbids.</li>
<li><strong>Territory fiction:</strong> “serving all of [metro]” when your protected ZIP set is smaller, or implying corporate-owned coverage.</li>
<li><strong>Required disclosures missing:</strong> licensed-profession, franchise-opportunity, or offer terms that must appear when certain claims run.</li>
</ul>
<p>Write every headline and description so it remains true and on-brand even if Google shows it next to any other approved asset. RSA combinations are not a place to hide weak compliance behind a strong pin.</p>
<figure style="margin: 28px auto; max-width: 760px; text-align: center;"><img decoding="async" style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" src="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-ad-copy-compliance-rsa-limits-infographic.png" alt="Multi-unit franchise ad copy compliance infographic: Google responsive search ad limits of 15 headlines, 4 descriptions and 3 headlines shown" width="1200" height="1500" /></figure>
<h2>Pin Strategy and the Approved Asset Library</h2>
<p>Create a shared library of pre-approved headlines and descriptions, then pin only the lines that must always show—ideally with multiple distinct compliant options per pinned slot. Pinning one weak mandatory line into Headline 1 is how compliant ads lose CTR.</p>
<p>Practical setup:</p>
<ul>
<li><strong>Library first:</strong> 15+ approved headlines and 4 descriptions per theme (brand, offer, service, local proof), version-dated and stored where brand/legal can see them.</li>
<li><strong>Pin sparingly:</strong> Google’s own guidance is that pinning reduces combinations and can hurt Ad Strength. Use pins for legal/brand must-haves, not for personal preference.</li>
<li><strong>Pin multiples:</strong> If Headline 1 must be brand-safe identity, pin 2–3 unique approved identity lines to that position so the auction can still choose among compliant options.</li>
<li><strong>Campaign-level text assets:</strong> Where available, campaign-level headlines/descriptions can push required lines across every RSA—still subject to policy review—and should be managed as part of the same library, not a second shadow set.</li>
<li><strong>Disclaimers:</strong> When a disclosure must appear in Search ads, prefer Google’s text-disclaimer (or brand-mandated equivalent) over burying fine print in a description you hope gets chosen.</li>
</ul>
<p>Keep unit-specific lines in a clearly labeled subset of the library so a Miami offer cannot accidentally publish on a Denver RSA.</p>
<h2>Review SLA: Who Approves What, How Fast</h2>
<p>A review SLA names the approver, the turnaround clock, the submission format, and what “approved” means for go-live. Without it, multi-unit launches stall on the same three headlines every month.</p>
<ul>
<li><strong>Owner:</strong> brand marketing, franchise compliance, or a named co-op reviewer—not “whoever is free in Slack.”</li>
<li><strong>Clock:</strong> for example, 3 business days for library adds, 1 business day for swaps among already-approved lines.</li>
<li><strong>Packet:</strong> exact asset text, final URLs, geos, offer dates, and which units will run it.</li>
<li><strong>Decision:</strong> approved / approved with edits / rejected with reason code (claim, offer, trademark, territory, other).</li>
<li><strong>Expiry:</strong> seasonal offers auto-expire in the library so stale promos cannot be re-pinned later.</li>
</ul>
<p>Agencies and in-house leads should not “soft launch” unapproved assets into low-budget ad groups. That pattern burns trust faster than a late submission.</p>
<figure style="margin: 28px auto; max-width: 760px; text-align: center;"><img decoding="async" style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" src="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-ad-copy-compliance-rejected-vs-approved-infographic.png" alt="Infographic comparing a rejected franchise RSA asset with one that passes brand review, plus a six-step compliant RSA workflow" width="1200" height="1500" /></figure>
<h2>Location-Specific Copy Under National Rules</h2>
<p>Location-specific copy is allowed when it is factually true for that unit’s territory and still fits national voice, offer, and trademark rules. Local does not mean freelance brand.</p>
<p>Safe local patterns:</p>
<ul>
<li>City or neighborhood served that sits inside the unit’s approved geo.</li>
<li>Hours, phone, and landing pages that match the GBP and call-tracking stack for that unit.</li>
<li>Local proof that brand permits (review counts, years in market) without inventing rankings.</li>
</ul>
<p>Unsafe local patterns:</p>
<ul>
<li>Metro-wide claims when you only cover a ZIP cluster.</li>
<li>Unit-invented guarantees or price points that conflict with national menus or co-op rules.</li>
<li>Headlines that imply the location is corporate-owned or the only location when it is not.</li>
</ul>
<p>Mirror the same geo discipline you use in campaigns—see our <a href="https://leadppc.com/franchise/multi-unit-franchise-territory-overlap-ads/">territory overlap playbook</a>—so copy and targeting tell the same story.</p>
<h2>Testing RSAs Without Breaking Compliance</h2>
<p>Test by rotating approved variants and measuring CTR/conversion within the compliant set—not by introducing unapproved claims as “experiments.” Compliance is a constraint on the test cell, not an excuse to skip learning.</p>
<ul>
<li>Hold pins constant when you test non-pinned headlines so you know what changed.</li>
<li>Change one theme at a time (benefit vs. offer vs. local proof) inside the approved library.</li>
<li>Retire losers back to “do not use” in the library rather than deleting history brand may need for audits.</li>
<li>If Ad Strength complains about pinning, answer with more unique approved pins—not by unpinning a legally required line.</li>
</ul>
<p>When a unit’s volume is too thin to learn, pool creative tests across similar units that share the same approved library and offer calendar, while keeping budgets and geos per unit.</p>
<h2>Handoff Mid-Creative Cycle</h2>
<p>When an agency, marketing lead, or unit owner changes while RSAs are live, freeze the approved library, document pins and final URLs, and re-submit only net-new copy. Mid-cycle chaos is a top source of accidental off-brand publishes.</p>
<ol>
<li>Export all RSA assets, pins, and policy statuses.</li>
<li>Mark library rows as active / expired / rejected.</li>
<li>Transfer brand portal or shared-drive ownership to a company login you control.</li>
<li>Pause anything not on the approved list before the new team gets edit access.</li>
<li>Schedule one brand re-review for assets the new team wants to add in the first 14 days.</li>
</ol>
<p>Resale and multi-unit handoffs should include this creative packet beside account access—pair it with the <a href="https://leadppc.com/franchise/buying-franchise-unit-marketing-handoff/">30-day marketing handoff checklist</a> when a unit changes hands.</p>
<h2>Frequently Asked Questions</h2>
<p><strong>What do franchise brand and legal teams usually reject in Google Ads RSAs?</strong><br />
Unapproved claims and offers, trademark misuse, pricing or financing language that was not cleared, territory claims that overreach the unit’s rights, and anything that sounds like a guaranteed outcome or earnings claim. If an asset is not safe in every combination, it does not belong in the RSA.</p>
<p><strong>Should I pin brand-required headlines if pinning can hurt Ad Strength?</strong><br />
Yes when a line must appear for legal or brand reasons—pin it, and pin 2–3 distinct approved alternatives to the same position when possible. Google recommends pinning sparingly because it limits combinations; compliance pins are the exception, preference pins are not.</p>
<p><strong>How fast should brand review RSA copy for multi-unit operators?</strong><br />
Set a written SLA. Many operators aim for a few business days on new library assets and faster turnaround for swaps among already-approved lines. The exact clock depends on your brand team; what matters is a named owner, a packet format, and reason codes for rejections.</p>
<p><strong>Can location-specific RSA copy stay compliant with national brand rules?</strong><br />
Yes if local lines are factually true for the unit’s territory, match approved offers, and keep national voice and trademark rules. Local copy fails when it invents metro-wide coverage, rogue discounts, or ranking claims corporate did not approve.</p>
<p><strong>How do you A/B test RSA headlines under strict brand review?</strong><br />
Rotate only pre-approved variants, hold required pins steady, and change one theme at a time. Do not treat unapproved claims as “temporary tests.” Retire underperformers in the library so they cannot reappear in another ad group.</p>
<p><strong>What should happen to RSA assets when agencies or unit owners change mid-flight?</strong><br />
Freeze the approved library, export pins and URLs, pause anything not approved, transfer ownership to company-controlled logins, and re-submit only new copy. Mid-cycle handoffs without a freeze are how off-brand assets go live under a new editor.</p>
<p><script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What do franchise brand and legal teams usually reject in Google Ads RSAs?","acceptedAnswer":{"@type":"Answer","text":"Unapproved claims and offers, trademark misuse, pricing or financing language that was not cleared, territory claims that overreach the unit’s rights, and anything that sounds like a guaranteed outcome or earnings claim. If an asset is not safe in every combination, it does not belong in the RSA."}},{"@type":"Question","name":"Should I pin brand-required headlines if pinning can hurt Ad Strength?","acceptedAnswer":{"@type":"Answer","text":"Yes when a line must appear for legal or brand reasons—pin it, and pin 2–3 distinct approved alternatives to the same position when possible. Google recommends pinning sparingly because it limits combinations; compliance pins are the exception, preference pins are not."}},{"@type":"Question","name":"How fast should brand review RSA copy for multi-unit operators?","acceptedAnswer":{"@type":"Answer","text":"Set a written SLA. Many operators aim for a few business days on new library assets and faster turnaround for swaps among already-approved lines. The exact clock depends on your brand team; what matters is a named owner, a packet format, and reason codes for rejections."}},{"@type":"Question","name":"Can location-specific RSA copy stay compliant with national brand rules?","acceptedAnswer":{"@type":"Answer","text":"Yes if local lines are factually true for the unit’s territory, match approved offers, and keep national voice and trademark rules. Local copy fails when it invents metro-wide coverage, rogue discounts, or ranking claims corporate did not approve."}},{"@type":"Question","name":"How do you A/B test RSA headlines under strict brand review?","acceptedAnswer":{"@type":"Answer","text":"Rotate only pre-approved variants, hold required pins steady, and change one theme at a time. Do not treat unapproved claims as “temporary tests.” Retire underperformers in the library so they cannot reappear in another ad group."}},{"@type":"Question","name":"What should happen to RSA assets when agencies or unit owners change mid-flight?","acceptedAnswer":{"@type":"Answer","text":"Freeze the approved library, export pins and URLs, pause anything not approved, transfer ownership to company-controlled logins, and re-submit only new copy. Mid-cycle handoffs without a freeze are how off-brand assets go live under a new editor."}}]}</script></p>
<h2>Need Help?</h2>
<p>If you run Google Ads across several franchise units and need RSA copy that clears brand review without flattening CTR—asset libraries, pins, review SLAs, or mid-cycle handoffs—fill out our <a href="https://go.leadppc.com/contact/">Contact Us</a> form.</p>
<p>The post <a href="https://leadppc.com/franchise/multi-unit-franchise-ad-copy-compliance/">Multi-Unit Franchise Ad Copy Compliance: RSAs That Pass Brand Review Without Killing CTR</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://leadppc.com/franchise/multi-unit-franchise-ad-copy-compliance/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		<enclosure url="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-ad-copy-compliance-video.mp4" length="1431792" type="video/mp4" />

			</item>
		<item>
		<title>Multi-Unit Franchise Brand Bidding Conflicts: When Corporate and Your Units Bid on the Same Terms</title>
		<link>https://leadppc.com/franchise/multi-unit-franchise-brand-bidding-conflicts/</link>
					<comments>https://leadppc.com/franchise/multi-unit-franchise-brand-bidding-conflicts/#respond</comments>
		
		<dc:creator><![CDATA[Grant James]]></dc:creator>
		<pubDate>Mon, 16 Nov 2026 22:14:40 +0000</pubDate>
				<category><![CDATA[Franchise]]></category>
		<guid isPermaLink="false">https://leadppc.com/?p=4433</guid>

					<description><![CDATA[<p>Multi-Unit Franchise Brand Bidding Conflicts: When Corporate and Your Units Bid on the Same Terms Multi-unit franchise brand bidding conflicts: what to do when corporate and your units bid on the same terms. Key Takeaways When corporate and your local units bid the same brand terms into the same geos, you inflate your own CPCs [...]</p>
<p>The post <a href="https://leadppc.com/franchise/multi-unit-franchise-brand-bidding-conflicts/">Multi-Unit Franchise Brand Bidding Conflicts: When Corporate and Your Units Bid on the Same Terms</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>Multi-Unit Franchise Brand Bidding Conflicts: When Corporate and Your Units Bid on the Same Terms</h1>
<div class="wp-caption alignnone" style="width: 1290px;">
<p><img loading="lazy" decoding="async" src="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-brand-bidding-conflicts-featured.jpg" alt="Multi-unit franchise brand bidding conflicts between corporate and franchisee campaigns" width="1280" height="720" /></p>
<p class="wp-caption-text">Multi-unit franchise brand bidding conflicts: what to do when corporate and your units bid on the same terms.</p>
</div>
<p><!-- HERO --></p>
<div class="key-takeaways" style="border: 1px solid #d9d9d9; border-left: 4px solid #1e73be; background: #f7f9fc; padding: 16px 20px; margin: 24px 0;">
<p><strong>Key Takeaways</strong></p>
<ul>
<li>When corporate and your local units bid the same brand terms into the same geos, you inflate your own CPCs and split credit for navigational demand the brand already earned.</li>
<li>Start with Auction Insights and search-term reports to prove overlap before you negotiate—impression share stolen by “you” is the clearest waste signal.</li>
<li>Write down who owns brand keywords, close variants, match types, and which geos each party may defend. Handshake rules fail the first time budgets tighten.</li>
<li>You can usually reduce conflict with geo fencing, shared negatives, and separate budgets without violating the franchise agreement—if those tactics stay inside the brand’s written advertising rules.</li>
<li>Escalate when corporate policy or account access blocks a clean split; absorb when the wasted dollars are smaller than the political cost of a fight.</li>
<li>Measure wasted brand spend as excess CPC × overlapping impressions (or as branded CPA vs. a non-overlapped baseline), not as “brand is expensive so it must be wrong.”</li>
</ul>
</div>
<p>Brand bidding conflicts show up as rising branded CPCs, messy attribution, and franchisees arguing with corporate about who “owns” navigational traffic. If you run several units and also see national brand ads in your ZIPs, you need a written split—not another round of “let’s both bid and see.”</p>
<p>This playbook is for multi-unit operators who control local Google Ads spend and keep colliding with corporate (or neighboring owners) on the same brand terms. Franchise agreements and co-op guides differ, so confirm what your brand allows before you change targeting or pause campaigns. Google Ads policies and auction behavior also change; treat the tactics below as operator practice, not a promise that any specific setup is always permitted.</p>
<figure style="margin: 28px 0;"><video style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" title="Multi-unit franchise brand bidding conflicts in 25 seconds" poster="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-brand-bidding-conflicts-video-poster.jpg" preload="metadata" muted="" controls="controls" width="1280" height="720"><source src="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-brand-bidding-conflicts-video.mp4" type="video/mp4" /></video><figcaption style="font-size: 14px; color: #5c687c; text-align: center; margin-top: 8px;">Multi-unit franchise brand bidding conflicts: the key points in 25 seconds.</figcaption></figure>
<h2>What Corporate vs. Franchisee Brand Auction Conflict Looks Like</h2>
<p>Corporate vs. franchisee brand conflict is when two (or more) accounts in the same system bid on the brand name, close variants, or branded + city terms into overlapping locations—so your own network raises the price of traffic it already earned. The SERP may still show one ad, but the auction price and the lead-routing mess are real.</p>
<p>Typical symptoms:</p>
<ul>
<li>Branded CPC climbs while non-brand stays flat.</li>
<li>Auction Insights shows another account (often labeled as you/your brand) with overlapping impression share in your core ZIPs.</li>
<li>Calls and forms land in a national queue while local crews sit idle—or the reverse.</li>
<li>Co-op claims get rejected because local brand spend duplicated national coverage.</li>
</ul>
<p>Since Google updated overlapping-ad rules, more than one ad for the same business can sometimes appear in different ad locations on a results page. That does not make internal brand competition a good idea. Two owners bidding the same navigational query still push price up and fragment learning.</p>
<h2>How to Prove Overlap With Auction Insights and Search Terms</h2>
<p>Prove overlap with Auction Insights on branded campaigns plus search-term reports that show exact brand queries, then map those impressions to the geos both parties target. Screenshots and date-stamped CSVs beat anecdotes in any corporate negotiation.</p>
<ol>
<li><strong>Isolate a brand campaign or ad group</strong> with exact and phrase brand terms (and the close variants you actually care about).</li>
<li><strong>Pull Auction Insights</strong> for the overlapping ZIP/city set and note impression share, overlap rate, and position above rate against your own brand domains or known national account patterns.</li>
<li><strong>Export search terms</strong> for branded queries and flag any that also appear in corporate reporting if you have visibility—or ask brand for a parallel export for the same weeks.</li>
<li><strong>Compare conversion paths</strong>: same phone/email within 30 days credited twice is a credit problem, not a demand problem.</li>
</ol>
<p>If you cannot see corporate’s account, ask for a standing brand-overlap report as a condition of continued local brand bidding. Without data, every argument becomes opinion.</p>
<figure style="margin: 28px auto; max-width: 760px; text-align: center;"><img loading="lazy" decoding="async" style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" src="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-brand-bidding-conflicts-who-owns-what-infographic.png" alt="Multi-unit franchise brand bidding conflicts infographic: who should own which search terms, corporate or the multi-unit operator" width="1200" height="1500" /></figure>
<h2>Who Should Own Brand, Geo, and Match Types</h2>
<p>Someone must own the brand keyword set, the geos where brand may be defended, and which match types are allowed—ideally in a one-page addendum both sides sign. Leaving it to “common sense” is how multi-unit operators inherit silent auction wars.</p>
<p>A workable ownership model many systems use:</p>
<ul>
<li><strong>Corporate owns core brand exact/phrase</strong> nationally (or by region) and routes leads by territory through the CRM.</li>
<li><strong>Local units own non-brand and local service terms</strong> inside their protected geos, with brand terms on a shared negative list.</li>
<li><strong>Branded + city / “near me”</strong> is either corporate-only or allowed locally only inside the unit’s core ZIPs with presence-only location targeting.</li>
<li><strong>Close variants and misspellings</strong> follow the same owner as the root brand term so nobody “accidentally” reopens the fight with a clever misspelling list.</li>
</ul>
<p>If your agreement already assigns brand advertising to corporate, stop local brand bidding and focus spend where you control outcomes. If the agreement is silent, negotiate the split before the next budget cycle—not after CPCs spike.</p>
<figure style="margin: 28px auto; max-width: 760px; text-align: center;"><img loading="lazy" decoding="async" style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" src="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-brand-bidding-conflicts-negotiation-packet-infographic.png" alt="Infographic: the brand bidding negotiation packet a multi-unit franchisee should bring to corporate" width="1200" height="1500" /></figure>
<h2>Negotiation Checklist for Multi-Unit Operators</h2>
<p>Negotiate with a short packet: proof of overlap, proposed ownership split, geo map, negative list, budget boundaries, and a 30-day test with shared metrics. Go in asking for a written rule, not a verbal “we’ll be careful.”</p>
<ul>
<li><strong>Packet:</strong> Auction Insights, branded CPC trend, duplicate-lead examples, and estimated wasted spend.</li>
<li><strong>Ask:</strong> Who bids brand? Where? Which match types? Who owns close variants?</li>
<li><strong>Map:</strong> Exclusive core ZIPs per unit; seam rule for borders; presence-only location targeting.</li>
<li><strong>Lists:</strong> Shared negatives for brand terms in local non-brand campaigns (or the reverse if locals keep brand).</li>
<li><strong>Money:</strong> Separate budgets—no shared budget that lets brand steal from non-brand learning.</li>
<li><strong>Credit:</strong> One lead / one credit rule when national and local both touch the same household.</li>
<li><strong>Review:</strong> Quarterly check of Auction Insights so the conflict cannot quietly return.</li>
</ul>
<p>For structure choices that make this easier to see and enforce, see our <a href="https://leadppc.com/franchise/multi-unit-franchisee-google-ads-account-structure/">Google Ads account structure guide</a>. For ZIP fencing between units you own, use the <a href="https://leadppc.com/franchise/multi-unit-franchise-territory-overlap-ads/">territory overlap playbook</a>.</p>
<h2>Geo, Negatives, and Budgets Without Violating the Agreement</h2>
<p>Most brands will accept geo fencing, shared negatives, and per-campaign budgets that reduce internal competition—as long as you do not bid off-brand creative, leave your territory, or break co-op creative rules. Read the advertising addendum and co-op guide before you change anything corporate might audit.</p>
<ul>
<li><strong>Geo:</strong> Target presence (people in or regularly in your locations), not “presence or interest,” when brand conflict is the issue. Exclude neighboring cores you do not serve.</li>
<li><strong>Negatives:</strong> Keep brand terms on a shared negative list in local non-brand campaigns if corporate owns brand. Keep competitor and job-seeker negatives shared either way.</li>
<li><strong>Budgets:</strong> Separate brand and non-brand budgets so Smart Bidding cannot drain service-term learning to chase cheap branded clicks—or the reverse.</li>
<li><strong>Co-op:</strong> If you claim reimbursement, document that local brand spend (if allowed) did not duplicate a national brand campaign your fund already pays for.</li>
</ul>
<p>If corporate requires their MCC linked, that can help visibility—but linking alone does not stop overlap. Structure and written ownership do.</p>
<h2>Escalate vs. Absorb: How to Decide</h2>
<p>Escalate when overlap is material, measurable, and blocked by policy or access you cannot fix alone; absorb when the dollar waste is small relative to relationship cost or when a 30-day test already shows a clean path. Put the decision rule in writing so you do not re-argue it every quarter.</p>
<ul>
<li><strong>Escalate</strong> if branded CPC is up sharply with high overlap rate, leads misroute, or co-op rejects local brand spend as duplicative.</li>
<li><strong>Absorb</strong> if overlap is occasional on seam ZIPs, volumes are tiny, or corporate already commits to a dated fix you can verify in Auction Insights.</li>
<li><strong>Hybrid</strong>: pause local brand for 30 days, measure non-brand and call volume, then decide with data instead of politics.</li>
</ul>
<h2>How to Measure Wasted Brand Spend</h2>
<p>Measure waste as the premium you pay because an internal competitor is in the same auction—not as total brand spend. Brand traffic can still be valuable; the waste is the self-inflicted premium and the duplicated credit.</p>
<p>Practical approaches:</p>
<ul>
<li><strong>Overlap premium:</strong> Compare branded CPC (or cost/conv) in high-overlap weeks vs. low-overlap weeks after a pause or geo fix.</li>
<li><strong>Impression-share method:</strong> Estimate spend on impressions where Auction Insights shows material overlap with your own brand, using average CPC for that segment.</li>
<li><strong>Credit cleanup:</strong> Count duplicate CRM records (same phone/email, national + local) and assign one owner; the second “conversion” is reporting fiction.</li>
</ul>
<p>Report the number monthly next to unit-level non-brand CPA so leadership sees brand conflict as an operations cost, not a creative debate.</p>
<h2>Frequently Asked Questions</h2>
<p><strong>Can my franchise units bid on the brand name if corporate already does?</strong><br />
Only if your franchise agreement and advertising rules allow it—and even then it is usually a bad default. Many systems reserve brand terms for corporate and route leads by territory. If locals may bid brand, limit it to each unit’s core geos with presence-only targeting and a written one-credit rule.</p>
<p><strong>How do Auction Insights prove corporate and local brand conflict?</strong><br />
On branded campaigns, Auction Insights shows overlapping impression share and related metrics against other advertisers. When the overlapping domain is your own brand or a known national account pattern—and search terms confirm navigational queries—you have evidence of internal auction pressure, not just “the market got more competitive.”</p>
<p><strong>Who should own brand keywords, geos, and match types?</strong><br />
Put ownership in writing. A common model: corporate owns core brand exact/phrase and close variants; local units own non-brand inside protected geos; branded + city is either corporate-only or local-only inside core ZIPs. Match-type rules should follow the same owner so variants do not reopen the fight.</p>
<p><strong>Can geo fencing and shared negatives fix this without breaking the franchise agreement?</strong><br />
Often yes, if you stay inside brand creative, territory, and co-op rules. Presence-only location targeting, exclusions for neighboring cores, shared brand negatives on the non-owner’s campaigns, and separate brand/non-brand budgets reduce conflict without requiring a contract amendment—though a short written addendum still helps.</p>
<p><strong>When should I escalate to corporate instead of absorbing the cost?</strong><br />
Escalate when overlap is material (CPC premium, misrouted leads, failed co-op claims) and you lack access or authority to fix it. Absorb when waste is small or a dated corporate fix is already in motion. Use a 30-day pause test when politics are hot and data is thin.</p>
<p><strong>How do I calculate wasted spend from brand bidding overlap?</strong><br />
Compare branded CPC or cost/conversion in high-overlap vs. cleaned-up periods, or estimate spend on impressions with material internal overlap using Auction Insights and average CPC. Also deduct duplicate CRM credits so you do not treat double-counted leads as performance.</p>
<p><script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Can my franchise units bid on the brand name if corporate already does?","acceptedAnswer":{"@type":"Answer","text":"Only if your franchise agreement and advertising rules allow it—and even then it is usually a bad default. Many systems reserve brand terms for corporate and route leads by territory. If locals may bid brand, limit it to each unit’s core geos with presence-only targeting and a written one-credit rule."}},{"@type":"Question","name":"How do Auction Insights prove corporate and local brand conflict?","acceptedAnswer":{"@type":"Answer","text":"On branded campaigns, Auction Insights shows overlapping impression share and related metrics against other advertisers. When the overlapping domain is your own brand or a known national account pattern—and search terms confirm navigational queries—you have evidence of internal auction pressure, not just “the market got more competitive.”"}},{"@type":"Question","name":"Who should own brand keywords, geos, and match types?","acceptedAnswer":{"@type":"Answer","text":"Put ownership in writing. A common model: corporate owns core brand exact/phrase and close variants; local units own non-brand inside protected geos; branded + city is either corporate-only or local-only inside core ZIPs. Match-type rules should follow the same owner so variants do not reopen the fight."}},{"@type":"Question","name":"Can geo fencing and shared negatives fix this without breaking the franchise agreement?","acceptedAnswer":{"@type":"Answer","text":"Often yes, if you stay inside brand creative, territory, and co-op rules. Presence-only location targeting, exclusions for neighboring cores, shared brand negatives on the non-owner’s campaigns, and separate brand/non-brand budgets reduce conflict without requiring a contract amendment—though a short written addendum still helps."}},{"@type":"Question","name":"When should I escalate to corporate instead of absorbing the cost?","acceptedAnswer":{"@type":"Answer","text":"Escalate when overlap is material (CPC premium, misrouted leads, failed co-op claims) and you lack access or authority to fix it. Absorb when waste is small or a dated corporate fix is already in motion. Use a 30-day pause test when politics are hot and data is thin."}},{"@type":"Question","name":"How do I calculate wasted spend from brand bidding overlap?","acceptedAnswer":{"@type":"Answer","text":"Compare branded CPC or cost/conversion in high-overlap vs. cleaned-up periods, or estimate spend on impressions with material internal overlap using Auction Insights and average CPC. Also deduct duplicate CRM credits so you do not treat double-counted leads as performance."}}]}</script></p>
<h2>Need Help?</h2>
<p>If you own several franchise units and brand auctions are colliding with corporate or neighboring owners—ownership splits, geo fencing, negatives, or measuring wasted branded spend—fill out our <a href="https://go.leadppc.com/contact/">Contact Us</a> form.</p>
<p>The post <a href="https://leadppc.com/franchise/multi-unit-franchise-brand-bidding-conflicts/">Multi-Unit Franchise Brand Bidding Conflicts: When Corporate and Your Units Bid on the Same Terms</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://leadppc.com/franchise/multi-unit-franchise-brand-bidding-conflicts/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		<enclosure url="https://leadppc.com/wp-content/uploads/2026/11/multi-unit-franchise-brand-bidding-conflicts-video.mp4" length="1505658" type="video/mp4" />

			</item>
		<item>
		<title>Multi-Location Google Business Profiles for Franchisees Who Own Several Units</title>
		<link>https://leadppc.com/franchise/multi-location-franchisee-google-business-profiles/</link>
					<comments>https://leadppc.com/franchise/multi-location-franchisee-google-business-profiles/#respond</comments>
		
		<dc:creator><![CDATA[Grant James]]></dc:creator>
		<pubDate>Sat, 14 Nov 2026 16:17:32 +0000</pubDate>
				<category><![CDATA[Franchise]]></category>
		<guid isPermaLink="false">https://leadppc.com/?p=4379</guid>

					<description><![CDATA[<p>Operator playbook for multi-unit franchisees running Google Business Profiles across several locations — eligibility, NAP, reviews, ads/LSA linking, and suspension recovery.</p>
<p>The post <a href="https://leadppc.com/franchise/multi-location-franchisee-google-business-profiles/">Multi-Location Google Business Profiles for Franchisees Who Own Several Units</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>Multi-Location Google Business Profiles for Franchisees Who Own Several Units</h1>
<div id="attachment_4381" class="wp-caption alignnone" style="width: 1290px;">
<p><img loading="lazy" decoding="async" class="size-full wp-image-4582" src="https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-featured.jpg" alt="Multi-Location Google Business Profiles for Franchisees Who Own Several Units" width="1280" height="720" srcset="https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-featured-200x113.jpg 200w, https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-featured-300x169.jpg 300w, https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-featured-400x225.jpg 400w, https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-featured-600x338.jpg 600w, https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-featured-800x450.jpg 800w, https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-featured-1024x576.jpg 1024w, https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-featured-1200x675.jpg 1200w, https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-featured.jpg 1280w" sizes="auto, (max-width: 1280px) 100vw, 1280px" /></p>
<p id="caption-attachment-4381" class="wp-caption-text">Multi-location Google Business Profiles for franchisees who own several units — operator playbook for eligibility, NAP, reviews, and unit-level Maps ops.</p>
</div>
<p>If you own several franchise units, Google Business Profile (GBP) stops being “set up the listing and forget it.” You’re managing a small portfolio of Maps presence — each with its own address truth, phone, hours, reviews, photos, and verification history — under one brand.</p>
<p>I’ve sold franchise units myself and I’ve helped a lot of multi-unit operators (typically 2–10 units) keep local demand from getting messy. The pattern I see: owners treat GBP like a single-location chore times N, or they let corporate “handle listings” without a unit-level ops sheet. That usually creates duplicate profiles, mixed phone numbers, review blind spots, and suspensions that take weeks to unwind.</p>
<p>This playbook is <strong>GBP operations only</strong> — for multi-unit franchisee operators who already own the locations. For paid search/Meta geo and budgets across units you own, use our <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit franchise advertising playbook</a>. For Local Service Ads eligibility, routing, and unit budgets, see <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">Google LSA operations across several locations</a>. Those are complementary channels. This page stays on Maps / Business Profile ops.</p>
<p>We’re not rewriting <a href="https://leadppc.com/franchise/local-franchise-marketing/">local franchise marketing</a> ideas lists or a generic local SEO checklist. The job here is how <em>you</em> run GBP when you own several units.</p>
<figure style="margin: 28px 0;"><video style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" title="Multi-location Google Business Profiles in 25 seconds" poster="https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-video-poster.jpg" preload="metadata" muted="" controls="controls" width="1280" height="720"><source src="https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-video.mp4" type="video/mp4" /></video><figcaption style="font-size: 14px; color: #5c687c; text-align: center; margin-top: 8px;">Multi-location Google Business Profiles for franchisees: the key points in 25 seconds.</figcaption></figure>
<h2>Why Multi-Unit GBP Is Different When YOU Own the Locations</h2>
<p>When corporate owns hundreds of locations, GBP is a platform problem. When <em>you</em> own 2–10 units, GBP is an <strong>operator problem</strong>:</p>
<ul>
<li>You (or your GM) live the phone tree, the hours exceptions, and the angry review.</li>
<li>One weak unit’s rating still colors how customers talk about “the brand” in your metro.</li>
<li>Acquisitions, remodels, and “we might sell Unit 4 next year” force handoff decisions corporate templates don’t cover.</li>
<li>Ads, LSA, and the website all want clean per-unit NAP (name / address / phone) — GBP is usually the source of truth customers trust first.</li>
</ul>
<p>Shared ownership also creates a false sense of safety. Operators assume, “I own all three, so Google will treat them as one business.” It won’t. Each profile is scored and policed as its own location. Your org chart is irrelevant to Maps until the NAP, categories, hours, and proof match that location.</p>
<p>What “good” looks like for a multi-unit owner is boring on purpose: every unit has a claimed profile, a short list of managers who still work there, a phone that humans answer, hours that match the door, photos that look like that building, and a review SLA someone owns.</p>
<p><strong>[Universal]</strong> Google evaluates each profile as a real business location. Shared ownership does not give you permission to invent storefronts, share one address across units, or recycle a verified profile for a different site.</p>
<p><strong>[Confirm with your franchisor]</strong> Who is allowed to claim, edit, and transfer GBP managers; required business-name format; and whether brand requires centralized admin access.</p>
<h2>One Profile Per Real Location: Eligibility, Storefront vs Service-Area, Address and Phone Rules</h2>
<p>Start with a blunt rule: <strong>one Google Business Profile per real operating location you can prove.</strong> A shared brand name is not a substitute for a real address, real hours, and real customer-facing presence.</p>
<table>
<tbody>
<tr>
<th>Unit</th>
<th>Primary category</th>
<th>Storefront or service-area?</th>
<th>Public address</th>
<th>Phone</th>
<th>Website / landing URL</th>
<th>Hours match ops?</th>
<th>Verification</th>
<th>Notes</th>
</tr>
<tr>
<td>Unit 1</td>
<td>Set</td>
<td>Choose one model</td>
<td>Documented</td>
<td>Unique / approved</td>
<td>Unit URL</td>
<td>Y/N</td>
<td>Verified / pending / failed</td>
<td></td>
</tr>
<tr>
<td>Unit 2</td>
<td>Set</td>
<td>Choose one model</td>
<td>Documented</td>
<td>Unique / approved</td>
<td>Unit URL</td>
<td>Y/N</td>
<td>Verified / pending / failed</td>
<td></td>
</tr>
<tr>
<td>Unit 3</td>
<td>Set</td>
<td>Choose one model</td>
<td>Documented</td>
<td>Unique / approved</td>
<td>Unit URL</td>
<td>Y/N</td>
<td>Verified / pending / failed</td>
<td></td>
</tr>
</tbody>
</table>
<p>Decision points that trip multi-unit owners:</p>
<ul>
<li><strong>Storefront vs service-area.</strong> If customers visit you, you generally need a public address. If you go to them and hide the address, service-area rules apply — and inventing a fake suite to “get on the map” is how suspensions start.</li>
<li><strong>Address truth.</strong> Suite numbers, shared retail pads, and “use the warehouse” tricks create duplicate and verification risk. If two units share a parking lot but have distinct customer entrances and ops, treat them as distinct locations unless brand legal says otherwise <em>and</em> Google’s model matches that reality.</li>
<li><strong>Phone.</strong> Prefer a stable, unit-true number that matches how you answer. Random tracking swaps without a NAP plan confuse Maps and customers. If Unit 2’s GBP rings a call center that doesn’t know which unit the customer is near, you’ve bought confusion.</li>
<li><strong>Acquired units.</strong> The old owner’s profile may still exist, unclaimed, or claimed by someone who left. Inventory every Maps result for the brand + address before you create anything new. Creating first and cleaning later is how you manufacture duplicates.</li>
<li><strong>Remodels and temporary closures.</strong> Update hours and posts on the <em>same</em> profile. Don’t open a temporary second listing “for the pop-up window.”</li>
</ul>
<p><strong>[Universal]</strong> Don’t create a second profile “just in case,” and don’t point two units at one address.</p>
<p><strong>[Confirm with your franchisor]</strong> Approved NAP format vs the corporate directory, whether tracking numbers are allowed on GBP, and who owns the listing if you exit the unit.</p>
<h2>Naming, Categories, and Brand Consistency Without Looking Like Duplicates</h2>
<p>Brand consistency and “looking like spam duplicates” are different problems. Google cares whether profiles represent distinct places. Customers care whether Unit A and Unit B feel like the same trustworthy brand.</p>
<p>Practical naming habits for multi-unit owners:</p>
<ul>
<li>Follow the brand’s legal / DBA pattern exactly — including city or neighborhood modifiers <strong>only</strong> when the brand standard allows them.</li>
<li>Keep primary categories aligned unit-to-unit unless a location truly offers a different primary service mix.</li>
<li>Secondary categories can reflect real local offerings; don’t keyword-stuff every unit with every service the brand has ever sold.</li>
<li>Descriptions: shared proof points + local facts (parking, neighborhoods served, team) beat copy-paste walls of keyword spam.</li>
<li>Attributes and services lists should match what that unit can actually fulfill this month — not what the brand brochure promised nationally.</li>
</ul>
<p>If two of your units show up next to each other in Maps with near-identical names, photos, and descriptions, that can still be fine <strong>when the addresses are distinct and true</strong>. What gets you in trouble is sameness <em>plus</em> weak address/phone differentiation, or keyword-stuffed names that look like spam clones.</p>
<p><strong>[Confirm with your franchisor]</strong> Exact business-name string, logo, and category shortlist. If corporate pushes a naming change network-wide, schedule it — don’t freelance Unit 7 overnight.</p>
<p><strong>[Universal]</strong> Keyword-stuffed names (“Best HVAC Near Me — Brand — City”) and near-identical profiles for the same address are classic duplicate / policy failure modes.</p>
<h2>Reviews Ops Across Units: Request, Respond, Escalate — and How One Bad Unit Hurts the Brand</h2>
<p>Reviews are <strong>location-level assets</strong> with <strong>portfolio-level consequences</strong>. Prospects often read two or three of your units before they call any of them.</p>
<p>Run reviews like operations:</p>
<ol>
<li><strong>Request:</strong> Who asks, on which completed jobs, within what time window — per unit.</li>
<li><strong>Respond:</strong> Owner or manager SLA for positives <em>and</em> negatives (same-day / 48-hour — pick one and measure it).</li>
<li><strong>Escalate:</strong> Safety, legal, discrimination, or brand-risk complaints leave the unit manager’s inbox on a written path.</li>
<li><strong>Coach:</strong> A unit stuck at 3.6 stars with slow replies is an ops problem first, a “GBP SEO” problem second.</li>
<li><strong>Compare fairly:</strong> Don’t beat up a 90-day-old acquisition for not matching a five-year unit’s review velocity. Do beat it up for unanswered 1-stars.</li>
</ol>
<p>One unit with ignored 1-star reviews can poison brand searchers in the whole DMA even when your other units are at 4.8. Don’t average the pain away in a blended dashboard — fix the unit. If Unit 5’s service failure is a staffing issue, buying more ads into Unit 5 (see the <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit ads playbook</a>) just amplifies the reputation problem.</p>
<p><strong>[Confirm with your franchisor]</strong> Approved response templates, banned admissions, and when corporate communications must take over.</p>
<h2>Photos, Hours, Posts, Products/Services — What to Centralize vs Keep Local</h2>
<p>Same organizing rule as multi-unit ads: <strong>centralize what benefits from shared standards; keep local what is unit-true.</strong></p>
<p><strong>Centralize (operator / brand layer)</strong></p>
<ul>
<li>Photo quality bar and banned imagery</li>
<li>Post templates and offer approval workflow</li>
<li>Products/services naming conventions</li>
<li>Weekly audit checklist and KPI pack</li>
<li>Manager-user access policy</li>
<li>Crisis / suspension playbook (who files what)</li>
</ul>
<p><strong>Keep local (per unit)</strong></p>
<ul>
<li>Exterior / interior / team photos of <em>that</em> site</li>
<li>Holiday hours, temporary closures, remodel notes</li>
<li>Parking, entrance, and accessibility details</li>
<li>Local posts tied to real unit events</li>
<li>Services actually fulfilled at that unit’s capacity</li>
<li>Q&amp;A answers that match how <em>that</em> unit operates</li>
</ul>
<p>A useful cadence for 2–10 units: weekly 15-minute portfolio scan (verification flags, hours mismatches, unanswered reviews), monthly photo/post refresh on the weakest units, quarterly manager-user audit. You’re not trying to “out-SEO” corporate. You’re trying to stop easy losses.</p>
<p><strong>[Confirm with your franchisor]</strong> Creative and offer approval SLAs. If approval takes three weeks, batch posts — don’t let Unit 2 go dark while Unit 5 waits on a headline.</p>
<figure style="margin: 28px auto; max-width: 760px;"><img loading="lazy" decoding="async" style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" src="https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-centralize-vs-local-infographic.png" alt="Infographic: what to centralize vs. keep local in Google Business Profile for multi-unit franchisees, plus six per-unit setup steps" width="1200" height="1500" /><figcaption style="font-size: 14px; color: #5c687c; text-align: center; margin-top: 8px;">What to centralize at the operator layer and what to keep local for each unit.</figcaption></figure>
<h2>Linking GBP to Ads, LSA, and Website Tracking Without Mixing Units</h2>
<p>GBP, Google Ads location assets, LSA, and your site should agree on <strong>which unit is which</strong>. Mixing units is how dashboards lie.</p>
<p>Minimum hygiene:</p>
<ul>
<li>Each GBP website URL points to the correct unit landing page (or brand-approved locator behavior).</li>
<li>Phone on GBP matches the number you intend customers to call for that unit — don’t silently rotate tracking numbers without a NAP policy.</li>
<li>Ads location extensions / assets and LSA profiles should map to the same real locations as GBP — not a blended “metro” fiction.</li>
<li>CRM fields: unit, source, campaign/profile, disposition — so a Maps call and an LSA call don’t both get credited as whatever unit answered last.</li>
<li>UTM or landing rules that preserve unit identity when someone clicks from Maps to the site.</li>
</ul>
<p>Deep dives on the paid side live in the <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit advertising playbook</a> and <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">LSA operations playbook</a>. For Search tactics outside Maps ops, <a href="https://leadppc.com/franchise/local-franchise-ppc/">local franchise PPC</a> is the channel companion. Light SEO context (not a substitute for this SOP) sits in <a href="https://leadppc.com/franchise/franchise-seo-ideas/">franchise SEO ideas</a>.</p>
<p><strong>[Universal]</strong> Call-recording and SMS consent rules vary by state. If tracking crosses state lines, use a clear announcement and get counsel to review all-party-consent exposure.</p>
<p><strong>[Confirm with your franchisor]</strong> Whether tracking numbers may appear on GBP / web / LSA without breaking directory NAP standards, and who owns the customer record.</p>
<h2>Suspension, Duplicate, and Verification Failure Modes — and How Operators Recover</h2>
<p>Multi-unit portfolios see the same failure modes on loop:</p>
<table>
<tbody>
<tr>
<th>Failure mode</th>
<th>Typical trigger</th>
<th>Operator recovery posture</th>
</tr>
<tr>
<td>Duplicate</td>
<td>Re-created profile after acquisition; old unclaimed listing still live</td>
<td>Claim or request merge/remove; don’t keep posting to both</td>
</tr>
<tr>
<td>Verification failed / stuck</td>
<td>Docs don’t match address entity; mailbox issues; prior owner still listed</td>
<td>Fix entity/address proof; use brand-approved legal name; document chain of ownership</td>
</tr>
<tr>
<td>Suspended</td>
<td>Policy, fake address, keyword name, or contested ownership</td>
<td>Stop “quick new profile” recreates; assemble proof; appeal with consistent NAP</td>
</tr>
<tr>
<td>Edit wars</td>
<td>Ex-employee, landlord, or prior owner still a manager</td>
<td>Audit users; remove stale managers; lock who can invite</td>
</tr>
</tbody>
</table>
<p>Recovery habits that save weeks:</p>
<ul>
<li>Keep a folder per unit: lease/utility proof, license, photos of signage, prior verification mail if any, list of managers.</li>
<li>When you acquire a unit, make “Maps inventory + ownership transfer” a closing checklist item — same priority as utilities and POS.</li>
<li>If Google asks for video or document verification, film <em>that</em> address and door, not a prettier sister unit across town.</li>
</ul>
<p><strong>[Universal]</strong> Creating a fresh profile to dodge a suspension often makes the duplicate problem worse. Fix the authoritative listing.</p>
<p><strong>[Confirm with your franchisor]</strong> Whether brand legal or a designated vendor must file appeals, and what proof packets they already keep for each site.</p>
<h2>When to Consolidate vs Keep Separate (Adjacent Units, Acquisitions, Soon-to-Sell)</h2>
<table>
<tbody>
<tr>
<th>Situation</th>
<th>Default</th>
<th>Why</th>
</tr>
<tr>
<td>Two real storefronts, even if close</td>
<td><strong>Keep separate</strong></td>
<td>Distinct customer-facing places</td>
</tr>
<tr>
<td>One unit acquired mid-year</td>
<td><strong>Keep separate</strong>; reclaim/repair that unit’s listing</td>
<td>Don’t clone another unit’s profile</td>
</tr>
<tr>
<td>Unit you plan to sell in 12–24 months</td>
<td><strong>Keep separate</strong> with clean manager handoff plan</td>
<td>Buyer needs a detachable asset</td>
</tr>
<tr>
<td>Truly one operating site that was split into two profiles by mistake</td>
<td><strong>Consolidate</strong> to the accurate listing</td>
<td>Duplicates hurt Maps trust</td>
</tr>
<tr>
<td>Service-area business with overlapping polygons, no public address</td>
<td>Still <strong>one profile per legitimate business presence</strong> your docs support — not “one mega profile for the metro”</td>
<td>Simplifying admin is how you invent presence</td>
</tr>
</tbody>
</table>
<p>Adjacent units you own are still separate places if customers experience them as separate. Consolidating to “make reporting easier” is almost always the wrong trade. Same for “we’ll just use Unit 1’s profile until Unit 2 verifies” — that shortcut becomes a year-long mess.</p>
<p>If you are preparing a unit for resale, treat GBP managers, review history, and phone portability as part of diligence — not as an afterthought the week before closing.</p>
<h2>Per-Unit GBP Checklist (Operator Sheet)</h2>
<table>
<tbody>
<tr>
<th>Checklist item</th>
<th>Unit 1</th>
<th>Unit 2</th>
<th>Unit 3</th>
</tr>
<tr>
<td>Claimed + correct owners/managers</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Name matches brand standard</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Primary category correct</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Address / service area truthful</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Phone stable + answered</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Hours match ops (incl. holidays)</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Website URL unit-correct</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Photos fresh (exterior/interior/team)</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Review request + response SLA live</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>No duplicate Maps listings for same site</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Linked cleanly to ads/LSA/CRM unit ID</td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>
<p>Print this (or put it in your ops wiki) and review it monthly. The operators who stay out of suspension hell are the ones who catch NAP drift early — not the ones who “optimize categories” every other week.</p>
<p>ChatGPT now has its own business profiles, too. Once each unit&#8217;s GBP is clean, claim it there with our <a href="https://leadppc.com/franchise/chatgpt-business-profiles-franchise-locations/">ChatGPT business profiles playbook for franchise locations</a>, using the exact same name, address, phone and hours.</p>
<figure style="margin: 28px auto; max-width: 760px;"><img loading="lazy" decoding="async" style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" src="https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-per-unit-checklist-infographic.png" alt="Infographic: the per-unit Google Business Profile checklist for franchisees, with weekly, monthly and quarterly review cadence" width="1200" height="1500" /><figcaption style="font-size: 14px; color: #5c687c; text-align: center; margin-top: 8px;">The per-unit GBP checklist and the review cadence for 2 to 10 units.</figcaption></figure>
<h2>FAQs</h2>
<p><strong>Can I run one Google Business Profile for every unit I own?</strong><br />
No — not if those are separate real operating locations. One profile per legitimate location is the operating assumption.</p>
<p><strong>What if two units sit a mile apart in the same metro?</strong><br />
Keep separate profiles, separate phones/hours/photos, and a review ops plan for each. Proximity is not a merge reason.</p>
<p><strong>Should the GBP phone be my call-tracking number?</strong><br />
Only inside a written NAP policy your franchisor accepts. Stability and answer rate beat clever tracking every time.</p>
<p><strong>Who should respond to reviews — corporate or the unit manager?</strong><br />
Usually the unit manager with a brand escalation path. Corporate sets standards; the local operator owns the reputation.</p>
<p><strong>We bought a unit and Maps still shows the old owner. Now what?</strong><br />
Inventory claims and duplicates first. Reclaim or request ownership transfer with proof — don’t create a second profile on day one.</p>
<h2>Need Help?</h2>
<p>If you would like to speak with us about multi-location Google Business Profile operations for the units you own — eligibility, NAP hygiene, reviews ops, and clean links to ads/LSA — please fill out our <a href="https://go.leadppc.com/contact/">Contact Us</a> form.</p>
<p>We can also tie GBP into the wider multi-unit stack (Search, LSA, tracking, and capacity-aware allocation) without turning this into another generic local SEO ideas list.</p>
<p>The post <a href="https://leadppc.com/franchise/multi-location-franchisee-google-business-profiles/">Multi-Location Google Business Profiles for Franchisees Who Own Several Units</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://leadppc.com/franchise/multi-location-franchisee-google-business-profiles/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		<enclosure url="https://leadppc.com/wp-content/uploads/2026/11/multi-location-franchisee-google-business-profiles-video.mp4" length="1236214" type="video/mp4" />

			</item>
		<item>
		<title>ChatGPT Business Profiles for Franchise Locations: How to Claim Every Unit Next to Your GBP and LSA</title>
		<link>https://leadppc.com/franchise/chatgpt-business-profiles-franchise-locations/</link>
					<comments>https://leadppc.com/franchise/chatgpt-business-profiles-franchise-locations/#respond</comments>
		
		<dc:creator><![CDATA[Grant James]]></dc:creator>
		<pubDate>Sat, 14 Nov 2026 16:12:48 +0000</pubDate>
				<category><![CDATA[Franchise]]></category>
		<guid isPermaLink="false">https://leadppc.com/uncategorized/chatgpt-business-profiles-franchise-locations/</guid>

					<description><![CDATA[<p>OpenAI opened ChatGPT business profiles in beta on November 10, 2026. Here is how multi-unit franchisees claim, verify and govern every unit next to their Google Business Profiles and LSA.</p>
<p>The post <a href="https://leadppc.com/franchise/chatgpt-business-profiles-franchise-locations/">ChatGPT Business Profiles for Franchise Locations: How to Claim Every Unit Next to Your GBP and LSA</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>ChatGPT Business Profiles for Franchise Locations: How to Claim Every Unit Next to Your GBP and LSA</h1>
<div class="wp-caption alignnone" style="width: 1290px;">
<p><img loading="lazy" decoding="async" src="https://leadppc.com/wp-content/uploads/2026/11/chatgpt-business-profiles-franchise-locations-featured.jpg" alt="ChatGPT business profiles for franchise locations" width="1280" height="720" /></p>
<p class="wp-caption-text">ChatGPT business profiles for franchise locations: an operator playbook for claiming, verifying, and governing every unit you own.</p>
</div>
<p>On November 10, 2026, OpenAI opened a beta called Businesses in ChatGPT. For the first time, a business can claim the profile ChatGPT shows when someone asks about it, correct the details, and see how often it gets mentioned. The press is calling it ChatGPT&#8217;s answer to Google Business Profile, and for franchise operators that framing is about right.</p>
<p>I&#8217;ve spent years on both sides of franchise growth, selling units and running paid local demand for operators who own anywhere from two to ten of them. My read on ChatGPT business profiles is simple: claim every real unit you can now, keep each one identical to your Google Business Profile, and don&#8217;t expect an agent or a flood of leads yet. This playbook covers what launched, who can claim today, how to do it unit by unit, and who should own the profile when corporate and the franchisee both care about the listing.</p>
<p>If you haven&#8217;t cleaned up your Google listings yet, start with our <a href="https://leadppc.com/franchise/multi-location-franchisee-google-business-profiles/">multi-location Google Business Profile playbook</a>. ChatGPT cross-checks what it finds, so a messy GBP becomes a messy ChatGPT profile.</p>
<figure style="margin: 28px 0;"><video style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" title="ChatGPT business profiles for franchise locations in 25 seconds" poster="https://leadppc.com/wp-content/uploads/2026/11/chatgpt-business-profiles-franchise-locations-video-poster.jpg" preload="metadata" muted="" controls="controls" width="1280" height="720"><source src="https://leadppc.com/wp-content/uploads/2026/11/chatgpt-business-profiles-franchise-locations-video.mp4" type="video/mp4" /></video><figcaption style="font-size: 14px; color: #5c687c; text-align: center; margin-top: 8px;">ChatGPT business profiles for franchise locations: the key points in 25 seconds.</figcaption></figure>
<h2>What OpenAI Launched on November 10, 2026 (and What It Isn&#8217;t)</h2>
<p>Businesses in ChatGPT has two parts, and they are not available on the same terms.</p>
<ul>
<li><strong>Business Hub:</strong> the management side. You open it from ChatGPT, find your business, verify you own it or are authorized to represent it, and then keep its details current. After verification you can update key information like your website, description, products and services. Hub also shows aggregated insights on mentions and clicks, but only once a business has enough conversations to meet OpenAI&#8217;s thresholds.</li>
<li><strong>Business Agents:</strong> an optional chat assistant that a ChatGPT user can open from your profile. At launch, agents are limited to eligible ecommerce and online service businesses in the United States. A claimable profile does not automatically qualify for an agent.</li>
</ul>
<p>OpenAI has also said businesses will be able to sponsor their agents as destinations for ChatGPT ads, with sponsored placements clearly labeled and kept separate from regular answers. ChatGPT now reaches roughly 1.2 billion people a week, which is why this matters even in beta.</p>
<p>What it isn&#8217;t: a map pack, a lead form, or a pay-per-lead channel like Google Local Services Ads. Claiming a profile doesn&#8217;t make ChatGPT recommend you more often on its own. It makes sure that when ChatGPT does name your unit, the facts are yours.</p>
<h2>ChatGPT Business Profiles vs. Google Business Profile vs. LSA</h2>
<p>Franchisees ask where this fits in the local stack. Here&#8217;s how I lay it out for operators:</p>
<table>
<tbody>
<tr>
<th>Channel</th>
<th>What it controls</th>
<th>How customers reach you</th>
<th>Cost</th>
<th>Unit-level priority today</th>
</tr>
<tr>
<td>Google Business Profile</td>
<td>Your Maps listing, hours, reviews, photos</td>
<td>Map pack, Maps, Google Search</td>
<td>Free</td>
<td>Mandatory for every real location</td>
</tr>
<tr>
<td>Google Local Services Ads</td>
<td>A paid, verified lead placement</td>
<td>Calls and messages from the LSA unit</td>
<td>Pay per lead</td>
<td>Where the category and economics fit</td>
</tr>
<tr>
<td>ChatGPT business profile</td>
<td>The details ChatGPT uses about your business</td>
<td>ChatGPT answers and your profile page</td>
<td>Free to claim in beta</td>
<td>Claim now, keep it identical to GBP</td>
</tr>
</tbody>
</table>
<p>If you run LSA, nothing changes there. Our <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">Google LSA operations playbook</a> still applies. The ChatGPT profile is one more place your name, address, phone and hours have to match.</p>
<h2>Why Local Operators Can&#8217;t Ignore This</h2>
<p>The behavior shift is already measurable. BrightLocal&#8217;s 2026 consumer survey found the share of people using AI to find a local business jumped from 6% to 45% in a single year. On the other side, SOCi&#8217;s 2026 Local Visibility Index, which looked at more than 350,000 locations across 2,751 brands, found ChatGPT recommends only about 1.2% of local business locations.</p>
<figure style="margin: 28px auto; max-width: 760px;"><img loading="lazy" decoding="async" style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" src="https://leadppc.com/wp-content/uploads/2026/11/chatgpt-business-profiles-franchise-locations-ai-local-search-infographic.png" alt="Infographic: 45% of consumers now use AI to find a local business, up from 6%; ChatGPT recommends about 1.2% of local business locations; Lead PPC has served 500+ franchise brands" width="1200" height="1500" /><figcaption style="font-size: 14px; color: #5c687c; text-align: center; margin-top: 8px;">AI local search grew from 6% to 45% in a year, while ChatGPT names only about 1.2% of locations.</figcaption></figure>
<p>Put those together and you get the opportunity: almost half of customers are asking AI where to go, and very few locations are getting named. ChatGPT also pulls from third parties. OpenAI licensed Yelp&#8217;s reviews, ratings and photos for local answers, and many local SEO practitioners treat Bing Places as a direct input because Bing sits underneath ChatGPT search. The units that get named are the ones whose facts line up everywhere.</p>
<h2>Who Can Claim Today: Franchise Locations, Franchisors, and the Agent Gap</h2>
<p>Eligibility is the part most people get wrong, so check it before you block out an afternoon.</p>
<ul>
<li><strong>Local units:</strong> local businesses, such as stores and restaurants, can currently claim only an existing U.S. listing. If ChatGPT doesn&#8217;t already have a listing for a unit, you can&#8217;t add one yet. Search for each unit; don&#8217;t assume they&#8217;re all there.</li>
<li><strong>The franchisor brand:</strong> an online business with its own website can claim through Business Hub, and online businesses may see an option to add a profile if none exists. The brand site and franchise development site fall here.</li>
<li><strong>Agents:</strong> U.S. ecommerce and online service businesses only at launch. Most franchise service units won&#8217;t get an agent in this beta, so don&#8217;t build plans around one yet.</li>
<li><strong>Holds and refusals:</strong> OpenAI says not every business can create or claim a profile and some categories are on hold. If you see &#8220;Contact support&#8221; instead of verification options, the listing is locked.</li>
</ul>
<p>You must own the business or be authorized to represent it. For a franchise unit, that&#8217;s the franchisee or an employee the franchisee authorizes, not an agency acting on its own.</p>
<h2>How to Claim a ChatGPT Business Profile for Each Unit</h2>
<p>Do this one unit at a time and log it on the same sheet you use for GBP.</p>
<ol>
<li><strong>Open Business Hub</strong> from ChatGPT while signed in with the account you use for work, not a personal one.</li>
<li><strong>Search for the unit</strong> by the exact name and address on its Google Business Profile.</li>
<li><strong>Verify the claim</strong> with one of the methods offered: phone, business email, website domain, or Shopify. For a service unit, the unit&#8217;s own phone or an email on the brand domain is usually the clean path.</li>
<li><strong>Wait for approval.</strong> OpenAI emails its decision or asks for more information.</li>
<li><strong>Complete the Persona ID check.</strong> Claim approval isn&#8217;t the final gate. Approved Persona verification adds the blue check to the profile.</li>
<li><strong>Update the details</strong> so they match the unit&#8217;s GBP exactly: name, address or service area, phone, hours, website URL for that unit, and the services that unit actually delivers.</li>
</ol>
<figure style="margin: 28px auto; max-width: 760px;"><img loading="lazy" decoding="async" style="width: 100%; height: auto; border-radius: 8px; box-shadow: 0 2px 14px rgba(8,30,60,0.15);" src="https://leadppc.com/wp-content/uploads/2026/11/chatgpt-business-profiles-franchise-locations-claim-vs-ignore-infographic.png" alt="Infographic comparing an unclaimed ChatGPT business profile with a claimed, verified one, plus the six steps to claim a franchise unit in Business Hub" width="1200" height="1500" /><figcaption style="font-size: 14px; color: #5c687c; text-align: center; margin-top: 8px;">Unclaimed vs. claimed and verified, and the six steps to claim each unit.</figcaption></figure>
<p>Two mistakes to avoid. Don&#8217;t point every unit at the brand homepage; use the unit&#8217;s location page so ChatGPT and your tracking agree on which unit got the visit. And don&#8217;t invent profiles for units that aren&#8217;t operating yet. The same rule we use for GBP and LSA applies here: one legitimate presence per real operating location.</p>
<h2>Brand Governance: Who Owns the Profile, Corporate or the Unit?</h2>
<p>This is where franchise systems will feel friction first. Corporate wants consistent naming and messaging. The franchisee owns the local truth: hours, phone, service area, and who actually picks up.</p>
<p>The split that works for GBP works here too:</p>
<ul>
<li><strong>Corporate sets the standard:</strong> naming format, approved description language, which services can be listed, and the escalation path if a profile gets locked or claimed by the wrong person.</li>
<li><strong>The unit owns the claim:</strong> the franchisee or an authorized manager verifies and maintains the profile, because they are the one who can prove the phone, the address and the hours.</li>
<li><strong>Write it down:</strong> add ChatGPT profiles to the same access sheet you use for GBP managers, with who verified, which method, and the date.</li>
</ul>
<p>If you&#8217;re a franchisor, send your units a one-page standard this month. If you wait, you&#8217;ll be cleaning up 40 different descriptions next year.</p>
<h2>What Actually Feeds ChatGPT&#8217;s Local Answers</h2>
<p>A claimed profile is your direct line, but ChatGPT still compares it against everything else it can read. Before you claim, run this consistency pass on every unit:</p>
<ul>
<li><strong>Google Business Profile:</strong> the reference record. Category, hours, phone and address must be current.</li>
<li><strong>Yelp:</strong> reviews, ratings and photos now show up inside ChatGPT local answers with Yelp branding.</li>
<li><strong>Bing Places:</strong> free to claim and widely treated as an input to ChatGPT search.</li>
<li><strong>Your unit location page:</strong> crawlable, with the same name, address, phone and hours, plus LocalBusiness schema.</li>
<li><strong>Reviews:</strong> recent, steady reviews on the platforms customers actually use, with responses.</li>
</ul>
<p>Most &#8220;ChatGPT visibility&#8221; problems I see are really name, address and phone drift that nobody fixed on Google, Yelp or the location page.</p>
<h2>Measuring It: Business Hub Insights vs. Calls and Booked Jobs</h2>
<p>Business Hub insights show mentions and clicks, and only when a business clears OpenAI&#8217;s volume thresholds. That&#8217;s useful directional data, not a lead count. Treat it the way you treat GBP views: a signal, not revenue.</p>
<p>What to measure instead:</p>
<ul>
<li>Calls and form fills from the unit&#8217;s location page, tagged so you can see referral traffic from chatgpt.com.</li>
<li>A &#8220;how did you hear about us&#8221; option that includes ChatGPT or AI, asked at booking.</li>
<li>Booked jobs and revenue by unit, so ChatGPT sits next to Search, Maps, LSA and referrals on the same scorecard.</li>
</ul>
<p>If your call tracking isn&#8217;t unit-level yet, fix that first. Our <a href="https://leadppc.com/franchise/multi-unit-franchise-call-tracking/">multi-unit call tracking guide</a> walks through one stack across locations you own.</p>
<h2>A 30-Day Rollout Plan for Multi-Unit Operators</h2>
<table>
<tbody>
<tr>
<th>Week</th>
<th>What to do</th>
<th>Done when</th>
</tr>
<tr>
<td>Week 1</td>
<td>Audit GBP, Yelp, Bing Places and location pages for every unit</td>
<td>Name, address, phone and hours match everywhere</td>
</tr>
<tr>
<td>Week 2</td>
<td>Search every unit in Business Hub and start claims</td>
<td>Each unit is claimed, pending, or logged as &#8220;no listing yet&#8221;</td>
</tr>
<tr>
<td>Week 3</td>
<td>Finish Persona verification and update details</td>
<td>Blue check, unit-specific URL, accurate services</td>
</tr>
<tr>
<td>Week 4</td>
<td>Add ChatGPT to tracking and the access sheet</td>
<td>Referral tagging live and owners recorded</td>
</tr>
</tbody>
</table>
<p>Recheck the units that had no listing once a month. OpenAI says it plans to expand Businesses in ChatGPT and Business Agents to more markets and business categories over time.</p>
<h2>FAQs</h2>
<p><strong>Is a ChatGPT business profile the same as a Google Business Profile?</strong><br />
No. It&#8217;s OpenAI&#8217;s own profile that controls what ChatGPT shows about your business. It&#8217;s free to claim in the beta, but it doesn&#8217;t replace GBP, and your GBP is still the record ChatGPT compares against.</p>
<p><strong>Can I claim ChatGPT business profiles for all my franchise units at once?</strong><br />
Claim them one at a time. Each unit is its own location, and local businesses can currently claim only an existing U.S. listing, so some units may not have a profile yet.</p>
<p><strong>Will a claimed profile get my unit recommended more often?</strong><br />
Not by itself. It makes sure the details are right when ChatGPT does name you. Recommendations still depend on consistent facts across your site, GBP, Yelp, Bing Places and reviews.</p>
<p><strong>Can my franchise unit get a Business Agent?</strong><br />
Probably not yet. At launch, agents are limited to eligible ecommerce and online service businesses in the U.S.</p>
<p><strong>Should corporate or the franchisee claim the unit&#8217;s profile?</strong><br />
Usually the franchisee or an authorized manager, under a written brand standard from corporate. The person who claims it has to be able to verify the unit&#8217;s phone, email or domain.</p>
<p><strong>Does it cost anything?</strong><br />
Claiming a profile and publishing an eligible agent are free at launch. Sponsored placements in ChatGPT are a separate, paid, clearly labeled product.</p>
<h2>Need Help?</h2>
<p>If you would like to speak with us about ChatGPT business profiles for the franchise units you own, alongside your Google Business Profiles, LSA and paid search, please fill out our <a href="https://go.leadppc.com/contact/">Contact Us</a> form.</p>
<p>We can audit every unit&#8217;s listings, set the governance standard with your franchisor, and track ChatGPT next to the rest of your local lead sources.</p>
<p>The post <a href="https://leadppc.com/franchise/chatgpt-business-profiles-franchise-locations/">ChatGPT Business Profiles for Franchise Locations: How to Claim Every Unit Next to Your GBP and LSA</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://leadppc.com/franchise/chatgpt-business-profiles-franchise-locations/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		<enclosure url="https://leadppc.com/wp-content/uploads/2026/11/chatgpt-business-profiles-franchise-locations-video.mp4" length="1227667" type="video/mp4" />

			</item>
		<item>
		<title>Google Ads Account Structure for Multi-Unit Franchisees: MCC vs One Account vs Per-Location</title>
		<link>https://leadppc.com/franchise/multi-unit-franchisee-google-ads-account-structure/</link>
					<comments>https://leadppc.com/franchise/multi-unit-franchisee-google-ads-account-structure/#respond</comments>
		
		<dc:creator><![CDATA[Grant James]]></dc:creator>
		<pubDate>Mon, 28 Sep 2026 12:15:37 +0000</pubDate>
				<category><![CDATA[Franchise]]></category>
		<guid isPermaLink="false">https://leadppc.com/?p=4421</guid>

					<description><![CDATA[<p>One account, an MCC with sub-accounts, or separate accounts per location? How multi-unit franchisees should structure Google Ads around billing, conversion sharing, negatives, and buying or selling units.</p>
<p>The post <a href="https://leadppc.com/franchise/multi-unit-franchisee-google-ads-account-structure/">Google Ads Account Structure for Multi-Unit Franchisees: MCC vs One Account vs Per-Location</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>Google Ads Account Structure for Multi-Unit Franchisees: MCC vs One Account vs Per-Location</h1>
<div id="attachment_4423" class="wp-caption alignnone" style="width: 1290px;"><img loading="lazy" decoding="async" class="size-full wp-image-4423" src="https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchisee-google-ads-account-structure-hero.png" alt="One account or ten? Google Ads account structure for multi-unit franchisees" width="1280" height="720" aria-describedby="caption-attachment-4423" srcset="https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchisee-google-ads-account-structure-hero-200x113.png 200w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchisee-google-ads-account-structure-hero-300x169.png 300w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchisee-google-ads-account-structure-hero-400x225.png 400w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchisee-google-ads-account-structure-hero-600x338.png 600w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchisee-google-ads-account-structure-hero-800x450.png 800w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchisee-google-ads-account-structure-hero-1024x576.png 1024w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchisee-google-ads-account-structure-hero-1200x675.png 1200w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchisee-google-ads-account-structure-hero.png 1280w" sizes="auto, (max-width: 1280px) 100vw, 1280px" /></p>
<p id="caption-attachment-4423" class="wp-caption-text">ONE ACCOUNT OR TEN? GOOGLE ADS STRUCTURE FOR MULTI-UNIT FRANCHISEES</p>
</div>
<div class="key-takeaways" style="border: 1px solid #d9d9d9; border-left: 4px solid #1e73be; background: #f7f9fc; padding: 16px 20px; margin: 24px 0;">
<p><strong>Key Takeaways</strong></p>
<ul>
<li>There are three workable structures: one Google Ads account with campaigns per unit, a manager account (MCC) with sub-accounts, or fully separate accounts. Who pays the invoice, how often units change hands, and how much territories overlap decide which fits.</li>
<li>One account with per-unit campaigns is usually simplest for one owner and one entity running a few units in one metro.</li>
<li>An MCC with sub-accounts wins once units sit in different LLCs, you buy or sell units, or you pass roughly ten locations.</li>
<li>Fully separate accounts with no common manager are the weakest option: duplicated work, fragmented data, and a higher risk of your own ads competing in the same auction.</li>
<li>Your company should own the manager account and hold admin on every unit account. Agencies and franchisors get linked; they don’t own your structure.</li>
<li>Decide structure before the next unit, not after. Restructuring a live account costs history and learning time.</li>
</ul>
</div>
<p>Plenty of multi-unit operators never chose their Google Ads structure; it accumulated. Unit one got an account from the franchisor’s recommended agency, unit two became a campaign in that account, and unit three arrived through a resale with its own account on the seller’s login. A few years later nobody can say which location a conversion belongs to, and nobody can sell a unit without breaking something.</p>
<p>This is the operator version of the decision, for franchisees who own 2 to 20+ units and control their own local spend. It’s about what you own, what you pay for, and what you might sell someday, not how a franchisor structures national brand campaigns. For budgets, geo, and creative once the structure is set, see our <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit franchise advertising</a> playbook.</p>
<p><strong>A note on rules:</strong> Google Ads features, limits, and policies change, and franchise agreements vary. Confirm current specifics in Google’s help center, and check your franchise agreement before you move or link any account your franchisor may have an interest in.</p>
<h2>Why Account Structure Breaks Before Creative Does</h2>
<p>Structure breaks first because every unit you add multiplies the billing, tracking, and access decisions, while the ads themselves barely change. Bad copy costs you some click-through rate. A bad structure costs you the ability to see which unit is profitable, to hand off a unit cleanly, and to stop your own locations from bidding against each other.</p>
<ul>
<li><strong>Reporting blur:</strong> conversions roll up into one number, so you can’t tell which unit’s spend pays for itself.</li>
<li><strong>Billing tangles:</strong> three LLCs share one card, and your bookkeeper splits the invoice by hand.</li>
<li><strong>Auction overlap:</strong> two of your units target the same ZIP codes with the same keywords, and you pay more for your own customers.</li>
<li><strong>Access risk:</strong> a former employee or agency owns the account, so you can’t change users or billing without them.</li>
<li><strong>Transfer paralysis:</strong> you want to sell one unit, but its campaigns share an account and history with units you’re keeping.</li>
</ul>
<p>Better headlines fix none of these. The right structure makes all of them easier.</p>
<h2>The Three Models: One Account, MCC With Sub-Accounts, or Fully Separate Accounts</h2>
<p>You can run all units as campaigns in one Google Ads account, run one sub-account per unit (or per market) under a manager account you own, or run fully separate accounts with no common manager. Each works in some situations. Here’s how they compare.</p>
<table>
<thead>
<tr>
<th>Model</th>
<th>Best fit</th>
<th>Main trade-off</th>
</tr>
</thead>
<tbody>
<tr>
<td>One account, campaigns per unit</td>
<td>One owner and one paying entity, 2–5 units, especially in one metro</td>
<td>One billing setup for everything; selling a single unit means rebuilding its campaigns elsewhere</td>
</tr>
<tr>
<td>MCC with sub-accounts</td>
<td>Units in separate LLCs, active buying and selling, or roughly 10+ units</td>
<td>More setup and more places to check; conversion and negative sharing must be configured on purpose</td>
</tr>
<tr>
<td>Fully separate accounts</td>
<td>Units with different ownership groups, or a short bridge during a sale</td>
<td>No shared negatives or conversions, duplicated work, higher risk of competing in the same auctions</td>
</tr>
</tbody>
</table>
<h3>Model 1: One account with campaigns per unit</h3>
<p>Each unit gets its own campaigns, location targeting, and budget inside one account. Conversion data, audiences, and negatives stay in one place. Keep naming strict (for example, <em>U03 | Metro North | Search | Non-Brand</em>) so reports sort by unit.</p>
<p>The limits: a Google Ads account connects to a single billing setup, so every unit’s spend is paid by one entity. And an account can’t be split, so a sold unit’s campaigns get exported and rebuilt by the buyer.</p>
<h3>Model 2: A manager account with sub-accounts</h3>
<p>A Google Ads manager account (still widely called an MCC) lets you view and manage linked accounts from one login. Each unit, or each cluster of nearby units, gets its own sub-account and billing. Google ties the active-account limit to spend, and even the smallest tier allows 50, far more than a franchisee needs.</p>
<p>For operators, the payoff is that each sub-account can be billed to the entity that owns that unit, negatives and conversion actions can still be shared from the manager, and selling a unit means handing over its sub-account instead of rebuilding it.</p>
<h3>Model 3: Fully separate accounts</h3>
<p>Each unit has its own account with no common manager. You get separation but give up everything shared: negatives, conversion setup, and one view of the business. It’s also the setup most likely to end up with two of your own accounts bidding on the same searches in the same area. Google’s Unfair advantage policy doesn’t allow advertisers to try to show more than one ad for the same business in a single ad location, and separate accounts with overlapping keywords and geos are a common way to drift into that.</p>
<p>Fully separate accounts make sense when the units really are separate businesses, such as different partner groups, or as a temporary state while a unit is being sold. Otherwise, link them under a manager account you control.</p>
<h2>Billing, Conversion Sharing, and Negative Lists Under Each Model</h2>
<p>Billing follows the account, conversion data follows how you set up conversion actions, and negatives follow wherever you build your lists. A manager account is what lets you keep billing separate while sharing the other two.</p>
<p><strong>Billing.</strong> If each unit is its own LLC, your accountant will likely want each unit’s spend billed to that entity, the strongest single argument for sub-accounts. Consolidated billing (one monthly invoice with spend broken out per account) requires a manager account, Google’s monthly invoicing payment setting, and one currency per invoice. Many smaller operators won’t qualify for invoicing, so plan on separate card or bank billing per sub-account.</p>
<p><strong>Conversions.</strong> With cross-account conversion tracking, conversion actions live in the manager and each sub-account uses the manager as its conversion account. Google suggests this when all accounts under the manager belong to the same business, which fits most multi-unit operators. You get one definition of a lead or booked job across units. The trap is doing it halfway, so the same call gets counted under different names in different accounts. It also matters for offline conversion imports: with cross-account tracking on, imports are uploaded at the manager level.</p>
<p><strong>Negatives.</strong> Keep universal negatives (jobs, DIY, free, competitor franchise opportunities, brand-fund campaign terms) in shared lists. In a manager account you build those lists once, they show up in each sub-account’s shared library, and you apply them there. Keep unit-specific negatives, like neighboring towns another unit covers, local to the unit’s campaigns.</p>
<h2>Who Owns the MCC When You Sell or Add a Unit</h2>
<p>Your operating or holding company should own the manager account and hold admin access on every unit’s account. Agencies, consultants, and franchisors get linked or invited as users, and they can come and go without taking your structure with them.</p>
<ul>
<li><strong>Create the manager account and every unit account with company logins you control</strong>, not a personal Gmail or an agency employee’s address. Keep at least two admins from your side.</li>
<li><strong>Link your agency’s manager account, don’t live inside it.</strong> A Google Ads account can be linked directly to up to five manager accounts, so your manager account, your agency’s, and a franchisor’s can all coexist. When the agency leaves, you unlink them and nothing moves.</li>
<li><strong>Know where your franchisor sits.</strong> Some require their manager account linked, or own the local account outright. Read the agreement before relinking anything.</li>
</ul>
<p><strong>When you add a unit</strong>, decide on day one whether it becomes campaigns in an existing account or its own sub-account. For a resale unit, you either link its account into your manager or rebuild; our <a href="https://leadppc.com/franchise/buying-franchise-unit-marketing-handoff/">30-day marketing handoff checklist</a> covers that transition.</p>
<p><strong>When you sell a unit</strong> that has its own sub-account, the buyer’s manager account or login gets admin access, the buyer sets up its own billing, and you unlink after closing. The account’s history goes with it. If the unit only exists as campaigns inside your shared account, you can’t hand over part of an account. Export the campaigns, keywords, negatives, and ads, and let the buyer rebuild. If you expect to sell units, that alone is a reason to give each one its own sub-account now.</p>
<h2>How Structure Interacts With Territory Overlap and Call Tracking</h2>
<p>Structure decides whether you can control overlap and attribution at all. Geo fencing and number routing do the actual work, and those are covered in their own guides, so this section only covers where structure helps or hurts.</p>
<ul>
<li><strong>Territory overlap.</strong> Units in one account can share negatives and exclusions, and you can see both sets of campaigns side by side. Units in separate accounts can’t see each other, so overlap goes unnoticed until you check auction insights. If two units border each other, fence them the way our <a href="https://leadppc.com/franchise/multi-unit-franchise-territory-overlap-ads/">territory overlap playbook</a> describes, whichever structure you use.</li>
<li><strong>Shared metro campaigns.</strong> When several units split one dense metro, one campaign with lead routing can beat several thin per-unit campaigns. That only works inside one account, so group metro clusters instead of forcing one sub-account per unit.</li>
<li><strong>Call tracking.</strong> Your call tracking setup should map each tracking number to one unit and one account. If you run one call tracking stack across units, as we recommend in our <a href="https://leadppc.com/franchise/multi-unit-franchise-call-tracking/">multi-unit call tracking guide</a>, mirror your Google Ads structure in it: same unit IDs, same naming, same account boundaries.</li>
<li><strong>Local Services Ads.</strong> LSA runs separately from Search, but its service areas and budgets should line up with the same unit map. See our <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">LSA operations guide</a>.</li>
</ul>
<h2>Decision Checklist by Unit Count and Who Pays the Invoice</h2>
<p>Start with who pays, then how many units you run, then whether units will change hands. That order settles most cases.</p>
<p><strong>Step 1: Who pays the invoice?</strong></p>
<ul>
<li>One entity pays for all units → one account is on the table.</li>
<li>Each unit, or each group of units, is a separate entity that should carry its own spend → sub-accounts under your manager account.</li>
<li>Different ownership groups (partners, family members, a JV) → separate sub-accounts at minimum, and possibly separate managers if they don’t share control.</li>
</ul>
<p><strong>Step 2: How many units?</strong></p>
<ul>
<li><strong>2–5 units, one metro, one entity:</strong> One account, campaigns per unit, strict naming, shared negatives. Put a manager account above it anyway for clean access.</li>
<li><strong>5–10 units or two or more metros:</strong> A manager account with a sub-account per metro cluster or per entity. Keep adjacent units that share a metro in the same sub-account.</li>
<li><strong>10–20+ units:</strong> A manager account is standard. Use sub-accounts per unit or market, cross-account conversion tracking, manager-level negative lists, and a written naming standard. Look at consolidated billing if you qualify.</li>
</ul>
<p><strong>Step 3: Will units change hands?</strong> If you expect to buy or sell in the next 12–24 months, put each affected unit in its own sub-account now. If the portfolio is stable, optimize for reporting and shared data instead.</p>
<p><strong>Step 4: Check constraints and document.</strong> Confirm franchisor requirements (access, approved agencies, brand-owned accounts) and how your accountant wants spend billed. Then write down account IDs, unit IDs, owners, billing, and linked managers.</p>
<p>Don’t restructure a working account on a whim. Moving campaigns into new accounts resets history and sends Smart Bidding back into learning, so migrate one cluster at a time on a planned date, ideally in a slow season. If lead volume is already stretching your crews, fix capacity first. Our <a href="https://leadppc.com/franchise/franchise-lead-capacity-planning/">lead capacity planning</a> guide explains why spend should never outrun the people who answer and close.</p>
<h2>Frequently Asked Questions</h2>
<h3>Should I use one Google Ads account or one per location?</h3>
<p>If one entity pays for a few units in the same metro, one account with campaigns per unit is usually simpler. If units sit in different LLCs, you plan to buy or sell units, or you run roughly ten or more, use a manager account with a sub-account per unit or market.</p>
<h3>Who should own the MCC when I sell or add a unit?</h3>
<p>Your operating or holding company should own it and keep admin access on every unit account. Agencies and franchisors get linked. When you sell a unit in its own sub-account, the buyer gets admin access, sets up its own billing, and you unlink after closing.</p>
<h3>When is a shared account actually safer than separate ones?</h3>
<p>When your units overlap in one metro, share an owner and entity, and run modest budgets. One account lets you see every campaign together, share negatives and exclusions, pool conversion data for bidding, and avoid entering two of your own ads into the same auction.</p>
<h3>Do separate Google Ads accounts for my units break Google’s policies?</h3>
<p>Not by themselves. Google’s Unfair advantage policy prohibits trying to show more than one ad for the same business in a single ad location, so overlapping keywords and territories across your accounts are the risk. Keep geos distinct and link accounts under one manager so overlap is visible.</p>
<h3>Can my locations share conversion tracking and negative keyword lists?</h3>
<p>Yes, with a manager account. Cross-account conversion tracking lets sub-accounts use conversion actions defined in the manager, and negative keyword lists created in the manager show up in each sub-account’s shared library, where you apply them.</p>
<h3>Can I get one invoice for all my franchise units?</h3>
<p>Only with consolidated billing, which requires a manager account, all accounts linked to one paying manager, Google’s monthly invoicing payment setting, and the same currency across accounts. Otherwise each account is billed on its own, though one payment method can pay for several accounts.</p>
<p><script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Should I use one Google Ads account or one per location?","acceptedAnswer":{"@type":"Answer","text":"If one entity pays for a few units in the same metro, one account with campaigns per unit is usually simpler. If units sit in different LLCs, you plan to buy or sell units, or you run roughly ten or more, use a manager account with a sub-account per unit or market."}},{"@type":"Question","name":"Who should own the MCC when I sell or add a unit?","acceptedAnswer":{"@type":"Answer","text":"Your operating or holding company should own it and keep admin access on every unit account. Agencies and franchisors get linked. When you sell a unit in its own sub-account, the buyer gets admin access, sets up its own billing, and you unlink after closing."}},{"@type":"Question","name":"When is a shared account actually safer than separate ones?","acceptedAnswer":{"@type":"Answer","text":"When your units overlap in one metro, share an owner and entity, and run modest budgets. One account lets you see every campaign together, share negatives and exclusions, pool conversion data for bidding, and avoid entering two of your own ads into the same auction."}},{"@type":"Question","name":"Do separate Google Ads accounts for my units break Google’s policies?","acceptedAnswer":{"@type":"Answer","text":"Not by themselves. Google’s Unfair advantage policy prohibits trying to show more than one ad for the same business in a single ad location, so overlapping keywords and territories across your accounts are the risk. Keep geos distinct and link accounts under one manager so overlap is visible."}},{"@type":"Question","name":"Can my locations share conversion tracking and negative keyword lists?","acceptedAnswer":{"@type":"Answer","text":"Yes, with a manager account. Cross-account conversion tracking lets sub-accounts use conversion actions defined in the manager, and negative keyword lists created in the manager show up in each sub-account’s shared library, where you apply them."}},{"@type":"Question","name":"Can I get one invoice for all my franchise units?","acceptedAnswer":{"@type":"Answer","text":"Only with consolidated billing, which requires a manager account, all accounts linked to one paying manager, Google’s monthly invoicing payment setting, and the same currency across accounts. Otherwise each account is billed on its own, though one payment method can pay for several accounts."}}]}</script></p>
<h2>Need Help?</h2>
<p>If you own several franchise units and want a second set of eyes on your Google Ads structure — one account vs. an MCC, billing by entity, shared negatives and conversions, or getting ready to buy or sell a unit — fill out our <a href="https://go.leadppc.com/contact/">Contact Us</a> form.</p>
<p>We can map what you have today, recommend a structure that fits how you own and pay for your units, and plan the move so you don’t lose conversion history along the way.</p>
<p>The post <a href="https://leadppc.com/franchise/multi-unit-franchisee-google-ads-account-structure/">Google Ads Account Structure for Multi-Unit Franchisees: MCC vs One Account vs Per-Location</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://leadppc.com/franchise/multi-unit-franchisee-google-ads-account-structure/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Buying an Existing Franchise Unit? The 30-Day Marketing Handoff Checklist for Ads, LSA, GBP, and Phone Numbers</title>
		<link>https://leadppc.com/franchise/buying-franchise-unit-marketing-handoff/</link>
					<comments>https://leadppc.com/franchise/buying-franchise-unit-marketing-handoff/#respond</comments>
		
		<dc:creator><![CDATA[Grant James]]></dc:creator>
		<pubDate>Sat, 26 Sep 2026 12:37:34 +0000</pubDate>
				<category><![CDATA[Franchise]]></category>
		<guid isPermaLink="false">https://leadppc.com/?p=4417</guid>

					<description><![CDATA[<p>Buying an Existing Franchise Unit? The 30-Day Marketing Handoff Checklist for Ads, LSA, GBP, and Phone Numbers Buying an existing franchise unit? Use a 30-day marketing handoff so ads, LSA, GBP, and phone numbers keep producing leads. Key Takeaways Inventory every marketing asset before closing: ad accounts, LSA profile, Google Business Profile, tracking numbers, domains, [...]</p>
<p>The post <a href="https://leadppc.com/franchise/buying-franchise-unit-marketing-handoff/">Buying an Existing Franchise Unit? The 30-Day Marketing Handoff Checklist for Ads, LSA, GBP, and Phone Numbers</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>Buying an Existing Franchise Unit? The 30-Day Marketing Handoff Checklist for Ads, LSA, GBP, and Phone Numbers</h1>
<div id="attachment_4418" class="wp-caption alignnone" style="width: 1290px;"><img loading="lazy" decoding="async" class="size-full wp-image-4418" src="https://leadppc.com/wp-content/uploads/2026/09/buying-franchise-unit-marketing-handoff-canva-hero.png" alt="Buying an existing franchise unit: 30-day marketing handoff checklist" width="1280" height="720" aria-describedby="caption-attachment-4418" srcset="https://leadppc.com/wp-content/uploads/2026/09/buying-franchise-unit-marketing-handoff-canva-hero-200x113.png 200w, https://leadppc.com/wp-content/uploads/2026/09/buying-franchise-unit-marketing-handoff-canva-hero-300x169.png 300w, https://leadppc.com/wp-content/uploads/2026/09/buying-franchise-unit-marketing-handoff-canva-hero-400x225.png 400w, https://leadppc.com/wp-content/uploads/2026/09/buying-franchise-unit-marketing-handoff-canva-hero-600x338.png 600w, https://leadppc.com/wp-content/uploads/2026/09/buying-franchise-unit-marketing-handoff-canva-hero-800x450.png 800w, https://leadppc.com/wp-content/uploads/2026/09/buying-franchise-unit-marketing-handoff-canva-hero-1024x576.png 1024w, https://leadppc.com/wp-content/uploads/2026/09/buying-franchise-unit-marketing-handoff-canva-hero-1200x675.png 1200w, https://leadppc.com/wp-content/uploads/2026/09/buying-franchise-unit-marketing-handoff-canva-hero.png 1280w" sizes="auto, (max-width: 1280px) 100vw, 1280px" /></p>
<p id="caption-attachment-4418" class="wp-caption-text">Buying an existing franchise unit? Use a 30-day marketing handoff so ads, LSA, GBP, and phone numbers keep producing leads.</p>
</div>
<div class="key-takeaways" style="border: 1px solid #d9d9d9; border-left: 4px solid #1e73be; background: #f7f9fc; padding: 16px 20px; margin: 24px 0;">
<p><strong>Key Takeaways</strong></p>
<ul>
<li>Inventory every marketing asset before closing: ad accounts, LSA profile, Google Business Profile, tracking numbers, domains, analytics, social pages, and customer data. If it isn’t on the list, assume it won’t transfer.</li>
<li>Find out who actually owns each asset. Many unit-level accounts sit inside a franchisor, agency, or seller manager account, and the seller can’t hand over what they don’t control.</li>
<li>Get admin access added before close and billing switched at close. Expect Google to ask the new entity to re-verify for Local Services Ads and possibly for Google Ads.</li>
<li>Port the phone numbers that matter and use forwarding only as a short, written bridge. Never let the seller cancel a line before the port completes.</li>
<li>Reviews generally stay with an existing Google Business Profile when the same business keeps operating at the same location; ad account history stays with the account, not the person.</li>
<li>Run the handoff as a 30-day checklist with named owners on the buyer, seller, and franchisor side.</li>
</ul>
</div>
<p>Buying an existing franchise unit is supposed to be the shortcut: you get a location that already has customers, a phone that already rings, and reviews that already exist. Then closing day arrives and you find out the Google Ads account belongs to the seller’s agency, the tracking numbers are on the seller’s personal credit card, and nobody knows the Google Business Profile login.</p>
<p>I’ve sold franchise units myself, and I’ve worked with a lot of multi-unit operators who grow through resales and takeovers. The lawyers spend weeks on the purchase agreement, and the marketing handoff gets one line about intangible assets transferring. That line doesn’t port a phone number or change a primary owner on a Business Profile.</p>
<p>This is the operator checklist for the 30 days around a unit acquisition. It pairs with our <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit franchise advertising</a> playbook, which covers budgets and campaign structure once the unit is yours.</p>
<p><strong>A note on rules:</strong> Google policies, porting procedures, and franchise agreements vary and change. Confirm specifics with Google support and your franchisor, and let your attorney handle the purchase agreement.</p>
<h2>What You’re Actually Buying: Inventory the Marketing Assets Before Closing</h2>
<p>You’re buying a set of accounts, listings, numbers, and data, and each one has its own owner and transfer path. Build a written inventory during due diligence so every asset is either transferring, being rebuilt, or knowingly left behind.</p>
<p>Ask the seller for a marketing asset list and verify it yourself. At minimum it should cover:</p>
<table>
<thead>
<tr>
<th>Asset</th>
<th>What to confirm</th>
</tr>
</thead>
<tbody>
<tr>
<td>Google Ads account(s)</td>
<td>Account ID, who holds admin access, which manager account it sits under, payments profile owner, whether it also serves other units the seller keeps</td>
</tr>
<tr>
<td>Local Services Ads profile</td>
<td>Business name, license and insurance on file, who passed background checks, service area, lead history</td>
</tr>
<tr>
<td>Google Business Profile</td>
<td>Primary owner, other owners and managers, whether it’s in a franchisor organization account, review count and response history</td>
</tr>
<tr>
<td>Phone numbers</td>
<td>Main line, tracking numbers, LSA forwarding destination, carrier or provider, account holder, whether each number is portable</td>
</tr>
<tr>
<td>Website and landing pages</td>
<td>Brand-site local page vs. seller-owned domains, registrar and hosting logins, form routing, analytics and tag manager access</td>
</tr>
<tr>
<td>Social and directory profiles</td>
<td>Facebook and Instagram pages, ad accounts in Meta Business Suite, Yelp, Nextdoor, industry directories</td>
</tr>
<tr>
<td>Customer and lead data</td>
<td>CRM or field-service software records, email and SMS lists, call recordings, and who owns them under the franchise agreement</td>
</tr>
</tbody>
</table>
<p>Two questions matter most. First: <strong>who legally controls each asset?</strong> In many systems the franchisor owns the local web page, the Business Profile, or even the ad account, and the seller only had access. Second: <strong>is the asset shared with anything the seller keeps?</strong> If the seller runs three units out of one Google Ads account and is only selling you one, you won’t be taking that account. You’ll be rebuilding.</p>
<p>Also pull several months of reporting before close (search terms, call logs by source, LSA lead history). That’s your baseline, and it’s much harder to get once the seller has moved on.</p>
<h2>Access and Ownership Transfer: Google Ads, LSA, GBP, Call Tracking, and the Website</h2>
<p>Transfer works by getting the buyer added with the highest level of access before closing, then switching billing and removing the seller at or after closing. Each platform has its own mechanics and waiting periods, so start the week the purchase agreement is signed, not the week you take the keys.</p>
<h3>Google Ads</h3>
<p>Google Ads doesn’t have a transfer button. Control comes from admin access plus the payments profile. The usual path is for the seller to invite the buyer’s Google account, or link the buyer’s manager account, with admin access. At closing, the buyer sets up billing under the new entity and the seller’s access is removed.</p>
<ul>
<li>Payments profiles belong to a legal entity. The buyer usually creates a new one; settle the seller’s outstanding balance in the purchase agreement.</li>
<li>Advertiser verification is tied to the business behind the account. If the paying entity changes, expect that Google may ask you to verify again.</li>
<li>If you’re rebuilding instead of inheriting, get an export of campaigns, keywords, negative keywords, and ad copy before the seller’s access ends.</li>
</ul>
<h3>Local Services Ads</h3>
<p>LSA is built on verifying a specific business: its licenses, insurance, and in many categories background checks on the owner and field staff. When the owner and the entity change, plan on re-verification. The license and insurance need to be in the new entity’s name, and the new owner may need to complete checks. Leads can pause while that happens, so start the paperwork early and don’t budget the new unit as if LSA will run uninterrupted. See our <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">LSA operations guide</a> for profile details.</p>
<h3>Google Business Profile</h3>
<p>Only the current primary owner can transfer primary ownership. The buyer is invited as an owner, accepts, and is then made primary owner. Google restricts some actions for newly added users for roughly the first week, so add the buyer well before closing. If the profile lives in your franchisor’s organization account, the franchisor controls it and simply changes whose people have access.</p>
<p>Don’t create a second profile for the same location because you can’t get into the first one. Use Google’s ownership request process or the franchisor instead.</p>
<h3>Call tracking</h3>
<p>Call tracking accounts are usually subscriptions in the seller’s name. The cleanest path is to move the numbers into your existing call tracking account, which is often a port between providers, and rebuild routing there. If you run one stack across units, as we recommend in our <a href="https://leadppc.com/franchise/multi-unit-franchise-call-tracking/">multi-unit franchise call tracking</a> guide, the new unit should come into that stack, not keep its own island.</p>
<h3>Website and landing pages</h3>
<p>If the unit’s web presence is a page on the franchisor’s site, the franchisor updates contact details and form routing. If the seller owns separate domains or landing pages, transfer the domain at the registrar, move or rebuild hosting, and get admin access to Google Analytics and Google Tag Manager. Check where every form sends leads; forms emailing the seller’s inbox after close is a common, expensive oversight.</p>
<h2>Keeping the Phones Ringing: Porting vs. Forwarding</h2>
<p>Port the numbers customers already know, and use call forwarding only as a short bridge while ports complete. Porting gives you permanent control; forwarding leaves the seller holding the line.</p>
<p>In the U.S., most local and toll-free numbers can be ported to a new carrier or provider. The gaining provider runs the port, and it needs a letter of authorization plus details that match the current account exactly: account holder name, service address, account number, and often a PIN. That means the seller has to cooperate, so put the obligation, and a deadline, in the purchase agreement.</p>
<table>
<thead>
<tr>
<th>Option</th>
<th>Use it when</th>
<th>Watch out for</th>
</tr>
</thead>
<tbody>
<tr>
<td>Port the number</td>
<td>Main line, numbers on trucks, signage, GBP, and anything customers have saved</td>
<td>Timelines vary by carrier and number type; mismatched account details cause rejections</td>
</tr>
<tr>
<td>Forward temporarily</td>
<td>Bridging the gap until a port completes</td>
<td>The seller still controls the line and the bill; forwarding can drop if their account lapses</td>
</tr>
<tr>
<td>Replace the number</td>
<td>Tracking numbers used only in ads you’re rebuilding anyway</td>
<td>Every place the old number appears keeps sending calls to the old account</td>
</tr>
</tbody>
</table>
<p>Rules that save deals:</p>
<ul>
<li><strong>Never cancel the old service before the port completes.</strong> Cancelling can release the number, and you may not get it back.</li>
<li>Check your call tracking provider’s terms on porting numbers out. Some numbers are portable and some aren’t.</li>
<li>For LSA, calls typically route through a Google-provided number to a destination number you set, so update the destination as part of re-verification.</li>
</ul>
<h2>Reviews, History, and Reputation: What Carries Over and What Resets</h2>
<p>Assets tied to an account or listing usually carry over with it; things tied to a person or legal entity usually reset. Reviews on an existing Business Profile generally stay, ad account history stays with the account, and verifications tied to the old owner typically have to be redone.</p>
<ul>
<li><strong>Google reviews:</strong> When the same branded business keeps operating at the same location and you take over the existing profile, the reviews stay with it. If the profile is lost or duplicated, they don’t follow you to a new one.</li>
<li><strong>LSA reviews and lead history:</strong> These depend on whether the existing LSA profile continues after re-verification or a new one is created. Ask Google support how your specific change of ownership will be handled.</li>
<li><strong>Google Ads history:</strong> Conversion data and audiences live in the account. Inheriting keeps them; rebuilding means relearning.</li>
<li><strong>Customer data:</strong> Who owns the customer list is usually set by the franchise agreement, and consent for email and SMS marketing may not transfer cleanly to a new entity. Have counsel confirm before you blast the seller’s list.</li>
<li><strong>Reputation:</strong> Bad reviews stay too. Respond as the business, without blaming the prior owner.</li>
</ul>
<p>Don’t change the Business Profile name to your LLC. The name should match the real-world branded business.</p>
<h2>Folding the New Unit Into Your Stack: Geo, Budgets, and the Scoreboard</h2>
<p>Treat the new unit like any other unit you own: same definitions, same CRM fields, same weekly scoreboard, with its own geo, numbers, and budget line. The first job is making sure it doesn’t overlap or cannibalize the units you already run.</p>
<ul>
<li><strong>Geo:</strong> Map the new territory against your existing ones. If they border each other, set location targeting and negatives so two of your own units aren’t bidding against each other in the same ZIP codes. Our <a href="https://leadppc.com/franchise/multi-unit-franchise-territory-overlap-ads/">territory overlap guide</a> walks through this.</li>
<li><strong>Budgets:</strong> Start with a floor budget based on the seller’s history and your cost per booked job in similar units; add flex budget once you have a few weeks of clean data.</li>
<li><strong>Scoreboard:</strong> Add the unit as a row on your weekly scoreboard: qualified calls, answer rate, booked jobs, and cost per booked job by channel. Compare it to the seller’s baseline, not to your best unit.</li>
<li><strong>Staff:</strong> Train whoever answers the phone on your intake script and dispositions.</li>
</ul>
<h2>The 30-Day Handoff Checklist: Buyer, Seller, and Franchisor Roles</h2>
<p>A clean handoff runs on a dated checklist with one named owner per task on the buyer, seller, and franchisor side. Start before closing and keep going for 30 days after.</p>
<p><strong>Before closing (buyer and seller)</strong></p>
<ul>
<li>Buyer: complete the asset inventory and confirm who controls each item.</li>
<li>Seller: add the buyer as admin or owner on Google Ads, GBP, analytics, tag manager, social pages, and call tracking.</li>
<li>Seller: provide carrier account details and sign letters of authorization for porting.</li>
<li>Both: put transfer obligations, deadlines, and a forwarding bridge in the purchase agreement.</li>
<li>Buyer: pull baseline reports and exports.</li>
</ul>
<p><strong>Days 1–7 (buyer leads)</strong></p>
<ul>
<li>Switch Google Ads billing to your payments profile and complete any verification Google requests.</li>
<li>Submit port requests; confirm forwarding is live on every number in the meantime.</li>
<li>Start LSA re-verification with the new entity’s license and insurance.</li>
<li>Update form routing, CRM user access, and voicemail.</li>
<li>Franchisor: approve the transfer in its systems, update the brand-site location page, and change GBP access if it holds the profile.</li>
</ul>
<p><strong>Days 8–14</strong></p>
<ul>
<li>Transfer GBP primary ownership once Google allows it; remove the seller.</li>
<li>Move tracking numbers into your call tracking account and rebuild routing.</li>
<li>Set geo targeting and negatives against your neighboring units.</li>
<li>Test-call every number.</li>
</ul>
<p><strong>Days 15–30</strong></p>
<ul>
<li>Confirm all ports completed; seller can then cancel old services.</li>
<li>Remove seller access everywhere and cancel or reassign seller-billed tools.</li>
<li>Add the unit to the weekly scoreboard and compare against baseline.</li>
<li>Franchisor: confirm the unit meets brand standards for listings and local marketing.</li>
</ul>
<h2>Frequently Asked Questions</h2>
<h3>Does a Google Ads account transfer when you buy a franchise unit?</h3>
<p>There’s no transfer button. The seller adds the buyer as an admin or links the buyer’s manager account, the buyer sets up a new payments profile under the new entity, and the seller’s access is removed. If the account belongs to an agency or franchisor, or serves units the seller keeps, plan to rebuild instead.</p>
<h3>Do Local Services Ads need to be re-verified after a change of ownership?</h3>
<p>Usually, yes. LSA verification is tied to the business’s licenses, insurance, and in many categories background checks, so a new owner and entity typically means updated documents and checks. Leads can pause during that process, so start early and confirm details with Google support.</p>
<h3>How do I take over the Google Business Profile for a unit I’m buying?</h3>
<p>The current primary owner invites you as an owner, you accept, and they make you primary owner. Google restricts some actions for newly added users for roughly the first week, so do this before closing. If the franchisor holds the profile in its organization account, work through the franchisor.</p>
<h3>Do Google reviews stay with the business after a franchise resale?</h3>
<p>Generally, yes, when the same branded business keeps operating at the same location and you take over the existing profile. Reviews don’t follow you to a new or duplicate profile, so protect access to the original listing.</p>
<h3>Should I port the seller’s phone numbers or just forward them?</h3>
<p>Port the numbers customers know, such as the main line and numbers on vehicles, signage, and listings. Use forwarding only as a short, written bridge while ports complete, because the seller still controls a forwarded line.</p>
<h3>What does the seller need to provide to port phone numbers?</h3>
<p>The gaining carrier typically needs a signed letter of authorization and account details that match the current account exactly, including the account holder name, service address, account number, and often a PIN. The seller must not cancel the service before the port finishes.</p>
<h3>Who owns the customer list when you buy a franchise unit?</h3>
<p>It depends on the franchise agreement and the purchase agreement. Many franchise agreements give the franchisor ownership of customer data, and marketing consent may not transfer cleanly to a new entity, so have counsel confirm before using the list.</p>
<h3>How long does a franchise marketing handoff take?</h3>
<p>Plan on about 30 days, starting before closing. Access changes can happen in days, while phone ports, LSA re-verification, and Business Profile ownership changes can take longer depending on the carrier, category, and account.</p>
<p><script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Does a Google Ads account transfer when you buy a franchise unit?","acceptedAnswer":{"@type":"Answer","text":"There’s no transfer button. The seller adds the buyer as an admin or links the buyer’s manager account, the buyer sets up a new payments profile under the new entity, and the seller’s access is removed. If the account belongs to an agency or franchisor, or serves units the seller keeps, plan to rebuild instead."}},{"@type":"Question","name":"Do Local Services Ads need to be re-verified after a change of ownership?","acceptedAnswer":{"@type":"Answer","text":"Usually, yes. LSA verification is tied to the business’s licenses, insurance, and in many categories background checks, so a new owner and entity typically means updated documents and checks. Leads can pause during that process, so start early and confirm details with Google support."}},{"@type":"Question","name":"How do I take over the Google Business Profile for a unit I’m buying?","acceptedAnswer":{"@type":"Answer","text":"The current primary owner invites you as an owner, you accept, and they make you primary owner. Google restricts some actions for newly added users for roughly the first week, so do this before closing. If the franchisor holds the profile in its organization account, work through the franchisor."}},{"@type":"Question","name":"Do Google reviews stay with the business after a franchise resale?","acceptedAnswer":{"@type":"Answer","text":"Generally, yes, when the same branded business keeps operating at the same location and you take over the existing profile. Reviews don’t follow you to a new or duplicate profile, so protect access to the original listing."}},{"@type":"Question","name":"Should I port the seller’s phone numbers or just forward them?","acceptedAnswer":{"@type":"Answer","text":"Port the numbers customers know, such as the main line and numbers on vehicles, signage, and listings. Use forwarding only as a short, written bridge while ports complete, because the seller still controls a forwarded line."}},{"@type":"Question","name":"What does the seller need to provide to port phone numbers?","acceptedAnswer":{"@type":"Answer","text":"The gaining carrier typically needs a signed letter of authorization and account details that match the current account exactly, including the account holder name, service address, account number, and often a PIN. The seller must not cancel the service before the port finishes."}},{"@type":"Question","name":"Who owns the customer list when you buy a franchise unit?","acceptedAnswer":{"@type":"Answer","text":"It depends on the franchise agreement and the purchase agreement. Many franchise agreements give the franchisor ownership of customer data, and marketing consent may not transfer cleanly to a new entity, so have counsel confirm before using the list."}},{"@type":"Question","name":"How long does a franchise marketing handoff take?","acceptedAnswer":{"@type":"Answer","text":"Plan on about 30 days, starting before closing. Access changes can happen in days, while phone ports, LSA re-verification, and Business Profile ownership changes can take longer depending on the carrier, category, and account."}}]}</script></p>
<h2>Need Help?</h2>
<p>If you’re buying or taking over a franchise unit and want a second set of eyes on the marketing handoff — ad accounts, LSA, Business Profiles, tracking numbers, or folding the new unit into your scoreboard — fill out our <a href="https://go.leadppc.com/contact/">Contact Us</a> form.</p>
<p>We can help you inventory what you’re buying, keep the phones ringing through closing, and get the new unit reporting the same way as the rest of your locations.</p>
<p>The post <a href="https://leadppc.com/franchise/buying-franchise-unit-marketing-handoff/">Buying an Existing Franchise Unit? The 30-Day Marketing Handoff Checklist for Ads, LSA, GBP, and Phone Numbers</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://leadppc.com/franchise/buying-franchise-unit-marketing-handoff/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>When Two Units You Own Compete in the Same Zips: A Multi-Unit Geo Playbook</title>
		<link>https://leadppc.com/franchise/multi-unit-franchise-territory-overlap-ads/</link>
					<comments>https://leadppc.com/franchise/multi-unit-franchise-territory-overlap-ads/#respond</comments>
		
		<dc:creator><![CDATA[Grant James]]></dc:creator>
		<pubDate>Fri, 25 Sep 2026 11:47:32 +0000</pubDate>
				<category><![CDATA[Franchise]]></category>
		<guid isPermaLink="false">https://leadppc.com/?p=4398</guid>

					<description><![CDATA[<p>When Two Units You Own Compete in the Same Zips: A Multi-Unit Geo Playbook Multi-unit geo playbook — radius and ZIP fencing when two units you own compete in the same zips. Key Takeaways If two units you own target the same ZIPs with the same keywords, you are likely bidding against yourself and paying [...]</p>
<p>The post <a href="https://leadppc.com/franchise/multi-unit-franchise-territory-overlap-ads/">When Two Units You Own Compete in the Same Zips: A Multi-Unit Geo Playbook</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>When Two Units You Own Compete in the Same Zips: A Multi-Unit Geo Playbook</h1>
<div id="attachment_4411" class="wp-caption alignnone" style="width: 1290px;"><img loading="lazy" decoding="async" class="size-full wp-image-4411" src="https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-territory-overlap-canva-hero.png" alt="Two franchise units you own competing in the same zip codes" width="1280" height="720" aria-describedby="caption-attachment-4403" srcset="https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-territory-overlap-canva-hero-200x113.png 200w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-territory-overlap-canva-hero-300x169.png 300w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-territory-overlap-canva-hero-400x225.png 400w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-territory-overlap-canva-hero-600x338.png 600w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-territory-overlap-canva-hero-800x450.png 800w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-territory-overlap-canva-hero-1024x576.png 1024w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-territory-overlap-canva-hero-1200x675.png 1200w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-territory-overlap-canva-hero.png 1280w" sizes="auto, (max-width: 1280px) 100vw, 1280px" /></p>
<p id="caption-attachment-4403" class="wp-caption-text">Multi-unit geo playbook — radius and ZIP fencing when two units you own compete in the same zips.</p>
</div>
<div class="key-takeaways" style="border: 1px solid #d9d9d9; border-left: 4px solid #1e73be; background: #f7f9fc; padding: 16px 20px; margin: 24px 0;">
<p><strong>Key Takeaways</strong></p>
<ul>
<li>If two units you own target the same ZIPs with the same keywords, you are likely bidding against yourself and paying more for the same customers.</li>
<li>Confirm the problem first with location reports, auction insights, and CRM duplicates in the seam ZIPs between units.</li>
<li>The practical default is an exclusive core for each unit plus a written rule for seam ZIPs, with the other unit’s core excluded from non-brand campaigns.</li>
<li>Use ZIP or polygon targeting in dense metros; radius targets overlap by design.</li>
<li>Align LSA service areas to the same map as your Google Ads geos so you don’t pay twice for one household.</li>
<li>Write a one-page lead ownership policy and check your franchise agreement before advertising into another unit’s territory, even one you own.</li>
</ul>
</div>
<p>If you own two (or five) franchise units that sit near each other, Google will happily let both of them bid into the same household. That isn’t “market share.” That’s you paying twice for one customer — and then arguing about who “owns” the lead.</p>
<p>I’ve sold franchise units myself and I’ve cleaned up a lot of multi-unit Google Ads and LSA setups where Unit A and Unit B were quietly taxing the same ZIPs. This playbook is <strong>only</strong> about that problem: radius and ZIP fencing, exclusive vs intentional overlap, brand vs non-brand geo splits, shared negatives, LSA/Ads double-tax, and internal lead-ownership rules.</p>
<p>For account structure, budget floors, creative, and brand-fund mechanics, use <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit franchise advertising</a> — don’t rebuild that overview here. For LSA ops across several locations (profiles, disputes, budgets), see <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">Google LSA operations for several locations</a>. This article is the <strong>geo conflict</strong> slice: how to stop your own units from competing in the same auction for the same household.</p>
<p>Audience note: this is <strong>multi-unit franchisee</strong> customer-demand geo — not franchisor development capacity. If you’re matching franchise <em>buyer</em> lead volume to closers, that’s a different desk (<a href="https://leadppc.com/franchise/franchise-lead-capacity-planning/">franchise lead capacity planning</a>).</p>
<h2>Diagnosing Self-Competition Before You Touch a Fence</h2>
<p>Your units are competing if both target the same keywords in overlapping locations and you see rising CPCs, your own ads in auction insights, or CRM duplicates in the ZIPs between them. Confirm it with data before redrawing any maps.</p>
<p>Don’t redraw maps until you’ve proven the tax is real.</p>
<p><strong>Signals I look for when two of your units share a metro:</strong></p>
<ol>
<li><strong>Same keywords, overlapping location targets</strong> in two campaigns (or two accounts) — classic auction self-competition.</li>
<li><strong>Impression share / auction insights</strong> that keep surfacing your other unit’s ads as “competitors.”</li>
<li><strong>Call or form volume that spikes in the seam ZIPs</strong> while both units’ CPCs climb.</li>
<li><strong>CRM duplicates</strong> — same phone or address credited to Unit A and Unit B within days.</li>
<li><strong>LSA leads and Google Ads leads</strong> for the same household in the same week (double-tax across products).</li>
</ol>
<p>Separate four problems that operators mash into one bad phrase:</p>
<table>
<thead>
<tr>
<th>Problem</th>
<th>What it actually is</th>
</tr>
</thead>
<tbody>
<tr>
<td>Auction self-competition</td>
<td>Two of <em>your</em> campaigns bidding the same intent into overlapping geo</td>
</tr>
<tr>
<td>Territory compliance</td>
<td>Agreement limits on where you may advertise (even between units you own)</td>
</tr>
<tr>
<td>Attribution ambiguity</td>
<td>Same household, two tracking numbers, unclear credit</td>
</tr>
<tr>
<td>Operational fit</td>
<td>Drive time / staffing decide which unit should fulfill — media should follow that</td>
</tr>
</tbody>
</table>
<p>A customer walking into Unit B instead of Unit A is still <strong>your</strong> customer. What you fix is the auction tax and the ownership fight — not “cannibalization” as a vague brand fear.</p>
<p><strong>Quick diagnostic checklist (one afternoon):</strong></p>
<ul>
<li>Export location reports (or ZIP performance) for both units for 30–60 days.</li>
<li>Highlight ZIPs where <strong>both</strong> spend and both convert.</li>
<li>Pull auction insights / search terms for shared brand and non-brand queries.</li>
<li>Count CRM duplicates and “wrong unit answered” tickets in the seam.</li>
<li>Confirm whether LSA service areas overlap the same seam ZIPs as Ads.</li>
</ul>
<p>If the seam is thin and CPC is stable, you may not need a hard exclusive fence. If the seam is fat and you’re double-paying, fence first — creative later.</p>
<h2>Radius and ZIP Fencing Rules That Actually Hold</h2>
<p>Give each unit an exclusive core of ZIPs or a polygon, exclude the other unit’s core from non-brand campaigns, and write down a rule for the seam. In dense metros, ZIP or polygon targets hold better than radius.</p>
<p>Quick terminology: most operators need <strong>geo-targeting</strong> (radius, ZIP, city, polygon, location exclusions). <strong>Geofencing</strong> usually means ads to devices that enter a drawn polygon (often a competitor storefront). Useful sometimes. Not your default tool for splitting two units you own.</p>
<p><strong>Rules I use when fencing adjacent units:</strong></p>
<ol>
<li><strong>Map the agreement first.</strong> Advertising territory ≠ delivery territory ≠ “wherever Google thinks people search.” Confirm with your franchisor in writing where Unit A may advertise vs Unit B.</li>
<li><strong>Prefer ZIP or polygon over pure radius in dense metros.</strong> Circles overlap by design. Territory lines usually don’t.</li>
<li><strong>Core vs halo.</strong> Give each unit a <strong>core</strong> (exclusive ZIPs / tight polygon) and a controlled <strong>halo</strong> (shared or intentional overlap) if you want intentional competition for overflow.</li>
<li><strong>Exclusions beat hope.</strong> Explicitly exclude the other unit’s core from Unit A’s non-brand campaigns. Hoping Smart Bidding “figures it out” is how you keep paying twice.</li>
<li><strong>Match presence, not ego.</strong> If Unit A’s GBP, landing page, and phone all say one address, don’t let Unit B’s ads own that ZIP without a routing plan.</li>
<li><strong>Revisit after every unit open / remodel / hours change.</strong> Fences rot when operations change and media doesn’t.</li>
</ol>
<table>
<thead>
<tr>
<th>Fence type</th>
<th>Best when</th>
<th>Watch-outs</th>
</tr>
</thead>
<tbody>
<tr>
<td>Radius</td>
<td>Rural / clear drive-time bubbles</td>
<td>Circles overlap in suburbs</td>
</tr>
<tr>
<td>ZIP lists</td>
<td>Agreement is ZIP-defined</td>
<td>Seam ZIPs still need a rule</td>
</tr>
<tr>
<td>Polygon</td>
<td>Odd-shaped territories</td>
<td>Maintenance cost; keep a source-of-truth map</td>
</tr>
<tr>
<td>Location exclusions</td>
<td>You own both sides of the seam</td>
<td>Miss an exclusion and self-competition returns</td>
</tr>
</tbody>
</table>
<p><strong>Practical default for two nearby units you own:</strong> exclusive cores + documented seam rule (exclusive to closer unit, or intentional shared with ownership rules below). Don’t leave the seam undefined.</p>
<h2>Exclusive Geos vs Intentional Overlap — When Each Wins</h2>
<p>Exclusive geos win when the agreement requires them, when both units are busy, or when you see frequent double credits. Intentional overlap works only when one unit needs overflow help and there is a written routing and credit rule.</p>
<p>Not every overlap is a mistake. Some are a strategy.</p>
<p><strong>Force exclusive geos when:</strong></p>
<ul>
<li>The agreement forbids advertising into the other territory (even if you own both).</li>
<li>Both units are at capacity and you’re burning cash on CPC inflation.</li>
<li>CRM shows frequent same-household double credits and staff fights.</li>
<li>Brand terms are expensive and both units are bidding them into the same ZIPs.</li>
<li>Drive time clearly favors one unit for a ZIP (15 minutes vs 40).</li>
</ul>
<p><strong>Allow intentional overlap when:</strong></p>
<ul>
<li>One unit is capacity-constrained and the other can take overflow <strong>with a written routing rule</strong>.</li>
<li>You’re testing a shared-metro brand campaign with unit-level routing after the click/call.</li>
<li>The seam ZIP is low volume and fencing cost (missed demand) exceeds auction tax.</li>
<li>Corporate requires a DMA-level brand presence and local units split fulfillment downstream.</li>
</ul>
<table>
<thead>
<tr>
<th>Situation</th>
<th>Default geo stance</th>
</tr>
</thead>
<tbody>
<tr>
<td>Dense metro, two stores 10–20 min apart, both healthy</td>
<td>Exclusive cores + thin intentional halo OR exclusive everything</td>
</tr>
<tr>
<td>One unit new / ramping, one mature</td>
<td>Protect mature core; let new unit own its core; shared halo only with routing</td>
</tr>
<tr>
<td>Units 40+ minutes apart</td>
<td>Per-unit exclusive geos — overlap rarely worth it</td>
</tr>
<tr>
<td>Agreement says “no advertising into Unit B territory”</td>
<td>Exclusive — period</td>
</tr>
</tbody>
</table>
<p>Write the decision down. “We’ll just see who converts” is how both managers claim the same lead and neither fixes the fence.</p>
<h2>Brand vs Non-Brand Geo Splits</h2>
<p>Brand and non-brand should not share the same geo logic.</p>
<p><strong>Brand (your franchise name / unit name variants):</strong></p>
<ul>
<li>Often belongs in a <strong>tighter geo</strong> — people searching the brand already know you; don’t spray brand bids into a ZIP you can’t serve well.</li>
<li>If corporate runs national brand, confirm whether local units may bid brand at all.</li>
<li>When two of your units bid brand into the same ZIP, you are almost always overpaying for navigational demand.</li>
</ul>
<p><strong>Non-brand (category / service / “near me” intent):</strong></p>
<ul>
<li>This is where self-competition hurts most: generic intent + overlapping radius = pure auction tax.</li>
<li>Fence non-brand aggressively by core ZIP / polygon.</li>
<li>Shared negatives (next section) matter more here than on brand.</li>
</ul>
<table>
<thead>
<tr>
<th>Campaign type</th>
<th>Geo stance I default to</th>
</tr>
</thead>
<tbody>
<tr>
<td>Brand — Unit A</td>
<td>Unit A core (+ tiny halo if intentional)</td>
</tr>
<tr>
<td>Brand — Unit B</td>
<td>Unit B core</td>
</tr>
<tr>
<td>Non-brand — Unit A</td>
<td>Unit A core; exclude Unit B core</td>
</tr>
<tr>
<td>Non-brand — Unit B</td>
<td>Unit B core; exclude Unit A core</td>
</tr>
<tr>
<td>Shared brand (rare, intentional)</td>
<td>Metro/halo with <strong>post-click unit routing</strong> and one-lead/one-credit</td>
</tr>
</tbody>
</table>
<p>If you must run a shared brand campaign across units you own, pair it with per-unit phones / landing paths and an ownership rule. A blended brand campaign with two managers and no routing is a dispute factory.</p>
<h2>Shared Negative Lists (And What Must Stay Unit-Local)</h2>
<p>Consolidate what benefits from shared volume. Separate what is locally determined. Negatives are usually <strong>shared</strong>; geos and budgets stay <strong>per unit</strong>.</p>
<p><strong>Share across units (one maintained list):</strong></p>
<ul>
<li>Junk intent (jobs, DIY, wholesale, competitor brand names you’re not allowed to bid, irrelevant services).</li>
<li>Franchisee-vs-franchisor confusion terms if your category attracts “buy a franchise” searches you don’t want on local customer campaigns.</li>
<li>Misspellings and known money-wasters discovered in any unit’s search terms.</li>
</ul>
<p><strong>Keep unit-local:</strong></p>
<ul>
<li>Geo exclusions tied to the other unit’s core.</li>
<li>Local competitor names that only matter near one store.</li>
<li>Offer / service negatives that only one unit doesn’t sell.</li>
</ul>
<p><strong>Operating habit:</strong> one owner updates the shared negative sheet weekly from all units’ search-term exports. Five managers editing five copies is how Unit A blocks a term Unit B still burns money on.</p>
<p>For the broader consolidate-vs-separate matrix (budgets, creative, tracking), stay on the <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit advertising playbook</a> — here we only care that <strong>shared negatives + exclusive cores</strong> kill most self-competition without rebuilding the whole account.</p>
<h2>LSA and Google Ads Double-Tax on the Same Household</h2>
<p>Local Services Ads and Google Ads can both charge you for demand from the same ZIP — and if two of your units both run LSAs into that ZIP, you can pay <strong>three</strong> ways for one household.</p>
<p>This section is <strong>not</strong> full LSA setup. For multi-location LSA operations, use the <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">LSA several-locations guide</a>. Here we only cover geo / lead-ownership collision with Ads.</p>
<p><strong>Double-tax patterns I see:</strong></p>
<ol>
<li>Unit A Ads + Unit A LSA covering the same core (sometimes fine if you measure incremental; often not).</li>
<li>Unit A Ads + Unit B LSA covering the seam ZIP (classic cross-unit tax).</li>
<li>Both units’ LSAs with overlapping service areas and no lead-ownership rule.</li>
</ol>
<p><strong>Geo rules that reduce the tax:</strong></p>
<ul>
<li>Align LSA service areas to the <strong>same cores</strong> you use in Ads — don’t let LSA stay “loose” while Ads are fenced.</li>
<li>If Ads owns a ZIP exclusively for Unit A, Unit B’s LSA shouldn’t casually cover it unless overflow is intentional and credited once.</li>
<li>When a household generates both an LSA lead and an Ads call, apply <strong>one-lead / one-credit</strong> (below) — don’t let both dashboards celebrate.</li>
</ul>
<table>
<thead>
<tr>
<th>Channel combo</th>
<th>Risk</th>
<th>Move</th>
</tr>
</thead>
<tbody>
<tr>
<td>Ads Unit A + LSA Unit A, same core</td>
<td>Product double-tax</td>
<td>Measure incrementality; tighten one if CPA stacks</td>
</tr>
<tr>
<td>Ads Unit A + LSA Unit B, shared ZIP</td>
<td>Cross-unit double-tax</td>
<td>Fence LSA or Ads; fix ownership</td>
</tr>
<tr>
<td>LSA Unit A + LSA Unit B overlap</td>
<td>Self-competition inside LSA</td>
<td>Exclusive service areas or written overflow</td>
</tr>
</tbody>
</table>
<h2>Internal Lead Ownership Rules (Who Gets the Lead)</h2>
<p>Decide who owns a lead before it arrives: ZIP-based ownership for cores, first valid contact for seam ZIPs, and one credit per household. Put those rules in the CRM as required fields.</p>
<p>Media fences fail if the phone tree and CRM still fight.</p>
<p><strong>Write a one-page ownership policy.</strong> Example rules that work in practice:</p>
<ol>
<li><strong>Geo-first:</strong> Lead’s ZIP in Unit A core → Unit A credit and fulfillment (unless Unit A is closed / over capacity).</li>
<li><strong>First valid contact:</strong> If seam ZIP and intentional overlap, first unit to answer on SLA keeps it — other unit does not re-dial the same day to “steal.”</li>
<li><strong>One-lead / one-credit:</strong> Same phone/email within 30 days = one owner. Second unit can assist fulfillment only with a transfer note — not a second marketing credit.</li>
<li><strong>Channel priority (optional):</strong> If LSA and Ads both fire, pick a primary credit channel for reporting so you don’t optimize two CPAs for one job.</li>
<li><strong>Capacity override:</strong> If Unit A is red on answer rate / bookable slots, seam leads route to Unit B <strong>and</strong> Unit A’s fence or budget throttles until green.</li>
</ol>
<table>
<thead>
<tr>
<th>Scenario</th>
<th>Owner</th>
</tr>
</thead>
<tbody>
<tr>
<td>ZIP in Unit A exclusive core</td>
<td>Unit A</td>
</tr>
<tr>
<td>ZIP in Unit B exclusive core</td>
<td>Unit B</td>
</tr>
<tr>
<td>Seam ZIP, Unit A answered first on SLA</td>
<td>Unit A</td>
</tr>
<tr>
<td>Seam ZIP, Unit A missed SLA, Unit B booked</td>
<td>Unit B (note the miss — fix staffing, not the fence alone)</td>
</tr>
<tr>
<td>Duplicate form + call same day</td>
<td>First qualified contact’s unit</td>
</tr>
</tbody>
</table>
<p>Put the policy in the CRM as a required field: <code>credited_unit</code>, <code>fulfillment_unit</code>, <code>seam_flag</code>. Dashboards without those fields will keep starting arguments in the Monday meeting.</p>
<h2>Weekly Geo Scoreboard</h2>
<p>Track core and seam ZIPs separately every week, along with duplicate rate and LSA and Ads overlap. That shows whether the seam is costing you or earning you money.</p>
<p>If your weekly meeting is only CPL by unit, you’ll miss the seam tax.</p>
<p><strong>One-page geo scoreboard:</strong></p>
<table>
<thead>
<tr>
<th>Metric</th>
<th>Why it matters</th>
</tr>
</thead>
<tbody>
<tr>
<td>Spend + conv in exclusive cores (A vs B)</td>
<td>Are cores healthy?</td>
</tr>
<tr>
<td>Spend + conv in seam ZIPs</td>
<td>Is the tax / opportunity concentrated?</td>
</tr>
<tr>
<td>% of seam leads with clear credited_unit</td>
<td>Ownership discipline</td>
</tr>
<tr>
<td>Duplicate rate (same phone/email, both units, 30 days)</td>
<td>Self-competition residue</td>
</tr>
<tr>
<td>Avg CPC brand vs non-brand in seam vs core</td>
<td>Auction inflation signal</td>
</tr>
<tr>
<td>LSA leads from ZIPs also paying in Ads</td>
<td>Cross-product double-tax</td>
</tr>
<tr>
<td>Answer / book rate by unit in seam</td>
<td>Capacity vs media mismatch</td>
</tr>
</tbody>
</table>
<p><strong>How to use it:</strong></p>
<ul>
<li>Seam spend up + duplicates up → tighten exclusions or ownership SLA.</li>
<li>Core healthy, seam thin → stop obsessing; protect cores.</li>
<li>Seam converting but one unit never answers → route + capacity fix before more budget.</li>
<li>LSA + Ads both fat in same ZIP with flat total jobs → cut one product’s geo, not “more creative.”</li>
</ul>
<p>Owners: media owns fences and exclusions; ops owns answer SLA and credited_unit; whoever owns LSA owns service-area alignment to the same map.</p>
<h2>Pitfalls That Keep You Paying Twice</h2>
<ol>
<li><strong>Radius-only maps in a ZIP-defined agreement.</strong> Circles ignore the contract and each other.</li>
<li><strong>Two accounts, same keywords, soft geos.</strong> Double-serving risk plus self-competition — fix overlap before you scale.</li>
<li><strong>Shared budget, separate egos.</strong> Floor-and-flex is fine; undocumented seam fighting is not.</li>
<li><strong>Brand campaigns left unfenced</strong> while non-brand gets all the attention — navigational CPCs quietly inflate.</li>
<li><strong>LSA service areas never updated</strong> after Ads fences change.</li>
<li><strong>No CRM credited_unit field</strong> — every dashboard lies differently.</li>
<li><strong>“Temporary” overlap</strong> that lasts nine months because nobody owns the map file.</li>
<li><strong>Copying Unit A’s campaign and only changing the radius by two miles</strong> — exclusions and negatives don’t magically follow.</li>
<li><strong>Solving a staffing miss with more overlap</strong> — if Unit A can’t answer, throttle Unit A; don’t just let Unit B bid harder into A’s core without a policy.</li>
<li><strong>Rewriting the whole multi-unit advertising stack</strong> when you only needed a seam rule — keep structure docs on the <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit advertising</a> page and keep this page about geos and ownership.</li>
</ol>
<h2>Frequently Asked Questions</h2>
<h3>How can I tell if my own franchise units are bidding against each other?</h3>
<p>Look for the same keywords targeted in overlapping locations across two campaigns or accounts. Auction insights showing your other unit as a competitor, rising CPCs in the ZIPs between units, and the same household credited to both units in the CRM are strong signs. Pull 30–60 days of location data for both units to confirm.</p>
<h3>Should my units share one Google Ads campaign or have separate campaigns?</h3>
<p>Most operators do better with separate campaigns per unit, each targeting its own core and excluding the other unit’s core. Share negative keyword lists across units, but keep geos and budgets per unit. A shared campaign can work for brand terms only if calls and forms route to the right unit after the click.</p>
<h3>Is radius or ZIP code targeting better for overlapping franchise territories?</h3>
<p>In dense metros, ZIP or polygon targeting is usually better because radius circles overlap by design and rarely match territory lines. Radius works in rural areas where drive-time bubbles are clear. If your agreement defines territory by ZIP, target by ZIP.</p>
<h3>How do I split Local Services Ads service areas between units I own?</h3>
<p>Match each unit’s LSA service area to the same core ZIPs you use in Google Ads. Avoid letting two units’ service areas overlap unless one is intentionally taking overflow under a written rule. Review LSA service areas whenever you change your Ads geos.</p>
<h3>What should I do when a lead comes in from a ZIP on the border between two units?</h3>
<p>Follow a written seam rule instead of deciding case by case. A common approach is that the first unit to make valid contact within your response-time standard keeps the lead, and the other unit doesn’t call the same customer. Record a seam flag and a single credited unit so the lead isn’t counted twice.</p>
<h3>Do franchise agreements restrict advertising between units I own?</h3>
<p>Often they do, even when you own both units. Advertising territory can differ from delivery territory, and some agreements limit where each unit may advertise. Check your FDD and franchise agreement, and confirm with your franchisor in writing before setting up overlap.</p>
<h3>Should both of my units bid on our brand name in the same area?</h3>
<p>Usually not. People searching your brand already know you, so two units bidding the brand into the same ZIPs mostly raises your own cost. Keep brand campaigns tight to each unit’s core, and confirm whether corporate allows local brand bidding at all.</p>
<h3>How often should I review territory fences for my units?</h3>
<p>Review them weekly on a geo scoreboard and redo the map after any unit opens, relocates, remodels, or changes hours or staffing. Fences drift out of date when operations change and campaigns don’t. Keep one source-of-truth map with a single owner.</p>
<p><script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How can I tell if my own franchise units are bidding against each other?","acceptedAnswer":{"@type":"Answer","text":"Look for the same keywords targeted in overlapping locations across two campaigns or accounts. Auction insights showing your other unit as a competitor, rising CPCs in the ZIPs between units, and the same household credited to both units in the CRM are strong signs. Pull 30–60 days of location data for both units to confirm."}},{"@type":"Question","name":"Should my units share one Google Ads campaign or have separate campaigns?","acceptedAnswer":{"@type":"Answer","text":"Most operators do better with separate campaigns per unit, each targeting its own core and excluding the other unit’s core. Share negative keyword lists across units, but keep geos and budgets per unit. A shared campaign can work for brand terms only if calls and forms route to the right unit after the click."}},{"@type":"Question","name":"Is radius or ZIP code targeting better for overlapping franchise territories?","acceptedAnswer":{"@type":"Answer","text":"In dense metros, ZIP or polygon targeting is usually better because radius circles overlap by design and rarely match territory lines. Radius works in rural areas where drive-time bubbles are clear. If your agreement defines territory by ZIP, target by ZIP."}},{"@type":"Question","name":"How do I split Local Services Ads service areas between units I own?","acceptedAnswer":{"@type":"Answer","text":"Match each unit’s LSA service area to the same core ZIPs you use in Google Ads. Avoid letting two units’ service areas overlap unless one is intentionally taking overflow under a written rule. Review LSA service areas whenever you change your Ads geos."}},{"@type":"Question","name":"What should I do when a lead comes in from a ZIP on the border between two units?","acceptedAnswer":{"@type":"Answer","text":"Follow a written seam rule instead of deciding case by case. A common approach is that the first unit to make valid contact within your response-time standard keeps the lead, and the other unit doesn’t call the same customer. Record a seam flag and a single credited unit so the lead isn’t counted twice."}},{"@type":"Question","name":"Do franchise agreements restrict advertising between units I own?","acceptedAnswer":{"@type":"Answer","text":"Often they do, even when you own both units. Advertising territory can differ from delivery territory, and some agreements limit where each unit may advertise. Check your FDD and franchise agreement, and confirm with your franchisor in writing before setting up overlap."}},{"@type":"Question","name":"Should both of my units bid on our brand name in the same area?","acceptedAnswer":{"@type":"Answer","text":"Usually not. People searching your brand already know you, so two units bidding the brand into the same ZIPs mostly raises your own cost. Keep brand campaigns tight to each unit’s core, and confirm whether corporate allows local brand bidding at all."}},{"@type":"Question","name":"How often should I review territory fences for my units?","acceptedAnswer":{"@type":"Answer","text":"Review them weekly on a geo scoreboard and redo the map after any unit opens, relocates, remodels, or changes hours or staffing. Fences drift out of date when operations change and campaigns don’t. Keep one source-of-truth map with a single owner."}}]}</script></p>
<h2>Need Help?</h2>
<p>If two (or more) units you own are bidding into the same ZIPs and you want a clean fence + ownership map — without rebuilding your whole media stack — fill out our <a href="https://go.leadppc.com/contact/">Contact Us</a> form.</p>
<p>We can walk your cores, seam ZIPs, Ads vs LSA overlap, and the one-page lead-ownership rules that stop Google from taxing you twice for the same household.</p>
<p>The post <a href="https://leadppc.com/franchise/multi-unit-franchise-territory-overlap-ads/">When Two Units You Own Compete in the Same Zips: A Multi-Unit Geo Playbook</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://leadppc.com/franchise/multi-unit-franchise-territory-overlap-ads/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Multi-Unit Franchise Call Tracking: One Stack Across Locations You Own</title>
		<link>https://leadppc.com/franchise/multi-unit-franchise-call-tracking/</link>
					<comments>https://leadppc.com/franchise/multi-unit-franchise-call-tracking/#respond</comments>
		
		<dc:creator><![CDATA[Grant James]]></dc:creator>
		<pubDate>Fri, 25 Sep 2026 11:47:30 +0000</pubDate>
				<category><![CDATA[Franchise]]></category>
		<guid isPermaLink="false">https://leadppc.com/?p=4400</guid>

					<description><![CDATA[<p>Multi-Unit Franchise Call Tracking: One Stack Across Locations You Own Multi-unit franchise call tracking — one stack across locations you own for honest source attribution. Key Takeaways Use one call tracking account and one set of definitions for every unit you own, but give each unit its own tracking numbers. The default that fails least [...]</p>
<p>The post <a href="https://leadppc.com/franchise/multi-unit-franchise-call-tracking/">Multi-Unit Franchise Call Tracking: One Stack Across Locations You Own</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>Multi-Unit Franchise Call Tracking: One Stack Across Locations You Own</h1>
<div id="attachment_4409" class="wp-caption alignnone" style="width: 1290px;"><img loading="lazy" decoding="async" class="size-full wp-image-4409" src="https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-call-tracking-canva-hero.png" alt="Multi-unit franchise call tracking across locations you own" width="1280" height="720" aria-describedby="caption-attachment-4401" srcset="https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-call-tracking-canva-hero-200x113.png 200w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-call-tracking-canva-hero-300x169.png 300w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-call-tracking-canva-hero-400x225.png 400w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-call-tracking-canva-hero-600x338.png 600w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-call-tracking-canva-hero-800x450.png 800w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-call-tracking-canva-hero-1024x576.png 1024w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-call-tracking-canva-hero-1200x675.png 1200w, https://leadppc.com/wp-content/uploads/2026/09/multi-unit-franchise-call-tracking-canva-hero.png 1280w" sizes="auto, (max-width: 1280px) 100vw, 1280px" /></p>
<p id="caption-attachment-4401" class="wp-caption-text">Multi-unit franchise call tracking — one stack across locations you own for honest source attribution.</p>
</div>
<div class="key-takeaways" style="border: 1px solid #d9d9d9; border-left: 4px solid #1e73be; background: #f7f9fc; padding: 16px 20px; margin: 24px 0;">
<p><strong>Key Takeaways</strong></p>
<ul>
<li>Use one call tracking account and one set of definitions for every unit you own, but give each unit its own tracking numbers.</li>
<li>The default that fails least for 2–10 units is a primary number per unit plus separate PPC and LSA call pools per unit.</li>
<li>Dynamic number insertion (DNI) tells you the channel, not the unit — unit ownership should come from the landing page, geo, or the agent.</li>
<li>Keep a stable primary number on your Google Business Profile and footer so NAP stays consistent; confirm tracking-number rules with your franchisor.</li>
<li>Require CRM fields for unit, source, disposition, fulfilling unit, and credit unit so attribution survives handoffs between locations.</li>
<li>Judge channels by cost per booked job by unit, and keep co-op and brand-fund calls out of your local numbers.</li>
</ul>
</div>
<p>If you own several franchise units and your dashboards still argue about which store “got” the call, you don’t have a media problem yet — you have a <strong>tracking stack</strong> problem.</p>
<p>I’ve sold franchise units myself and I’ve helped a lot of multi-unit operators (typically 2–10 locations) clean up call attribution for local service demand. The pattern is familiar: corporate co-op reports look fine, Google Ads shows “calls,” LSA shows “leads,” and your P&amp;L still can’t say which unit and which channel booked the job.</p>
<p>This playbook is the <strong>operator call-tracking layer</strong> — shared vs per-location numbers, dynamic number insertion (DNI), LSA vs PPC call pools, CRM fields that survive handoffs, a weekly scoreboard, and co-op data hygiene. It is for multi-unit franchisee operators buying <strong>customer / local service</strong> leads.</p>
<p>It is <strong>not</strong> bid strategy or creative (that’s our <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit franchise advertising</a> playbook). It is <strong>not</strong> LSA eligibility, verification, or profile ops (see <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">Google LSA operations across several locations</a>). And it is <strong>not</strong> franchisor development capacity planning — that closer-bandwidth piece is <a href="https://leadppc.com/franchise/franchise-lead-capacity-planning/">franchise lead capacity planning</a>, a different audience.</p>
<h2>Why Multi-Unit Call Attribution Breaks First</h2>
<p>Multi-unit call attribution breaks because shared numbers, mixed call pools, cross-unit handoffs, and co-op reports all land in one bucket. Until each call carries a unit and a source, no dashboard can tell you which location and channel booked the job.</p>
<p>When Unit A and Unit B sit in the same metro, four tracking failures get smashed into one shrug:</p>
<ol>
<li><strong>Shared vanity numbers</strong> on the website, GBP, and truck wraps with no source tags.</li>
<li><strong>Pool mixing</strong> — LSA platform numbers, PPC call extensions, and organic DNI all dump into one CRM “Phone” bucket.</li>
<li><strong>Handoff amnesia</strong> — Unit A answers, Unit B fulfills, both claim the sale (or neither does).</li>
<li><strong>Co-op contamination</strong> — corporate or DMA reports get pasted into your unit P&amp;L as if they were your local paid outcomes.</li>
</ol>
<p>You don’t fix that with a better keyword list. You fix it with a <strong>one-stack tracking design</strong> every unit can run the same way.</p>
<h2>The One-Stack Rule: Same Definitions, Unit-True Numbers</h2>
<p>The one-stack rule is simple: every unit uses the same definitions and CRM fields, but each unit keeps its own tracking numbers and phone identity. Shared definitions make units comparable; separate numbers make them attributable.</p>
<p>The organizing rule I use with multi-unit owners:</p>
<p><strong>Share definitions. Separate identity.</strong></p>
<table>
<thead>
<tr>
<th>Share across units</th>
<th>Keep unit-true</th>
</tr>
</thead>
<tbody>
<tr>
<td>What counts as a “qualified call” (duration, intent, not spam)</td>
<td>Tracking numbers / pools mapped to unit</td>
</tr>
<tr>
<td>CRM field names and disposition list</td>
<td>Landing page / GBP phone where brand allows</td>
</tr>
<tr>
<td>One-lead / one-credit rule</td>
<td>Answer ownership and overflow path</td>
</tr>
<tr>
<td>Weekly scoreboard columns</td>
<td>Budget and capacity ceilings</td>
</tr>
<tr>
<td>Recording / consent language standard</td>
<td>Hours and staffing</td>
</tr>
</tbody>
</table>
<p>If Unit 3 invents its own “lead” definition, your portfolio dashboard is fiction. If every unit shares one phone number, your portfolio dashboard is also fiction — just a prettier one.</p>
<p>For broader consolidate-vs-separate decisions (accounts, geo, floors), stay on the <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit advertising</a> page. This article stays on <strong>calls and attribution</strong>.</p>
<h2>Shared Vs Per-Location Tracking Numbers</h2>
<p>There is no universal winner. There is a default that fails less often for 2–10 units.</p>
<p><strong>Default I recommend:</strong> per-location (or per-unit × channel) tracking numbers, with a small shared pool only where the agreement or brand directory forces a single NAP (name/address/phone).</p>
<table>
<thead>
<tr>
<th>Pattern</th>
<th>When it works</th>
<th>How it breaks</th>
</tr>
</thead>
<tbody>
<tr>
<td>One shared number for all units</td>
<td>Tiny portfolio, central dispatch that tags unit in CRM on every call</td>
<td>Attribution collapses the week dispatch is busy</td>
</tr>
<tr>
<td>Per-unit primary + channel pools</td>
<td>Most 2–10 unit operators</td>
<td>Admin overhead if you never document the map</td>
</tr>
<tr>
<td>Per-unit × channel (PPC, LSA, organic, offline)</td>
<td>You actually reallocate budget by unit and channel</td>
<td>Too many numbers if nobody owns the spreadsheet</td>
</tr>
</tbody>
</table>
<p>Practical minimum:</p>
<ul>
<li>One <strong>primary</strong> tracking number per unit for organic / GBP / site (confirm NAP rules with your franchisor).</li>
<li>Separate <strong>PPC call pool</strong> per unit (or per campaign group that maps cleanly to a unit).</li>
<li>Separate <strong>LSA pool</strong> per unit — LSA already thinks in location-true leads; don’t launder it into the PPC pool.</li>
<li>Offline / wrap / print: either a dedicated offline number per unit or a tagged vanity that still lands in that unit’s CRM row.</li>
</ul>
<p><strong>Confirm with your franchisor:</strong> whether tracking numbers are allowed on the website and Google Business Profile without breaking directory NAP standards. Local listing hygiene still matters — see <a href="https://leadppc.com/franchise/local-franchise-marketing/">local franchise marketing</a> if GBP is an afterthought.</p>
<h2>Dynamic Number Insertion (DNI) Without Lying to Yourself</h2>
<p>DNI swaps the visible phone number based on how the visitor arrived (paid search, paid social, organic, direct). Used well, it attributes website callers to channel. Used badly, it creates three new problems:</p>
<ol>
<li><strong>Session pollution</strong> — a prospect sees a PPC number on Monday, Googles the brand Tuesday, calls the organic number, and PPC still “won” in someone’s head.</li>
<li><strong>NAP flicker</strong> — if DNI rewrites the GBP-matching number on every page view, you can create listing inconsistency. Keep a stable primary for footer/GBP alignment where brand rules require it; use DNI on dedicated landing pages when allowed.</li>
<li><strong>Missed mobile</strong> — click-to-call on Maps/GBP bypasses your website DNI entirely. Those calls need their own mapping (often the unit primary or an LSA/GBP-associated number).</li>
</ol>
<p>Operator rules that keep DNI honest:</p>
<ul>
<li>DNI is a <strong>source tag</strong>, not a unit resolver. Unit still comes from landing page, geo, or agent selection.</li>
<li>Never let DNI overwrite the CRM’s unit field after a human has assigned the job.</li>
<li>Test with a burner phone: paid landing → number A; organic homepage → number B; GBP → number C. Write the three results on the unit matrix.</li>
</ul>
<p><strong>Universal:</strong> Call-recording consent varies by state. If recording is on, use a clear announcement and get counsel to review all-party-consent exposure when calls cross state lines. Don’t improvise this.</p>
<h2>LSA Vs PPC Call Pools (Tracking Only)</h2>
<p>Keep LSA calls and PPC calls in separate number pools for each unit. Mixing them makes it impossible to see what each channel actually costs per booked job.</p>
<p>Keep this section narrow on purpose. LSA setup, eligibility, and profile ops live on the <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">LSA multi-location playbook</a>. Here you only need pool discipline.</p>
<table>
<thead>
<tr>
<th>Pool</th>
<th>What it should prove</th>
<th>Do not do</th>
</tr>
</thead>
<tbody>
<tr>
<td>LSA per unit</td>
<td>Cost and booked rate of LSA leads for that unit</td>
<td>Merge LSA calls into the PPC “Calls from ads” story</td>
</tr>
<tr>
<td>PPC per unit</td>
<td>Cost and booked rate of Search/call-extension callers</td>
<td>Use one blended PPC number for every unit in a metro</td>
</tr>
<tr>
<td>Organic / site DNI</td>
<td>Non-paid web callers</td>
<td>Treat unpaid branded callers as “PPC wins” because they saw an ad last week</td>
</tr>
<tr>
<td>Offline</td>
<td>Wrap / print / referral phone demand</td>
<td>Dump offline into “Google” because the CRM default source is Google</td>
</tr>
</tbody>
</table>
<p>One-lead / one-credit still applies: if LSA at Unit A produces the call and the customer books at Unit B, <strong>Unit A owns the lead-cost conversation; Unit B owns the job.</strong> Both dashboards claiming the sale is how operators fight instead of reallocate.</p>
<h2>CRM Fields That Survive Handoffs</h2>
<p>Make unit, source, disposition, fulfilling unit, and credit unit required fields in your CRM. Required fields are the only ones that survive a busy week and a job that moves between locations.</p>
<p>If the field isn’t required, it won’t survive a busy Saturday.</p>
<p>Minimum CRM schema for multi-unit call tracking:</p>
<table>
<thead>
<tr>
<th>Field</th>
<th>Why it exists</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>unit</code></td>
<td>Which P&amp;L owns the outcome</td>
</tr>
<tr>
<td><code>source</code></td>
<td>LSA / PPC / organic / offline / referral / co-op (separate!)</td>
</tr>
<tr>
<td><code>campaign</code> or <code>pool_id</code></td>
<td>Ties to the tracking number / ad group</td>
</tr>
<tr>
<td><code>call_duration</code></td>
<td>Supports your qualified-call definition</td>
</tr>
<tr>
<td><code>disposition</code></td>
<td>Qualified / booked / spam / out-of-area / duplicate / employee</td>
</tr>
<tr>
<td><code>booked_job</code> (Y/N + date)</td>
<td>The number that actually matters</td>
</tr>
<tr>
<td><code>fulfilling_unit</code></td>
<td>When answer unit ≠ fulfill unit</td>
</tr>
<tr>
<td><code>credit_unit</code></td>
<td>Who gets marketing credit under your one-lead rule</td>
</tr>
<tr>
<td><code>co_op_flag</code></td>
<td>Marks corporate/DMA traffic so it never mixes into local P&amp;L</td>
</tr>
</tbody>
</table>
<p>Handoff rules worth writing down:</p>
<ol>
<li>First agent to save <code>unit</code> + <code>source</code> locks those fields unless a manager override exists.</li>
<li>If the job moves units, update <code>fulfilling_unit</code> — do <strong>not</strong> silently rewrite <code>credit_unit</code>.</li>
<li>Spam and employee calls get dispositions the same day so they don’t inflate “leads.”</li>
<li>Duplicates: one primary record; secondary calls link to it. Two open leads for one household is how both managers claim victory.</li>
</ol>
<h2>The Weekly Scoreboard: Unit × Channel → Booked Jobs</h2>
<p>The number to manage weekly is booked jobs and cost per booked job by unit and channel, not raw call volume. A one-page scoreboard with the same definitions every week keeps that honest.</p>
<p>If your weekly meeting is “how many calls did we get?”, you’re managing the wrong number.</p>
<p>Run a <strong>one-page scoreboard</strong> every week — per unit and rolled up:</p>
<table>
<thead>
<tr>
<th>Metric</th>
<th>What it tells you</th>
</tr>
</thead>
<tbody>
<tr>
<td>Qualified calls (your definition)</td>
<td>Real demand</td>
</tr>
<tr>
<td>Answer rate during open hours</td>
<td>Ops health</td>
</tr>
<tr>
<td>Booked jobs from calls</td>
<td>Outcome</td>
</tr>
<tr>
<td>Cost per booked job by channel (LSA pool / PPC pool / organic / offline)</td>
<td>Where the next dollar goes</td>
</tr>
<tr>
<td>Share of calls missing <code>unit</code> or <code>source</code></td>
<td>Tracking debt</td>
</tr>
<tr>
<td>Co-op / brand-fund calls (separated)</td>
<td>Hygiene — not your local CPL story</td>
</tr>
<tr>
<td>Overflow / misroute count</td>
<td>Routing quality</td>
</tr>
</tbody>
</table>
<p>Keep media tactics on the advertising playbook. The scoreboard’s job is <strong>attribution honesty</strong>: which unit and which pool booked work.</p>
<p>A healthy pattern I look for: booked rate stable while you reallocate flex budget toward the units and pools that convert — without “averaging away” a dying unit by blending it into a portfolio CPL.</p>
<h2>Co-Op And Brand-Fund Data Hygiene</h2>
<p>Multi-unit operators routinely paste corporate reports into local decision sheets. That’s how you fund the wrong unit.</p>
<p>Separate three money stories:</p>
<ol>
<li><strong>National brand fund / corporate media</strong> — not your unit P&amp;L’s local paid outcome.</li>
<li><strong>Regional / DMA co-op</strong> — pooled; attribute only what your agreement says you can claim.</li>
<li><strong>Your local paid + organic</strong> — the only story your floor-and-flex budget should optimize.</li>
</ol>
<p>Operator hygiene:</p>
<ul>
<li>Tag co-op and brand-fund sourced calls with <code>co_op_flag</code> (or a dedicated <code>source</code> value).</li>
<li>Never let co-op CPL “prove” that Unit 2’s local PPC is efficient.</li>
<li>When corporate sends a blended DMA report, park it in a <strong>Co-op</strong> tab — not in the unit scoreboard.</li>
</ul>
<p><strong>Confirm with your franchisor:</strong> what local spend counts toward minimums, what reporting format they expect, and who owns customer data for uploads / offline conversions.</p>
<h2>Pitfalls That Quietly Wreck Multi-Unit Tracking</h2>
<ol>
<li><strong>One Google Ads “call” column for five units</strong> — you cannot reallocate what you cannot see.</li>
<li><strong>LSA refunds ignored in the CRM</strong> — platform lead cost ≠ your booked economics if spam isn’t dispositioned.</li>
<li><strong>DNI on every template including legal/NAP blocks</strong> — brand compliance risk for a few attribution crumbs.</li>
<li><strong>Managers editing <code>source</code> after the fact to protect a pet channel</strong> — lock fields; audit overrides.</li>
<li><strong>Celebrating call volume while answer rate is red</strong> — buying calls into a full desk is the franchisee version of the capacity trap (different audience than <a href="https://leadppc.com/franchise/franchise-lead-capacity-planning/">franchisor capacity planning</a>, same math instinct).</li>
<li><strong>No overflow plan across adjacent units</strong> — boundary customers become double-counted arguments.</li>
<li><strong>Recording without a consistent disclosure</strong> — legal risk is not a marketing KPI, but it ends marketing meetings.</li>
</ol>
<h2>Build This Week: Unit Matrix + Number Map + Scoreboard</h2>
<p>Don’t leave tracking as vibes. Build three artifacts:</p>
<p><strong>1) Unit matrix (one row per unit)</strong></p>
<table>
<thead>
<tr>
<th>Unit</th>
<th>Primary phone</th>
<th>PPC pool</th>
<th>LSA pool</th>
<th>Offline</th>
<th>Landing page</th>
<th>GBP phone rule</th>
<th>Capacity ceiling</th>
</tr>
</thead>
<tbody>
<tr>
<td>Unit 1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Unit 2</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>
<p><strong>2) Number map</strong> — every tracking number → unit → source → CRM <code>pool_id</code>. One owner. Update when you swap vendors.</p>
<p><strong>3) Weekly scoreboard</strong> — the table above, same definitions every Monday.</p>
<p>That’s the stack: definitions shared, identity unit-true, pools separated, CRM fields that survive handoffs, co-op kept out of your local P&amp;L.</p>
<h2>Frequently Asked Questions</h2>
<h3>Should I use one call tracking account for all my franchise locations?</h3>
<p>Usually yes. One account keeps qualified-call definitions, dispositions, and reporting identical across units, which is what makes them comparable. Inside that account, give each unit its own numbers and pools so calls still attribute to the right location.</p>
<h3>Should each franchise location have its own tracking number?</h3>
<p>For most operators with 2–10 units, yes. A primary tracking number per unit, plus separate PPC and LSA pools per unit, lets you see which location and channel produced each call. A single shared number only works if dispatch reliably tags the unit on every call.</p>
<h3>How does dynamic number insertion work across multiple locations?</h3>
<p>DNI swaps the phone number shown on your website based on how the visitor arrived, such as paid search or organic. It identifies the channel, not the unit, so the location should come from the landing page, the visitor’s geo, or the agent who takes the call. Test each unit’s pages with a real phone before you trust the reports.</p>
<h3>Will call tracking numbers hurt NAP consistency on my Google Business Profiles?</h3>
<p>They can if the number on your listing keeps changing or doesn’t match your site. Keep a stable primary number on each Google Business Profile and in your site footer, and use DNI mainly on landing pages. Confirm with your franchisor what numbers are allowed on listings and brand directories.</p>
<h3>Is it legal to record calls across my franchise locations?</h3>
<p>It depends on the states involved. Some states require consent from everyone on the call, so use a clear recording announcement on every line and have counsel review your setup, especially when calls cross state lines. Check your state’s consent laws before turning recording on.</p>
<h3>How do I attribute a call when one unit answers and another unit does the job?</h3>
<p>Track the answering unit, the fulfilling unit, and the credited unit as separate CRM fields. Decide in advance who gets marketing credit under a one-lead, one-credit rule, and update the fulfilling unit when a job moves instead of rewriting the credit. That keeps both managers’ reports honest.</p>
<h3>What should count as a qualified call for a multi-unit franchise?</h3>
<p>Define it once for all units: a real prospect asking about a service you offer in an area you serve, above a minimum duration you choose, and not spam, a vendor, an employee, or a duplicate. Disposition calls the same day so junk doesn’t inflate lead counts. Then measure booked jobs, not just qualified calls.</p>
<h3>How do I keep co-op and brand-fund calls out of my local numbers?</h3>
<p>Tag co-op and brand-fund sourced calls with their own source value or flag in the CRM. Keep corporate or DMA reports on a separate tab instead of the unit scoreboard. Your local budget decisions should rest only on your local paid and organic results.</p>
<p><script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Should I use one call tracking account for all my franchise locations?","acceptedAnswer":{"@type":"Answer","text":"Usually yes. One account keeps qualified-call definitions, dispositions, and reporting identical across units, which is what makes them comparable. Inside that account, give each unit its own numbers and pools so calls still attribute to the right location."}},{"@type":"Question","name":"Should each franchise location have its own tracking number?","acceptedAnswer":{"@type":"Answer","text":"For most operators with 2–10 units, yes. A primary tracking number per unit, plus separate PPC and LSA pools per unit, lets you see which location and channel produced each call. A single shared number only works if dispatch reliably tags the unit on every call."}},{"@type":"Question","name":"How does dynamic number insertion work across multiple locations?","acceptedAnswer":{"@type":"Answer","text":"DNI swaps the phone number shown on your website based on how the visitor arrived, such as paid search or organic. It identifies the channel, not the unit, so the location should come from the landing page, the visitor’s geo, or the agent who takes the call. Test each unit’s pages with a real phone before you trust the reports."}},{"@type":"Question","name":"Will call tracking numbers hurt NAP consistency on my Google Business Profiles?","acceptedAnswer":{"@type":"Answer","text":"They can if the number on your listing keeps changing or doesn’t match your site. Keep a stable primary number on each Google Business Profile and in your site footer, and use DNI mainly on landing pages. Confirm with your franchisor what numbers are allowed on listings and brand directories."}},{"@type":"Question","name":"Is it legal to record calls across my franchise locations?","acceptedAnswer":{"@type":"Answer","text":"It depends on the states involved. Some states require consent from everyone on the call, so use a clear recording announcement on every line and have counsel review your setup, especially when calls cross state lines. Check your state’s consent laws before turning recording on."}},{"@type":"Question","name":"How do I attribute a call when one unit answers and another unit does the job?","acceptedAnswer":{"@type":"Answer","text":"Track the answering unit, the fulfilling unit, and the credited unit as separate CRM fields. Decide in advance who gets marketing credit under a one-lead, one-credit rule, and update the fulfilling unit when a job moves instead of rewriting the credit. That keeps both managers’ reports honest."}},{"@type":"Question","name":"What should count as a qualified call for a multi-unit franchise?","acceptedAnswer":{"@type":"Answer","text":"Define it once for all units: a real prospect asking about a service you offer in an area you serve, above a minimum duration you choose, and not spam, a vendor, an employee, or a duplicate. Disposition calls the same day so junk doesn’t inflate lead counts. Then measure booked jobs, not just qualified calls."}},{"@type":"Question","name":"How do I keep co-op and brand-fund calls out of my local numbers?","acceptedAnswer":{"@type":"Answer","text":"Tag co-op and brand-fund sourced calls with their own source value or flag in the CRM. Keep corporate or DMA reports on a separate tab instead of the unit scoreboard. Your local budget decisions should rest only on your local paid and organic results."}}]}</script></p>
<h2>Need Help?</h2>
<p>If you want a second set of eyes on multi-unit call tracking — number architecture, DNI, LSA vs PPC pools, or a scoreboard your managers will actually use — fill out our <a href="https://go.leadppc.com/contact/">Contact Us</a> form.</p>
<p>We can talk through attribution across the units you own without mixing co-op vanity into local decisions, and without turning this into another bid-strategy meeting.</p>
<p>The post <a href="https://leadppc.com/franchise/multi-unit-franchise-call-tracking/">Multi-Unit Franchise Call Tracking: One Stack Across Locations You Own</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://leadppc.com/franchise/multi-unit-franchise-call-tracking/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Franchise Lead Capacity Planning: Match Ad Spend and Broker Volume to Your Closers</title>
		<link>https://leadppc.com/franchise/franchise-lead-capacity-planning/</link>
					<comments>https://leadppc.com/franchise/franchise-lead-capacity-planning/#respond</comments>
		
		<dc:creator><![CDATA[Grant James]]></dc:creator>
		<pubDate>Thu, 24 Sep 2026 02:15:34 +0000</pubDate>
				<category><![CDATA[Franchise]]></category>
		<guid isPermaLink="false">https://leadppc.com/?p=4384</guid>

					<description><![CDATA[<p>Ops playbook: size PPC, broker, and portal intake to closer bandwidth — stage SLAs, routing rules, weekly scoreboard, and when to hire vs cut spend.</p>
<p>The post <a href="https://leadppc.com/franchise/franchise-lead-capacity-planning/">Franchise Lead Capacity Planning: Match Ad Spend and Broker Volume to Your Closers</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>Franchise Lead Capacity Planning: Match Ad Spend and Broker Volume to Your Closers</h1>
<div id="attachment_4393" class="wp-caption alignnone" style="width: 1290px;"><img loading="lazy" decoding="async" class="size-full wp-image-4393" src="https://leadppc.com/wp-content/uploads/2026/09/Franchise-Lead-Capacity-Planning-canva-v3.png" alt="Franchise Lead Capacity Planning" width="1280" height="720" aria-describedby="caption-attachment-4393" srcset="https://leadppc.com/wp-content/uploads/2026/09/Franchise-Lead-Capacity-Planning-canva-v3-200x113.png 200w, https://leadppc.com/wp-content/uploads/2026/09/Franchise-Lead-Capacity-Planning-canva-v3-300x169.png 300w, https://leadppc.com/wp-content/uploads/2026/09/Franchise-Lead-Capacity-Planning-canva-v3-400x225.png 400w, https://leadppc.com/wp-content/uploads/2026/09/Franchise-Lead-Capacity-Planning-canva-v3-600x338.png 600w, https://leadppc.com/wp-content/uploads/2026/09/Franchise-Lead-Capacity-Planning-canva-v3-800x450.png 800w, https://leadppc.com/wp-content/uploads/2026/09/Franchise-Lead-Capacity-Planning-canva-v3-1024x576.png 1024w, https://leadppc.com/wp-content/uploads/2026/09/Franchise-Lead-Capacity-Planning-canva-v3-1200x675.png 1200w, https://leadppc.com/wp-content/uploads/2026/09/Franchise-Lead-Capacity-Planning-canva-v3.png 1280w" sizes="auto, (max-width: 1280px) 100vw, 1280px" /></p>
<p id="caption-attachment-4393" class="wp-caption-text">Franchise lead capacity planning — match ad spend and broker volume to closer bandwidth.</p>
</div>
<p>If you’re viewing this page, you already buy franchise leads — Google + Meta, brokers, portals, maybe a mix — and something still feels off. Either your closers are drowning and CPL looks “fine” while set rates rot, or you’re starving a good rep because marketing got scared after one bad month.</p>
<p>I’ve sold franchise units myself and I’ve watched a lot of franchise development teams treat lead gen like a faucet you leave open. Volume without capacity is how you burn cash and burn your brand with slow follow-up. This playbook is about <strong>matching intake to closer bandwidth</strong> — stage SLAs, channel routing, and when to kill or pause spend when the desk is full.</p>
<p>This is <strong>not</strong> another “where do franchise leads come from” list. For channel overviews, use <a href="https://leadppc.com/franchise/how-to-get-franchise-leads/">how to get franchise leads</a>, <a href="https://leadppc.com/franchise/franchise-sales-lead-generation/">franchise sales lead generation</a>, and <a href="https://leadppc.com/franchise/franchise-lead-generation-strategies/">franchise lead generation strategies</a>. For cost bands, protect and read <a href="https://leadppc.com/franchise/how-much-does-franchise-lead-generation-cost/">how much does franchise lead generation cost</a> — I’m not republishing price tables here. For definitions, see <a href="https://leadppc.com/franchise/what-are-franchise-leads/">what are franchise leads</a>. And this is <strong>franchisor development</strong> capacity — not multi-unit franchisee customer leads.</p>
<h2>Why Franchise Lead Gen Fails When Volume Outruns Closer Capacity</h2>
<p>The fail mode is predictable:</p>
<ol>
<li>Marketing celebrates lead count.</li>
<li>Sales quietly ages the queue.</li>
<li>Speed-to-lead slips from minutes to hours (then days).</li>
<li>Broker intros go cold because nobody called back the same day.</li>
<li>CPL still looks “acceptable” on a dashboard that doesn’t care about set rate.</li>
</ol>
<p>When volume beats capacity, you don’t just waste ad spend. You train brokers that you’re slow. You teach PPC prospects that your brand ghosts people. You inflate CPA (Cost Per Appointment) and CPS (Cost Per Sale) without anyone admitting the bottleneck was <strong>people</strong>, not media.</p>
<p>A veteran closer working a real franchise pipeline can usually stay healthy around <strong>~200–300 workable leads per month</strong> depending on how dirty the sources are, how much travel/discovery-day load they carry, and whether they also own broker relationship management. Push past that without process and the queue becomes a graveyard.</p>
<p>Capacity planning means you treat closer hours as inventory. Leads you can’t touch on SLA are leads you should not buy.</p>
<h2>Capacity Math: Leads Per Closer, Working Hours, and Realistic First-Touch SLAs</h2>
<p>Start with hours, not vanity CPL.</p>
<p><strong>Rough capacity math (experience-based, not a guarantee):</strong></p>
<table>
<thead>
<tr>
<th>Input</th>
<th>Example</th>
</tr>
</thead>
<tbody>
<tr>
<td>Selling hours / closer / week</td>
<td>~30–35 after admin, travel, FDD Q&amp;A</td>
</tr>
<tr>
<td>First-touch + qualify attempt</td>
<td>~8–12 minutes average including voicemail/SMS</td>
</tr>
<tr>
<td>Meaningful dials + follow-ups per lead in week 1</td>
<td>~4–6 touches</td>
</tr>
<tr>
<td>Workable new leads / closer / month</td>
<td>Often ~200–300 if sources are clean</td>
</tr>
<tr>
<td>Discovery days / month one closer can run well</td>
<td>Often a handful, not 20</td>
</tr>
</tbody>
</table>
<p>Then set <strong>first-touch SLAs</strong> you can actually defend:</p>
<table>
<thead>
<tr>
<th>Channel</th>
<th>First-touch target</th>
<th>Why</th>
</tr>
</thead>
<tbody>
<tr>
<td>Paid inbound (Google/Meta form or call)</td>
<td>Under 5–15 minutes during business hours</td>
<td>Heat dies fast; competitors call</td>
</tr>
<tr>
<td>Broker intro</td>
<td>Same business day (ideally under 2 hours)</td>
<td>Brokers remember who is responsive</td>
</tr>
<tr>
<td>Portal / drip</td>
<td>Same day triage; many get nurture, not closer time</td>
<td>Quality mix is noisy</td>
</tr>
<tr>
<td>Organic / website long-form</td>
<td>Same day; route hot intents first</td>
<td>Not all organic is equal</td>
</tr>
</tbody>
</table>
<p>If you can’t hit the SLA, you don’t “try harder” forever — you <strong>throttle intake</strong>.</p>
<p>Also define what counts as a <strong>workable</strong> lead: real contact info, franchise-buyer intent (not a job seeker), geography/fit screens your brand uses, and not an obvious duplicate. Junk that hits the closer’s queue is stolen capacity.</p>
<p>Practical tip from <a href="https://leadppc.com/franchise/franchise-development-tips/">franchise development tips</a>: track CPL and CPS <strong>by medium</strong>. Capacity planning adds a second lens — <strong>leads accepted into closer queue per week</strong> vs <strong>touches completed on SLA</strong>.</p>
<h2>Channel Mix by Capacity Stage (PPC Throttle, Broker Caps, Portal Pause)</h2>
<p>Assume PPC is already running. Don’t rebuild keyword strategy here — that’s <a href="https://leadppc.com/franchise/franchise-ppc-advertising-strategies/">franchise PPC advertising strategies</a>. The capacity question is <strong>how much volume each channel is allowed to dump on the desk</strong>.</p>
<h3>Stage A — One closer, early brand / thin pipeline</h3>
<ul>
<li>Keep <strong>one primary paid engine</strong> (usually Google + a controlled Meta test) at a spend you can work same-day.</li>
<li>Cap broker partners to a number you can intro-call every day (quality over “more logos”).</li>
<li>Portals: drip only if someone owns triage; otherwise pause.</li>
<li>Goal: protect SLA and learn set/show rates before scaling.</li>
</ul>
<h3>Stage B — One strong closer at healthy utilization (~70–85%)</h3>
<ul>
<li>Raise PPC carefully while watching first-touch and set rate weekly.</li>
<li>Add broker volume only when intro SLA is green for 2–3 weeks.</li>
<li>Portals stay capped; use as overflow only if triage exists.</li>
<li>Do <strong>not</strong> celebrate lead count if set rate falls.</li>
</ul>
<h3>Stage C — Capacity full (SLA red for 7+ days)</h3>
<ul>
<li><strong>Kill or pause</strong> the lowest-intent sources first (often noisy portals, weak Meta audiences, leftover lead packs).</li>
<li>Throttle PPC budgets or dayparting before you ghost broker intros — brokers are relationship inventory.</li>
<li>Stop “temporary” overtime as a strategy. Overtime is a bandage that hides the hire/cut decision.</li>
</ul>
<h3>Stage D — Second closer hired / ramping</h3>
<ul>
<li>Hold intake flat for 2–4 weeks while ramp happens.</li>
<li>Then reopen throttled channels in order of historical set rate, not cheapest CPL.</li>
</ul>
<p>Rule of thumb: <strong>cheapest CPL is irrelevant if it can’t be worked</strong>. Expensive broker intros that set discovery days can beat cheap portal sludge on true cost per appointment.</p>
<h2>Routing Rules: Which Leads Go to Which Rep (And What Never Hits the Closer)</h2>
<p>Routing is capacity control.</p>
<p><strong>Never dump everything on the closer.</strong> A simple rule set:</p>
<ol>
<li><strong>Auto-disqualify before human time:</strong> job seekers, existing franchisees looking for vendor pitches, incomplete forms, known competitors, out-of-geo if your brand is strict.</li>
<li><strong>Triage lane (coordinator / SDR-lite):</strong> portals, vague “info” requests, incomplete budgets — qualify or nurture, don’t burn closer calendar.</li>
<li><strong>Closer lane:</strong> paid inbound that passes screens, broker intros, warm organic with clear buyer language.</li>
<li><strong>Director lane:</strong> multi-unit buyers, strategic territories, sensitive broker politics, VIP referrals.</li>
</ol>
<p>If you have two closers:</p>
<table>
<thead>
<tr>
<th>Lead type</th>
<th>Route</th>
</tr>
</thead>
<tbody>
<tr>
<td>Broker intros</td>
<td>Named liaison / primary closer for that broker relationship</td>
</tr>
<tr>
<td>Paid inbound</td>
<td>Round-robin <strong>or</strong> weighted to the closer under SLA</td>
</tr>
<tr>
<td>Hot geography / brand priority markets</td>
<td>Specialist if you have one</td>
</tr>
<tr>
<td>Re-engagement / old CRM leftovers</td>
<td>Separate campaign hours — don’t mix with same-day SLA work</td>
</tr>
</tbody>
</table>
<p>Write the rules down. “Whoever feels like it” is how VIP broker leads sit for three days.</p>
<p>Also decide what <strong>never</strong> hits the closer: webinar tire-kickers without a next step, purchased lists, and anything your brand can’t legally sell in that state. Protecting closer calendar is part of brand compliance, not just sales ops.</p>
<h2>Weekly Scoreboard: Set Rate, Show Rate, Discovery-Day Throughput, Cost Per Appointment</h2>
<p>If your weekly meeting is “how many leads did we get?”, you’re managing the wrong number.</p>
<p>Run a <strong>one-page scoreboard</strong> every week:</p>
<table>
<thead>
<tr>
<th>Metric</th>
<th>What it tells you</th>
</tr>
</thead>
<tbody>
<tr>
<td>New workable leads accepted</td>
<td>Intake</td>
</tr>
<tr>
<td>% first-touched on SLA</td>
<td>Capacity health</td>
</tr>
<tr>
<td>Set rate (appointment set / workable leads)</td>
<td>Sales + quality</td>
</tr>
<tr>
<td>Show rate</td>
<td>Process + confirmation discipline</td>
</tr>
<tr>
<td>Discovery days held</td>
<td>Real pipeline throughput</td>
</tr>
<tr>
<td>Cost per appointment (media + broker + portal)</td>
<td>True efficiency</td>
</tr>
<tr>
<td>Leads sitting &gt;72 hours untouched</td>
<td>Hidden burn</td>
</tr>
</tbody>
</table>
<p>Keep CPL and CPS in view — again, see the <a href="https://leadppc.com/franchise/how-much-does-franchise-lead-generation-cost/">cost article</a> for ranges — but <strong>appointments and SLA</strong> decide whether to scale spend this week.</p>
<p>A healthy pattern I look for: set rate stable or rising while volume rises. If volume rises and set rate falls while SLA slips, you don’t have a media problem yet — you have a capacity problem.</p>
<p>Use the scoreboard to assign <strong>owners</strong>: marketing owns spend throttle; sales owns touches and sets; whoever owns brokers owns intro speed. Shared dashboards with no owners are decoration.</p>
<h2>When to Hire the Next Closer vs. When to Cut Spend (Decision Tree)</h2>
<p>Use a boring decision tree. Drama is expensive.</p>
<p><strong>Hire / ramp next closer when most of these are true for 3–4 weeks:</strong><br />
&#8211; First-touch SLA is red or barely green only via overtime<br />
&#8211; Set rate is still acceptable (quality isn’t collapsing)<br />
&#8211; Discovery-day calendar is full enough that good leads wait<br />
&#8211; Broker partners are asking for more capacity and you’re declining good intros<br />
&#8211; Unit economics (CPA / CPS) still support another comp plan</p>
<p><strong>Cut or pause spend when most of these are true:</strong><br />
&#8211; SLA red <strong>and</strong> set rate falling (you’re buying leads you can’t work <em>and</em> quality/process is slipping)<br />
&#8211; Queue age climbing (&gt;72 hours untouched becoming normal)<br />
&#8211; Closers spending time on junk that triage should have caught<br />
&#8211; You’re funding channels with historically weak set rates “to hit lead goals”</p>
<p><strong>Hold and fix process (don’t hire, don’t spend more) when:</strong><br />
&#8211; SLA is green but set rate is weak → script, offer, FDD timing, confirmation, or source mix<br />
&#8211; Show rate is weak → confirmation cadence, calendar friction, travel logistics<br />
&#8211; One channel is carrying all the appointments → don’t hire for volume until mix is healthier</p>
<table>
<thead>
<tr>
<th>Signal</th>
<th>Default move</th>
</tr>
</thead>
<tbody>
<tr>
<td>SLA red + set rate OK</td>
<td>Hire or throttle (prefer hire if economics work)</td>
</tr>
<tr>
<td>SLA red + set rate down</td>
<td>Throttle first; fix triage; then reassess hire</td>
</tr>
<tr>
<td>SLA green + set rate down</td>
<td>Fix sales process / source quality — not more spend</td>
</tr>
<tr>
<td>SLA green + set rate OK + empty calendar</td>
<td>Cautiously increase best channel</td>
</tr>
</tbody>
</table>
<p>Capacity planning is the grown-up version of lead gen. Sources and costs matter — we’ve written plenty on both — but <strong>matching ad spend and broker volume to your closers</strong> is what keeps CPL from rotting in a queue.</p>
<h2>Need Help?</h2>
<p>If you want a second set of eyes on franchise lead capacity — spend vs closer bandwidth, routing, or what to pause — fill out our <a href="https://go.leadppc.com/contact/">Contact Us</a> form.</p>
<p>We can talk through your scoreboard, channel mix, and what tends to work for development teams that already buy leads and need the ops layer tightened.</p>
<p>The post <a href="https://leadppc.com/franchise/franchise-lead-capacity-planning/">Franchise Lead Capacity Planning: Match Ad Spend and Broker Volume to Your Closers</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://leadppc.com/franchise/franchise-lead-capacity-planning/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Google LSA Operations Across Several Locations: A Franchisee Playbook</title>
		<link>https://leadppc.com/franchise/google-lsa-operations-several-locations/</link>
					<comments>https://leadppc.com/franchise/google-lsa-operations-several-locations/#respond</comments>
		
		<dc:creator><![CDATA[Grant James]]></dc:creator>
		<pubDate>Wed, 23 Sep 2026 03:43:04 +0000</pubDate>
				<category><![CDATA[Franchise]]></category>
		<guid isPermaLink="false">https://leadppc.com/?p=4373</guid>

					<description><![CDATA[<p>Google LSA Operations Across Several Locations: A Franchisee Playbook Google LSA operations across several locations — franchisee operator playbook for eligibility, routing, and unit budgets. If you own several franchise units and you’re trying to make Google Local Service Ads work across them, the hard part usually isn’t “should we try LSA?” It’s eligibility, verification, [...]</p>
<p>The post <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">Google LSA Operations Across Several Locations: A Franchisee Playbook</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>Google LSA Operations Across Several Locations: A Franchisee Playbook</h1>
<div id="attachment_4375" class="wp-caption alignnone" style="width: 1290px;"><img loading="lazy" decoding="async" class="size-full wp-image-4583" src="https://leadppc.com/wp-content/uploads/2026/11/google-lsa-operations-several-locations-featured.jpg" alt="Google LSA Operations Across Several Locations" width="1280" height="720" srcset="https://leadppc.com/wp-content/uploads/2026/11/google-lsa-operations-several-locations-featured-200x113.jpg 200w, https://leadppc.com/wp-content/uploads/2026/11/google-lsa-operations-several-locations-featured-300x169.jpg 300w, https://leadppc.com/wp-content/uploads/2026/11/google-lsa-operations-several-locations-featured-400x225.jpg 400w, https://leadppc.com/wp-content/uploads/2026/11/google-lsa-operations-several-locations-featured-600x338.jpg 600w, https://leadppc.com/wp-content/uploads/2026/11/google-lsa-operations-several-locations-featured-800x450.jpg 800w, https://leadppc.com/wp-content/uploads/2026/11/google-lsa-operations-several-locations-featured-1024x576.jpg 1024w, https://leadppc.com/wp-content/uploads/2026/11/google-lsa-operations-several-locations-featured-1200x675.jpg 1200w, https://leadppc.com/wp-content/uploads/2026/11/google-lsa-operations-several-locations-featured.jpg 1280w" sizes="auto, (max-width: 1280px) 100vw, 1280px" /></p>
<p id="caption-attachment-4372" class="wp-caption-text">Google LSA operations across several locations — franchisee operator playbook for eligibility, routing, and unit budgets.</p>
</div>
<p>If you own several franchise units and you’re trying to make Google Local Service Ads work across them, the hard part usually isn’t “should we try LSA?” It’s eligibility, verification, routing, and unit-level money — without breaking brand rules or inventing fake local profiles.</p>
<p>I’ve sold franchise units myself and I’ve helped a lot of multi-unit operators (typically 2–10 units) run paid local demand. The pattern I see: owners treat LSA like a single-location channel times N, or they bolt it onto a blended Google Ads setup and hope Google sorts the rest. That usually creates verification headaches, misrouted calls, and budgets that ignore capacity.</p>
<p>This playbook is <strong>LSA operations only</strong> — for multi-unit franchisee operators who already own the locations. For the broader ads stack (Search, Meta, geo, brand funds, attribution across channels), use our <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit franchise advertising playbook</a>. That piece is the wider frame; this one goes deeper on Local Service Ads (also called GLA in some older industry writeups).</p>
<h2>Eligibility: One Legitimate LSA Presence Per Real Operating Location</h2>
<p>Start with a blunt rule: <strong>one legitimate LSA presence per real operating location.</strong> A shared brand name does not replace market-specific proof. Duplicate or “placeholder” profiles are not a shortcut — they’re a compliance and trust problem waiting to happen.</p>
<p>Build a unit-by-unit eligibility matrix before you spend a dollar:</p>
<table>
<tbody>
<tr>
<th>Unit</th>
<th>Category available?</th>
<th>Address / service area</th>
<th>License</th>
<th>Insurance</th>
<th>Credential (if required)</th>
<th>Hours</th>
<th>Phone</th>
<th>Verification status</th>
<th>LSA eligible?</th>
</tr>
<tr>
<td>Unit 1</td>
<td>Y/N</td>
<td>Documented</td>
<td>On file</td>
<td>On file</td>
<td>Y/N/NA</td>
<td>Set</td>
<td>Unique</td>
<td>Pending / Verified / Failed</td>
<td>Y/N</td>
</tr>
<tr>
<td>Unit 2</td>
<td>Y/N</td>
<td>Documented</td>
<td>On file</td>
<td>On file</td>
<td>Y/N/NA</td>
<td>Set</td>
<td>Unique</td>
<td>Pending / Verified / Failed</td>
<td>Y/N</td>
</tr>
<tr>
<td>Unit 3</td>
<td>Y/N</td>
<td>Documented</td>
<td>On file</td>
<td>On file</td>
<td>Y/N/NA</td>
<td>Set</td>
<td>Unique</td>
<td>Pending / Verified / Failed</td>
<td>Y/N</td>
</tr>
</tbody>
</table>
<p>What this matrix forces you to confront:</p>
<ul>
<li><strong>Category and market availability differ by location.</strong> A service that’s LSA-eligible in one metro may not be in another. Don’t assume corporate “we do LSA” language means every unit can run it.</li>
<li><strong>Proof is local.</strong> Business license, insurance certificate, professional credential, and proof of address (or service-area documentation Google accepts for your category) are evaluated against the location — not against your brand’s national reputation.</li>
<li><strong>Hours and phone are operational inputs</strong>, not afterthoughts. If the unit can’t answer during advertised hours, you’re buying leads you can’t fulfill.</li>
<li><strong>Shared ownership ≠ shared eligibility.</strong> Acquiring Unit 4 does not automatically inherit Unit 1’s verified status.</li>
</ul>
<p><strong>[Universal]</strong> Only claim a real operating location you can substantiate. Fictitious storefronts, borrowed addresses, or “HQ only” profiles for units that don’t actually operate there are a non-starter.</p>
<p><strong>[Confirm with your franchisor]</strong> Whether LSA is an approved local channel, who may create/own the profile, and what NAP (name/address/phone) standards you must follow relative to Google Business Profile and the corporate directory.</p>
<p>If a unit fails eligibility, park LSA for that unit. Push demand through Search, Maps/local SEO, or referrals instead of inventing a presence. For broader local visibility context (not LSA ops), see <a href="https://leadppc.com/franchise/local-franchise-marketing/">local franchise marketing</a>.</p>
<h2>LSA Account And Profile Architecture: Shared Controls Vs Unit-Specific Details</h2>
<p>Think in two layers: <strong>operator-level controls</strong> and <strong>unit-specific profile facts</strong>.</p>
<p><strong>Shared (operator / brand governance)</strong></p>
<ul>
<li>Who may edit profiles and ads</li>
<li>Claim language and disclaimer standards</li>
<li>Reporting pack and KPI definitions</li>
<li>Refund / dispute review process</li>
<li>Escalation path when a unit’s reputation tanks</li>
<li>Brand photo / logo usage rules</li>
</ul>
<p><strong>Unit-specific (must stay local)</strong></p>
<ul>
<li>Legal business entity details where Google requires them</li>
<li>Address and service area</li>
<li>Hours and capacity windows</li>
<li>Phone number used for LSA calls</li>
<li>License, insurance, and credential documents</li>
<li>Photos that represent <em>that</em> location’s team and work</li>
<li>Reviews and response ownership</li>
</ul>
<p>Decision tree I use with 2–10 unit owners:</p>
<ol>
<li><strong>Distinct legal entities per unit</strong> → plan for separate documentation and cleaner handoff if you sell a unit later.</li>
<li><strong>Same entity, adjacent units in one metro</strong> → still keep service areas, phones, hours, and docs unit-true; don’t merge two operating locations into one LSA presence to “simplify.”</li>
<li><strong>Acquired unit mid-year</strong> → rebuild verification from that unit’s paperwork; don’t clone the old owner’s profile and hope.</li>
<li><strong>Unit may be sold in 12–24 months</strong> → architecture that lets you detach that profile without wrecking the rest of the portfolio.</li>
</ol>
<p><strong>[Universal]</strong> Follow current Google LSA / Local Services program rules for your category and market at launch time. Rules and verification flows change; re-check before you scale.</p>
<p><strong>[Confirm with your franchisor]</strong> Approved business name format on LSA (DBA vs corporate), logo use, and whether brand can require centralized admin access.</p>
<p>This is not the same decision as “one Google Ads account or many.” LSA profile legitimacy is about real local business presence. For Search/PPC account structure across units you own, the <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit advertising playbook</a> covers that layer.</p>
<h2>Lead Routing For Calls, Messages, Overflow, And One-Lead / One-Credit</h2>
<p>LSA sends <strong>calls and messages</strong>, not keyword clicks. Your routing plan has to survive real customers who live near a boundary, call after hours, or book at a different unit than the one that got the lead credit.</p>
<p>Minimum routing stack:</p>
<ul>
<li><strong>Unit-specific LSA phone numbers</strong> (or platform numbers mapped cleanly to units in your CRM).</li>
<li><strong>CRM fields:</strong> unit, source = LSA, market, disposition (qualified / booked / spam / out-of-area / duplicate).</li>
<li><strong>Overflow rule:</strong> if Unit A misses two rings during open hours, who gets it — Unit B, a central dispatch desk, or a missed-call text SLA?</li>
<li><strong>After-hours rule:</strong> voicemail + callback SLA, or overnight answering service with unit tagging — pick one and measure it.</li>
<li><strong>One-lead / one-credit:</strong> if the caller books at Unit B after Unit A’s LSA call, Unit A still owns the <em>lead cost</em> conversation; Unit B owns the <em>job</em>. Don’t let both dashboards claim the sale.</li>
</ul>
<p>Operational SLAs that matter more than vanity lead counts:</p>
<ul>
<li>Answer rate during open hours</li>
<li>Speed-to-first-response on messages</li>
<li>Qualified-lead rate (not just “lead”)</li>
<li>Booked job / patient / appointment rate</li>
<li>Refund / dispute success rate on spam and irrelevant leads</li>
</ul>
<p><strong>[Universal]</strong> Call-recording and SMS consent rules vary by state. If your answering path crosses state lines, use a clear recording announcement and get counsel to review all-party-consent exposure. Don’t freestyle this.</p>
<p><strong>[Confirm with your franchisor]</strong> Whether tracking numbers are allowed on LSA / GBP / web without breaking NAP standards, and who owns the customer record in the CRM.</p>
<p>If you can’t route a lead to a unit that can answer and fulfill, pause that unit’s LSA before you “optimize” budget. Misrouted LSA spend feels cheap until you look at booked outcomes.</p>
<h2>Per-Unit Floor, Cap, And Flex Budgets Tied To Capacity And Qualified Outcomes</h2>
<p>Do not run one shared LSA wallet across every unit and celebrate the blended cost per lead. LSA is lead-priced; your constraint is <strong>capacity and qualified outcomes by unit</strong>.</p>
<p>Use a per-unit budget sheet:</p>
<table>
<tbody>
<tr>
<th>Unit</th>
<th>Eligible?</th>
<th>Weekly capacity (jobs/appts)</th>
<th>Response rate</th>
<th>Qualified lead rate</th>
<th>Booked rate</th>
<th>Seasonality</th>
<th>Floor ($/mo)</th>
<th>Cap ($/mo)</th>
<th>Flex eligible?</th>
<th>Notes</th>
</tr>
<tr>
<td>Unit 1</td>
<td>Y</td>
<td>25</td>
<td>High</td>
<td>60%</td>
<td>35%</td>
<td>Peak</td>
<td>1,500</td>
<td>3,500</td>
<td>Y</td>
<td>Strong closer</td>
</tr>
<tr>
<td>Unit 2</td>
<td>Y</td>
<td>12</td>
<td>Med</td>
<td>45%</td>
<td>22%</td>
<td>Flat</td>
<td>800</td>
<td>1,500</td>
<td>Hold</td>
<td>Staffing thin</td>
</tr>
<tr>
<td>Unit 3</td>
<td>N</td>
<td>—</td>
<td>—</td>
<td>—</td>
<td>—</td>
<td>—</td>
<td>0</td>
<td>0</td>
<td>N</td>
<td>Verification failed</td>
</tr>
</tbody>
</table>
<p>Rules that keep this honest:</p>
<ul>
<li><strong>Floor:</strong> every <em>eligible, staffed</em> unit gets enough budget to stay visible — not enough to flood a thin team.</li>
<li><strong>Cap:</strong> if phones or operations can’t fulfill, stop buying leads for that unit no matter how pretty the CPL looks.</li>
<li><strong>Flex pool:</strong> reallocate only after comparing <strong>marginal cost per qualified lead or booked outcome</strong>, not raw lead volume. A mature unit’s lower CPL should not automatically vacuum every flex dollar if another unit has capacity and acceptable close economics.</li>
<li><strong>Lead cost ≠ sale economics.</strong> LSA lead price is the top of the funnel. Unit margin, ticket size, and close rate decide whether the next dollar is worth it.</li>
</ul>
<p>Experience-framed, not a promise: operators I work with often start with a tight pilot budget on 1–3 units, then expand floors only after answer rate and booked rate clear a written threshold. Cap monthly shifts so you don’t thrash learning — the same discipline we use on Search budgets in the <a href="https://leadppc.com/franchise/multi-location-franchisee-advertising/">multi-unit playbook</a>.</p>
<p>For paid-search tactics outside LSA, <a href="https://leadppc.com/franchise/local-franchise-ppc/">local franchise PPC</a> is the channel companion — keep LSA budgets and Search budgets on separate decision sheets so one channel’s CPL doesn’t launder the other’s story.</p>
<h2>Reviews, Screening, Badges / Guarantees, And Brand Governance</h2>
<p>Reviews are <strong>location-level operational assets</strong>. One unit’s service failure can stain brand perception, while LSA eligibility and reputation signals still get evaluated on that local profile.</p>
<p>Run reviews like ops, not like a hope strategy:</p>
<ul>
<li>Per-unit review request process (who asks, when, on which jobs)</li>
<li>Owner or manager response SLA (including negative reviews)</li>
<li>Escalation path for safety, legal, or brand-risk complaints</li>
<li>Screening readiness: can the unit pass background / business screening requirements for the badge or guarantee program in your category?</li>
</ul>
<p>Separate three things operators mash together:</p>
<ol>
<li><strong>Google’s program badge / guarantee language</strong> (whatever Google currently offers in your category — don’t invent the wording).</li>
<li><strong>Your franchise’s warranty or service guarantee.</strong></li>
<li><strong>Local offers and claims</strong> you want on the profile or in follow-up scripts.</li>
</ol>
<p><strong>[Confirm with your franchisor]</strong> Approved claim language, disclaimers, local offer rules, and who must approve profile copy before it goes live. Central brand governance exists so Unit 7 doesn’t invent a “lifetime guarantee” that corporate never authorized.</p>
<p><strong>[Universal]</strong> Don’t imply a guarantee or badge you haven’t actually earned under current program rules. Misrepresenting trust signals is worse than not running LSA.</p>
<p>If a unit’s reviews and response hygiene aren’t ready, fix ops first. Buying LSA leads into a reputation problem accelerates the damage.</p>
<h2>When Not To Use LSA — And Pilot / Stop / Scale Rules</h2>
<p>LSA is optional. Force-fitting it across every unit is how operators burn cash and patience.</p>
<p><strong>Don’t run LSA (yet) when:</strong></p>
<ul>
<li>The category or market isn’t available, or verification can’t be substantiated with real docs</li>
<li>The unit lacks a real eligible location, license, insurance, or required credential</li>
<li>Calls and messages can’t be answered quickly during open hours</li>
<li>Service areas overlap with no routing / overflow plan</li>
<li>Lead quality or close rate fails unit economics after a fair test window</li>
<li>Reviews, screening, or ops aren’t ready for public trust signals</li>
<li>Search demand is too thin to justify the admin and lead cost</li>
</ul>
<p><strong>Pilot / stop / scale rules I recommend writing down before launch:</strong></p>
<ol>
<li><strong>Pilot:</strong> 1–3 eligible units with clear floors/caps, tracking, and an owner of answer rate.</li>
<li><strong>Stop:</strong> miss answer-rate or booked-rate thresholds for two consecutive review cycles, or fail verification / compliance — pause that unit; don’t “average it out” with winners.</li>
<li><strong>Scale:</strong> only expand floors or add units after qualified and booked outcomes clear the written bar <em>and</em> capacity exists.</li>
<li><strong>Compare:</strong> keep LSA next to Search, Maps/local SEO, referrals, and other local channels. LSA doesn’t have to win every market to earn a seat — it has to win <em>its</em> seat on economics and ops fit.</li>
</ol>
<p>For location-level vendor and rollout thinking outside pure LSA ops, <a href="https://leadppc.com/franchise/franchise-location-advertising/">franchise location advertising</a> covers agency/economics context. Keep this page focused on how <em>you</em> operate LSA across units you own.</p>
<h2>FAQs</h2>
<p><strong>Can I use one LSA profile for every unit I own?</strong><br />
No — not if those are separate real operating locations. Eligibility and trust are location-true. One profile per legitimate operating location is the operating assumption.</p>
<p><strong>What if two of my units sit in the same metro?</strong><br />
Keep profiles and docs unit-specific, then invest in routing, overflow, and one-lead/one-credit rules. Overlapping service areas without a dispatch plan is how LSA budgets turn into arguments.</p>
<p><strong>How is LSA budgeting different from Google Ads budgeting?</strong><br />
You’re buying leads (and operational follow-through), not clicks. Caps should track capacity and booked outcomes, not blended CPL vanity.</p>
<p><strong>Who should own review responses — corporate or the unit manager?</strong><br />
Usually the unit manager with a brand escalation path. Corporate can set standards; the local operator lives the reputation.</p>
<p><strong>When should I pause a unit’s LSA?</strong><br />
Failed verification, weak answer rate, failed unit economics, or ops/reputation unreadiness. Pausing is a control, not a failure.</p>
<h2>Need Help?</h2>
<p>If you would like to speak with us about Google LSA operations across the units you own — eligibility, routing, unit budgets, and brand-safe profile governance — please fill out our <a href="https://go.leadppc.com/contact/">Contact Us</a> form.</p>
<p>We can also tie LSA into the wider multi-unit stack (Search, tracking, and capacity-aware allocation) without treating Local Service Ads as a mandatory channel for every location.</p>
<p>The post <a href="https://leadppc.com/franchise/google-lsa-operations-several-locations/">Google LSA Operations Across Several Locations: A Franchisee Playbook</a> appeared first on <a href="https://leadppc.com">Lead PPC</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://leadppc.com/franchise/google-lsa-operations-several-locations/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
