πŸ”Ž 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

ScraperX

ScraperX

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 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