Accept
, Cookie
, or Referer
. These can be useful for:
https://www.google.com
can help simulate a user arriving from a Google search, which some websites use as a trust signal to serve less restricted or personalized content.
User-Agent
Accept-Encoding
Sec-Ch-Ua
(Client Hints)Sec-Fetch-Mode
Sec-Fetch-Site
Sec-Fetch-User
custom_headers
parameter to true in your API request. This enables your custom headers while ZenRows continues to manage sensitive browser-specific ones.
Referer
Referer
header. For instance, if you’re scraping a product page and want it to appear as if a user clicked on a Google search result, you might set:
What are custom headers, and why would I use them?
Referer
, Accept
, or Cookie
, to control how the request is perceived by the target server. This can be useful for handling sessions, mimicking specific browser behaviors, or requesting specific content types.Which headers are automatically managed by ZenRows®?
User-Agent
, Accept-Encoding
, Sec-Fetch-*
, and Client-Hints
. This helps ensure success and reliability when scraping protected or complex websites.Why are some headers forbidden?
Sec-Ch-Ua
and Accept-Encoding
are tightly coupled with browser behavior and could trigger anti-scraping mechanisms if set improperly. ZenRows prevents manual customization of these headers to ensure optimal success rates and avoid unnecessary blocks.What happens if I set a forbidden header?
Can I override the browser-based headers handled by ZenRows®?
Sec-Ch-Ua
, Accept-Encoding
, and Sec-Fetch-*
. These are managed by ZenRows to optimize performance and prevent blocks during web scraping.