Does your content survive without JavaScript?
Some storefronts put the price, the variants or the whole product block behind JavaScript. A plain fetch then sees a page that looks complete and is not. This loads it in a real browser and compares what the browser builds against the raw HTML.
Runs a real browser on one page and fetches the raw HTML to compare. Costs 10 credits per run; nothing is stored.
Not connected. Sign in and Connect Search Console to read Google's own verdict for this page. The check below still runs from public signals without it.
How this check works
Shipwork fetches the page the way a crawler without JavaScript does, then loads the same address in a real browser and measures the text each one sees. It reports how much content only appears after JavaScript runs, any JavaScript errors, changes to the status or the title, the transfer weight and the request count.
Questions
- Why does JavaScript-only content matter?
- Googlebot renders pages, but it renders late and not always. If the price, the stock or the whole product block is built by JavaScript, a crawler can see the page without it and index the empty version.
- How is this different from the free checks?
- The free checks read the HTML a plain fetch returns. This runs a real browser, which is the only way to see what JavaScript adds and to measure it against the raw response.
- Why does it cost 10 credits?
- A real browser is the heaviest thing the product runs: it launches, loads the page and waits for it to settle. Your first full run is free; after that it draws 10 credits.