JavaScript to load structured data<\/a>.<\/p>\nUnlike Google Search, which uses Googlebot and a rendering queue to process JavaScript, the Shopping crawler runs at a dramatically higher pace. It must fetch:<\/span><\/p>\n\n- Real-time pricing<\/span><\/li>\n
- Inventory updates<\/span><\/li>\n
- Availability changes<\/span><\/li>\n
- Configuration data<\/span><\/li>\n
- Sale status<\/span><\/li>\n
- Variants<\/span><\/li>\n
- Merchant feed updates<\/span><\/li>\n<\/ul>\n
Because pricing and availability shift constantly, the Shopping Graph needs near real-time data ingestion.<\/span><\/p>\nSimply put, the Shopping crawler has a job to do and JavaScript slows it down.<\/span><\/p>\n<\/span>How Does the Shopping Crawler Differ from Google Search?<\/b><\/span><\/h2>\nThis is the core misunderstanding that many developers and SEOs had until now:<\/span><\/p>\nGoogle Search \u2192 JavaScript is processed<\/b><\/h3>\n
Googlebot waits, renders, and extracts structured data, even if it is loaded through JavaScript. Rendering can be delayed due to queueing, but it eventually happens.<\/span><\/p>\nGoogle Shopping \u2192 JavaScript is ignored<\/b><\/h3>\n
The Shopping crawler does not wait for JS. If the structured data is not present in raw HTML, it will not be read.<\/span><\/p>\nThis difference explains Google\u2019s strict recommendation to always provide static, server-side structured data for product pages.<\/span><\/p>\nAt the Zurich event, Barry Schwartz summarized it on X:<\/span><\/p>\n\u201cGoogle Shopping won\u2019t process structured data loaded through JavaScript because Shopping crawls a lot, fast\u2026 It is different from Google Search.\u201d<\/span><\/p>\nThis distinction matters for every retailer that relies on dynamically injected product data.<\/span><\/p>\n<\/span>How Fast Does the Shopping Bot Crawl and Why Does Speed Matter?<\/b><\/span><\/h2>\nThe Google engineer didn\u2019t provide exact crawl-rate numbers, but the context makes the situation clear:<\/span><\/p>\nThe Shopping crawler must ingest data at industrial scale.<\/b><\/h3>\n
Retail data changes constantly:<\/span><\/p>\n\n- Flash sales<\/span><\/li>\n
- Stock-outs<\/span><\/li>\n
- Price adjustments<\/span><\/li>\n
- Promotions<\/span><\/li>\n
- Currency fluctuations<\/span><\/li>\n
- Merchant feed updates<\/span><\/li>\n
- Local inventory changes<\/span><\/li>\n<\/ul>\n
If the bot waited for JavaScript rendering:<\/span><\/p>\n\n- The Shopping Graph would lag<\/span><\/li>\n
- Prices could be outdated<\/span><\/li>\n
- Unavailable products might appear<\/span><\/li>\n
- Merchants could lose sales<\/span><\/li>\n
- Google could show incorrect listings<\/span><\/li>\n<\/ul>\n
Because Google Shopping handles millions of SKUs across global retailers, its crawlers simply cannot afford rendering delays.<\/span><\/p>\nThis is why Google considers JavaScript-loaded schema too slow and too unreliable for high-frequency shopping data.<\/span><\/p>\n<\/span>What Risks Do Retailers Face If They Use JavaScript for Structured Data?<\/b><\/span><\/h2>\nRetailers still using JavaScript-based structured data may experience serious issues, often without knowing the cause:<\/span><\/p>\n1. Incorrect or missing product data in Google Shopping<\/b><\/h3>\n
If the bot cannot read the JS-rendered schema, it may not see: price, availability, product variants, brands, SKU and shipping details.\u00a0<\/span><\/p>\nThis affects product rich results and Shopping listings.<\/span><\/p>\n2. Reduced visibility in Shopping results<\/b><\/h3>\n
Google Shopping prioritizes accurate, stable data sources. Missing structured data can cause ranking loss in: free listings, Shopping ads, product carousels and knowledge-based shopping formats<\/span><\/p>\n3. Merchant Center disapprovals<\/b><\/h3>\n
Inconsistent or missing structured data (between schema, Merchant Center feed, and on-page content) can trigger: mismatched price errors, availability mismatches<\/span>
\n<\/span>and structured data inconsistencies.\u00a0<\/span><\/p>\n4. Slower inclusion in the Shopping Graph<\/b><\/h3>\n
Because the bot skips JavaScript rendering, any JS-only product data is effectively invisible. Retailers may unknowingly be operating at a severe disadvantage.<\/span><\/p>\n<\/span>What Did Industry Experts Say About the Announcement?<\/b><\/span><\/h2>\nAleyda Solis added important clarification on X:<\/span><\/p>\n\u201cIn Search, they\u2019re parsing JavaScript\u2026<\/span>
\n<\/span>In Shopping, it\u2019s different because they crawl a lot. If they have to crawl more, structured data should not rely on client-side rendering.\u201d<\/span><\/p>\n