# Website Screenshot: Full Page or Mobile, with Blank-Page Checks (`madrasco/website-screenshot-checked`) Actor

Website screenshots of the URLs you list (first screen or full page, desktop or mobile, PNG/JPEG), each checked for blank page, HTTP error, bot-check page and height cut. Cookie banners hidden, never accepted. Honours robots.txt by default; blocked pages are reported, not bypassed.

- **URL**: https://apify.com/madrasco/website-screenshot-checked.md
- **Developed by:** [Jack Valmadre](https://apify.com/madrasco) (community)
- **Categories:** Developer tools, Automation, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 screenshot without problems

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Website Screenshots with Checks

Screenshots of the web pages you list — first screen or full page, desktop or mobile, PNG or JPEG —
and a machine check on every image, so you can tell a good capture from a blank page, an error page
or a bot-check page without opening each file. Made by Madrasco.

### What it does

For each URL you give it, the actor loads the page once in a headless Chromium browser, optionally
hides cookie banners, takes the screenshot, saves it in the run's key-value store and writes one
dataset row with the result of these checks:

| Problem code | Meaning |
|---|---|
| `http_error` | The page answered with an HTTP status of 400 or more (404, 429, 500 …). |
| `blank_image` | The image is almost one colour (a white or still-loading page). |
| `bot_check_page` | The page shows a bot check or challenge ("Just a moment…", "Verify you are human", captcha). It is reported, never bypassed. |
| `height_cut` | Full-page mode: the page is taller than your maximum height, so the image was cut there. |
| `load_timeout_partial` | The page had not finished loading after 30 s; the screenshot shows what was there. |
| `load_error` | The page could not be loaded at all (DNS error, refused connection, TLS error …). |
| `robots_txt_disallowed` | The site's robots.txt disallows the page (or the page it redirected to), so no screenshot was taken. |
| `robots_txt_unreachable` | The site's robots.txt could not be fetched (timeout, network error or server error), so the page was treated as disallowed and not loaded. |

A row with `ok: true` has no problems. Rows with problems are still returned, so you see every URL.

**Full page that is really full.** In full-page mode the actor scrolls down the page one screen at a
time so lazy-loaded images and sections appear, returns to the top, then captures the whole height up
to your maximum (default 15,000 px, up to 30,000 px). Longer pages are cut and flagged `height_cut`.

**Cookie banners hidden, never accepted.** With "Hide common cookie banners" on (the default), the
actor hides the banners of common consent tools (OneTrust, Cookiebot, Usercentrics, Didomi, Quantcast
and others) and banners it recognises by their text: a banner-like element that mentions cookies or
consent and has an accept/reject-style button. Nothing is clicked, accepted or rejected. It does not
catch every banner; `cookieBannersHidden` in each row says how many elements were hidden.

### Input

| Field | Default | |
|---|---|---|
| `urls` | — | Pages to capture, one per line. Also accepted: `startUrls` (strings or `{"url": …}` objects), `url`, `domains`. A missing `https://` is added. |
| `fullPage` | `false` | Whole scrollable page instead of the first screen. |
| `maxHeight` | `15000` | Full-page cut-off in pixels (500–30,000). |
| `device` | `desktop` | `desktop` (1280×800) or `mobile` (390×844 at 2× pixel density, iPhone user agent). |
| `format` | `png` | `png` or `jpeg` (quality 80). |
| `delaySecs` | `1` | Extra wait after the page's load event, for late content (0–30 s). |
| `hideCookieBanners` | `true` | Hide cookie banners as described above. |
| `respectRobotsTxt` | `true` | Skip pages the site's robots.txt disallows (also checked after redirects; an unreachable robots.txt counts as disallowed). |
| `concurrency` | `3` | Pages loaded at once in one browser (1–8). |

Example:

```json
{"urls": ["https://example.com/", "https://www.python.org/"], "fullPage": true, "device": "mobile"}
```

### Output

One dataset row per URL:

```json
{
  "url": "https://www.gov.uk/",
  "ok": true,
  "problems": [],
  "httpStatus": 200,
  "finalUrl": "https://www.gov.uk/",
  "title": "Welcome to GOV.UK",
  "screenshotKey": "screenshot-00000-01f7ac0c92.png",
  "screenshotUrl": "https://api.apify.com/v2/key-value-stores/…/records/screenshot-00000-01f7ac0c92.png?signature=…",
  "width": 1280, "height": 4550, "fullHeight": 4550,
  "bytes": 408995, "loadMs": 2829, "cookieBannersHidden": 1, "error": null
}
```

The screenshot files are in the run's key-value store, and a run summary (counts per problem) is in
its `OUTPUT` record. The dataset's "Screenshots" view shows the images inline.

### Measured on our test runs (2026-09-26, 1 GB memory)

- 20 well-known public sites, first screen: 17 OK; the 3 others were correctly flagged (an HTTP 429
  blank page, a 30 s load timeout, a deliberate 404). Median page time 4.2 s.
- 5 public sites, full page (2,078 to 4,550 px tall): 5 OK in 13 s of work; the GOV.UK cookie banner
  was hidden.
- 1 URL: 2.5 s of work, 5.5 s run time.

These are our runs, not a guarantee: speed depends on the sites you capture.

### Pricing

Pay per event: US$0.0015 per screenshot without problems (`screenshot`, rows with `ok` true), plus a
start fee of US$0.00005 per GB of run memory, charged once per run (US$0.00005 at the default 1 GB).
Rows with problems (`ok` false) are not charged. There is no extra charge for Apify platform usage.
Apify shows the price before you run, and you can set a maximum cost per run: once it is reached,
the remaining URLs are skipped and get no row.

### Limitations

- No proxies, logins or cookies you supply: pages are captured as an anonymous visitor from Apify's
  servers. Sites that block data-centre traffic show up as `http_error` or `bot_check_page`.
- Bot checks and captchas are never solved or bypassed, and robots.txt is respected by default.
- The checks are heuristics: a page that is mostly one colour on purpose may be flagged `blank_image`,
  and an unusual bot-check page may not be recognised.
- The text-based pass may occasionally hide a page element that isn't a banner but mentions cookies;
  turn the option off if something is missing.
- Cookie banners are hidden, not dismissed: some sites also dim or lock the page behind the banner,
  and some banners are not recognised.
- Only Chromium. Pages are loaded once each; no retries.

### Use with AI agents

Call it with just a list of URLs: `{"urls": ["https://example.com/"]}`. Read the dataset items; use
`ok` and `problems` to decide which screenshots to trust, and `screenshotUrl` to fetch each image.

### Your responsibility

You choose which pages are captured. Make sure your use of the screenshots respects the sites' terms
and any rights in their content; screenshots can contain personal data shown on the page. The actor
itself collects nothing beyond what the run stores in your own Apify storage.

### Support

Open an issue in the actor's Issues tab. Replies are written with AI assistance; the human owner
can be reached on request.

# Actor input Schema

## `urls` (type: `array`):

Pages to screenshot, one per line (http or https).

## `fullPage` (type: `boolean`):

Capture the whole scrollable page instead of the first screen.

## `maxHeight` (type: `integer`):

Full-page captures longer than this are cut here and flagged.

## `device` (type: `string`):

Screen size and device type.

## `format` (type: `string`):

PNG (lossless) or JPEG (smaller).

## `delaySecs` (type: `integer`):

Wait this long after the page has loaded, for late content.

## `hideCookieBanners` (type: `boolean`):

Hide the banners of common consent tools with CSS before capturing (nothing is clicked or accepted).

## `respectRobotsTxt` (type: `boolean`):

Skip pages the site's robots.txt disallows (also checked after redirects). If robots.txt can't be fetched (timeout, network or server error), the page is skipped and reported.

## `concurrency` (type: `integer`):

How many pages load in parallel in one browser.

## Actor input object example

```json
{
  "urls": [
    "https://example.com/",
    "https://www.python.org/"
  ],
  "fullPage": false,
  "maxHeight": 15000,
  "device": "desktop",
  "format": "png",
  "delaySecs": 1,
  "hideCookieBanners": true,
  "respectRobotsTxt": true,
  "concurrency": 3
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `files` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://example.com/",
        "https://www.python.org/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("madrasco/website-screenshot-checked").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": [
        "https://example.com/",
        "https://www.python.org/",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("madrasco/website-screenshot-checked").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://example.com/",
    "https://www.python.org/"
  ]
}' |
apify call madrasco/website-screenshot-checked --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,madrasco/website-screenshot-checked"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/HLX1Cn1loUVJJmJuJ/builds/2N18FzfUFtZrHbncq/openapi.json