๐Ÿ”Ž LinkedIn Mass Company Profile Finder avatar

๐Ÿ”Ž LinkedIn Mass Company Profile Finder

Pricing

from $3.99 / 1,000 results

Go to Apify Store
๐Ÿ”Ž LinkedIn Mass Company Profile Finder

๐Ÿ”Ž LinkedIn Mass Company Profile Finder

Pricing

from $3.99 / 1,000 results

Rating

0.0

(0)

Developer

Scrapium

Scrapium

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Share

Find LinkedIn company profile URLs in bulk from any list of keywords โ€” domains, brand names, product names, or plain descriptions. Powered by multi-engine search with smart proxy fallback, designed for sales & marketing teams who need verified LinkedIn pages at scale.


โœจ Why Choose Us?

  • ๐Ÿง  Multi-engine search โ€” DuckDuckGo + Bing combined for maximum coverage; results auto-merged and deduplicated.
  • ๐ŸŒ Country-subdomain aware โ€” Captures linkedin.com/company/โ€ฆ, fr.linkedin.com/company/โ€ฆ, uk.linkedin.com/โ€ฆ, etc., and normalizes to the canonical URL.
  • ๐Ÿ›ก๏ธ Smart proxy fallback โ€” Starts with no proxy (cost-saving), automatically escalates to datacenter then residential (3 retries) if blocked. Once a tier works, it sticks.
  • โšก Live results โ€” Every URL is pushed to the dataset as it's found so you can watch the run in real time.
  • ๐Ÿงฐ Robust โ€” Per-engine retries with exponential backoff, async concurrency, request jitter, and detailed logs.
  • ๐Ÿ’ธ Cost-efficient โ€” Default = no proxy = $0 traffic until needed.

๐Ÿš€ Key Features

FeatureWhat it gives you
๐Ÿ” Bulk keyword inputOne run, hundreds of companies
๐Ÿฆ† + ๐Ÿ”ท Two enginesDuckDuckGo + Bing for wider coverage
๐Ÿ›ก๏ธ 3-tier proxy ladderno-proxy โ†’ datacenter โ†’ residential
๐Ÿ” 3 residential retriesEach retry rotates the IP
๐Ÿงต Concurrent workersProcess many keywords in parallel
๐Ÿ“ฆ Live dataset pushWatch URLs roll in as they're found
๐Ÿ“Š Per-row attributionSee which engine returned each URL

๐Ÿ“ Input

FieldTypeRequiredDescription
urlsarray of stringsโœ… YesList of keywords to search for. Each line is searched independently.
proxyConfigurationobjectโŒ NoApify proxy config. Default = no proxy. Auto-escalates on block.

โš™๏ธ Internal defaults (not exposed in the UI): engines = DuckDuckGo + Bing โ€ข max results per keyword = 30 โ€ข base delay = 0.5 s with jitter โ€ข per-engine retries = 2 โ€ข concurrent workers = 3.

๐Ÿ’ก Example input

{
"urls": [
"alma.fr",
"Stripe payments",
"Anthropic AI",
"\"OpenAI\""
],
"proxyConfiguration": { "useApifyProxy": false }
}

๐Ÿ“ค Output

Each pushed item represents one (keyword โ†’ LinkedIn URL) pair. Live in the dataset, exportable as JSON / CSV / XLSX.

[
{
"linkedin": "https://www.linkedin.com/company/alma-studio-paris",
"input": "alma.fr",
"slug": "alma-studio-paris",
"foundBy": "bing+ddgs",
"proxyMode": "no-proxy"
},
{
"linkedin": "https://www.linkedin.com/company/alma-france-communication",
"input": "alma.fr",
"slug": "alma-france-communication",
"foundBy": "ddgs",
"proxyMode": "no-proxy"
},
{
"linkedin": null,
"input": "very-rare-keyword-12345",
"error": "ddgs: no results; bing: no results",
"proxyMode": "residential"
}
]

Field reference

FieldDescription
linkedinCanonical LinkedIn company URL (https://www.linkedin.com/company/<slug>). null if no results.
inputThe keyword exactly as you typed it.
slugThe LinkedIn slug (everything after /company/).
foundByEngines that returned this URL (ddgs, bing, or bing+ddgs).
proxyModeProxy tier in use when this result was fetched (no-proxy, datacenter, residential).
errorPresent only if all engines failed for this keyword.

๐Ÿš€ How to Use (Apify Console)

  1. Log in at https://console.apify.com โ†’ Actors.
  2. Open LinkedIn Mass Company Profile Finder.
  3. Paste your keywords (one per line) into the Keywords field.
  4. (Optional) Adjust Max Results / Keyword, Workers, Proxy.
  5. Click โ–ถ Start.
  6. Watch the logs โ€” each LinkedIn URL is logged as it is found.
  7. Open the OUTPUT tab when the run finishes (or while it's running).
  8. Export to JSON / CSV / XLSX.

๐Ÿค– Use via API

Trigger a run via the Apify REST API:

curl -X POST "https://api.apify.com/v2/acts/<ACTOR_ID>/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"urls": ["alma.fr", "Stripe payments"],
"maxResultsPerKeyword": 30,
"proxyConfiguration": { "useApifyProxy": false }
}'

Or asynchronously (returns a run ID):

curl -X POST "https://api.apify.com/v2/acts/<ACTOR_ID>/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "urls": ["alma.fr"] }'

๐Ÿ’ผ Best Use Cases

  • ๐ŸŽฏ B2B lead generation โ€” Convert a list of domains into LinkedIn company pages.
  • ๐Ÿ”ฌ Market research โ€” Map all companies matching a niche keyword.
  • ๐Ÿ“ˆ Sales intelligence โ€” Enrich CRM records with verified LinkedIn URLs.
  • ๐Ÿท๏ธ Brand tracking โ€” Find every public LinkedIn page mentioning a brand.
  • ๐ŸŒ Local market mapping โ€” Surface country-subdomain pages (fr., uk., de., โ€ฆ).

โ“ Frequently Asked Questions

Q: Does it work without a proxy? A: Yes โ€” by default it runs with no proxy to save cost. If a search engine blocks the request, it automatically escalates to datacenter โ†’ residential (3 retries).

Q: What does "found by bing+ddgs" mean? A: Both DuckDuckGo and Bing returned the same LinkedIn URL โ€” a strong signal that it is the correct match.

Q: Can I use my own proxy? A: Yes. Configure Apify proxy in the input. The fallback ladder still applies if your chosen tier gets blocked.

Q: Why some keywords return more URLs than others? A: Different brand names match different numbers of LinkedIn pages. Common words return more results; specific domains often return one or two.

Q: Are results live? A: Yes โ€” every LinkedIn URL is pushed to the dataset the moment it's found. You can monitor & export results while the run is still going.

Q: Is this scraping LinkedIn directly? A: No. The actor only reads publicly indexed metadata from search engines. It never logs into LinkedIn, never scrapes LinkedIn HTML, and never touches authenticated content.


  • โœ… Data is collected exclusively from publicly indexed search-engine results.
  • โŒ No private accounts. No authenticated content. No LinkedIn ToS-violating scraping.
  • โš–๏ธ End users are responsible for compliance (GDPR, CCPA, anti-spam, target ToS).

๐Ÿ“ฌ Support & Feedback