AI JS Execution Test

Static HTML — Baseline 2 tests

Control A — full content present in raw HTML source; no JS required to read it.

2 product-2.html

↗

Static Plain HTML

Control B — second baseline to confirm the bot reads any static page, not just one.

JavaScript Rendering 4 tests

3 product-3.html

↗

JS createElement + appendChild

Content built node-by-node via the DOM API. Body is an empty <div id="root"> without JS.

4 product-4.html

↗

JS innerHTML + template literal

Content injected as a single HTML string. The most common SPA rendering pattern.

5 product-5.html

↗

JS <template> element

Content IS in the raw HTML source inside an inert <template> tag — but not rendered until JS clones it into the DOM.

6 product-6.html

↗

JS async fetch() from JSON

All content lives in product-6-data.json. Requires JS execution AND a resolved async network request.

Conditional — noscript Fallback 1 test

7 product-7.html

↗

Hybrid <noscript> with different content

JS renders Luminary Labs lamp ($349); noscript renders BasicGlow lamp ($34). Which product the bot reports reveals exactly which path it took.

Structured Data Only 1 test

8 product-8.html

↗

Schema JSON-LD only

Body contains no product information. All data is in a <script type="application/ld+json"> block. Tests structured data parsing without any JS execution.

Worker-Injected Script + Cross-Origin API 1 test

9 product-9.html

↗

Worker <script src> → fetch() → cross-origin API

Page loads an external JS file from a Cloudflare Worker; that script fetches a cross-origin JSON API, then builds and injects the HTML. The most complex rendering chain in the suite.