AI search engines and shopping bots read product data by fetching raw server HTML and parsing structured JSON-LD (Product, Offer, priceCurrency). If your product details and prices only appear after client-side JavaScript execution, AI crawlers see an empty container and cannot cite or recommend your items.
Enter your website address to check crawler access (GPTBot, ClaudeBot), server-rendered HTML, and JSON-LD schemas.
How AI models and shopping agents read product data
Unlike human shoppers who execute JavaScript in a full browser, AI bots (like GPTBot, OAI-SearchBot, ClaudeBot, and PerplexityBot) fetch raw HTML to save compute. They extract product names, specifications, pricing, stock availability, and return policies directly from server-rendered markup and Schema.org Product & Offer JSON-LD blocks.
Try one product you know well
Open a published product, then search View Page Source for its exact name and one specification, such as a material or size. Can you find the details that a buyer sees on screen? If you only find a loading message and scripts, ask how the product data is delivered. Repeat the check on another product before changing the whole store.
Align the visible information and structured data
When you add product markup, keep it consistent with the actual page and update it when details change. Avoid invented ratings or stale values copied across products. Check both the template and a live product because missing database fields can produce different output for individual items.
Use discovery to check the public inventory
List concrete product URLs in a sitemap and link from relevant categories. SiteReadyFor.SI can inspect the discovered pages’ HTML and JSON-LD within the chosen scope. It does not verify your inventory system, run a checkout, or measure whether a shopping assistant recommends the product.