HighLevel Adds Google Merchant Center Sync: What Actually Syncs

August 17, 2026. HighLevel shipped a Google Merchant Center app on August 14, letting an account connect its Ecommerce Store to Merchant Center and sync eligible products to Google Shopping and other Google surfaces. For any agency running stores inside HighLevel, this closes a gap that previously meant a manual feed or a third party connector. It also arrives with a set of boundaries stated plainly in HighLevel's own release note, and three of them will decide whether the thing you promise a client is the thing they get.

What HighLevel shipped

1. A Marketplace app, not a core setting. You install Google Merchant Center from Marketplace, connect a Google account, then pick the Merchant Center account and the Ecommerce Store to link.
2. Only products assigned to the connected store sync. Products belonging to other stores, or products not assigned to the connected store, are not sent.
3. A data source named leadconnector is created for you. It is built using the country and language configured for the shipping origin.
4. Updates keep flowing after setup. Supported changes to product information, pricing, inventory, images and variants continue syncing automatically, with a Force Sync for manual refreshes.
5. One store maps to one Merchant Center account. Multiple mappings are supported across an account, but once a store or a Merchant Center account is used it cannot join another mapping until the existing connection is removed.

Three limits that change the scope of work

The supported list is short and it is a boundary. HighLevel names one time payment products and digital products as supported. It does not name recurring or subscription products anywhere in the release note. Plenty of HighLevel stores sell memberships, coaching retainers and course access on recurring billing, so confirm what actually lands in the feed before you tell a client their catalogue is on Google.

Deleting the data source deletes the listings. HighLevel states that removing the leadconnector data source removes the synced products, and that a new one can be created with Force Sync. Merchant Center accounts collect stale data sources, and tidying them up is exactly the kind of housekeeping a client or a paid media freelancer does without asking. Label it and say so in the handover document.

The locale comes from the shipping origin. The data source is created using the country and language configured for the shipping origin rather than the market being sold into. For a store that ships from one country and sells into another, check that pairing on day one instead of debugging disapprovals in week three.

This buys free listings, not paid campaigns

The release note says the integration syncs products with Merchant Center but does not create or manage Google Ads campaigns. That sentence is easy to skim and expensive to misread in a proposal.

Google's own documentation on free listings for products is that unpaid product listings run from the Merchant Center data source with no Google Ads spend attached, while Shopping ads and Performance Max are configured separately in Google Ads and billed on clicks. So the deliverable here is eligibility for the free surfaces. A paid Shopping build remains a separate scope line and a separate budget.

The second thing to fix in your reporting: HighLevel surfaces errors and warnings during and after linking, but Google reviews the submitted products and decides approval and eligibility. Synced is not live. Report approved products, not synced products, or your first status update will be wrong in the client's favour.

What it means for operators

Do this in order. Audit which products are actually assigned to the store you intend to connect, because assignment is the filter. Check whether any revenue sits in recurring products before you scope the work. Verify the shipping origin country and language against the market you sell into. Then baseline your reporting on Google approvals rather than on the sync counter, and annotate the date, since free listings move impressions without moving spend.

We build and maintain GoHighLevel systems for agencies and handle the feed side of ecommerce operations, including the part where a clean product catalogue is the actual prerequisite rather than the integration.