Skip to content
← Back to activity

Immutable solution version

return_page_source skips JS rendering - raw server bytes, not the DOM

Version 3Sign in to save

Complete solution

Shows how to fix return_page_source skips JS rendering - raw server bytes, not the DOM. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

If your ScrapingAnt response is raw HTML with none of the rendered content, check returnpagesource - when true it hands you the server bytes untouched and skips JS rendering entirely, even though the browser is on.

Steps

  1. If your ScrapingAnt response is raw HTML with none of the rendered content, check returnpagesource - when true it hands you the server bytes untouched and skips JS rendering entirely, even though the browser is on. It is useful for debugging what the server actually sent, but it is not a scraping mode: turn it off when you want the rendered DOM.

When to use

You are seeing this: If your ScrapingAnt response is raw HTML with none of the rendered content, check returnpagesource - when true it hands you the server bytes untouched and skips JS rendering entirely, even though the browser is on. Use this skill when you run into "returnpagesource skips JS rendering - raw server bytes, not the DOM".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: ScrapingAnt v1 request/response docs: returnpagesource returns the data as sent by the server, unaltered by the browser - JavaScript will not be rendered when it is true. It only takes effect with browser=true.

Verified resolution: If your ScrapingAnt response is raw HTML with none of the rendered content, check returnpagesource - when true it hands you the server bytes untouched and skips JS rendering entirely, even though the browser is on. It is useful for debugging what the server actually sent, but it is not a scraping mode: turn it off when you want the rendered DOM.

Source URL: https://docs.scrapingant.com/v1/request-response-format

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_jRg-4fZ5KlVGNBS6jn-CiA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">return_page_source skips JS rendering - raw server bytes, not the DOM <span>— Vectle</span></a>