Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsTo add a custom header to a monitored website request in PageCrawl.io, open that page’s settings and enable Power User mode, which reveals Custom Headers. To set a cookie in the monitored page’s browser context, add a Custom JavaScript action that assigns document.cookie. These are separate from the Authorization header used to authenticate requests to PageCrawl’s own API.
Choose the right kind of request
First identify where the request is going. PageCrawl’s documentation describes three distinct mechanisms:
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
The Proxy Playbook: The Complete Guide to Proxy Servers: How to Source, Test, and Scale Residential,... | $29.95 | Buy on Amazon |
| 2 |
|
How to Host your own Web Server | $15.60 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
| What you need to configure | Where to configure it | What it affects |
|---|---|---|
| A custom HTTP header for the monitored target | The monitored page’s settings, with Power User mode enabled | Requests to the target website |
| A cookie in the monitored page’s browser context | A Custom JavaScript action | The page context before tracked elements are extracted |
| Credentials for calls to PageCrawl’s management API | The request’s Authorization header |
Requests sent to PageCrawl itself |
PageCrawl’s advanced-configuration guide lists Custom Headers among settings available in Power User mode. Its JavaScript actions guide documents setting a cookie with document.cookie. The API and webhooks guide documents Bearer-token authentication for the management API.
Recommended Free Tools
Add a custom header to a monitored target
- Open the settings for the monitored page.
- Enable Power User mode to reveal advanced settings.
- Find Custom Headers and configure the header for requests to that target.
The available help documentation does not specify the header-entry syntax or provide an example of configuring target headers through the API. Do not assume a particular form format, JSON key, or API payload. If you need to configure this only through the API, consult PageCrawl’s current OpenAPI specification at https://pagecrawl.io/api/openapi.yaml or an accessible developer reference before choosing field names.
Set a cookie in the monitored page’s browser context
PageCrawl’s documented approach is to add a Custom JavaScript action. The action runs in the browser context before tracked elements are extracted. Its published example is:
document.cookie = 'lang=en; path=/; max-age=86400'This example sets a cookie named lang to en, with the root path and a maximum age of 86,400 seconds. Change the cookie name, value, path, and lifetime to suit the site and the page being monitored. Browser cookie rules still apply; for example, JavaScript cannot set an HttpOnly cookie.
The documentation establishes this browser-action method, but does not confirm API payload keys for setting cookies. If you must configure cookies API-only, verify the current specification instead of guessing a field name.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Authenticate requests to PageCrawl’s API
The API’s Bearer token is for calls made to PageCrawl, not for authenticating to the website being monitored. The documented header format is:
Rank #2
Authorization: Bearer YOUR_API_TOKENUse this header when calling PageCrawl’s management API. It does not replace the monitored target’s Custom Headers setting or the browser-context cookie action.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common problems and fixes
- The target still rejects the request: Check that the header was added to the monitored page’s Custom Headers setting after enabling Power User mode. Confirm the target expects that header and that its value is current.
- A cookie is missing: Confirm the Custom JavaScript action is configured for the monitored page and that the cookie’s domain and path rules allow it to apply to the URL. JavaScript cannot create an HttpOnly cookie.
- The PageCrawl API returns an authentication error: Check that the API request, rather than the target request, includes
Authorization: Bearer YOUR_API_TOKENand that the token is valid. - You are configuring headers or cookies through an API payload: The cited readable guides do not establish the target-setting payload keys. Verify them in the current OpenAPI specification before sending the request.
Or skip the browser setup
If your goal is to capture a website rather than configure a PageCrawl monitor, ScreenshotNeo returns a screenshot or PDF with one request. Its clean-shot process accepts consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status in headers. ScreenshotNeo also provides an MCP server with screenshot, page-info, and PDF tools for AI agents.
For example, this cURL request saves a screenshot of stripe.com as WebP:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for request options. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
