Google Shopping Feed Setup Perth

I'm Brad Farleigh, a Perth developer who builds and repairs product feeds. If half your catalogue is disapproved in Google Shopping, or the feed says a product is in stock when it isn't, the problem is in the data rather than in Google.

Email hello@bradfarleigh.com or use the live chat. I don't take phone calls, so everything is in writing from the start.

Get in touch

What a Shopping feed actually is

Google's merchant account holds your product data: ID, title, description, link, image, price, availability, brand, GTIN, condition, shipping and category. Google uses that data for free listings in the Shopping tab and as the product source for paid Shopping and Performance Max campaigns.

Feed work is data work. The feed has to describe exactly what is on the landing page, and it has to stay that way as prices and stock change. Most disapproval problems are a mismatch between those two things.

Where feeds break

• Missing product identifiers. No GTIN, brand or MPN, so Google can't match the product. You get "insufficient product identifiers" and no impressions.
• Image problems. Too small, watermarked, a promotional overlay, or a lifestyle shot where Google expects the product on a plain background.
• Price and availability mismatch. The feed says $49, the landing page says $45, and Google trusts the page.
• Shipping and returns not configured. Common in new accounts. Products stay limited until the settings exist.
• Variants handled badly. No item_group_id, so a shirt in six sizes looks like six unrelated products, or worse, duplicates.
• Category mapping left to guesswork. Google's own category and your internal product type are two different fields, and both matter for how products surface.
• GST handled inconsistently. Australian prices need to be the price the customer pays, tax included, and the same on the page.

What setup involves

1. Merchant account and business identity. Business details, contact information and domain verification through DNS, an HTML file or Search Console.
2. Shipping, returns and tax settings. Set for Australia first, then any other country you sell into. This is the step most new accounts skip.
3. Build the feed. A generated feed file on a schedule, a Google Sheets feed, a WooCommerce export, or the Content API. The choice depends on catalogue size and how often price and stock move.
4. Attribute mapping. Titles and descriptions written for how people search, not copied from the internal SKU name. Images checked against Google's requirements. Identifiers filled in properly.
5. Feed rules and supplemental feeds. Some fixes can't be made in the source system, especially on a platform you don't control. Feed rules handle those without a site rebuild.
6. Fix diagnostics until products are eligible. Work through disapprovals by cause rather than one product at a time.
7. Keep it in sync. Real-time price and stock through the Content API, or a fetch schedule short enough that stale data doesn't cost you sales.
8. Verify and hand over. Confirm products actually serve, document the feed source, and leave you able to change a title without calling me.

I fix the feed, not the campaigns

I don't manage Google Ads campaigns, Performance Max, bidding or budgets. What I do is make sure the data Google receives is correct, complete and current, and that the product pages match it.

If you need someone to run campaigns, that's a different job and I'll tell you so.

What does it cost?

Every job starts with the diagnostic: a review of the merchant account, the feed source, the diagnostics tab and the product pages behind the worst-performing items. Usually within 3 business days.

Then you get a fixed quote in dollars, not hours, and no GST is added. Work starts on a deposit. There's more on how a job runs on Working With Me.

Why work with me

• 17+ years of ecommerce work on WooCommerce, Maropost and Neto, plus custom builds where the feed had to be generated rather than exported.
• I work on both sides. The feed and the site that has to match it, which is where most mismatches come from.
• Data debugging is the job. The same skills that fix a broken GA4 event fix a feed full of bad identifiers.
• Diagnostic first. If your data is fine and the problem is elsewhere, you'll hear that.
• Remote and in writing. No phone calls.

Ready to fix your product feed?

Email hello@bradfarleigh.com or use the live chat, and tell me how many products are in Google Shopping and how many are actually serving. I'll book in the diagnostic.

Get in touch