SynupHelp Center
Browse help
LOCATIONS

Use publisher overrides

How do I make a field different for one publisher?

An override lets one publisher carry a different value while every other publisher keeps the shared one. You create it from that publisher's tab, using Edit — and the drawer that opens can write either scope, so the button you press is the decision: Save for Google writes the Google-only exception, Save to Master changes the record everyone gets. Picking the wrong one is the whole risk in this workflow.

Key facts

Where it livesA location → a publisher tab (Google, Facebook, Apple, Bing) → Edit
Drawer titleEdit details — Google, with Override for Google only. Switch on the left.
Scope switcherMaster (syndicates to all), Google, Facebook, Apple, Bing — on the left of the drawer
Write the exceptionSave for Google
Write the shared recordSave to Master
Undo the exceptionThe tab row's ⋮ → Reset Google to Master
Not connected yetThe tab reads Not connected — saved here, will publish on connect

Why this matters

An override is the right tool for a narrow set of cases: a publisher that enforces its own name format, a call-tracking number you want only on one directory, a landing page that should differ for one channel. It is the wrong tool for a correction. If the value is simply wrong, it is wrong everywhere, and fixing it on one tab leaves every other publisher stale.

The cost of an override is that it is silent and permanent. Once Google carries its own phone number, updating the shared record will not change it, and nothing on the Master tab announces that an exception exists.

Steps

  1. Open the location and click the publisher's tab. The caption confirms the scope you are now in — What Google Business Profile shows. Edits here apply to Google only.

    Location editor with Master and Google publisher tabs annotated above the Master identity explanation

    ① Master is the shared/default record. ② Google is where a Google-only value can override it; Facebook, Apple and Bing follow the same model.

  2. Click Edit. Check the left-hand switcher and the footer caption before typing: the drawer can write either the publisher exception or the shared record, and the footer tells you which one is currently in scope.

    Edit details for Google drawer with the publisher switcher on the left and Save to Master and Save for Google buttons

  3. Change only the field that genuinely needs to differ. Everything you leave alone keeps inheriting from the shared record, which is what you want.

  4. Commit with Save for Google. Use Save to Master only if you have realised the change belongs everywhere after all.

  5. If you are changing name, address, phone, primary category or website, Synup interrupts with Update core business info? before saving. Read it: for a connected location this pushes to the live listing and may trigger Google re-verification. Cancel stops the save; Save anyway continues it.

    Update core business info dialog warning that the change pushes to the live listing, with Cancel and Save anyway buttons

  6. To remove the exception later, open that publisher's tab and use ⋮ → Reset Google to Master. The publisher goes back to inheriting the shared values.

    Publisher tab row with the overflow menu open on Reset Google to Master

What you'll see when it's done

  • The publisher tab shows the overridden value while the Master tab keeps the shared one
  • Other publisher tabs are unaffected
  • Where the publisher is not connected yet, the tab reads Not connected — saved here, will publish on connect, and the value is held until it is
  • After a reset, that publisher's fields match Master again

Watch out for

The drawer opens from a publisher tab but can still write the shared record. Its title says Override for Google only while the footer describes the Master scope, so confirm the scope on the left and use Save for Google deliberately rather than pressing whichever button is nearer.
Reset Google to Master applies as soon as you choose it — there is no confirmation step, and it clears that publisher's overridden values rather than the single field you had in mind. On a tab carrying several Google-specific values, expect to lose all of them.
Overrides are invisible from the Master tab. Nothing there flags that a publisher is diverging, so an override set months ago will keep quietly overriding shared updates. Note them somewhere, or check the publisher tab when a change fails to appear.
Publishers apply changes on their own schedule. Saving an override does not mean the live listing has changed yet.

Questions people ask

Should I override or fix the shared record?

Override only when the difference is intentional and permanent for that one publisher. If you are correcting a mistake, fix the shared record so every publisher gets it — see updating name, address and phone.

Can I override the business name for one publisher?

Yes — the drawer exposes the full identity and address for each publisher. It is rarely a good idea, because inconsistent names across directories are exactly what weakens the match, but the capability exists for publishers that enforce their own format.

What happens if I save an override on a publisher that isn't connected yet?

It is stored against that publisher and held. The tab tells you so directly: Not connected — saved here, will publish on connect.

Why did Synup ask me to confirm before saving?

Because the field you changed is one of the core business details — name, address, phone, primary category or website. On a connected location those push to the live listing and can trigger re-verification with Google, so the confirmation is there to make that consequence explicit.

Next

For the shared record these exceptions sit on top of, see updating name, address and phone. To check what each publisher will actually receive, see previewing publisher-specific values. To send pending changes onward, see publishing saved location changes.