## 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.

## Steps

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. 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 return_page_source - 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 "return_page_source 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.
