Learning Center · Explain it to my boss · JavaScript, rendering and what agents can read
Many AI assistants can't see content our website adds with scripts
Many AI assistants read only the page our server sends and never run the scripts that fill in prices, products and policies. If that content only appears after scripts run, they see a logo, a spinner and not much else. Ranking well in Google hides the problem, because Google runs scripts and AI assistants often don't.
15% 15% of stores don't put prices in the product page's HTML, where most agents look. Source
What it costs the business
- Prices, products and policies that only appear after scripts run may be invisible to a large share of AI traffic.
- When prices load with scripts, agents see a product with no price, and often skip it.
- Strong Google rankings can mask the gap: the same site can be well indexed by Google and nearly blank to assistants.
What to do
- Ask developers to put the essentials in the server's page: product name, price, availability, key specifications, shipping, returns and plan pricing.
- Turn on server-side rendering for key pages, usually the biggest single fix.
- Use pre-rendering only as a stopgap: it means maintaining two versions of each page.
- Check with AgentScore, which passes when at least 70% of a page's text arrives without scripts.
Who owns it: DeveloperEffort: Weeks
The detail is in JavaScript, rendering and what agents can read. Based on Why AI agents can't see your JavaScript-only content, We scanned 255 online stores with AgentScore. Here's what trips up AI agents.