Fixing Google Merchant Center Structured Data Errors in Shopware

Addressing Google Merchant Center Structured Data Errors in Shopware

A recent discussion in the Shopware forum highlights persistent issues with structured data type 'Merchant Listings' (Händlereinträge) reported by Google. The core of the problem appears to stem from incomplete or incorrectly implemented schema.org properties within Shopware's default JSON-LD output, specifically impacting product detail pages.

The Root Cause: `json-ld-product.html.twig`

The primary template identified as the source of these discrepancies is json-ld-product.html.twig. Users are finding that crucial sections or property names required by Google are either missing or incorrect, leading to warnings and errors in Google Search Console.

Key Missing or Incorrect Schema.org Properties:

One user, R4M, meticulously analyzed the required schema and identified several areas needing attention:

Missing `hasMerchantReturnPolicy` in the `Offer` block: Google expects detailed return policy information. The suggested structure for this missing block is:

"hasMerchantReturnPolicy": {
  "@type": "MerchantReturnPolicy",
  "applicableCountry": "DE",
  "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
  "merchantReturnDays": 30,
  "returnMethod": "https://schema.org",
  "returnFees": "https://schema.org"
}

`transitTime` instead of `handlingTime` in `shippingDetails`: Google specifically looks for `transitTime` at this location.
Missing `shippingDestination`: This crucial section defines the countries to which a product can be shipped. An example structure for a single country is:
```
shippingDestination: {
  '@type': 'DefinedRegion',
  addressCountry: 'DE'
},
```
The complexity of implementing this for multiple countries dynamically remains a challenge.

Missing `shippingRate`: Google also requires explicit shipping rate information. The suggested structure is:

shippingRate: {
  '@type': 'MonetaryAmount',
  'value': calculatedPrice.unitPrice,
  'currency': context.currency.isoCode
}

Challenges in Customization

A significant hurdle for developers is the limited number of override blocks within the json-ld-product.html.twig file. This often necessitates copying the entire template into a custom theme for modification, which can make future updates more complex and potentially lead to maintenance issues.

Community Insights and Solutions

The discussion also touched upon the practicalities of testing and implementation:

Regression after Shopware Updates: R4M noted that these issues were not present previously, suggesting a potential regression or change in how Shopware handles structured data after an update.
Testing Live Shops: The impracticality of reverting a live shop to a standard setup for testing Google's re-indexing was highlighted, emphasizing the need for robust development and staging environments.
Plugin Solution: A user from frip-tech.de suggested their plugin, "Debugger für Google Search Console," available in the Shopware Store, as a potential tool to help resolve schema errors and optimize product display for rich snippets. They also offered to update the plugin for new Google data requirements.

Conclusion

Accurate and complete structured data is paramount for e-commerce success, directly impacting a shop's visibility in Google Shopping and search results through rich snippets. The ongoing need to adapt Shopware's JSON-LD output to Google's evolving schema requirements underscores the importance of continuous monitoring and development. While direct template modifications offer a solution, the community also benefits from specialized plugins that streamline this complex process.

Shopware's Structured Data: Tackling Google Merchant Center Issues with JSON-LD