Domain to LinkedIn URL Resolver Clay-Ready Company URL

🔗 What can Domain to LinkedIn URL Resolver do?

Give it a company domain or name and it returns that company's LinkedIn company URL, with social URLs and optional firmographics in the same flat row.

It derives the slug from the domain and validates it directly against LinkedIn, falling back to a web search when no variant matches. Every row carries a confidence value and a slug_mismatch flag so you know how much to trust it.

📦 What you get	⚙️ Features and integrations
🔗 LinkedIn company URL and slug, validated 💯 confidence and resolution_method on every row 🌐 Facebook, Instagram, X and YouTube URLs 🧾 19 flat fields, snake_case, one row per company	🎯 Nine slug variants validated by HEAD request 🧬 Firmographics from LinkedIn JSON-LD, optional 🚩 slug_mismatch quality flag for spot checks ⬇️ Export to JSON, CSV, Excel, HTML or XML

Bought by Clay users and RevOps teams whose LinkedIn URL column has gaps, and by anyone who needs a LinkedIn anchor before a social or ABM workflow.

🚫 Every field is best-effort and nullable. When a source is blocked, rate-limited, or simply does not carry the data for a company, the field returns null rather than a guess. Breakage shows up as null, never as a wrong value. Gate downstream logic on presence, not on assuming every row is complete.

💡 Why use Domain to LinkedIn URL Resolver?

If you want	Read these fields
The LinkedIn page	linkedin_company_url, linkedin_slug
To know whether to trust it	confidence, resolution_method, slug_mismatch
Other social profiles	facebook_url, instagram_url, twitter_url, youtube_url
Company size and sector	employee_count_approx, industry, hq_location, founded_year
Audience and copy	follower_count, company_description, logo_url

💯 confidence and resolution_method, and how to use them

resolution_method tells you how the URL was found:

Value	Means
pattern_match	Slug derived from the domain and validated directly against LinkedIn. Fastest and most reliable.
google_search	Found via web search. The value stays google_search for Clay column compatibility; the engine is actually DuckDuckGo.
not_found	Neither method returned a result.
error	No valid input was provided.

confidence tells you how much to trust it:

Value	Means
high	A pattern_match hit, or a search result that validates against LinkedIn and whose slug closely matches the domain
medium	A search result that validates but whose slug is only a loose match. Worth a quick review.
low	No result, a result that did not validate, or an error state

Pass high rows straight to enrichment. Route medium, not_found and any rows with key firmographics missing to manual review.

🚩 slug_mismatch is a quality flag, not an error

It is true when the resolved slug differs from the one derived from the domain. brex.com derives the stem brex, but the live page is /company/brexhq, so slug_mismatch is true.

That is the resolver landing on a non-obvious slug and telling you so. Useful when spot-checking a batch.

▶️ Ready-to-run examples

Example	What it does
Find a LinkedIn Company URL from a Domain	The core job
Get a LinkedIn URL from a Company Name	Name-only input
Domain to LinkedIn with Firmographics	URL plus company data
Company Domain to Social Media URLs	All four social platforms
Force a Fresh Re-resolution	Bypass the cache

📋 What data can Domain to LinkedIn URL Resolver extract?

19 fields per company.

Field	What it holds
linkedin_company_url, linkedin_slug	The resolved page
resolution_method, confidence, slug_mismatch	How it was found and how much to trust it
facebook_url, instagram_url, twitter_url, youtube_url	Other social profiles
employee_count_approx, industry, hq_location, founded_year	Firmographics, when includeFirmographics is on
follower_count	LinkedIn audience size
company_name, company_description, logo_url	Identity and copy
company_domain, run_date	Input echo and bookkeeping

⚠️ industry fills for roughly 80% of established companies and is null for the rest, because smaller companies leave the About section blank on their profile. The same applies to employee_count_approx and hq_location. These are explicitly nullable so a missing value never blocks downstream logic, and a null means "not published", never "zero".

⚠️ false and null mean different things on every row. false is a measurement: the actor looked and the answer was no. null is the absence of one: the actor could not look. When something it needed fails, the row comes back with degraded: true, a plain-language degradation_reason, and every field it could not measure set to null rather than to a confident false or 0. Filter on degraded before you trust a negative.

🛠️ How to find a company's LinkedIn URL from its domain

1. Open the Input tab and put a bare domain in company_domain.
2. Add company_name if you have it. It helps the search fallback.
3. Set includeFirmographics to "true" if you want company data as well as the URL.
4. Click Start.
5. Filter on confidence and spot-check anything with slug_mismatch: true.

🧪 Using it in Clay

Add an Apify enrichment column and map your domain column to company_domain. Every input is accepted as a string, which is what Clay sends.

Build a view filtered on confidence = "high" and route the rest to review. That single filter is the difference between a LinkedIn column you can automate against and one you cannot.

🧭 How resolution works

The actor derives a stem from the domain and validates up to nine slug variants against LinkedIn by HEAD request, with five attempts and residential IP rotation. When no variant matches, it falls back to a web search.

Firmographics, when enabled, come from the Organization JSON-LD on the public LinkedIn company page, with a search-snippet fallback for name and description when that page is unrecoverable. Social URLs come from a single search query with a site: restriction per platform, which stops a "share on LinkedIn" link inside a Facebook result from producing a cross-platform false positive.

💵 How much does it cost to resolve a LinkedIn URL?

You are charged once per company resolved.

Plan	Per company	Per 1,000 companies
Free	$0.006	$6.00
Bronze	$0.0057	$5.70
Silver	$0.0054	$5.40
Gold	$0.0051	$5.10

There is also an Actor start event at $0.00005, charged once per run per GB of memory.

💳 A not_found row is still billed. The actor validated up to nine slug variants against LinkedIn and then ran a search fallback, and reporting honestly that no page exists is a real answer. Turning includeFirmographics on does not change the price; it adds a page fetch and makes the run slower.

⌨️ Input

Everything is on the Input tab. Provide at least one of the first two.

Field	Type	Default	What it does
company_domain	string	none	Bare domain. Pattern matching needs this.
company_name	string	none	Helps the search fallback. Name-only input skips pattern matching.
includeFirmographics	string	"false"	"true" also fetches the LinkedIn page for company data.
skipCache	string	"false"	"true" forces a fresh resolution.

📤 Output

One flat row per company, exportable as JSON, CSV, Excel, HTML or XML.

{
  "company_domain": "brex.com",
  "company_name": "Brex",
  "linkedin_company_url": "https://www.linkedin.com/company/brexhq",
  "linkedin_slug": "brexhq",
  "resolution_method": "pattern_match",
  "confidence": "high",
  "slug_mismatch": true,
  "facebook_url": "https://www.facebook.com/brexhq",
  "instagram_url": "https://www.instagram.com/brexhq",
  "twitter_url": "https://twitter.com/brexHQ",
  "youtube_url": null,
  "employee_count_approx": 1200,
  "industry": "Financial Services",
  "hq_location": "San Francisco, California",
  "follower_count": 96000,
  "founded_year": "2017",
  "logo_url": "https://media.licdn.com/.../logo.png",
  "run_date": "2026-06-18T16:19:30.468Z"
}

💡 Tips

• Filter on confidence = "high" before anything automated touches the URL.
• Leave includeFirmographics off when you only need the URL. It is faster and costs the same.
• Supply both domain and name where you have them. Pattern matching needs the domain; the search fallback works better with the name.
• Treat a sustained pattern of one field going null across many rows (every row missing industry for a week, say) as a provider-side change worth flagging rather than a data problem on your side.

⚠️ Known limits

Renamed or recently deleted LinkedIn pages may stop validating until the slug heuristics catch up.

Smaller companies often omit industry, employee_count_approx or hq_location on their profile. Those fields return null rather than a guess.

Search engines can rate-limit entire proxy pools. The five-attempt residential retry contract defeats the common case, but a persistent pool-wide block nulls out the affected fields. The LinkedIn URL itself still resolves via pattern matching, which only touches LinkedIn directly.

Name-only input skips pattern matching and goes straight to the search fallback, which lands at medium confidence more often.

Two structural risks worth knowing. If LinkedIn ships a major About-section rewrite, industry is the most likely casualty and follower_count second; the JSON-LD fields are the most resilient because the actor reads schema.org contracts and stable data-test-id markers rather than CSS class names. Any breakage shows up as null, never as a wrong value.

❓ FAQ

Why does resolution_method say google_search when you use DuckDuckGo?

The value is kept for Clay column compatibility with existing tables. The engine behind it is DuckDuckGo.

What does slug_mismatch: true mean? Did something go wrong?

No. It means the live LinkedIn slug is not the one the domain implies, like brexhq for brex.com. It is a spot-check flag, not an error.

Why is follower_count null but the URL resolved?

Firmographics require a page fetch, which is only done when includeFirmographics is on, and it can be blocked transiently. The URL resolves independently.

Can I pass a company name with no domain?

Yes, but expect medium confidence more often, because pattern matching needs a domain.

Does it read personal LinkedIn profiles?

No. Company pages only.

🧩 Want other GTM data?

Mamba Labs builds custom actors for B2B go-to-market teams. The public versions of that work live here on the Store, so our users get the same tooling we build under contract.

🧑‍💼 GTM Hiring Signal Scraper	🧱 Tech Stack Detector
📡 B2B Buying Signals Aggregator	🔑 Job Board Keyword Scanner
🎯 ICP Fit Scorer	📋 Job Posting Monitor
📬 Domain Deliverability Checker	🏢 Company Firmographic Enricher
🌐 Company Social Presence Mapper	🪪 Company Identity Resolver
💰 Funding and Press Signal Scanner	🔄 Company Change-Event Feed
👤 People Finder and Email Verifier	🚀 Prospect Engine
🤖 AI Tooling Detector	📮 Outbound Stack Detector
📝 Publishing Frequency Tracker	✉️ Work Email Waterfall Finder
⏩ Sequencer Lead Push	🏅 Workplace Program Detector
👥 Team Page People Extractor	🧭 Company Discovery List Builder

Every actor in the suite takes a domain or a company and returns one flat row, so they stack in the same Clay table without reshaping anything.

🛠️ Need something custom built for you or your team? Tell us what you are trying to find and we will build it. Talk to Mamba Labs.

🆘 Support

Found a bug or a company that resolves incorrectly? Open an issue on the Issues tab with the domain and the row, and we will look at it.

ℹ️ Sourcing and legal. The LinkedIn URL is validated by HEAD request against LinkedIn's public company pages, and firmographics are read from the schema.org JSON-LD those pages publish. Social URLs come from public search with a per-platform site: restriction. No login is used and no personal profiles are read: company pages only. You are responsible for how you use the output.

⚖️ Unofficial

This actor is unofficial. It is not affiliated with, sponsored by, or endorsed by LinkedIn, Microsoft, Bing, DuckDuckGo or Brave. It reads publicly available pages only, with no account and no authenticated session.

Built by Mamba Labs.