Home › Guides › LinkedIn company data

LinkedIn company data without a login: what's public, what isn't, and what each field means

A LinkedIn company page is one of the few places where firmographics, hiring activity and advertising sit side by side for almost every B2B company on earth. Most of that page is public HTML — no login, no API key. This guide covers exactly which fields you can read, which ones you cannot, where the numbers disagree with each other, and how to turn the page into a usable dataset.

What's actually public on a LinkedIn company page

LinkedIn renders the core of a company page server-side so that search engines can index it. That public layer is richer than most people assume:

• Identity — company name, LinkedIn slug, website, industry, company type (public, private, nonprofit).
• Scale — the self-selected company size band, the live employee count (members listing that employer) and the follower count.
• Location — headquarters, and the full street / locality / region / postal / country breakdown when the company has filled it in.
• Narrative — the tagline, the "About" description, founding year and specialties.
• Hiring — the number of open roles the company is advertising, and a link into that job list.

What is not public is everything attached to a person: member profiles, work histories, connection graphs, and any personal email or phone number. A no-login scraper reads the organisation, never its people. That distinction matters legally, and it also explains why tools promising "LinkedIn employee emails" are doing something categorically different — they are either using an authenticated session or joining against a separate contact database.

The three numbers that disagree — and which one to trust

Company pages carry three measures of size, and teams routinely mix them up:

The band and the count often disagree by a full tier, and that gap is itself information: a company still showing 51-200 while its member count crossed 400 is growing faster than its own page admits.

Hiring signals: reading intent, not just roles

The open-role count on a company page is the raw number. On its own it is a weak signal — big companies always have roles open. Three refinements turn it into a buying signal:

1. Department mix. Ten new sales roles and ten new platform-engineering roles imply completely different budgets opening. The function is the signal, not the count.
2. Velocity. The same page sampled weekly shows whether a company is expanding or backfilling. One snapshot cannot tell you that.
3. Seniority and location. A first senior hire in a new city is an expansion signal that precedes the press release by months.

LinkedIn is not the only place this shows up. Companies post the same roles on whichever applicant tracking system they bought — Greenhouse, Lever, Ashby, Workday and others — and those boards are fully public. If you do not know which ATS a target uses, an ATS-detecting scraper resolves it from the domain and returns the roles with the same schema whichever system it finds.

Advertising: the layer most teams forget

LinkedIn's Ad Library makes advertiser activity public. For competitive intelligence this is often more valuable than firmographics, because ad copy states positioning in the company's own words and the targeting parameters reveal who they think their buyer is. Two distinct questions live here:

• What is this specific company advertising? — track a known advertiser over time.
• Who is advertising in my category at all? — discover advertisers you did not know existed.

One honest caveat from our own measurements: LinkedIn serves the Ad Library through Cloudflare and blocks most datacenter and residential proxy IPs. Ad data is materially harder to collect reliably than company firmographics, and any tool that claims otherwise is either using a privileged network position or quietly returning partial results.

Turning a page into a dataset

A single company page is a research task. A thousand of them is a data pipeline, and the design questions change:

• Identify by slug, not by name. Company names collide across countries; the LinkedIn slug is unique and stable.
• Keep the raw and the derived. Store the size band and the parsed bucket, the employee count and the formatted string. Downstream systems want different shapes.
• Expect sparse fields. In our measured runs, specialties, founded and slogan populate on roughly half of pages — companies simply leave them blank. Build for that instead of treating a null as an error.
• Join on domain. The website host is the key that lets LinkedIn data merge with registry filings, funding data and tech-stack signals.

Which dataset for which question

Where LinkedIn fits in a wider stack

LinkedIn is a strong narrative source — how a company presents itself, what it says it does, how it describes its own growth. It is weaker as a source of verified fact, because every field on the page was written by the company.

That makes it a complement rather than a foundation. For verified identity and status you want the official register — see the KYB guide for what a register proves and what it does not. For size and sector at scale, firmographic enrichment is cheaper per record. For evidence of what a company is actually doing right now, ATS hiring data is harder to stage than a company page.

Used together the sources check each other. A company page claiming rapid growth alongside no open roles and a registry record showing no filings for two years is a story that does not hold up — and you only see the contradiction if you hold more than one source.

Is it legal?

Two separate questions get conflated here. Access: US courts have repeatedly declined to treat the reading of public web pages as unauthorised access under the Computer Fraud and Abuse Act. Contract: LinkedIn's terms of service prohibit automated collection, which is a matter between you and LinkedIn rather than a criminal one. On top of both sits data protection — and this is where the public/private line does real work. Company-level firmographics are business information about an organisation. Member profiles are personal data about an individual, and in the EU/UK that brings GDPR obligations with it. Staying on the company layer is not just safer technically; it is a different legal category.

None of this is legal advice. It is the distinction we build to: organisations, not people.

Frequently asked questions

Can you get LinkedIn company data without logging in?

Yes. The core of a company page — name, industry, size band, HQ, website, followers and description — is public HTML served to search engines. That layer needs no login and no API key. What sits behind authentication (member profiles, connections, personal contact details) is not available this way.

What's the difference between employee count and company size?

Company size is the band the company selected itself and rarely updates. Employee count is the live number of members listing that employer. For growth tracking use the count; for stable CRM matching use the band.

How do you detect hiring intent?

Open-role count tells you volume, department mix tells you where budget is opening, and week-over-week change separates expansion from backfill. The trend matters more than any single snapshot.

Why are some fields empty?

Companies leave them blank. In our measured runs, specialties, founding year and tagline each populate on about half of pages. That is the source being honest, not the scraper failing.

Try LinkedIn Company Scraper → See all 87 datasets