Google clarifies merchant return policies and loyalty programs documentation – PPC Land
Google's July 11 update targets documentation gaps affecting e-commerce structured data implementation across return policies and member programs.
According to Google’s latest documentation update, the search giant has modified multiple help documents to resolve implementation confusion surrounding merchant return policies and loyalty programs. The update, announced on July 11, 2025, addresses specific technical requirements that have created uncertainty for e-commerce businesses using structured data markup.
The modifications center on two critical areas of merchant structured data implementation. First, Google has clarified that offer-level return policies support only a subset of organization-level return policies. Second, the documentation now explicitly states that merchant-level return policies must be defined under Organization markup. These clarifications stem from ongoing confusion about proper implementation hierarchy within Google’s structured data framework.
Subscribe the PPC Land newsletter ✉️ for similar stories like this one. Receive the news every day in your inbox. Free of ads. 10 USD per year.
Who: Google Search Central team updating documentation for merchants using structured data markup for return policies and loyalty programs.
What: Documentation clarification requiring offer-level return policies to support only organization-level subsets, merchant return policies under Organization markup, loyalty program information separate from offer-level benefits, and confirmation that shipping/returns loyalty benefits are unsupported.
When: July 11, 2025, with immediate implementation and no transition period for existing merchants.
Where: Google Search Central documentation affecting structured data implementation across e-commerce websites globally.
Why: To remove implementation confusion and clarify technical requirements following merchant feedback about proper structured data implementation approaches for return policies and loyalty programs.
Subscribe the PPC Land newsletter ✉️ for similar stories like this one. Receive the news every day in your inbox. Free of ads. 10 USD per year.
Google’s update establishes clear technical boundaries for return policy implementation. According to the updated documentation, merchants can no longer assume that all organization-level return policy properties are available at the offer level. The restriction affects properties such as seasonal overrides, complex fee structures, and multi-country configurations that remain exclusive to organization-level markup.
The organization-level requirement for merchant return policies represents a significant structural change. Previously, the documentation contained ambiguous language about where merchants should place return policy information. The July 11 update eliminates this uncertainty by mandating that MerchantReturnPolicy structured data must appear under Organization markup for proper recognition.
These technical boundaries affect merchants operating complex return structures. Organizations with multiple return policies for different product categories or regions must implement these policies at the organization level rather than attempting to duplicate them across individual product offers. The change ensures consistency in how Google processes return policy information while reducing markup complexity for merchants.
The loyalty program documentation underwent substantial revision to address implementation confusion. According to Google’s update, loyalty program information must be defined separately from offer-level loyalty benefits under Organization markup. This separation creates distinct requirements for program-level information versus individual product benefits.
The documentation now explicitly states that loyalty program benefits such as prices and points must be implemented through separate markup structures. Program-level information, including tier definitions and membership requirements, belongs under Organization structured data. Individual product benefits require implementation through UnitPriceSpecification markup within product offers.
Google has also clarified that shipping and returns loyalty benefits are not currently supported. This limitation affects merchants who previously attempted to implement these features through structured data markup. The restriction applies across all loyalty program implementations, regardless of whether merchants use structured data or Merchant Center configurations.
The documentation updates reflect broader changes in how Google processes merchant information. The requirement for organization-level return policies aligns with Google’s move toward centralized merchant data management. This approach reduces duplicate information across product listings while ensuring consistent policy application.
The separation of loyalty program information from offer-level benefits creates clearer technical boundaries. Merchants must now implement loyalty programs through a two-tier approach: organization-level program definitions combined with product-specific benefit specifications. This structure enables more granular control over loyalty program features while maintaining program-wide consistency.
These structural changes also affect how merchants with existing Merchant Center accounts should approach implementation. Google continues to recommend that merchants with Merchant Center access use those tools rather than structured data markup. However, the updated documentation provides clearer guidance for merchants without Merchant Center access who rely on structured data implementation.
The documentation clarifications carry significant implications for e-commerce search visibility. Merchants with incorrectly implemented return policies may experience reduced visibility in Google Shopping results. The requirement for organization-level markup means that merchants must audit their current implementations to ensure compliance with the updated requirements.
PPC Land previously reported on Google’s introduction of loyalty program structured data support in June 2025. The July 11 documentation update addresses implementation questions that arose following that initial announcement. The clarifications particularly benefit merchants without Merchant Center accounts who rely on structured data for loyalty program implementation.
The updated requirements also affect how merchants should prioritize their structured data implementation efforts. Organizations must now focus on comprehensive organization-level markup before implementing product-specific features. This approach ensures that fundamental merchant information is properly configured before adding complex product-level enhancements.
Google’s approach to documentation updates reflects ongoing efforts to maintain technical accuracy across its developer resources. According to the announcement, these changes aim to “remove unclarities in the documentation and examples.” This maintenance approach indicates Google’s recognition of implementation challenges faced by merchants and developers.
The timing of these documentation updates follows several months of merchant feedback regarding structured data implementation. Google’s introduction of loyalty program support in June 2025 generated numerous questions about proper implementation approaches. The July 11 update directly addresses these concerns through explicit requirements and clearer examples.
The documentation changes also demonstrate Google’s commitment to structured data standardization. By clarifying implementation requirements, Google reduces the likelihood of incorrect markup that could affect search result quality. This approach benefits both merchants and users by ensuring more consistent and reliable structured data implementation.
The documentation updates maintain Google’s recommendation for Merchant Center usage among eligible merchants. According to the updated guidance, merchants with Merchant Center accounts should continue using those tools for return policy and loyalty program management. The structured data approach serves primarily as an alternative for merchants without Merchant Center access.
Earlier reporting from February 2025 highlighted Google’s introduction of member pricing data types for merchant listings. The July 11 documentation update clarifies how these features integrate with loyalty program structured data while maintaining compatibility with existing Merchant Center implementations.
The integration considerations extend to data precedence rules. When merchants implement both Merchant Center configurations and structured data markup, Google prioritizes Merchant Center settings. This precedence ensures that merchants with established Merchant Center workflows can continue using those tools without concern about conflicting structured data implementations.
Google has implemented these documentation changes immediately, with no grace period for existing implementations. Merchants using incorrect markup structures may experience immediate effects on their search result visibility. The lack of a transition period reflects the documentation nature of these changes rather than algorithmic modifications.
The immediate implementation affects merchants differently based on their current markup approaches. Organizations already using organization-level return policies face minimal disruption. However, merchants who implemented return policies at the offer level must restructure their markup to maintain compliance with Google’s requirements.
The documentation updates also provide merchants with clearer implementation pathways. Google’s updated examples demonstrate proper markup structure while highlighting common implementation errors. This guidance enables merchants to audit their current implementations and make necessary corrections to ensure continued search visibility.
