How to Scrape a Company Team Page
Use ProfileSpider to turn a public company team page into a structured list of people, roles, profile links, social links, and source URLs. Save the results to a list, enrich missing details, and export to CSV, Excel, or JSON.
Goal
What This Workflow Is For
Turn a public company team page into a structured people list you can save, enrich, and export.
Use this workflow when a company website has a public team, leadership, staff, advisory board, partner, or people page and you want the people data in a spreadsheet.
Company team pages are often useful for sales prospecting, recruiting, partnership research, agency research, founder research, investor mapping, and account-based research.
This workflow is product-specific: open the company team page in Chrome, extract visible people profiles with ProfileSpider, save the rows to a list, optionally enrich missing details, and export the result as CSV, Excel, or JSON.
Prerequisites
Before You Start
Confirm the page and tooling match this workflow.
Before you start, make sure you have:
- ProfileSpider installed in Chrome
- A public company team page open in a normal Chrome tab
- Team members, staff cards, leadership profiles, or people rows visible on the page
- A rough idea of which columns you want, such as name, role, company, LinkedIn URL, email, location, bio, and source URL
This workflow works best when the team page shows repeated people cards or profile sections in live HTML. If the page only uses images, PDFs, or hidden content, extraction may be limited.
Fit
Best For / Not Ideal For
Set expectations before you install or run an extract.
Best for
- Company team and leadership pages
- Agency staff pages
- Startup team pages
- Advisory board and partner pages
- Investor, founder, or portfolio team pages
- University lab, department, or research group pages
- Consulting, SaaS, and service-company people pages
Not ideal for
- Pages with only one person or one profile
- Team pages where names and roles are embedded in images
- Private intranet pages or pages you are not allowed to access
- Pages where team members only appear after complex filters or interactions
- Company websites that do not expose useful people data
Steps
Step-by-Step Workflow
- 1
Open the company team page in Chrome
Go to the company’s public team, about, leadership, people, staff, or advisors page. Wait until all team members are visible.
If the page has tabs such as Leadership, Sales, Engineering, or Advisors, open the relevant tab before extracting.
- 2
Open ProfileSpider
Click the ProfileSpider extension icon while the team page is open. The extension will analyze the visible page and prepare the extraction.
- 3
Review the fields you want to capture
Common fields for team pages include name, role, company, department, LinkedIn URL, email, location, bio, image URL, website, and source URL.
ProfileSpider structures the information visible or discoverable on the page. Fields that are not present on the source page may remain empty.
- 4
Run the extraction
Start the extraction. ProfileSpider turns repeated team member cards or profile sections into structured rows. A normal page scrape uses one credit.
- 5
Save the people to a list
Save the extracted rows to a new or existing list. Use tags or notes to identify the company, research project, client, campaign, or account.
For example, you could save the list as “Acme leadership team”, “HR SaaS founders”, or “Agency decision makers”.
- 6
Export or enrich the list
Export the saved team list as CSV, Excel, or JSON. If key details are missing, use enrichment or email finding where available before exporting.
Schema
What ProfileSpider Extracts
Default fields for this workflow. Add or remove columns before you extract.
- NameThe team member, founder, advisor, employee, or leadership name shown on the page.
- RoleThe person’s job title, function, seniority, or team role if listed.
- CompanyThe company whose team page is being extracted.
- DepartmentDepartment, team, or category when the page exposes it, such as Sales, Engineering, Leadership, or Advisors.
- LinkedIn URLA LinkedIn profile URL if the team page links to one.
- EmailAn email address if it is visible on the team page. Missing emails can be handled later with email finding where available.
- BioShort biography, profile description, expertise, or background text if available.
- LocationCity, country, region, or office location when shown.
- Source URLThe URL of the team page or profile source used for verification and deduplication.
Output
Example Output
What a downloaded file looks like. Real exports are saved as .csv, .xlsx, or .json.
| Name | Role | Company | Department | Location | Source | ||
|---|---|---|---|---|---|---|---|
| Sofia Martin | Head of People | ExampleTech | Leadership | linkedin.com/in/sofiamartin | sofia@exampletech.com | Barcelona, Spain | exampletech.com/team |
| Daniel Weber | VP Sales | ExampleTech | Sales | linkedin.com/in/danielweber | Berlin, Germany | exampletech.com/team | |
| Nina Verhoeven | Founder & CEO | ExampleTech | Leadership | linkedin.com/in/ninaverhoeven | nina@exampletech.com | Amsterdam, Netherlands | exampletech.com/team |
Troubleshooting
Common Problems
The team page uses tabs or filters
Open the tab or filter you want first, then run ProfileSpider. For multiple departments, extract each tab separately and save the rows to the same list.
Some people are hidden behind a “load more” button
Click “load more” until the people you need are visible, then run the extraction.
Emails are missing
Many team pages show names, roles, and social links but not email addresses. Export the visible data first, then use email finding where available.
LinkedIn links are missing
If the company page does not link to LinkedIn profiles, ProfileSpider cannot always infer the exact profile. Keep the person name, role, company, and source URL for later research.
The page only shows profile images
If names and roles are embedded inside images instead of live page text, extraction may be limited. Use pages where the information is rendered as normal web content.
Questions