One back office, two fronts
The briefing recommends running a single shared back office for admin, billing and reviews while keeping separate front ends — distinct service pages, photos and review flows — for landscaping and fitness. That alignment reduces duplicated admin work and makes it easier for Google and customers to understand two different service offers from the same company. The key technical detail is matching on-site schema and NAP data to the Google profile so the search signal stays consistent. ( )
A small business can save money by sharing one office team and still look like two different businesses online, but only if Google sees the same real-world identity behind both offers. Google’s Business Profile rules say your profile should represent the business “as it’s consistently represented and recognized,” while categories tell Google what the business does. (support.google.com, support.google.com) That is why the split usually happens on the website, not in the bookkeeping. One company can keep one admin stack for invoices, scheduling, and staff, while publishing separate service pages for landscaping and fitness so customers do not land on one mixed page that tries to sell lawn edging and personal training at the same time. (support.google.com, biziq.com) Google already gives businesses a way to organize different offers inside one profile. Its services editor lets owners group services under the appropriate category, add descriptions, and in some cases show those services directly on the profile when local customers search. (support.google.com) The website has to reinforce that same structure in machine-readable form. Google’s Local Business structured data documentation says structured data is a standardized format for classifying page content, and local business markup can describe hours, reviews, and even different departments. (developers.google.com) That markup comes from Schema.org, which defines “LocalBusiness” as a specific physical business or branch and includes fields for address and identity links. In plain terms, schema markup is the label on the box, and Google uses that label to decide whether the page is about a gym service, a lawn service, or a general company homepage. (schema.org, schema.org, schema.org) The fragile part is the contact data. BizIQ’s local SEO guides keep repeating the same point: name, address, and phone number have to stay consistent across the site and local listings, because mismatched details weaken local search signals instead of strengthening them. (biziq.com, biziq.com, biziq.com) Photos and reviews should split by service even if the payroll login does not. Google’s profile tools let businesses manage photos, services, and reviews in one place, but customers use those signals to judge whether a profile really matches the job they need, so landscaping photos belong with landscaping pages and fitness testimonials belong with fitness pages. (support.google.com, developers.google.com) That is the whole playbook: one back office for cost control, two front ends for clarity, and one set of business facts everywhere Google looks. When the profile category, on-site schema, and name-address-phone details all match, Google gets a cleaner local search signal and customers get a cleaner choice. (support.google.com, developers.google.com, biziq.com)
