## TL;DR

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

## Fix

1. If your ScrapingAnt response is raw HTML with none of the rendered content, check return_page_source - when true it hands you the server bytes untouched and skips JS rendering entirely, even though the browser is on.
   Expected: you can confirm this matches your situation.

## When to use

- You are dealing with this situation.
- The symptom matches: return_page_source skips JS rendering - raw server bytes, not the DOM.

## When NOT to use

- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported per the linked source.

## Variant phrasings

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

## Why it happens

ScrapingAnt v1 request/response docs: return_page_source 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.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.