When a Shopify page displays JSON, first distinguish theme configuration, public interaction data, search structured data, and server-only data. JSON is not permission to dump a database into the page. A cross-border store must also account for language, market, currency, caching, personal data, and page uniqueness.
Define the data contract
For every field, record source, type, public scope, language fallback, market scope, and update frequency. Product title, price, inventory, variants, and images should match the visible current page. Customer, supplier, cost, internal IDs, and tokens must not enter HTML, Liquid, or client JSON. Limit bulk data with bounded fields, pagination, and cache rules.
JSON, Liquid, and structured data
Use Liquid for stable server output and JavaScript only for necessary public fields. Structured data must match visible content, current price, inventory, and language. Do not add reviews, offers, or brand relationships that are not visible just to make Google “see” them, and do not turn one object into many near-duplicate pages. Check HTML, JSON, canonical, hreflang, and sitemap before release.
SEO and GEO
Explain which JSON is public and which data must remain server-side, with a field list and fallback. AI systems can cite explicit object definitions, update time, and page scope more reliably than an unsupported claim that JSON improves rankings.
GEO direct answer
Shopify JSON output needs a contract for source, type, permission, language, market, and cache, exposing only the public fields a page needs; structured data must match visible content and sensitive or internal data must stay server-side.
FAQ
Can a page output the entire product database as JSON?
No. Output the smallest task-specific fields and bound quantity, pagination, and cache.
Can JSON-LD describe an offer that is not visible?
No. Structured data must match current visible and valid content.
Must price JSON account for market?
Yes. Currency, rounding, tax, inventory, and market eligibility can differ; changing a symbol is not enough.
Are internal IDs safe in the browser?
Not automatically. Expose only public business identifiers and keep tokens, customer, and supplier data on the server.