WooCommerce × Google Merchant Center

A calmer, cleaner way to keep WooCommerce catalog data moving into Merchant Center.

MerchantFeed Pro helps stores generate, validate, and sync Google Merchant Center feed data with an explicit OAuth connection path, clear public documentation, and a reviewer-friendly trust surface.

Feed outputsXML + CSV
Google authOAuth-based
Public trust pagesDocs, privacy, support, terms
Review-ready surfaceStatic public site
01

Connect with consent

Merchants authenticate with Google through OAuth so account access stays explicit, revocable, and separate from store credentials.

02

Map the catalog

Configure WooCommerce fields, categories, and product attributes so feed data is shaped for Merchant Center requirements before export.

03

Generate with confidence

Create structured feed outputs and maintain a repeatable catalog workflow instead of patching exports manually each cycle.

Why this site exists

MerchantFeed Pro keeps the public story intentionally tight: what the plugin does, why Google access is requested, how merchants get support, and where privacy and legal terms are documented.

Clear privacy and support paths for Google OAuth review

Product messaging focused on Merchant Center-related functionality only

Static, readable public pages that explain setup and data handling without hype

What it solves

Built for catalog teams that want the feed layer to stay legible.

The product pitch is deliberately operational rather than flashy: cleaner exports, clearer mapping, and a public footprint that makes sense to both merchants and reviewers.

01

Structured feed generation

Generate XML and CSV outputs from WooCommerce products with attention to required Merchant Center fields and repeatable catalog formatting.

02

Attribute and category mapping

Translate store data into the feed structure Google expects, reducing cleanup work and helping merchants keep exports understandable.

03

Dedicated Google connection flow

The Google account connection is described and handled as a focused Merchant Center authorization flow rather than a broad account integration.

04

Validation-minded workflow

The product direction prioritizes feed correctness, policy-sensitive fields, and stable setup paths before more expansive automation is introduced.

Google access

Why Google access is requested

MerchantFeed Pro requests Google access only for the Merchant Center functionality needed to connect a merchant account and support feed operations. It is not intended to access Gmail, Drive, or unrelated Google account data.

  • Uses Google OAuth instead of asking merchants for Google passwords
  • Scopes should remain limited to what the Merchant Center integration actually needs
  • Access can be revoked by the merchant at any time through Google account settings

Approval posture

Signals a reviewer can validate quickly

Public documentation, privacy, support, and terms are available on the same domain.

Google access is described narrowly around merchant-authorized Merchant Center functionality.

Support contact and expected response window are clearly visible for merchants and reviewers.

Safeguards

Security and policy language stays narrow on purpose.

Google authentication happens through Google’s own consent flow rather than direct credential collection.

The site keeps privacy, support, and legal pages public so reviewers can validate the trust surface quickly.

Product language stays intentionally narrow: Merchant Center feed operations only.

Common questions

Short answers for merchants and reviewers.

What does MerchantFeed Pro do?

It helps WooCommerce stores generate and sync product feed data for Google Merchant Center so catalog information can be prepared for Google Shopping workflows.

Why does it need a Google connection?

The plugin uses Google OAuth so a merchant can explicitly authorize Merchant Center-related access without sharing account passwords.

What Google data is this site describing?

Only the data and access required for Merchant Center feed operations should be requested. Unrelated Google services are outside the intended scope.

Can merchants remove access later?

Yes. Merchants can revoke the app connection from their Google account security settings whenever they choose.

Documentation set

The public approval surface is live and easy to inspect.

Start with the setup guide, then review privacy, support, and terms. Each page is written to explain the intended Merchant Center connection without broad or vague claims.