LinkedIn company pages are the richest public source of firmographic data — industry tags, employee count ranges, founded years, headquarters, follower counts. Most B2B teams need this to score leads, plan ABM campaigns or build ICP-matched prospect lists.
Unlike profiles, small-medium company pages render fully without a cookie via JSON-LD. Big companies (Adobe, Apple, Microsoft) need a cookie because LinkedIn redirects them to the logged-in /posts/ view.
What you get per company
Up to 15 structured fields with graceful fallbacks when LinkedIn rotates layouts.
- Name + slug + canonical URL
- Industry classification
- Employee count range (e.g. "501-1,000")
- Type (Public, Private, Partnership, Non-Profit)
- Founded year
- Headquarters (city, country)
- Specialties (the tag list companies fill in)
- Website URL (LinkedIn redirect-wrapper unwrapped)
- Description (full About paragraph)
- Logo URL + follower count
Two-stage fallback for big companies
For companies like Adobe the main URL redirects to /posts/ which has no structured info. Kavex detects this and automatically navigates to /company/<slug>/about/ where the dt/dd panel lives. Transparent to the customer.
Multi-language label matching
LinkedIn renders labels in the cookie-owner's locale: "Industry" in EN, "Bedrijfstak" in NL, "Branche" in DE, "Secteur" in FR, "Sector" in ES, "Settore" in IT. Kavex maps all six to canonical English field names so your CSVs are uniform.
Every number on this page comes from that run, not from a price list.
Questions people ask
Do I need a cookie?
Not for most companies. Public pages have JSON-LD without auth. For big companies and highest fidelity, save a li_at cookie in Settings.
Can I scrape thousands in one job?
Practical cap ~500 per job (~30 min). We rate-limit to 1 req per 2.5-5.5s. Split bulk runs into multiple jobs.