Analyze a Page

Analyze a Page is the URL-paste audit tool. Drop in any product URL — yours, a retailer's, a competitor's — and eCommerce Insights detects the channel, runs the appropriate scoring model, checks crawler access, inventories structured data, and produces recommendations.

When to use it

Three use cases.

• Competitor audit. Paste a competitor's PDP. See how it scores, what schema they ship, and what their AI Agent Lens verdict looks like. Useful before a refresh of your own PDP.
• Retail-partner PDP. A SKU sold through Macy's or Target. The data lives on the retailer; you cannot edit robots.txt; but you can read their structured data and benchmark against what you ship to other channels.
• One-off audit. A landing page, a category page, or a guide. Anything outside your main catalogue that you want a quick read on.

Inputs

1. Paste a URL

   Any public product URL. Trailing slashes and query strings are normalised.

2. Optionally toggle "Force JavaScript rendering"

   For SPA pages where product content is JS-rendered. Defaults off.

3. Submit

   Audit completes in 15-60 seconds depending on fetcher path.

Channel detection

Same logic as catalogue import. Amazon URLs route to Rufus Score; known retailer hosts route to filtered PDP scoring; everything else to full PDP Score. The detected channel is shown as a card at the top of the result, with an override link if the detection is wrong.

Crawler access preflight

Before scoring, eCommerce Insights runs a preflight against the URL's robots.txt and tests the six AI crawlers. The card shows which bots are allowed, which are blocked, and whether Cloudflare or a similar gateway is interfering. This was added in v13 because most score-failure root causes were turning out to be crawler-access issues.

Force JavaScript rendering

Some PDPs only render product content after JS executes (typical for React/Vue/Svelte storefronts not using SSR or hydration). The default fetcher reads the static HTML, which on an SPA gives you an empty shell. Toggle this on and eCommerce Insights routes the fetch through ScrapingBee with render_js=true, which spins up a headless Chrome and reads the post-JS HTML.

The toggle has a cost (slower fetch, more expensive). It is off by default and only needed for SPA storefronts.

The report

Same shape as the catalogue PDP Score detail. Five-bucket breakdown for D2C, fifteen-relation breakdown for Amazon. Recommendations ranked by priority. The full audit detail uses the same shared audit_report partial as the rest of the app (introduced in v13), so the report looks identical to what you see on a catalogue SKU.

Common questions