# Site Render: website text, emails & phones ($13/1K pages) (`mathtec/site-render`) Actor

Open company websites in a real browser and return each page's rendered text, emails, phone numbers, final URL, HTTP status and bot-challenge signals.

- **URL**: https://apify.com/mathtec/site-render.md
- **Developed by:** [Adam Rudd](https://apify.com/mathtec) (community)
- **Categories:** Lead generation, Developer tools, Automation
- **Stats:** 1 total users, 0 monthly users, 70.0% runs succeeded, 2 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $9.10 / 1,000 page rendered (datacenter proxy)s

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Site Render: company website text, emails & phones

Open company websites in a real browser (Playwright + Chromium, through Apify Proxy) and get back, for every page it
visits, **the facts on that page**: rendered text, email addresses, phone numbers, page title, final URL after
redirects, HTTP status, and signals that a bot-challenge page was served instead of the site.

It is built for sites that ordinary HTTP fetches can't read: pages that answer `403`, or that only show content after
JavaScript runs.

### What you get

One dataset row per page:

| Field | Meaning |
|---|---|
| `site` | the site's hostname (without `www.`) |
| `url`, `final_url` | the page requested, and where it ended up after redirects |
| `http_status` | the status the browser received |
| `title` | page title |
| `text`, `text_chars` | the page's visible text after rendering (capped by `maxTextChars`) |
| `emails` | addresses found in the text and in `mailto:` links |
| `phones` | UK-format phone numbers found in the text |
| `challenge_signals` | which bot-challenge phrases matched ("just a moment", "verify you are human", captcha, ...). Empty = none |
| `depth` | 0 = the start URL, 1 = a page followed from it |
| `fetched_at` | time of the fetch |

A page that fails to load gives a row with an `error` field instead, **and is not charged**.

If the input can't be run (no start URLs, a start URL that isn't an `http(s)` URL, a proxy setting the Actor can't use),
the run still ends *Succeeded* and returns a row with `status: "rejected"` and the reason in `error`. Nothing is charged
for rejected rows. Invalid start URLs are skipped this way while the valid ones are crawled.

Nothing is filtered or graded. Every page fetched comes back, and you decide what to keep.

### Input

| Field | Default | Notes |
|---|---|---|
| `startUrls` | *(required)* | company homepages or any page to start from |
| `followLinkWords` | `contact`, `about`, `team`, `people`, `news`, `products`, `services` and similar (see the input tab) | from each start page, also follow same-site links whose URL or text contains one of these words. Empty list = start pages only |
| `maxPagesPerSite` | 12 | pages per site, including the start page. The input form is pre-filled with 2 (and `https://www.gov.uk/` as the start URL) so a first try finishes in seconds; raise it for real crawls |
| `proxyConfiguration` | Apify Proxy (datacenter) | datacenter by default. Residential proxy (for sites that block datacenter IPs) is priced separately, per page, because Apify bills residential traffic per GB |
| `blockResources` | false | skip images, media and fonts (`blockResourceTypes`) while pages load. Text, emails and phones come out the same; pages load faster and use less proxy traffic. Measured on 20 sites: residential traffic per loaded page fell about 4.5x |
| `navigationTimeoutSecs` | 45 | per page |
| `waitAfterLoadMillis` | 1500 | extra wait after load, for late JavaScript |
| `maxTextChars` | 60000 | text kept per page |
| `maxConcurrency` | 10 | pages fetched in parallel |

### Measured

On 50 UK company websites that returned **HTTP 403** to a plain fetch (2026-10-16, datacenter proxy,
`followLinkWords` contact/about/team-style words): the browser reached **46 of the 50**, read real page content on
**34**, found email addresses on **23** and phone numbers on **17**. 258 pages loaded, 20 failed. One run (n = 1).

### Pricing

**One price per page that loads** (see the Pricing tab), with a higher price for pages loaded through residential proxy. Pages that fail are not charged. If you set a maximum cost for
the run, the crawl stops once it's reached.

### Responsible use

You are responsible for how you use the data you collect, including any personal data such as names, email addresses and
phone numbers, under the laws that apply to you (for example the UK GDPR). Respect the sites' terms.

# Actor input Schema

## `startUrls` (type: `array`):

One URL per company site (homepage). Each may carry userData {company_number, hex} which is copied to every output row.

## `followLinkWords` (type: `array`):

Admin setting (Scout agent-chose 2026-10-16, unruled): which internal links count as worth opening. Empty = homepage only.

## `maxPagesPerSite` (type: `integer`):

Admin setting (Scout agent-chose 2026-10-16 from the harvest benchmark: max_pages 12 gave no gain beyond it; unruled). Spend control, not a data judgement.

## `proxyConfiguration` (type: `object`):

Datacenter by default; set apifyProxyGroups \['RESIDENTIAL'] for sites that block datacenter IPs (10 GB/month on mathtec).

## `navigationTimeoutSecs` (type: `integer`):

Admin setting (Scout agent-chose 2026-10-16, unruled): seconds before a page load counts as failed.

## `waitAfterLoadMillis` (type: `integer`):

Admin setting (Scout agent-chose 2026-10-16, unruled): extra wait so JavaScript-built pages fill in.

## `maxTextChars` (type: `integer`):

Admin setting (Scout agent-chose 2026-10-16, unruled): rendered text kept per page; the rest is cut, not judged.

## `blockResources` (type: `boolean`):

When on, the browser cancels requests for the resource types listed in 'Resource types to block' before they download. Page text, emails and phones come from the page's HTML and scripts, so they are not affected; less data goes through the proxy, which matters most on residential proxy (billed per GB). Off = every resource loads, as before.

## `blockResourceTypes` (type: `array`):

Used only when 'Block images, media and fonts' is on. Playwright resource types: image, media, font, stylesheet, script, xhr, fetch, websocket, manifest, other. Blocking 'script', 'xhr' or 'fetch' can stop JavaScript-built pages from showing their text.

## `maxConcurrency` (type: `integer`):

Admin setting (Scout agent-chose 2026-10-16, unruled): pages open at once (cost/speed only).

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.gov.uk/"
    }
  ],
  "followLinkWords": [
    "contact",
    "about",
    "team",
    "people",
    "leadership",
    "management",
    "board",
    "directors",
    "staff",
    "news",
    "press",
    "media",
    "products",
    "solutions",
    "services",
    "customers",
    "clients",
    "case-stud",
    "partners"
  ],
  "maxPagesPerSite": 2,
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "navigationTimeoutSecs": 45,
  "waitAfterLoadMillis": 1500,
  "maxTextChars": 60000,
  "blockResources": false,
  "blockResourceTypes": [
    "image",
    "media",
    "font"
  ],
  "maxConcurrency": 10
}
```

# Actor output Schema

## `pages` (type: `string`):

Dataset items: site, url, final_url, http_status, title, text, text_chars, emails, phones, challenge_signals, depth, fetched_at; a page that failed to load has error instead.

# 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 = {
    "startUrls": [
        {
            "url": "https://www.gov.uk/"
        }
    ],
    "maxPagesPerSite": 2
};

// Run the Actor and wait for it to finish
const run = await client.actor("mathtec/site-render").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 = {
    "startUrls": [{ "url": "https://www.gov.uk/" }],
    "maxPagesPerSite": 2,
}

# Run the Actor and wait for it to finish
run = client.actor("mathtec/site-render").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 '{
  "startUrls": [
    {
      "url": "https://www.gov.uk/"
    }
  ],
  "maxPagesPerSite": 2
}' |
apify call mathtec/site-render --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mathtec/site-render"
        }
    }
}
```

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/0GG7jQ1UNRmM88zhH/builds/Qk67K5szqqEVpDu7h/openapi.json