Decide whether a second mobile-service base needs its own profile

Distinguish a service destination from an operating base

Write what happens at the proposed second base on a normal day. Identify staff who actually operate from it, equipment or dispatch arrangements, and the customers that team serves. A place where one technician sometimes stops is different from a separate location with a real team.

Then list the service area of the original operation and the proposed team's area. Do not begin with a wish list of towns where you want to rank. Start with how the business can serve customers reliably; a profile should describe that operation, not manufacture it.

Check Google's separate-location conditions

Google's service-area guidance allows profiles for different locations with separate staff and separate service areas. Each represented business location still needs to meet the applicable eligibility and address rules. A virtual or mail-only office does not satisfy the operational test by itself.

Review whether customers visit either base. If not, apply the service-area address-hiding requirements rather than exposing a private or non-customer-facing base. If a location also receives customers, assess the hybrid model independently. Do not assume one correct profile setup automatically validates every future location.

Make the operational case before adding a profile

• Document the actual location and what work happens there.
• Identify the separately staffed team and who answers its customer enquiries.
• Define its real service area alongside the original team's area.
• Check whether the public contact and website destination represent the correct location.
• Only add a profile after the location independently meets the rules, and complete the offered verification honestly.

Avoid adding extra profiles for coverage alone

Do not use one profile per city served by the same roving team, add a friend’s address as a second office, or create separate profiles for different services from the same business. Those choices confuse locations with marketing targets and can produce duplicate or ineligible listings.

Keep internal routing clear. If both profiles send customers to one number, the business must still control the contact route and reliably connect callers with the right operation. A shared administrative function does not erase the need for a truthful location representation and customer expectations.

Review branch performance without confusing identity

Use a branch-specific private log for confirmed enquiries, service delivery, and misrouted calls. Compare those operational outcomes with each profile's interactions only after the location and access setup are correct. Keep the same location identity in your reports so results are not merged simply because the business name matches.

Recheck eligibility when staffing or operations change. If a second team closes and the original team resumes all travel, review the affected profile rather than leaving a dormant map presence. The useful outcome is accurate representation of genuinely separate operations, not a guaranteed increase in coverage.

Worked example

For example, Hemlock HVAC has one mobile team and considers a second profile in a town it already visits. A mailbox plan and the same traveling staff do not establish a second operation. In a different hypothetical plan, the business creates a real separately staffed base with a defined service area and branch-specific customer routing. The owner reviews that actual arrangement before adding a profile. The illustration tests operational facts; it is not a recommendation to open branches merely to obtain map pins.

Questions about this task