Skip to content

Leadership1 publisher2 min readPublished

Rendering price in JavaScript keeps a product out of ChatGPT's shopping answers

An ecommerce audit consultant writing in Entrepreneur says most AI crawlers read only a page's initial HTML, so a product page that ranks in Google can return nothing to an assistant fielding around 50 million shopping queries a day.

The Board Room · Leadership desk

What happened

  • Research by Vercel and MERJ, cited in an Entrepreneur contributor column, finds the large majority of AI crawlers cannot execute JavaScript, so they read a product page's initial HTML and stop.
  • The column's test is to open your top-selling product page, use View Page Source instead of Inspect Element, and check whether the price appears in the code at all.
  • OpenAI's economic research team has cited around 50 million daily shopping queries in ChatGPT alone, and the Google, Perplexity and Amazon assistants have their own volumes.
  • Amazon's robots.txt now lists the search and browsing agents of OpenAI, Anthropic and Perplexity, and the column says its listings are invisible to ChatGPT's organic shopping recommendations.
  • Walmart, Target, Best Buy, Home Depot and Etsy went the other way and allowed AI shopping surfaces to index their listings.

Compiled by The Board RoomSomething wrong?How this is made

Why it matters

  • cost Re-rendering price, stock and specs server-side lands on an engineering budget, and on some platforms it is expensive work; the benefit is booked by whoever owns the channel.
  • constraint An Amazon-only brand cannot bid its way into assistant recommendations, because the gate is a file on Amazon's own server.
  • decision The choice this quarter is whether to pay for machine-readable pages now or wait for crawlers to add JavaScript execution, and only the first option is under the seller's control.
  • precedent If Amazon's negotiations with shopping agents produce a deal, sellers who spent on Walmart and Target listings will have optimised against a gap that closed on them.

Nothing looks broken from the marketing side. The page ranks in Google and returns nothing to an AI assistant that tries to read it [3].

Fifty million shopping queries a day is about 18 billion a year [6]. The column gives no conversion rate and no average order value for them [18]. So a finance director asked to fund server-side rendering is weighing a quoted engineering job against a query count, and the contributor grants that the fix is expensive on some platforms [12].

Calling the own-site product page infrastructure [17] is, in practice, a hedge against a decision the brand does not control. Amazon's block is a business choice, not a technical limit: the company restricts external agents while building its own, currently available through Alexa for Shopping [9]. Amazon's chief executive has said publicly that the company is negotiating with third-party shopping agents and is sure a partnership will be found, the article reports [11]. A brand whose only product pages are Amazon listings, with no direct-to-consumer pages or press coverage, is close to invisible in that channel until the negotiation lands [16].

The second gate the article names is third-party reviews. Presence on a few relevant review sites can dramatically increase the likelihood of being recommended, the contributor writes, citing research Trustpilot commissioned from Seer Interactive [15].

The sequencing question is whether this is a this-quarter cost or a this-decade one. The contributor's position is that AI shopping features come and go while the requirements hold: complete product information, accurate real-time pricing, current inventory, pages a machine can read [13]. If that holds, the work survives the next shopping surface that replaces the current one.

Start with provenance. This is one practitioner's audit experience, published as a contributor column whose opinions Entrepreneur attributes to the author [14], and the crawler finding reaches the reader secondhand from Vercel and MERJ [2]. It matters most on the demand side, where every number belongs to somebody else. It matters less for the technical claim, which a team can reproduce against its own catalogue without anyone's cooperation. The one input a buyer can inspect without trusting a study is the file Amazon publishes at amazon.com/robots.txt [19].

What to watch

  • A refreshed Vercel or MERJ measurement showing AI crawlers executing JavaScript would cut the case for paying to re-render pages.
  • Published conversion or average-order-value data for assistant-driven shopping, which would let a rendering budget be underwritten with a revenue figure.
  • Any change to the AI bot entries in amazon.com/robots.txt covering third-party shopping agents.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories