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.