Fix a profile link that sends customers to the wrong branch

Follow the journey from the public profile

Open the branch that generated the enquiry rather than starting at your company homepage. Tap the public website link and inspect the name, location, service details, phone, and next action shown. A technically working page can still belong to the wrong branch.

Repeat the journey for any booking or ordering action actually supported by the profile. Keep those action links distinct from the main website field: Google's transaction-link guidance requires a dedicated destination for the relevant business or location and completion of the designated action. Do not assume the same generic page fits every field.

Identify where the branch context is lost

Write each step in a simple private path: profile, landing page, call or form, and confirmation. Mark the first step that changes location or silently selects a different team. A branch mismatch may be in the profile link, a website button, the booking provider, or the form's routing.

Ask the receiving team what happens to the resulting enquiry. If the correct page still sends a form to another branch's inbox, the public link is not the whole problem. Use a clearly labeled test request, and confirm it is received without introducing a real customer's private details.

Repair the exact destination and handoff

• Confirm the affected profile's true branch and service.
• Set the main website field to business-controlled information representing that location.
• Use a suitable location-specific action destination for a supported booking or order link.
• Correct website buttons, forms, or provider settings where branch context is lost.
• Test the full phone, form, or booking journey and the receiving team's acknowledgement.

Avoid a generic redirect that hides the choice

Do not send customers through a link shortener or unrelated social or messaging destination for a transaction link. Follow the action-link requirements and keep the relevant page usable. If the business offers several locations, make any customer branch choice explicit and ensure the intended one is clear.

Do not count a call-button tap, email draft, or form button press as a confirmed enquiry. A phone link must reach the right business team, an email route should address the intended inbox, and a form needs a delivered usable submission. These checks protect real operations without claiming a conversion problem from ranking data alone.

Measure misrouting after the fix

For a short review period, track anonymous counts of wrong-branch calls, forms transferred internally, and customers arriving at the wrong location. Recheck the public destinations after a website redesign, provider change, or branch move.

Measure success by correct customer context and delivery to the intended team. A higher website-click count is not enough to show the mismatch is fixed. Keep the profile's action metrics separate from confirmed location-specific enquiries and completed service.

Worked example

For example, a two-location repair business links the west profile to a booking page that defaults to the east shop. The owner follows the public journey on a phone and finds the first mismatch in the booking destination. They set the correct dedicated west destination, check the page's branch label, and submit a clearly marked test booking request. The receiving west team confirms it. This example demonstrates routing verification; it does not claim a measured conversion increase or that every profile supports booking links.

Questions about this task