Skip to main content
With your Google account connected, Rogus can send a feed’s products straight into Merchant Center instead of publishing a file for Google to fetch. You need a connected Google account first.

​
Two ways to reach Google

You do not need both. Pick whichever suits you.

​
Turning it on

Open a Google Shopping feed. The Google Merchant Center panel is on the feed page.
1

Generate the feed first

Rogus asks you to generate once before sending, so you can look at the products and the health report before Google does. The button stays unavailable until you have.
2

Press Send to Merchant Center

Rogus creates a data source in your Merchant Center account for this feed and sends the products across.
Only Google Shopping feeds can do this. A blank XML or CSV feed has fields you invented, and Google’s API has nowhere to put them.

​
What the panel tells you

Once sending is on, the panel shows:
  • Data source — the object Rogus created in your Merchant Center account for this feed
  • Live in Merchant Center — how many items Google currently holds from this feed
  • Last synced — when the last sync finished, or Syncing now…
  • Last sync — a breakdown: added, updated, removed, refreshed, and rejected by Google
Sync now sends changes immediately. Otherwise Rogus syncs on its own, and how often depends on your plan: On Pro and Scale the sync runs as soon as the feed has been rebuilt, so a change does not sit and wait once Rogus has picked it up. On Free, your products stay in Merchant Center and Rogus keeps refreshing them so they do not expire — but a change you make in Shopify only reaches Google when you send it yourself.

​
Status in Google

Below that, Rogus shows what Google has decided about your products: how many are approved, and a list of the problems Google reported with the number of products each one affects.
Google takes minutes to hours to process products. Right after a sync, items often show as still being reviewed.
Rogus updates these statuses in three ways, and you do not have to do anything for any of them:
  • When Google changes its mind. Google tells Rogus as soon as a product is approved or disapproved, and the status here follows within a few minutes.
  • After any sync that changed products, so you can see the result of a fix.
  • Once a day, as a safety net.
That last one is why the statuses stay right even if Google cannot reach Rogus for a while. Problems reported here come from Google, and are about your product data — a category that does not match, a missing identifier, a price that disagrees with your landing page. They are separate from what the Feed health tab shows, which is what Rogus itself found before sending.

​
The In Google tab

The panel tells you how many products Google is not showing. The In Google tab tells you which ones. It appears on a feed once you turn on sending, and lists every product this feed has in Merchant Center, one row each, with:
  • the product name — click it to open the product in Shopify
  • the item ID Google knows it by, which is what Merchant Center’s own screens show
  • Google’s decision
  • the problem Google reported, and which attribute it blames
  • when Rogus last sent it
Products with a problem are listed first. Use the Status filter to see one group at a time, or the search box to find one product.

​
What each status means

A problem here is a problem with the product’s data, and it does not stop the rest of the feed. The other products keep publishing normally. The fix is almost always in Shopify — correct the product, then generate and sync.
Very large catalogs show the first 500 products, problems first. The counts above the list always cover every product, so the number you see is the real one even when the list is shorter.

​
Only the changes are sent

Rogus keeps track of what it has already sent, and sends a product again only when something about it has actually changed. This matters because Google puts a daily ceiling on how much you can send. Sending only what changed means even an hourly sync stays comfortably inside it. Two things follow:
  • Products are refreshed even when nothing changes. Merchant Center expires a product 30 days after its last update, so Rogus re-sends products before they lapse.
  • Deleting a product in Shopify removes it from Google. Rogus notices it is gone and asks Google to remove it, rather than leaving a listing for something you no longer sell.

​
”Google’s daily quota was reached”

The sync stopped early because Google’s daily allowance ran out. This is not an error. The rest goes on the next sync. It usually happens on the first sync of a large catalog, when everything is new.

​
Stop sending

Stop sending disconnects this feed from Merchant Center. Rogus stops syncing it. Your products stay in Merchant Center. They are simply no longer refreshed, so they expire over the following 30 days. To remove them at once, delete the data source in Merchant Center itself. Your feed and its URL are unaffected — the file keeps generating and keeps serving.

​
If a sync fails

The failure and Google’s reason are shown on the panel. Common causes:
  • Access lost — reconnect on the Google page
  • The Merchant Center account is not ready — Google requires the account to be verified and set up before it accepts products
  • Everything rejected — nearly always one wrong setting affecting every product, such as a category. Look at the reported problems, fix the mapping, generate, then sync.
A failed sync leaves what is already in Google untouched.