Company Enrichment from Domain - Socials, Contacts, Logo, Tech

This Actor returns only what a company says on its own website. It does not return revenue or funding amounts, and it does not look anything up in outside databases, LinkedIn or search engines. A field the site does not state stays null; nothing is estimated.

Give it a list of company domains (the rows of a CRM or lead list where all you have is the domain) and get one row per company:

Group	Columns	Read from
Name	companyName, legalName	JSON-LD Organization, og:site_name, the copyright line, the page title
Description	description	meta description, og:description, JSON-LD (home page only)
Industry hints	schemaTypes, keywords	the JSON-LD @type and meta keywords the site itself declares; no classification is guessed
Address	addressRaw, street, city, region, postalCode, country	JSON-LD address
Founded, size	foundingYear, employeesMin, employeesMax	JSON-LD foundingDate, numberOfEmployees (only when the site declares them)
Official profiles	linkedinUrl, xUrl, facebookUrl, instagramUrl, youtubeUrl, githubUrl, tiktokUrl	JSON-LD sameAs, header and footer links
Contact	email, phone	JSON-LD, mailto: and tel: links
Logo	logoUrl	JSON-LD logo, header image, touch icon
Technologies	technologies (up to 10, with category)	home page HTML, scripts and response headers
Company pages	careersUrl, pricingUrl, blogUrl, docsUrl, statusUrl	home page links
Language	language	<html lang>

Every value comes with where it was read and how sure the reading is:

"provenance": {
  "companyName": { "source": "json-ld Organization.name", "page": "https://www.zotter.at/", "confidence": "high" },
  "xUrl": { "source": "footer link", "page": "https://example.com/", "confidence": "medium", "candidates": 2, "alternatives": ["https://x.com/other"] }
},
"lowConfidenceFields": ["phone"]

How it reads a site

• For each company the home page is read, plus up to 3 more pages of the same site found in its links (about, contact, legal notice): at most 4 pages per company. Each site's robots.txt is read first and followed.
• If you give a page address (an article, a product page), the site's home page is read instead, so the description is the company's and not one article's.
• No browser is used, so text that only appears after JavaScript runs is not seen. No proxies are used; a site that answers 403 or shows a check page is not retried through another route.

What is done about the usual mix-ups

• Share buttons (twitter.com/intent/tweet, facebook.com/sharer, linkedin.com/shareArticle), posts, videos, personal LinkedIn profiles and repositories are not accounts and are never returned.
• Other companies' accounts (customers, partners, embedded posts): a profile linked once in the header or footer, or listed in the company's own JSON-LD, is high. If a network has several different accounts, the one whose handle matches the company name is returned as medium; if none matches, the first is returned as low with the others in alternatives. A profile found only in the page body is low unless its handle matches the name.
• JSON-LD of someone else: parentOrganization, brand, seller, review and article authors are skipped; an organization whose url points to another site is not used.
• Several addresses or phone numbers: the first is returned as low, with the count.
• Email: only role addresses (info@, contact@, sales@ …) on the company's own domain (or a free-mail domain) and addresses the site declares in JSON-LD are returned. A role address on another organization's domain (a regulator or ombudsman named in a legal notice) is not returned. Addresses that look like a person's are not returned. A special-purpose address (press@, legal@, jobs@) is returned as low when it is the only one.

Measured on 40 real companies

Run in production on 2026-10-06 (Apify datacenter connection, no proxy): 12 SaaS, 8 manufacturers and retailers, 8 European, 4 Japanese, 8 small businesses. 34 of 40 home pages could be read; 4 sites refused the reader (HTTP 403/429), 1 disallows robots, 1 could not be reached. Those 6 rows were free.

"Read" is the number of the 34 readable sites where the field came back. "Right" is from a field-by-field check of 20 of them: each value was compared with the links and JSON-LD on the page it was read from and with the company's known official name and accounts (not every link was opened in a browser).

Field	Read (of 34)	Right (of those checked)	How it is returned
companyName	32	18 of 20	the 2 misses were site-edition names ("Brompton UK"); such names are now low
description	33	20 of 20	high
address	8	7 of 8	always low (below 90%; one site declares a regional office in its JSON-LD)
foundingYear	7	7 of 7 as the site states	high
employees	0	not measured	none of the 40 sites declares it
social profiles	26 sites, 117 links (109 high)	85 of 85 high links, no wrong one found	several candidates are medium or low
email	12	6 of 9 were a general contact	the 3 others were press@ / legal@, now low; a role address on another organization's domain is no longer returned
phone	4	3 of 3 with a single number	several numbers are low
careers / pricing / blog / docs / status	21 / 17 / 16 / 15 / 7	58 of 58 links, no wrong one found	high when address and link text agree, else medium
logo	34	not checked by eye	confidence from the source (JSON-LD logo high, favicon low)
technologies	33	not checked by eye	open fingerprint rules
language	34	as the site declares	high

Small sites and large retailers often state little in a machine-readable way; expect names, descriptions, profiles and pages far more often than addresses, founding years or employee counts.

Price

You pay per company row returned: company-returned, for a company whose name plus at least 3 more field groups were read. A site that could not be read, was refused, or stated too little is a free row that says why (and still carries whatever was read). No start fee.

Input

{ "domains": ["stripe.com", "www.hetzner.com", "https://www.zotter.at/"] }

1 to 500 domains per run. The same domain given twice is read and charged once.

Output example (shortened)

{
  "status": "ok",
  "input": "www.zotter.at",
  "domain": "zotter.at",
  "homepageUrl": "https://www.zotter.at/",
  "companyName": "Zotter Schokolade GmbH",
  "description": "500 verführerische Schokoladensorten im Online Shop …",
  "city": "Riegersburg",
  "country": "AT",
  "foundingYear": 1999,
  "linkedinUrl": "https://www.linkedin.com/company/zotter-schokolade",
  "xUrl": null,
  "email": "schokolade@zotter.at",
  "phone": "+43-3152-5554",
  "technologies": [{ "name": "TYPO3 CMS", "category": "CMS" }],
  "careersUrl": "https://www.zotter.at/das-ist-zotter/jobs",
  "language": "de",
  "fieldsFound": 11,
  "lowConfidenceFields": ["addressRaw", "street", "city", "region", "postalCode", "country"],
  "pagesRead": ["https://www.zotter.at/", "https://www.zotter.at/kontakt", "https://www.zotter.at/impressum"],
  "note": "Not stated on the pages read (left empty, nothing is guessed): employees. …"
}

Free rows have status too-little-data, blocked, robots-disallowed, robots-unreachable, login-required, not-found, unreachable, unreadable, not-html, bad-input or budget-reached, and a note with the reason.

Limits

• Values are what the site states; they are not checked against a register. Contact data is business contact data published by the company; you are responsible for using it lawfully.
• Pages built entirely by JavaScript return little (too-little-data, free).
• Related Actors by the same author: website-contacts for every email and phone on a site, website-technology-detector for the full technology list.

Thanks for using this Actor

We build these tools for people who run them every day, and we improve them from what users tell us.

• Missing a field, or need another filter? Tell us in the Issues tab. If the data is there, we add it.
• Found a bug or a wrong value? Post the run ID in the Issues tab. Wrong data is the thing we fix first.

If this Actor saved you time, a short review helps other people find it.