Questions, answered.

Locationes is a web app for businesses that manage several Google Business Profile locations. It puts every location, review, profile gap, local ranking and report in one workspace instead of leaving them spread across separate Google accounts.

Any business with more than a handful of locations: retail chains, supermarkets, clinics, veterinary groups, EV charging networks, franchises, and the agencies that run local marketing for them. The product assumes several people touch the same locations, which is why store codes, regions and per-user permissions exist.

Google shows you one profile at a time. Locationes adds the layer above it: one review inbox for all locations, a single action list that ranks what needs attention, a comparable profile score, and reports that use the same definitions across locations. You keep your Google access and can still work directly in Google whenever you want.

Each owner, or whoever they have given manager access, signs in for their own office listing and grants access. The accounts then join the same workspace, with permissions managed per user, so a partner sees their office while the group keeps the portfolio view. No listing is rebuilt in Google.

The person who controls each Google listing signs in once and grants access, and the accounts are then connected to the same workspace. Access inside the app is managed per user, so a clinic owner sees their own location while the group keeps the portfolio view. No listing is recreated in Google and no review data is migrated.

One is enough. Accounts holding different sites connect to the same workspace, and per-user access lets each brand lead see their own branches while the group keeps both. Replies publish under the correct listing, and reports roll up across the estate.

Yes. The franchisee grants access from their own Google account, and the salon then joins the group workspace without giving up ownership. Per-user permissions decide what head office sees — usually everything — while the salon manager replies to their own branch.

Yes. Each Google account that holds store listings signs in once and grants access, and the listings stay where they are. Access inside Locationes is per user, so a franchise partner sees their own stores while the brand team sees the estate. No listing is rebuilt in Google and no ownership changes hands.

One workspace. Each Google account that holds showroom listings connects to the same workspace, and access is managed per user, so a brand manager sees their rooftops while the group lead sees all of them. No listing is rebuilt in Google.

Yes. The person who controls each listing signs in once and grants access, and the accounts join the same workspace. Access is per user, so a franchisee sees their desk while the brand team sees the estate. No listing is rebuilt in Google, and each owner keeps control of their account.

Yes. The person who controls each listing signs in once and grants access, and the branches then appear in the same workspace. Access is managed per user, so a franchisee sees their own shop while the network keeps the portfolio view. No listing is rebuilt in Google and no data is migrated.

Yes. Each account is connected with the consent of whoever holds manager access, and per-user permissions let a venue manager see their own site while the circuit keeps the group view. Replies publish under the correct venue, and no listing is rebuilt.

Each franchisee, or whoever they have given manager access, signs in once and grants access, and the listings stay theirs in Google. The accounts join the same workspace, and access inside Locationes is managed per user, so an owner sees their branch while head office sees the group. No listing is recreated and no ownership is transferred.

Whoever holds manager or owner access to the practice listings signs in and grants access; that is usually the group's marketing lead or the practice owner, not IT. Locationes reads reviews and profile fields and writes replies and edits back — it does not connect to clinical records. Access inside the app is then split per user, and two-step verification is available.

Each owner, or whoever they have given manager access, signs in for their own practice listing; the four accounts then join the same workspace. Access inside the app is per user, so a partner sees their practice while the group marketing lead sees all four. No profile is rebuilt in Google.

The person who controls each Google listing signs in once and grants access, and the accounts are then connected to the same workspace. Access inside the app is managed per user, so a center manager sees their own location while head office keeps the portfolio view. No listing is recreated in Google and no review data is migrated.

Yes. The person who controls each Google listing signs in once and grants access, and the stores then appear in the same workspace. Access is managed per user, so a regional manager sees their own stores while the group keeps the portfolio view. No listing is rebuilt in Google and no data is migrated.

Someone with manager access at each setting signs in and grants access, and the accounts join the trust workspace. Per-user permissions let the trust see every setting while a manager sees only their own. Existing profiles are read as they are; nothing is migrated or rebuilt.

Yes. Accounts holding different sites can be connected to the same workspace, and access is then managed per user, so each operator sees their own sites while the network team keeps the group view. Replies still publish under the correct listing, and no API project or migration is needed.

The account that currently holds the listing has to grant access; if the previous owner still controls it, they must add you in Google first. Once access exists, the clubs join your workspace and per-user permissions apply. Locationes cannot recover a listing from an account nobody in the group controls.

Yes. Each operator, or the person who controls the Google listing, signs in once and grants access, and the accounts connect to the same workspace. Access inside the app is per user, so an operator sees their own site while the network keeps the portfolio view. No listing is rebuilt in Google.

Each store's Google account is connected with the consent of whoever controls it, and per-user permissions then decide visibility: a franchisee sees their showroom, head office sees the estate. Replies publish under the correct store, and no listing is recreated.

Yes. Each franchisee signs in for their own listing and the accounts join the same workspace. Access is per user, so a franchisee sees their branch while the brand team sees the estate. No listing is rebuilt in Google, and each owner keeps control of their account.

Nothing beyond the standard Google authorisation: a person with manager access signs in and grants permission for each account, and no API project, credentials or sync job is needed. Per-user permissions and two-step verification then control who can change live profile data. The first action list is usually ready in the same session.

Only if someone who still controls the listing grants access — an owner who has withdrawn manager rights has to add you again in Google. Once access is granted, the property connects like any other, and per-user permissions decide who at the hotel can reply. Locationes cannot take over a listing whose access was removed.

Correct them rather than ignore them. Each old listing stays under its own Google account, so the person who controls it signs in once and adds it to the workspace. From there the hours, phone and description can be updated, and the alerts check flags a listing Google has marked closed or moved.

Yes. The person who controls each listing signs in once and grants access, and the campuses then appear in the same workspace. Access is managed per user, so an operator sees their own campus while the group keeps the portfolio view. No listing is rebuilt in Google and no data is migrated.

Whoever holds owner or manager access to the office listing signs in and grants access. Locationes reads reviews and profile fields and writes replies and edits back; it does not connect to case files, client records or billing systems. Access inside the app is per user, so a partner sees their office while the managing partner sees all six.

Yes. Locationes works from Google Business Profile, so the product does not depend on bed count, emergency cover or a hospital licence. What matters is how many listings you run and whether the departments, hours and services on them match the visit. A six-branch polyclinic and a hospital group use the same profile checks and the same review queue.

Yes. Each owner grants access from their own account and the stores join the group workspace; nobody hands over a password. Per-user permissions let an owner keep working in their own listing while the group sees the portfolio and its comparison reports.

Yes. The person who controls each listing signs in once and grants access, and the accounts connect to the same workspace. Access inside the app is managed per user, so a site manager sees their own lot while head office keeps the portfolio view. No listing is rebuilt in Google and no review data is migrated.

Yes. Each account connects to the same workspace, and access is managed per user, so a regional manager sees their region while head office sees every branch. No listing is rebuilt in Google, and the owner of each account keeps control of it.

Whoever controls the listing signs in once with a Google account and grants access, and the listings then appear in the same workspace. Inside the app, access is per user, so a clinic owner sees their own branch while the group lead sees all nine. Nothing is rebuilt in Google, and no review history is migrated.

Google does not split reviews by department, so Locationes tags each review to the centre and lets the team assign it to a department inside the app. The inbox filters by tag, the department lead sees what belongs to them, and the centre keeps one public rating. Nothing is copied between listings.

The franchisee, or whoever holds manager access to the office listing, signs in and grants access; the office then joins the network workspace without surrendering the account. Per-user permissions decide what the branch sees and what head office sees, and replies publish under the correct office.

Yes, as long as someone with manager access to each listing signs in and grants it. Accounts holding different branches connect to one workspace, and access is then managed per user, so the area manager sees their own sites rather than every login. Nothing is recreated in Google.

You sign in with each account that holds listings and grant Locationes access to the Business Profile data; the app then reads reviews and profile fields and writes replies and edits back through Google's API. No API project, credentials or data migration is involved. The first action list is usually ready in the same session, and ownership of the Google account stays with your team.

Yes. The person who controls each listing signs in once and grants access, and the clinics then appear in the same workspace. Access is managed per user, so a practitioner sees their own clinic while the group keeps the portfolio view. No listing has to be recreated in Google and no data is migrated.

The person who controls each listing signs in once and grants access, and the listings then join the same workspace. Access inside the app is per user, so an operator sees their own residence while the group keeps the portfolio view. No listing is rebuilt in Google, and no review history is migrated.

Signing in with each account that holds store listings, granting access, and choosing which stores enter the first workspace. There is no migration and no script to install; the app reads the profiles as they are. A 90-store estate usually takes more than one session, mostly because the accounts have to be found first.

The person who controls each Google listing signs in once and grants access. The accounts then sit in the same workspace, with access managed per user, so a franchisee sees their own branch while head office keeps the portfolio view. No listing is rebuilt in Google and no data is migrated.

The person who controls each Google listing signs in once and grants access, and the accounts are then connected to the same workspace. Access inside the app is managed per user, so a clinic owner sees their own branch while the group keeps the portfolio view. No listing has to be recreated in Google and no data is migrated.

Yes, for the offices you select. Opening hours, services and the description are per-location fields, so the seasonal schedule is one bulk update. Run the audit afterwards: it lists the offices still showing the old hours, which is usually where a partner edited the listing locally.

No, and the wording matters more than the intent. Thank the person, apologise for the experience and invite them to contact the clinic directly. Do not repeat the treatment, the device, the doctor's name in a clinical context, or the fact that a consultation took place. Locationes keeps approved wording in templates and lets you control which users can reply, but it cannot verify medical facts and does not decide the policy for you.

Yes. Bulk update applies to the locations you select, so the six weekend workshops get the extended Saturday and the other three keep their schedule. Run the audit afterwards; a workshop manager who edited their profile on Thursday will still show the old hours.

Search her name across the review list, reply at each branch with the same short answer, and update the services description where the menu referenced her. Reporting is per location, not per stylist, so the text filter is the honest way to see every review that names a person.

Hours are a per-location field, so each store keeps its own schedule. When a bank holiday or a late-opening event affects a group of stores, the new hours are applied to the selected locations in one update, and the audit lists any store still showing the old schedule. Photos and descriptions remain per store.

Reviews cannot be split by department in Google, so Locationes tags each review to the location and lets the team assign it to sales or service inside the app. The inbox filters by tag, and the reply templates differ: a trade-in question gets one, a parts delay another.

Thank the reviewer, apologise for the experience and invite them to contact the branch directly with the rental agreement. Do not confirm the rental, describe the vehicle or argue the claim in public. The detail belongs in the claims process. Templates carry the approved wording so the desk does not improvise at midnight.

Yes, for the branches you select. Hours are a profile field, so a bulk update applies the new schedule to all of them, and the audit afterwards lists any branch still showing the old hours. In practice that is usually a franchisee who edited their own listing, and the fix takes one more edit.

The profile carries opening hours, not a session list; a weekly showtime grid belongs on your site, with the website field pointing to bookings. Holiday hours are the part worth bulk-updating, because that is where a customer finds a closed door instead of a film.

Yes. Services, service areas, hours and description are per-location fields. A branch that only does offices lists office cleaning and the postcodes it covers; a home branch lists the residential services. A service that several branches share can still be applied to a selected group in one update.

The action list ranks unanswered negatives first and links each one to its branch, so nobody starts by reading the whole inbox. Templates cover waiting time, parking, a cancelled appointment and a bill query; the manager edits the personal part and sends. If the review is in another language, the reply window translates it before anyone writes.

Yes. Services is a profile field, so a bulk update applies the new treatment to the fourteen practices and the audit lists the ones still not showing it. Photos and descriptions stay per practice, because a practice's rooms and tone are local.

No. Thank the person, apologise for the experience and invite them to contact the center directly. Do not repeat the diagnosis, the treatment, the shift or the fact that someone attends the center. Approved wording lives in templates, and who can reply can be limited per user, but the product cannot verify clinical facts and does not set the policy for you.

Thank the customer, apologise for the wasted trip and invite them to call the store before their next visit. Do not promise that the item is in stock, confirm what was bought or name the employee. Templates keep the approved wording, and the detail moves to a private conversation.

Start with the action list: unanswered negatives come first, each linked to its setting, and templates cover fees and settling-in without naming a child. The setting manager writes the reply, because they know what changed; the trust sees the backlog shrink and the response times.

Filter the inbox to that site and search the text for connector, payment or blocked, then export the last 30 days for whoever schedules maintenance with the location attached. Locationes does not create work orders in a field system; the public reply stays with the team that owns the listing, and operations gets the fault detail.

With the unanswered negatives, then the bulk reply for the routine thank-yous. Location and rating filters let each club manager work their own queue, and monthly comparison shows whether the wave changed the rating or only the volume.

Hours are a per-site field, so select the stations that change and apply the new schedule in one update. The audit then lists the sites still showing the old hours, which is usually where a local edit has overwritten the change. Special hours cover public holidays and closures for repair.

Search the model name across the review list, export the batch for logistics, and reply at each store with one honest sentence: the container is delayed, here is the new date, here is the store number. The cause belongs to logistics; the wording belongs to whoever owns the listing.

No. Service area is a profile field, so the new postcode list can be applied to the branches you select in one update. The audit then lists the locations still showing the previous area, which is the check that matters when dispatch and the listing disagree.

Filter the inbox to that site, search the text for waiting, and export the period with the location attached for the operations director. The rating breakdown shows whether response time also slipped, and the heat map shows whether other sites in the same district moved at the same time.

Yes. Check-in details sit in the profile fields, so a bulk update covers the five properties and leaves the others untouched. Run the audit afterwards, because a property that edited the same field earlier in the week can override the change without telling head office.

Thank the person for the feedback, apologise for the experience and invite them to contact the practice directly. Do not repeat the diagnosis, confirm that they are registered or discuss a referral. Templates keep the approved wording, and the detail moves to a private conversation.

Yes, for the campuses you select. Hours and lesson slots are profile fields, so a bulk update applies the schedule you choose to each location, and the audit lists the campuses still showing the old timetable. A campus that edited its own listing afterwards will be flagged there.

Yes, and the templates are written for exactly that. Thank the reviewer, apologise for the experience and invite them to contact the office directly. Do not confirm representation, name a matter or repeat a court date. The reply stays public; the detail moves to a private conversation.

The inbox tags every review with its location, and access is per user, so the imaging lead can see the imaging branch without seeing the whole group. Routing to a department is a human step: the branch manager forwards the review or replies with the department's approved wording. The product does not split one listing's reviews by department, because Google does not.

Yes. Description and services are profile fields, so the change goes to the selected stores in one action and the audit lists any store still showing the old description. The usual cause is a store manager editing their own listing the same week.

The tariff itself is not a Google Business Profile field, so the price table belongs on your website and on the payment machines. What you can keep accurate in the profile is the hours, the services and the description, including a line that event pricing applies. For a review about a charge, reply with the lot number and a direct number rather than arguing the amount in public.

No. Hours are a profile field, so a duty or holiday change can be applied to the branches you select in one update. The audit then lists the pharmacies still showing the previous schedule, which is the check that matters when the rota and the listing disagree.

Locationes does not set a speed limit, but it measures the time to first reply per location, so the group decides the standard. Routine reviews about waiting time, parking or session price can start from a template and be sent by the branch manager. A complaint about a cancelled session or a member of staff needs a person with authority to offer a phone call. Translation covers reviews in languages the team does not read.

Yes. Services and hours are profile fields, so a bulk update applies the new clinic to the three centres you select, and the audit lists any location still showing the old timetable. That is usually a centre that edited its own listing, and it takes one more edit to fix.

Run the alerts check: duplicate and closed listings have their own categories, and this is exactly the change worth rechecking for. Locationes keeps both pins tracked while Google processes the move; removing or merging a listing is Google's decision, and replies should go only where the listing is still managed.

Yes, for the branches that share the schedule. Opening hours are a profile field and a bulk update applies them to the selection; the audit afterwards finds branches where a manager's earlier edit survived. Kitchen closing time belongs in the description, because it changes more often than the listing should.

Hours and services are profile fields, so a bulk update applies the change to the stores you select rather than the whole estate by default. Run the profile audit afterwards: a manager editing their own listing can override the change, and the audit is where those stores surface.

Yes, for the clinics you select. The menu is a profile field, so a bulk update applies the new services to all of them, and the audit lists the branches still showing the old menu. That is usually a clinic that edited its own listing, and it takes one more edit to fix.

Someone with authority to offer a phone call and to sign a name: a residence manager or a regional manager, not a central social media desk. Locationes measures the time to first reply per location and flags the reviews that mention a death, a fall or a complaint about care, so they do not sit in a general queue. Templates are kept for routine questions about tours, hours and fees.

Yes. Opening hours are a profile field, so a bulk update applies the holiday schedule to the 74 stores you select and leaves the rest alone. Run the profile audit afterwards: stores whose listings were edited by someone else in the same week will still show the normal schedule.

Yes, for the branches you select. Opening hours, services and the description are per-location fields, so the changeover is one bulk update. Run the audit afterwards: it lists the branches still showing the old hours, which is usually where a manager edited the listing locally.

Hours are a per-branch field, so the rota change goes out as a bulk update to the branches it affects and the audit afterwards lists any branch still showing the old cover. Run the alerts check too, because a location Google has marked closed will not be fixed by an hours edit.

Yes, and the reply should not repeat the detail. Templates are written so a public answer never confirms that someone is a client or discusses their affairs; the reviewer is thanked, the concern is acknowledged, and the conversation moves to a direct number. The original review stays in the archive with its text, rating and date.

Acknowledge that the experience was disappointing, do not evaluate the clinical claim and move the conversation to the phone. If the review contains personal data or breaks Google's content policy, report it through Google's own process; no removal is guaranteed and Locationes does not delete reviews. The archive keeps a copy if the review later disappears.

Filter the inbox to that workshop, search the text for wait, and export thirty days with the location attached. The reply goes out with one accurate line — the delay was real, the booking slot has been extended — while the pattern goes to operations. Locationes does not open jobs in a workshop system.

It is a pattern worth checking. The action list flags days when a branch receives a suspicious cluster of five-star reviews, because Google often removes reviews that arrive that way and a removed batch takes part of the rating with it. Locationes raises the flag; the decision about how the reviews were collected is yours.

Services and the description are profile fields, so the new drink can be added to the stores that sell it in one action and the audit shows where it did not land. A launch announcement can be scheduled as a Google post per store. Locationes does not publish a menu feed, so the drink list itself stays on your site and in the description.

Yes. Hours are a profile field, so a bulk update applies the new schedule to the locations you select, and the audit lists any rooftop still showing the old hours. Photos and descriptions stay per site, because the cars on the forecourt are local.

There is no automatic topic classifier, so the queue is ordered by rating, date and desk rather than by subject. The 1–2★ set is where deposit and damage reviews collect; filters and the archive keep them together, and the templates make the answer consistent. Review analytics then shows whether the share of low ratings falls after the process changes.

Thank the customer, say the network is looking into it and give the branch's direct number. Do not confirm the shipment, the courier's name or what was in the parcel. Templates keep the approved wording, and the detail moves to a private conversation.

Yes, through the posts calendar, which schedules Google posts per location rather than a single brand feed. It is also the fastest way to say a screen is back in service without waiting for reviews to ask, and a recheck before a premiere keeps the listing current.

Add the service to the three locations, update the descriptions in the same bulk action and run the audit. It lists any branch still showing the old service list, usually because someone edited the profile locally. The same audit and alerts check also catch locations Google has marked closed or duplicated, which is what a moved branch tends to leave behind.

Yes. Every review is archived from the first day the account is connected, so one removed from Google stays in the app with its text, rating, date and location. The deleted review report then shows how many were removed and how removals split by star rating. Nothing is restored — only Google can do that.

Keyword performance reports visibility per location, so the same term can be strong in one city and absent in another. Rank tracking adds position data for the treatment terms you choose, and impressions show whether the clinic appears in maps or only in search.

Reply in general terms, without confirming any of the detail, and move the conversation to the phone. If the review contains personal data or breaks Google's content policy, report it through Google's own process; removal is not guaranteed and Locationes does not delete reviews. If it is removed later, the archive keeps a copy with its original text, rating, date and center.

Yes, for the stores you select. Hours are a profile field, so a bulk update applies the schedule to each location you choose, and the audit lists any store still showing the old hours. A store that edited its own listing afterwards will be flagged there.

Yes. Hours are a per-location field, so a bulk update applies the term calendar to the settings that follow it and the audit lists the ones still on the previous schedule. The posts calendar can carry the closure dates, which is what a parent checks on the day.

The Google alerts check looks for locations Google has marked closed, along with duplicates, permission problems and account changes, and it runs live each time you open the page. Correcting the status is a Google process; Locationes keeps the finding linked to the site so nobody discovers it at the monthly report.

It can create the pattern Google treats as fake: many five-star reviews in a short window. The action list flags the cluster, and a removed batch takes part of the rating with it. The reviews may be genuine; the pattern is still what Google acts on.

The price itself is not a Google Business Profile field, so it stays with your forecourt systems and signage. What you can fix in the profile is the hours, the services and the description. For the review, reply with the site number and invite the driver to call, without arguing about the amount in public.

Yes, through the text filter: search a model name or a phrase like missing part and the list narrows to those reviews, which you can export for buying or logistics. It searches review text, not a product catalogue, so a model nobody wrote about will return nothing.