Opening another location creates a second public record
The new branch page says the doors open on Monday. The Google Business Profile shows different hours, a directory lists the head office phone number, and a customer follows directions to an entrance that isn't ready. Each item may look small to the team publishing it. Together they create an unreliable location record at the moment the branch needs to earn trust.
Opening an additional staffed location is different from moving an existing one. The parent business continues, while a new customer-facing place, page, profile and measurement context must be established. If you're replacing one operating address, use the business relocation search visibility checklist instead.
This checklist begins after the business has approved an additional staffed location and runs through its first 90 days. Permanent closure, acquisition, rebranding and legal registration need separate plans. Treat inherited rankings, transferred reviews, immediate verification, Knowledge Panel changes and AI citations as outside the launch team's control.
Confirm what kind of expansion you're launching
Classify the operating model before creating a page or profile. A wrong classification carries through to the address, website structure, structured data and external listings.
- A customer-facing branch is a real location where the business's staff receive customers during stated hours.
- A service-area expansion extends where an existing team travels. It doesn't automatically create another physical location.
- A department is a distinct public-facing operation within a larger business and may have different eligibility requirements.
- An individual practitioner is a public-facing professional with their own customer relationship and may qualify under separate practitioner rules.
- A franchise, new brand or separate legal entity may need a different identity and ownership model, even when it shares premises or management.
Google's current guidelines for representing a business require accurate real-world representation. They say not to create more than one profile for each location, while separate staffed service-business locations may each be eligible for a profile. Departments and practitioners have their own conditions.
Address visibility also depends on how customers are served. Google's business address guidance says the address should represent a real location and that service-area businesses should hide an address when customers aren't served there. An eligible branch needs a real operating location rather than a virtual office, mail receiving address or future lease.
If the team can't tell whether the expansion is a location, service area, brand or entity, pause the release and work through how search systems understand the business. False certainty here creates expensive corrections later.
Create one approved record for the new branch
Launch facts often change between lease signing and opening day. Hours move, phone routing isn't finished, access instructions change and the public opening date slips. Give the branch one controlled record so the website, profile and external accounts aren't working from different documents.
Record the public business name, relationship to the parent, address or service area, local phone, staffed hours, opening date, available services, canonical branch page URL and Business Profile owner. Add the person who can verify each fact, the person authorised to release it and the date on which it becomes true.
The parent business record remains important. Google's Organization structured-data guidance supports administrative details and multiple applicable addresses. Keep the organisation's canonical identity maintained while giving the branch its own accurate location record. The organisation schema guide explains how to model that parent identity without turning launch week into a schema rewrite.
This approval method is an Off Piste governance recommendation, not a Google requirement. It gives every publishing team the same source and makes last-minute changes traceable.
Build the branch page around real customer decisions
The branch page becomes the owned source for that location. Give it a stable URL and enough specific information for a customer to decide whether this is the right place to contact or visit.
Show the approved name, address when public, phone, staffed hours and locally available services. Add directions, entrance and accessibility details, parking or public transport information, service limitations and a clear enquiry route where these are useful. Local staff, photographs and evidence of work can make the page more useful when they're genuine and maintained. Replacing the suburb name in generic copy doesn't do that job.
A business with several branches may also need a location finder or an index page. Its purpose is to help people choose a branch, while each branch page answers the detailed visit and contact questions. Link the new page from relevant navigation, service pages and the parent organisation context so it isn't an isolated URL.
Google's LocalBusiness structured-data documentation says to define each local business location as a LocalBusiness type and supports a URL for the specific business location. Markup should reflect facts people can see on the page. Use the existing LocalBusiness guide for real locations and service areas for subtype, privacy, identifiers and multi-location implementation rather than copying code from another branch.
If the CMS can't support stable branch URLs, reusable fields, local navigation and controlled updates, the constraint is the site's content model. A location-ready website design can resolve that architecture before more branches multiply the problem.
Prepare an eligible Business Profile
Create a Business Profile only after confirming that the location and operating model meet current requirements. Connect the approved business name, primary category, address visibility, local phone, customer-facing hours and website URL to the same branch record used by the website.
Google asks chains and brands to maintain consistent names and categories across comparable locations, unless their real-world representation or operation genuinely differs. It also asks for a phone number or website that represents the individual location. Don't add a suburb, service or marketing phrase to the profile name unless it is part of the established real-world name.
Confirm ownership and manager access before launch. Keep truthful evidence of signage, staffing and the operating location available if Google requests verification. The route and timing can vary, so record the verification state without announcing a completion date the platform hasn't confirmed.
Opening a second branch doesn't move the first branch's reviews or local visibility into the new profile. Treat the new profile as a separate customer record and follow the Google Business Profile guide for ongoing categories, content, reviews and optimisation after the launch setup is complete.
Capture a separate baseline for the new market
The established location provides business context. Set a fresh performance baseline for the branch. Google says local results are mainly shaped by relevance, distance and prominence. A new branch serves a different geography with different nearby customers, competitors and demand. Measuring that market separately avoids assuming another location's visibility will carry across. That's an inference from Google's framework, not a stated transfer rule.
Before launch, record whether the branch page is accessible and indexable, how the brand currently appears for location-specific searches and which prominent external sources already mention the new branch. Sample representative queries from documented locations. Preserve the query, device, date and measurement location so later checks have usable context.
Connect branch-level calls, forms, bookings and direction requests where those measures are available and appropriate. Test the routing rather than merely confirming that a tracking tag exists. Don't forecast rankings or lead volume from the established branch, and don't compare results gathered from different places as if they were equivalent.
Release the location across controlled systems
Order matters because every external release should point back to an approved owned source. The following sequence is Off Piste editorial judgement, not a platform requirement.
- Publish the branch page and confirm its visible facts, directions, contact routes and opening status.
- Deploy the location-level structured data, then validate that its facts match the rendered page.
- Connect the branch through navigation, relevant services, the location index and the parent business context.
- Create or update the eligible Business Profile from the approved record and begin any required verification.
- Test calls, forms, bookings, directions and branch-level measurement from a customer's path.
- Release the approved facts to other profiles and accounts the business controls.
- Record the visible outcome, owner and evidence for each system instead of marking a submission as complete.
Keep an exception log when a platform formats an address differently, suppresses a field or leaves an update pending. Consistent meaning matters more than forcing identical text into systems with different fields. A submission receipt proves an action was attempted. It doesn't prove the public result is correct.
Correct external signals after the source is live
Once the branch page and eligible Business Profile show the approved facts, review external sources in priority order. Start with maps, major directories, review platforms, industry profiles, social accounts and partner pages that customers actually use. Correct the records most likely to send somebody to the wrong place or present the wrong contact details.
Don't create a large listing campaign before the branch source is stable. It spreads uncertain facts and makes later correction harder. Exact wording doesn't need to be mechanically identical across every publisher, but the underlying identity, location, phone, hours and parent relationship shouldn't conflict.
Use the third-party business signal audit to inventory sources, set priorities and record correction evidence. That guide covers the full remediation method. The launch checklist only establishes when that work should begin.
Check opening week and the first 90 days
A launch isn't complete when every form has been submitted. Customers and search systems need to encounter the intended facts in the live environment. Off Piste recommends the following review cadence as a practical governance method, not as a Google processing timetable.
Opening week. Test the branch journey on mobile and desktop. Check the page, profile state, calls, forms, bookings, directions, opening hours and prominent map results. Fix customer harm first.
After 30 days. Review page indexing, profile verification state, material fact mismatches and high-priority external records. Compare discovery and conversions with the branch's own baseline using the same geographic method.
After 60 days. Recheck unresolved corrections, local query samples and contact routing. Look for repeated customer questions that the branch page should answer.
After 90 days. Review the branch as an operating location rather than a launch project. Confirm long-term owners, retire temporary launch checks and move recurring evidence into the business information monitoring framework.
Keep each observation dated. Search results and platform states change, and a screenshot without a query, location or date doesn't provide a reliable comparison.
Know when the launch needs a broader plan
Pause a routine rollout when eligibility remains unclear, several brands or legal entities share the premises, the CMS can't represent locations properly, or nobody has access to the profile and measurement systems. Those are planning and ownership problems, not boxes to skip on launch day.
Start by resolving the approved branch record and its relationship to the parent business. When profile eligibility, local visibility, external signals and measurement need coordinated ownership, an SEO plan for the new location can bring those decisions into one release. Website architecture work is warranted when the content model itself can't support useful branch pages and reliable updates.
A well-run launch doesn't guarantee a position in search. It gives customers, staff and search systems one defensible account of the new location, then provides the evidence needed to find and correct what diverges.