If you work with technical SEO, schema or AI indexing (AEO/GEO), this update deserves attention.

Shopify introduced a key restriction on JSON metafields in API version 2026-04:

Shopify API release schedule

JSON metafield write limit: 128KB

  • The limit takes effect from API version 2026-04.
  • A single JSON metafield can hold a maximum write payload of 128KB.
  • Writes above that size fail.
  • Existing larger fields remain readable, but cannot be updated or rewritten with content above the limit.

Which workflows are affected?

Basic product displays are unlikely to be affected. The impact is greater for structured, automated and AI-oriented website systems:

1. SEO and structured data

  • Large JSON-LD payloads, including product, FAQ and organization data.
  • Complex, nested schema structures.

2. AEO and GEO data structures

  • Semantic structures for AI stored in metafields.
  • Examples include product knowledge graphs, attribute mappings and question-and-answer structures.

3. Metaobjects and technical specification libraries

  • Fabric specifications, machinery parameters and configuration JSON.
  • B2B products with many attributes and deeply nested structures are particularly relevant.

4. Automated content systems

  • Bulk JSON writes from ERP, PIM and scripts.

Why this can become a hidden risk

Many Shopify projects start with assumptions such as:

  • “A metafield can store any amount of JSON.”
  • “We can expand the data structure later.”

The limit changes those assumptions:

  • The data model needs to be designed carefully from the start.
  • A JSON structure cannot grow indefinitely within one field.
  • Large writes can fail directly, especially in automated scripts.

Three ways to adapt the architecture

Option 1: split the JSON

  • Divide one large JSON object across multiple metafields.
  • For example:
product.metafields.specs.base
product.metafields.specs.material
product.metafields.specs.customization

Benefits:

  • A clearer structure.
  • Easier maintenance.

Option 2: use metaobjects

  • Replace a large JSON object with structured, field-based data.
  • Avoid placing every piece of information in a single field.

Useful for:

  • B2B product libraries.
  • Complex specification management.

Option 3: external storage with a reference

  • Store large JSON files externally, such as on a CDN or behind an API.
  • Keep only a reference URL in the metafield.

Example:

{
  "spec_url": "https://cdn.xxx.com/product-specs/123.json"
}

Benefits:

  • Room to expand beyond the field limit.
  • Suitable for AI data and complex models.

Implications for SEO and AI search

The update sends a signal:

Shopify is moving away from storing large, undifferentiated JSON payloads in pages or metafields.

The implications are:

  • Efficient parsing by Google becomes more important.
  • AI models such as ChatGPT and Gemini favor clear, separable data structures.
  • Future SEO is about better data modeling, rather than adding more JSON.

Recommendations for Shopify developers

  • Review every workflow that writes JSON metafields.
  • Avoid overloading a single field.
  • Design an expandable data structure rather than a one-off payload.
  • Prioritize SEO/AEO modeling over accumulating content.

What to take from the update

Comparison of data-modeling strategies

The change points toward:

  • A move from accumulated content to structured modeling.
  • A move from page-level SEO to data that AI can interpret.

If you work on any of the following:

  • B2B websites.
  • Technical product sites for machinery, textiles or custom products.
  • AI search optimization (AEO/GEO).

Treat this update as a signal to review your architecture.