Linkedin Company About Scraper

LinkedIn Company About Scraper — Industry, Size and HQ Data

LinkedIn Company About Scraper pulls a company's public "About" details — company name, industry, headcount range, headquarters location, and About-Us description — into structured JSON, no LinkedIn login or cookies required. Feed it a list of company URLs or plain usernames and get one typed row per company, ready for a CRM, spreadsheet, or database pipeline. Start a run on Apify to pull this data for your own company list.

What is LinkedIn Company About Scraper?

LinkedIn Company About Scraper is an Apify Actor that reads the public "About" section of any LinkedIn company page and returns it as clean JSON — company name, LinkedIn URL, website domain, industry, headcount, associated-members count, headquarters, and description. It does not require a LinkedIn account, login, or cookies; it only reads the logged-out public page. It's built for sales and recruiting teams building account lists, analysts tracking firmographics, and developers feeding a CRM or database pipeline.

What LinkedIn company data is publicly available to scrape?

A logged-out visitor to any LinkedIn company page can see its name, About-Us description, industry, headcount, headquarters, and website link — none of it requires a LinkedIn account.

Data Category	Publicly Available (no login)	Restricted (login required)
Company name & About description	Yes	—
Industry / category	Yes	—
Company size	Yes	—
Associated members count	Yes	—
Headquarters / location	Yes	—
Website domain	Yes	—
Employee list (names, titles)	No	Needs login
Job postings / open roles	No	Needs login

LinkedIn Company About Scraper only returns publicly visible data — what any visitor sees. Nothing behind a login wall.

What data can I extract with LinkedIn Company About Scraper?

Every run returns the same 10 fields for each company — identity/profile fields plus scrape-status fields — whether the lookup succeeds or fails.

Field	Description
company_name	The company's display name
linkedin_url	Normalized LinkedIn company URL that was scraped
domain	Company website URL, resolved from the About page
category	Industry / category shown on LinkedIn
location	Headquarters / locations text as shown on the page
description	The "About Us" summary text
number_employees	LinkedIn's "Company size" range or headcount text
associated_members	LinkedIn's "associated members" count (distinct from company size)
success	Whether the company name was successfully extracted
scraped_at	ISO timestamp of when the row was scraped

Company identity & profile fields

company_name, linkedin_url, domain, category, location, description — what the company is, where it's based, and what it does.

Scrape metrics & status fields

number_employees, associated_members, success, scraped_at — headcount signals plus whether the row is trustworthy and when it was collected.

🤖 Add-on: Need additional LinkedIn data?

If you also need this company's open-jobs count or individual job listings, LinkedIn Company Scraper & Open Jobs Finder returns everything here plus hiring data in one run. For employee rosters with decision-maker tagging, see LinkedIn Company Employees: AI & Lead Enrichment Scraper, and for contact emails tied to a company domain, see LinkedIn B2B Emails Scraper: Verified Email Finder.

How does LinkedIn Company About Scraper differ from the official LinkedIn API?

LinkedIn's official Organization API only returns data for LinkedIn Pages you administer, and requires manual Marketing Developer Platform partner approval before you can call it at all (LinkedIn API Partner Support Guide, checked 2026-07-25); LinkedIn Company About Scraper reads any public company page immediately, with no approval step.

Feature	LinkedIn Organization API	LinkedIn Company About Scraper
Access approval	Manual Marketing Developer Platform partner review	None — start a run directly
Company scope	Only pages you're an authorized admin of	Any public LinkedIn company page
Competitor/third-party data	Not accessible	Accessible (public pages only)
Login/auth required	OAuth2 app + member authorization	None
Setup time	Partner review cycle before first call	Minutes
Output	Platform-defined API response	Structured JSON dataset

Use the official API if you manage the LinkedIn Page yourself and are already an approved partner. Use LinkedIn Company About Scraper to pull public firmographics for any company — including ones you don't administer — without an approval process.

How to use LinkedIn Company About Scraper

Run LinkedIn Company About Scraper from its Apify Store listing or your Apify Console — no separate signup or API key beyond your Apify account.

1. Open LinkedIn Company About Scraper on Apify.
2. Add one or more entries to LinkedIn Company URLs or Usernames (startUrls) — the only required input.
3. Optionally set Proxy Configuration, Max Retries, and Request Delay to tune reliability.
4. Click Start.
5. Download results as JSON, CSV, or Excel from the dataset's Output tab.

How to scale to bulk LinkedIn company extraction

startUrls accepts an array, so one run can process any number of company URLs or usernames — add every company you need to the same list rather than starting separate runs. Each entry is fetched and pushed to the dataset as soon as it's scraped, so a long list of companies doesn't lose progress if a later URL fails.

What can you do with LinkedIn company data?

• A sales rep building an account list uses category and number_employees to shortlist companies before outreach.
• An operations analyst enriching a CRM uses company_name, location, and description to fill in missing account fields.
• A recruiter scoping a client uses number_employees and associated_members to gauge team size before reaching out.
• A market researcher compares category and location across a list of companies to map an industry's footprint.
• An AI engineer feeds description and category into an LLM or RAG pipeline to auto-summarize or classify a batch of companies by sector.

How does LinkedIn Company About Scraper handle rate limits and blocking?

Each company page is fetched with a headless Chromium browser (via Playwright) rather than a plain HTTP request, which reduces LinkedIn's HTTP 999 anti-bot response. A configurable Request Delay adds a base delay plus random jitter before every request to avoid firing requests back-to-back. If a request comes back blocked (HTTP 403, 429, or 999) and a residential proxy hasn't been tried yet, the Actor automatically switches from your configured proxy (or a direct connection) to Apify's Residential proxy pool and retries. Each company also gets its own retry budget, set by Max Retries, with a short increasing delay between attempts.

If a company still can't be fetched after all retries — or its page resolves to a genuine LinkedIn 404 (company not found) — the Actor pushes a row with success: false and empty fields rather than failing the whole run, so one bad URL never blocks the rest of the list. No CAPTCHA-solving is performed; a page that requires solving a challenge will exhaust its retries and return as a failed row.

⬇️ Input

Parameter	Required	Type	Description	Example Value
startUrls	Yes	array	List one or more LinkedIn company URLs (e.g., https://www.linkedin.com/company/company-name) or usernames (e.g., company-name).	["https://www.linkedin.com/company/microsoft", "google"]
proxyConfiguration	No	object	Choose which proxies to use. If LinkedIn rejects the proxy, a residential proxy will be used as a fallback.	{ "useApifyProxy": false }
maxRetries	No	integer	How many times to retry fetching a company page before giving up on it (e.g. on a temporary block or network error). Min 0, max 10.	3
requestDelay	No	integer	Base delay, in seconds, before each company request (a small random amount is added on top) to reduce the chance of rate-limiting. Min 0, max 30.	2

Example input

{
  "startUrls": [
    "https://www.linkedin.com/company/microsoft",
    "google",
    "gitlab"
  ],
  "proxyConfiguration": { "useApifyProxy": false },
  "maxRetries": 3,
  "requestDelay": 2
}

⬆️ Output

LinkedIn Company About Scraper writes one typed JSON row per company to the Apify dataset as soon as it's scraped, exportable as JSON, CSV, Excel, or HTML directly from the Output tab. Every row — success or failure — carries the same 10 fields, so the table never has misaligned columns.

Example output

[
  {
    "company_name": "GitLab",
    "linkedin_url": "https://www.linkedin.com/company/gitlab",
    "domain": "https://about.gitlab.com",
    "category": "Software Development",
    "number_employees": "1,001-5,000 employees",
    "associated_members": "8,214",
    "location": "San Francisco, California",
    "description": "GitLab is the most comprehensive AI-powered DevSecOps platform...",
    "success": true,
    "scraped_at": "2026-07-16T10:15:03.120Z"
  },
  {
    "company_name": "",
    "linkedin_url": "https://www.linkedin.com/company/a-company-that-blocked-the-request",
    "domain": "",
    "category": "",
    "number_employees": "",
    "associated_members": "",
    "location": "",
    "description": "",
    "success": false,
    "scraped_at": "2026-07-16T10:16:41.902Z"
  }
]

How does it work?

LinkedIn Company About Scraper opens each company URL in a headless Chromium browser, optionally routed through a proxy, and waits for the page's "Company size" and "associated members" sections to render before reading the HTML. It parses the page's embedded JSON-LD organization data, og: meta tags, and the visible About-panel text to fill each field, following external "Visit website" links (including LinkedIn's own redirector and common URL shorteners) to resolve the real company domain. If LinkedIn responds with a block status, the Actor switches to a residential proxy and retries; if a company slug genuinely doesn't exist, LinkedIn's own 404 response is detected and returned as a failed row rather than misread as real data. Only what a logged-out visitor can see is ever returned, and the same 10 field names are produced on every run regardless of how LinkedIn restyles its page.

Integrations

LinkedIn Company About Scraper runs on the Apify platform, so it works with anything that can call the Apify API, plus Apify's own no-code and agent integrations.

Calling LinkedIn Company About Scraper programmatically

from apify_client import ApifyClient

client = ApifyClient("<APIFY_API_TOKEN>")
run = client.actor("scraper-engine/linkedin-company-about-scraper").call(
    run_input={
        "startUrls": ["https://www.linkedin.com/company/microsoft", "google"],
        "maxRetries": 3,
        "requestDelay": 2,
    }
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Works in Go, Ruby, Node.js, cURL — any language that can make an HTTP request.

MCP integration for AI agents

This Actor is reachable through Apify's official MCP server, so an AI agent can call it as a tool. In Claude Desktop or Claude Code, add a connector pointed at https://mcp.apify.com and authorize your Apify account, or run the server locally with npx @apify/actors-mcp-server --actors scraper-engine/linkedin-company-about-scraper (APIFY_TOKEN set in the environment).

No-code tools (n8n, Make, LangChain)

In n8n, use the Apify node (or an HTTP Request node against the Apify run-sync-get-dataset-items endpoint) to trigger a run and pull results into your workflow. In Make, the Apify app's "Run an Actor and get dataset items" module does the same. In LangChain, Apify's integration lets you call this Actor as a tool or load its dataset into a document loader for RAG pipelines.

Is it legal to scrape LinkedIn company data?

Scraping publicly available company information — the kind any logged-out visitor can see on a LinkedIn company page — is generally permitted. LinkedIn Company About Scraper returns only publicly visible data: no login-gated content, no private messages, no employee-level personal data. Its output is business/product data (company name, industry, headcount, location, description) rather than personal data, so it's governed by LinkedIn's Terms of Service and general database-rights considerations rather than GDPR/CCPA-style personal-data rules. Consult legal counsel if your use case involves bulk storage of personal data.

Frequently asked questions

What LinkedIn company fields does LinkedIn Company About Scraper return?

It returns company_name, category (industry), number_employees, location, and description, plus linkedin_url, domain, associated_members, success, and scraped_at. See What data can I extract above for the full table.

Does LinkedIn Company About Scraper require a LinkedIn account or login?

No. It only reads the public, logged-out LinkedIn company page — no LinkedIn credentials, cookies, or session are needed.

How many companies can I extract in one run?

As many as you list in startUrls — it's an array, and every entry in it is processed in the same run. There's no separate bulk mode because the array input already handles it.

What happens if a company page is removed or doesn't exist?

The Actor returns a row with success: false and empty fields instead of failing the run. LinkedIn sometimes serves a localized "page not found" body at HTTP 404 for a nonexistent company slug; the Actor detects that 404 status and treats it as a genuine not-found rather than parsing the 404 page's own title/meta tags as if they were a real company.

Can I scrape multiple LinkedIn companies at once?

Yes — add multiple URLs or usernames to the startUrls array and they're all processed in the same run, each pushed to the dataset as soon as it's scraped.

Does LinkedIn Company About Scraper work with Claude, ChatGPT, and other AI agent tools?

Yes. It's reachable through Apify's MCP server for Claude and other MCP clients, and callable as a standard HTTP API endpoint by any agent framework that can make a request.

How does LinkedIn Company About Scraper compare to other LinkedIn company scrapers?

Compared to automation-lab's LinkedIn Company Scraper (checked 2026-07-25), which lists up to 18 fields including followerCount, foundedYear, specialties, and granular street/city/postal address, LinkedIn Company About Scraper is scoped to 10 About-page fields and additionally surfaces associated_members, a LinkedIn metric that competitor listing does not mention. It does not extract follower count, founded year, specialties, or logo/cover images.

Does LinkedIn Company About Scraper return data in a format LLMs can use directly?

Yes. Typed, normalized JSON with consistent field names across runs — no HTML parsing or CSS selectors needed. Pass it directly to an LLM, index it into a vector store, or feed it to an agent tool.

What happens when LinkedIn changes its layout or anti-bot system?

The Actor is maintained and its output field names stay stable across LinkedIn UI changes. No specific update turnaround is guaranteed.

Can I use LinkedIn Company About Scraper without managing proxies or browser infrastructure?

Yes. The Actor runs its own headless Chromium browser for every request and automatically escalates to Apify's Residential proxy pool on a block — you don't need to run a browser or manage proxy infrastructure yourself.

Which LinkedIn Company About Scraper fields work best for AI training data and RAG indexing?

For RAG, index description and category — the free-text fields with the most useful content. For structured training data, company_name, location, number_employees, and associated_members return consistently across records, though number_employees and associated_members are returned as the raw text LinkedIn displays (e.g. "1,001-5,000 employees"), not pre-parsed integers.

Related scrapers

Scraper	What it extracts
LinkedIn Company Scraper & Open Jobs Finder	Company firmographics plus open-jobs count and job listings
LinkedIn Company Employees: AI & Lead Enrichment Scraper	Employee rosters with decision-maker tagging and optional AI lead scoring
LinkedIn B2B Emails Scraper: Verified Email Finder	Business emails discovered via search, grouped by domain
LinkedIn Post Scraper	Public posts from a company or person's page
LinkedIn Profile & Credibility Analysis Scraper	Public profile data plus a 0-100 credibility score

Your feedback

Found a bug or missing a field? Let us know through the Actor's Issues tab on Apify or your usual Scraper Engine support channel — reports like these directly shape what we fix and add next.