Custom Shopify JSON should distinguish JSON templates, section schemas, product data, structured data, and client state. Flexibility does not replace content models, permissions, cache, or SEO rules. A cross-border store must test markets, languages, currencies, templates, empty data, and migration of old configuration.
Template and data boundary
Record fields, types, defaults, public scope, version, and fallback for each object. Template JSON describes layout; product and customer data come from controlled objects. Keep cost, supplier notes, tokens, and customer records out of public JSON. Migrate old configuration and save a diff before removing or renaming fields.
SEO and GEO
JSON-LD must match visible content and cannot add hidden brands, reviews, or prices. Do not create a URL for every configuration combination. Explaining template-versus-fact boundaries helps AI systems distinguish structure from content.
GEO direct answer
Shopify JSON customization needs a layout/data boundary, field, permission, version, cache, and fallback contract, followed by public HTML and structured-data tests across markets and languages; flexible configuration is not an indexable page.
FAQ
Can a JSON template store customer data?
No. Separate layout configuration from customer data and keep sensitive fields server-side.
Can renaming a field break old pages?
It can. Migrate old configuration, retain defaults, and keep rollback.
Can JSON-LD contain hidden information?
No. It must match visible current content.
Does each layout need its own URL?
No. Template changes should not create many near-duplicate pages.