LinkedIn Company Scraper with Brand Pages and followers
Pricing
from $3.99 / 1,000 results
LinkedIn Company Scraper with Brand Pages and followers
Scrapes public LinkedIn company pages. Live-saves results per URL. Starts with user-selected proxy (or direct), falls back to Apify Residential if blocked, and keeps it.
Pricing
from $3.99 / 1,000 results
Rating
0.0
(0)
Developer
Scraply
Maintained by CommunityActor stats
1
Bookmarked
10
Total users
4
Monthly active users
a month ago
Last modified
Categories
Share
LinkedIn Company Profile Scraper With Brand Pages and Followers
Scrape any public LinkedIn company page — about, industry, size, headquarters, specialties, sample employees and posts — plus every affiliated brand, showcase, and subsidiary page it links to, each returned as its own row with its own industry, location, page type, and follower count. No login required.
What it does
Give it a list of LinkedIn company page URLs (e.g. https://www.linkedin.com/company/microsoft). For each one it returns:
- Company profile: name, description, industry, company size, headquarters, founding year, specialties, logo, website, sample employees, sample posts, similar/competitor pages.
- Follower count: the real number shown on the page (not estimated), plus the raw display text (e.g.
"28,748,750 followers"). - Affiliated pages: every showcase page, subsidiary, and regional/brand page LinkedIn lists under "Affiliated pages" — name, link, industry, location, logo, page type (
showcase/company), and country subdomain — with an option to fetch each one as its own full company row.
This is the one gap every other LinkedIn company scraper on the Store shares: none of them surface a company's brand/showcase page family as structured, filterable rows. If you're evaluating a large enterprise's LinkedIn presence, its showcase pages (product lines, regional arms, sub-brands) often carry their own audience and posting cadence worth tracking separately.
Input
| Field | Type | Default | Description |
|---|---|---|---|
urls | array (required) | — | LinkedIn company page URLs to scrape |
includeAffiliatedPages | boolean | true | List each company's affiliated/showcase/subsidiary pages on the parent row |
scrapeAffiliatedPages | boolean | true | Also fetch each affiliated page as its own full dataset row |
maxAffiliatedPagesPerCompany | integer | 10 | Cap on affiliated pages listed/fetched per company |
affiliatedPageType | enum (all/showcase/company) | all | Filter affiliated pages by type before fetching |
affiliatedIndustries | array | [] | Keep only affiliated pages whose industry text matches one of these keywords |
proxy | proxy config | — | Optional starting proxy; the actor auto-escalates to Residential on a block |
Output
Each row (whether a parent company or an affiliated child page) includes:
inputUrl, success, name, description, location, employeeCount, followerCount, followerCountText, website, logo, slogan, industry, size, founded, headquarters, type, specialties, similarPages, employees, posts, affiliatedPages, affiliatedPageCount, affiliatedShowcaseCount, affiliatedCompanyCount, matchedAffiliatedFilter, isAffiliatedPage, parentCompanyUrl, pageType, countryCode, error.
Affiliated child rows carry the same full schema as a parent row (isAffiliatedPage: true, parentCompanyUrl pointing back to the input URL).
Honest limitations
- Public pages only. This actor does not use login cookies. If a page requires a LinkedIn login to view (an authwall redirect, or no company data found in the page), the row is returned with
success: falseand an explanatoryerror— never faked data. - Anonymous fetch success rate varies. Public LinkedIn company pages are not always reachable without a proxy; the actor auto-escalates through Datacenter → Residential proxies on a block, but a fraction of runs may still return
success: falseon some URLs. This reflects the real, current state of anonymous access, not a code defect. - Follower count and employee count reflect what LinkedIn's page itself displays at scrape time — not a computed estimate.
- Affiliated pages are read one level deep only — a child page's own affiliated-pages box (if any) is not recursed into.
Use cases
- Enrich a target account list (ABM/sales) with company size, industry, and headquarters.
- Map a large enterprise's brand/showcase page family for social-media competitive research.
- Track follower growth across a company's main page and its regional/product sub-pages over time.
- Feed CRM or lead-gen pipelines with structured company data at scale.