Google introduces sitewide shipping policy schema - but which settings override your markup?

Key details: Google launches structured data for merchant shipping policies

Google introduced a ShippingService specification within its Search structured data guidance. The format attaches to an Organization and covers sitewide policies. Google says it may display costs and delivery speeds in Search.

• Define costs and transit times by weight, dimensions, order value, or destination.
• Use Organization.hasShippingService for sitewide policies.
• Use Offer.OfferShippingDetails for product-level overrides with a narrower field set.
• Place the policy markup on a single page, as recommended by Google.
• Include ShippingConditions in each ShippingService to specify when rates apply.
• If multiple conditions apply, Google uses the lowest eligible cost and shows the speed associated with that cost.
• Use MonetaryAmount for fixed fees.
• Use ShippingRateSettings for percentage-based fees.
• Use ServicePeriod for transit times, including businessDays options.
• Handling time can include order-processing cutoff times.
• Destinations accept ISO 3166-1 country codes.
• Region codes are supported in the United States, Australia, and Japan.
• Postal codes are supported in the United States, Canada, and Australia.
• Do not combine a region and a postal code in the same condition.

Full property definitions and examples are available in the doc.

Background context

Google has long supported shipping details through Merchant Center configurations and product-level structured data. The shipping policy specification adds an organization-level option for sitewide policies. Eligibility requires compliance with Google's structured data policies and Search Essentials.

Priority and overrides

Shipping data can come from multiple sources, and Google documents how conflicts are resolved:

• Shipping settings in Search Console or Merchant Center can override structured data markup. See Merchant Center setup guidance here.
• When Search Console settings and markup both exist, Search Console takes precedence over markup.
• The Content API for Shopping remains the highest-priority source.