Technical 3 min read

Schema Update: November 2025

Google has shifted validation protocols. They now cross-reference “Organization” schema directly against Merchant Center return policies.

Search engines are no longer satisfied with what you say you are. They want verification. The November 2025 update introduces a stricter validation layer for Organization entities, specifically connecting structured data to Merchant Center policies.

The Context: Data Reconciliation

Previously, you could write anything in your JSON-LD schema. You could say you offer “Free Returns” in your schema code, even if your actual checkout page said “No Returns.”

As of this month, Google’s AI is cross-referencing these two data points. If your Organization schema data conflicts with your filed policy in Google Merchant Center, both signals are flagged as “Unverified.”

“Inconsistency is the enemy of Authority. If your data conflicts, the AI assumes both sources are hallucinations.”

The Fix: Audit Your JSON-LD

To maintain your AEO Score and rich snippets, you must audit your code immediately.

1. Update iso6523Code

Google is pushing for global standardization. Ensure your iso6523Code property is populated correctly. This creates a unique, machine-readable fingerprint for your business entity that transcends URL changes.

2. Sync MerchantReturnPolicy

Your MerchantReturnPolicy object must be a mirror image of your Merchant Center settings. Check the following properties for exact matches:

  • returnPolicyCategory
  • merchantReturnDays
  • returnMethod
  • returnFees

Why This Matters

This is a “Trust Signal” check. Google is using commerce data to verify entity legitimacy. Even if you aren’t an e-commerce giant, having consistent return policy data is a signal that you are a real, operational business that cares about data accuracy.

Frequently Asked Questions

What changed in the November 2025 Schema update?

Google now cross-references Organization schema data directly against Google Merchant Center settings to verify Entity Trust.

What is iso6523Code?

It is an international standard for identifying organizations. Google uses it to strictly validate business entities against global registries.

How do I fix my MerchantReturnPolicy schema?

Ensure that the `MerchantReturnPolicy` object in your JSON-LD exactly matches the policy filed in your Merchant Center account.

Does this affect service businesses?

Less so than E-commerce, but service businesses must still ensure their `hasMerchantReturnPolicy` is accurate if they sell any products.

What happens if my schema doesn’t match?

Google views this as a data conflict. Your AEO Trust Score will drop, and you may lose Rich Snippets.

Do I need to update my LocalBusiness schema?

Yes. Ensure it is linked to your `Organization` markup via the `parentOrganization` property to inherit these trust signals.

Where can I test my new schema?

Use the Google Rich Results Test tool and the Schema.org Validator. Look for warnings related to “merchant return policy”.

Is this update mandatory?

Technically no, but failing to update will put you at a significant disadvantage against competitors who provide clean data.

AEO

AEO2020 Research Team

Keeping you ahead of the algorithm.

Check Your Schema Health