# Domain to LinkedIn URL Resolver: Homepage-First, No Guessing (`themineworks/domain-to-linkedin-resolver`) Actor

Resolve a company domain to its LinkedIn company page URL. Checks the company's own homepage for its LinkedIn link first, falls back to a search only when that link isn't there. No login, no API key.

- **URL**: https://apify.com/themineworks/domain-to-linkedin-resolver.md
- **Developed by:** [The Mine Works](https://apify.com/themineworks) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$17.50 / 1,000 domain resolveds

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Domain to LinkedIn URL Resolver: Homepage-First, No Guessing

🏆 Part of The Mine Works' 149-actor portfolio · 40,000+ runs · 200,000+ results delivered across our full distribution stack · 99.9%+ success rate

💰 $17.50 / 1,000 results.

> ⚡ Homepage first, not a guess. It checks the company's own site for its
> LinkedIn link before ever falling back to search.
>
> 💸 A domain that can't be resolved is never billed.

Give it a company domain and get back its LinkedIn company page URL. No login, no browser session, no API key.

### How it resolves a domain, and why that order

Most company websites link to their own LinkedIn page somewhere on the homepage, usually in the footer or header social icons. This actor checks that first: it fetches the domain's own homepage and looks for a `linkedin.com/company/` link in the HTML. Verified live across five real company sites, four resolved this way directly: Stripe, Figma, Asana and HubSpot all link their own LinkedIn page on their homepage.

Only when that link isn't found does the actor fall back to a single, narrow search for the domain against LinkedIn's public company pages. This two-tier order matters for two reasons: the homepage link is free (one HTTP request, no proxy) and near-certain, since the company chose to publish that link itself, while the search fallback is a best-effort match and costs more to run. Checking the free, high-confidence signal first, and only paying for a search when it comes up empty, is the same reasoning that keeps this actor's own price low.

### Input

- **domains** (required): one or more company domains, e.g. `"stripe.com"`. A full URL is also accepted; only the domain is used.

### Example output

```json
{
  "domain": "stripe.com",
  "linkedin_url": "https://www.linkedin.com/company/stripe",
  "source": "website_link",
  "resolved": true,
  "checked_at": "2026-08-30T00:00:00.000Z"
}
```

`source` is either `website_link` (found directly on the company's own site, high confidence) or `search` (found via a LinkedIn-restricted search match, best-effort). A domain that couldn't be resolved either way returns `resolved: false` with `linkedin_url: null`, and is never charged.

### Who this is for

Sales and RevOps teams enriching a list of company domains with the matching LinkedIn page before outreach or CRM import. Lead generation workflows that start from a domain (from a form fill, an email address, a WHOIS record) and need the LinkedIn company profile to complete the record. Anyone chaining company research: resolve the domain, then hand the LinkedIn URL to a company-employees or company-posts tool.

### Run it on a schedule

Most people run this as a one-off enrichment step on a domain list rather than
as a recurring watch, so run it whenever the list grows. If you do want it on a
timer:

1. Run it once with the input you want repeated, then click **Save as a task**
   so that exact input is attached to every future run.
2. In the Apify Console go to **Schedules** and create a new one, either a
   preset (hourly / daily / weekly) or a cron expression.
3. Save. It then runs unattended, billed the same pay-per-result way. Nothing
   is charged for the schedule existing.

### Use from Claude, ChatGPT & any MCP agent

Hosted MCP endpoint, no install, OAuth on first connect:

```
https://mcp.apify.com/?tools=themineworks/domain-to-linkedin-resolver
```

Claude Desktop / Cursor config (token auth):

```json
{
  "mcpServers": {
    "domain-to-linkedin-resolver": {
      "url": "https://mcp.apify.com/?tools=themineworks/domain-to-linkedin-resolver",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}
```

Ask your agent: *"Find the LinkedIn company page for stripe.com."*

### Frequently asked questions

**Why does `source` matter?** A `website_link` result came from the company's own published link, so it is effectively certain. A `search` result is a best match and, on a very common company name, could occasionally point at the wrong company; treat it as a strong lead to confirm rather than an absolute guarantee.

**Why wasn't a domain resolved?** Either the homepage doesn't link its own LinkedIn page and the fallback search also found nothing, or the domain didn't respond. The run log states which happened for each domain.

**Does this need a LinkedIn login?** No. It reads a public homepage link, or performs a public search; it never logs into LinkedIn or scrapes a LinkedIn page directly.

**How many domains can I run at once?** Up to 30 per run. The fallback search tier is the more expensive path, so the cap keeps a run's cost bounded even if every domain needs it.

### Pricing

| Event | Price | You pay when |
| --- | --- | --- |
| Domain resolved | $0.0175 | A domain is matched to a LinkedIn company page URL |

$17.50 per 1,000 domains, one flat price on every Apify plan. There is no
per-run start fee on this actor. Pay per domain resolved, whichever tier found
it. A domain that couldn't be resolved is never charged.

### Part of the outbound prospecting toolkit

Chain domain to LinkedIn page to work email in one pipeline: this actor hands
off to [LinkedIn Email Finder](https://apify.com/themineworks/linkedin-email-finder).
If you're starting from a company name instead of a domain, resolve that first
with [Company Domain Finder](https://apify.com/themineworks/company-domain-finder).

Keywords: domain to LinkedIn, company LinkedIn page finder, resolve LinkedIn
company URL, CRM enrichment tool, B2B data enrichment, company research
automation

# Actor input Schema

## `domains` (type: `array`):

One or more company domains, e.g. "stripe.com". A full URL is also accepted; only the domain is used.

## Actor input object example

```json
{
  "domains": [
    "stripe.com"
  ]
}
```

# Actor output Schema

## `results` (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 = {
    "domains": [
        "stripe.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("themineworks/domain-to-linkedin-resolver").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 = { "domains": ["stripe.com"] }

# Run the Actor and wait for it to finish
run = client.actor("themineworks/domain-to-linkedin-resolver").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 '{
  "domains": [
    "stripe.com"
  ]
}' |
apify call themineworks/domain-to-linkedin-resolver --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,themineworks/domain-to-linkedin-resolver"
        }
    }
}

```

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/MhYq52BKgYPEQUvhC/builds/Fel03eAXzXerfIgsi/openapi.json