Google Merchant Center Audit Template: 65-Point Checklist
Ishant
Published : August 22, 2026 at 10:07 am
Updated : September 11, 2026 at 7:29 am
Ishant
Ishant Sharma is the Founder and CEO of Hustle Marketers, a Google Partner digital marketing agency. With 12+ years of experience in Google Ads, Meta Ads, SEO, and e-commerce PPC, he has helped 2500+ brands generate $780M+ in trackable revenue. Upwork Top Rated Plus with 99% Job Success Score. Ishant Sharma is the digital marketing specialist, not the Indian cricketer of the same name.
Summarize this blog post with:
FREE TEMPLATE + IMPLEMENTATION GUIDE
A practical audit framework for finding product-feed, policy, pricing, tracking and campaign-readiness problems, then assigning every correction to the right system and owner.
Key takeaways
A Google Merchant Center audit should do more than identify errors. More importantly, it should show where each correction belongs, who owns it, what blocks it and how the team will verify completion.
- The template contains 65 checkpoints across 14 audit areas.
- Every open item receives a priority, owner, correction location and next action.
- Teams should normally correct product data in the governing source, such as the ecommerce platform, feed platform or persistent attribute rule.
- In addition, auditors should group disapprovals by issue type instead of handling them product by product.
- A separate scorecard turns technical findings into a clear client update.
Download the template: Create your own Google Sheets copy. The link opens a copy screen, so your audit data remains in your own Drive. You can also open the view-only version first.
What is a Google Merchant Center audit?
A Google Merchant Center audit systematically reviews account configuration, product data, data sources, item issues, pricing, images, shipping, returns, reviews, promotions and measurement. Its purpose is to identify anything that can restrict product eligibility, weaken listing quality, reduce reporting reliability or prevent teams from segmenting campaigns effectively.
Merchant Center reflects information supplied by several connected systems. Those can include the ecommerce platform, a feed-management app, scheduled files, website structured data, account-level settings and Google Ads. The audit therefore needs to identify both the visible issue and the system that governs the correction.
If an audit does not identify the owner, correction location and verification step, it has recorded an observation rather than created an action plan.
What the 65-point audit covers
| Audit area | Checks | What it protects |
|---|---|---|
| Account setup | 7 | Verification, linking, access and account-level risk |
| Feed setup | 7 | Source processing, submitted count and destination coverage |
| Product data | 11 | Identifiers, variants, categories, attributes and segmentation |
| Titles and copy | 5 | Relevance, clarity and product-description hygiene |
| Images | 5 | Image compliance, resolution and additional-image coverage |
| Pricing | 4 | Landing-page consistency, sale pricing and tax accuracy |
| Disapprovals | 4 | Issue triage, crawler access and policy investigation |
| Shipping and returns | 4 | Delivery accuracy and policy consistency |
| Store quality | 5 | Contact details, checkout clarity and customer policies |
| Reviews | 3 | Store Ratings and Product Ratings readiness |
| Promotions | 2 | Offer accuracy and promotion eligibility |
| Free listings | 2 | Eligibility for unpaid product surfaces |
| Tracking | 3 | Tagging, purchase measurement and revenue reconciliation |
| Campaign readiness | 3 | Custom-label segmentation and product activation decisions |
| Total | 65 | Complete Merchant Center and Shopping readiness review |
Why most Merchant Center audits stall
The account-issues screen reports symptoms. For instance, it may show that several products have image overlays, a price mismatch or missing identifiers. However, it does not necessarily explain which connected system supplied the incorrect value, who can change it or what delays the correction.
For example, an image-overlay issue may require a designer to produce a clean primary image, a store administrator to replace it and a feed specialist to confirm the new submission. Treating the issue as a Merchant Center-only task leaves those dependencies invisible.
The tracker prevents this by requiring four operational fields:
- Where to check: the screen, report or source used to confirm the problem.
- Where to fix: the system that controls the governing value.
- Owner: the person or team responsible for implementation.
- Verification: the evidence the team needs before marking the item complete.
Where should Merchant Center issues be corrected?
There is no universal rule that every correction belongs outside Merchant Center. Instead, the best location depends on the submission method and the source with authority. As a general principle, correct reusable catalogue data in the system that governs it and use Merchant Center settings or rules when they provide the intended persistent control.
| Issue type | Preferred correction location | Why |
|---|---|---|
| Incorrect title, description or variant value | Ecommerce platform or feed platform | Keeps catalogue data consistent across future submissions and channels. |
| Custom labels used only for Google Ads | Feed platform, supplemental source or attribute rule | Supports campaign segmentation without changing customer-facing product data. |
| Price or availability mismatch | Store and primary data source | The landing page and submitted value must remain aligned. Automatic updates are a safeguard, not a replacement for accurate source data. |
| Shipping or return configuration | Merchant Center and website policy pages | Account settings and customer-facing claims must describe the same offer. |
| Merchant promotion | Merchant Center promotion setup and website | The submitted offer, eligibility, dates, code and landing page must agree. |
| Temporary exception | Direct edit or controlled rule, where appropriate | Useful for an urgent correction, but the tracker should stay open until the governing source is resolved. |
Important: Direct product edits do not disappear automatically in every configuration. Persistence depends on the data source, source precedence, attribute rules and automatic updates. Moreover, Google documents persistent attribute rules that teams can apply during future uploads.
How the three audit tabs work
Tab 1: How to Use
This reference tab defines the priority levels, status values and column responsibilities. It establishes one consistent language for the auditor, implementers and client.
Tab 2: GMC Audit Tracker
Each checkpoint occupies one row. The template prefills the checkpoint, area, check location and correction location. Then, the auditor records the priority, status, finding, completed work, blocker, next action, owner and completion date.
Tab 3: Scorecard
The scorecard summarizes completion by priority and audit area. It also highlights open Critical and High items and tasks blocked by people outside the advertising team. Any weighted score is an internal management signal, not a metric supplied or endorsed by Google.
Audit priority comparison
| Priority | Use when | Target response | Typical examples |
|---|---|---|---|
| Critical | Products cannot serve, the account is at risk or measurement is materially unreliable. | Investigate today | Account suspension, widespread price mismatch, broken purchase tracking |
| High | The issue materially limits visibility, data quality or profitable segmentation. | Correct this week | Missing GTINs, incomplete variants, major product-count gap |
| Medium | The issue reduces listing quality or prevents an optimization opportunity. | Plan this month | Weak titles, missing additional images, incomplete custom labels |
| Low | The improvement is useful but does not currently restrict core performance. | Complete after higher priorities | Naming cleanup, reporting refinements, optional programme review |
The four issues that most often block performance
1. Store catalogue versus submitted product count
First, compare the number of products the store publishes with the number submitted and eligible in Merchant Center. Feed-app selection rules, destination settings, plan limits, availability filters, market configuration or store-level publication settings can cause a large difference.
2. Submitted price versus landing-page price
Next, confirm that the submitted price and sale price represent the live offer. Do not use the compare-at price as the active price. Google can use website data to apply certain automatic updates. However, Google intends those updates to correct temporary inaccuracies affecting a small portion of products, not to replace regular accurate submissions. See Google’s guidance on automatic product updates.
3. Primary-image compliance
After that, inspect the primary image for promotional text, watermarks, borders and low resolution. Additional images can present lifestyle angles or details, but the primary image should show the product clearly and comply with the applicable image requirements.
4. Delivery-claim consistency
Finally, compare shipping settings, product descriptions, checkout messaging and policy pages. Handling time, transit time, minimum order values and free-shipping conditions should describe the same customer experience.
How to run the audit in five passes
Pass 1: Account and data-source health
Confirm website verification and claim, account access, Google Ads linking, data-source processing and catalogue coverage. Establish whether the account is structurally ready before spending time on title optimization.
Pass 2: Group item issues by cause
Do not create one task for every affected SKU. Group products by issue type and likely source. Ten products affected by the same image rule usually require one correction workflow, followed by verification across all affected items.
Pass 3: Product data and segmentation
Next, review identifiers, variant grouping, product types, Google product categories, titles, descriptions, images, prices and custom labels. Use Google’s product data specification as the primary reference for attribute requirements.
Pass 4: Policy, trust and measurement
Meanwhile, review shipping, returns, store information, review programmes, promotions, free listings and purchase measurement. Attach a precise question to anything awaiting client input.
Pass 5: Rewrite every next action
Lastly, a good next action names the system, setting, owner and expected outcome. Replace “fix price mapping” with “Feed specialist to map the active selling price to price and the previous price to sale-price logic, then reprocess the source and verify five affected SKUs.”
Store Ratings versus Product Ratings
Store Ratings and Product Ratings are separate programmes. Store Ratings describe the customer’s experience with the business. Product Ratings describe an individual product and depend on matching review data to submitted products.
| Feature | Store Ratings | Product Ratings |
|---|---|---|
| What is measured | Customer experience with the merchant | Reviews of individual products |
| Typical eligibility threshold | Google generally requires at least 100 eligible, unique country-specific reviews within the previous 12 months for ads eligibility. | Merchants submitting review data generally need at least 50 reviews across the product catalogue. |
| Rating requirement | A composite rating of at least 3.5 stars is required for Store Ratings to appear in text ads. | Display depends on programme eligibility, review-feed quality and product matching. |
| Data source | Google Customer Reviews and supported review partners | Approved Product Ratings feed or supported review aggregator |
| Key audit check | Country-level review volume, recency, domain and programme status | Feed approval, monthly updates, identifiers and rejected reviews |
Nevertheless, eligibility does not guarantee that ratings will appear on every impression. Check the current requirements in Google’s Store Ratings overview and Product Ratings eligibility guide.
Merchant promotions and Google Ads promotion assets
Merchant promotions and Google Ads promotion assets solve related but different presentation needs. On one hand, Merchant promotions can add an offer annotation to eligible Shopping listings. On the other hand, promotion assets add offer information to eligible Search ads.
Audit the offer wording, code, eligibility, start and end dates, destination and consistency with the website. An expired or inaccurate promotion can create customer friction and policy risk.
What access is needed before starting?
| Access | Why it is needed |
|---|---|
| Merchant Center administrator access | Review account configuration, data sources, item issues, policies and programmes. |
| Feed platform or app | Inspect mappings, filters, transformations and product exclusions. |
| Ecommerce platform | Verify source attributes, product images, prices, policies and website markup. |
| Google Ads | Confirm linking, conversions, product performance and campaign segmentation. |
| GA4 or analytics platform | Reconcile purchases, revenue and attribution. |
| Google Search Console | Investigate crawling, indexing and landing-page issues where relevant. |
What this template does not replace
- A complete Shopping or Performance Max campaign restructure
- Full conversion-tracking implementation and consent validation
- A legal review of returns, pricing, privacy or consumer-protection policies
- Suspension appeal preparation for a complex account-level enforcement action
- Product photography, image redesign or complete catalogue rewriting
A real lesson from our audit process
In one ecommerce account, we identified a price-mapping mismatch and marked it Critical. Although the diagnosis was correct, the next action did not identify the person responsible or the exact screen where the mapping needed to change. Consequently, campaign work continued while the issue remained open.
As the problem spread to more products, the account received a policy warning. Once the correct owner opened the feed platform, the mapping correction took less than an hour. Therefore, we added Owner, Where to Fix and Why It Is Still Pending to every audit row.
The uncomfortable blocker field is valuable because it makes repeated delay visible to the agency and the client.
How to turn findings into a client update
Do not send the working tracker without context. Instead, use the scorecard to summarize:
- Corrections completed and verified since the previous update
- Current blockers and the exact decision, access or asset required
- Next actions, responsible owners and delivery dates
A specific request such as “Confirm the actual handling time so the website, Merchant Center and checkout display the same delivery promise” is more actionable than “shipping settings need attention.”
Recommended Merchant Center resources
- Merchant Center suspension recovery
- GTIN and product identifier strategy
- Free listings in Google Merchant Center
- Supplemental data sources for Google Shopping
- Product review integration with Merchant Center
- Performance Max and product-feed optimization
- Merchant Center approval case study
Frequently asked questions
How often should you run a Google Merchant Center audit?
Run a complete audit during onboarding and then quarterly. Between full audits, check account issues, data-source processing and product counts weekly. As a result, you can catch small problems before they create large serving losses.
Can you complete the audit without feed-platform access?
You can diagnose many issues with Merchant Center access, but you may not be able to implement lasting source corrections. Therefore, request access to the ecommerce platform, feed platform, Google Ads and analytics at the start.
Does the feed always cause a low product count?
No. Source filters, availability, destination settings, country configuration, policy decisions or store-level publishing settings may exclude products. Therefore, compare the store catalogue, submitted items and eligible items before deciding on the cause.
Does improving the feed help free listings?
Yes. Shopping ads and free listings use much of the same product data and policy framework. Better titles, identifiers, images, pricing and landing-page consistency can support eligibility and presentation across both destinations. However, Google does not guarantee visibility.
Should you edit product data directly in Merchant Center?
Direct edits can help with controlled exceptions or temporary corrections. However, teams should normally correct source data in the system that governs it. The correct method depends on the data source, attribute rules, automatic updates and source precedence.
Do I need to request access to the audit template?
No. The copy link creates a separate version in your Google Drive. You can also open the view-only version before making a copy.
Download the 65-point audit template
A Merchant Center audit is only as valuable as the actions it produces. Use the tracker to connect each finding with the governing system, responsible owner, current blocker and verification step.
Create your own copy of the Google Merchant Center Audit Template
Need help implementing the findings? Request a free Merchant Center and Shopping audit from Hustle Marketers. We will identify the highest-priority feed, approval and tracking issues affecting product visibility.
About the author
Ishant Sharma is the Founder and CEO of Hustle Marketers and a performance marketing specialist across Google Ads, Meta Ads, SEO and ecommerce PPC. This is the digital marketer, not the Indian international cricketer. Author profile · LinkedIn
