How to Scrape a Staff Directory
Use ProfileSpider to turn a public staff directory into a structured list of employees, roles, departments, and contact details. Open the directory in Chrome, extract visible staff, save them to a list, and export to CSV, Excel, or JSON.
Goal
What This Workflow Is For
Turn a public staff directory into a structured employee list you can save, enrich, and export.
Use this workflow when a company, university, hospital, government body, or organization publishes a public staff directory and you want the employee data in a spreadsheet.
Staff directories are useful for sales prospecting, recruiting, account research, and partnership outreach because they often list names, roles, departments, and sometimes direct contact details in one place.
This page is focused on the ProfileSpider workflow: open the staff directory in Chrome, extract the visible employees, save the rows to a list, optionally enrich missing details, and export the list 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 and signed in
- A public staff directory open in a normal Chrome tab
- Staff listings, cards, or rows visible on the page
- A rough idea of the columns you want, such as name, role, department, email, phone, location, and source URL
This workflow works best when the staff directory shows repeated listings in live HTML. If staff are hidden behind an intranet login you cannot access, extraction may be limited.
Fit
Best For / Not Ideal For
Set expectations before you install or run an extract.
Best for
- Company and corporate staff directories
- University, school, and faculty directories
- Hospital, clinic, and healthcare staff pages
- Government and public sector staff listings
- Department, team, and office directory pages
- Professional services firm staff pages
Not ideal for
- Intranet or staff-only directories behind a login you are not authorized to access
- PDFs, screenshots, or scanned staff lists with no live HTML
- Pages that only show photos without names, roles, or links
- Directories where data only appears after complex in-page interactions
- Single-employee profile pages with no repeated rows
Steps
Step-by-Step Workflow
- 1
Open the staff directory in Chrome
Go to the public staff, faculty, or employee directory and wait until the listings are fully loaded and visible in the browser.
If the directory has department or location filters, apply the filter you want before extracting so you capture the right segment.
- 2
Open ProfileSpider
Click the ProfileSpider extension icon. The extension will analyze the current page and prepare the extraction workflow.
- 3
Review the fields you want to capture
Common fields for staff directories include name, role or title, department, email, phone, location, profile URL, and source URL.
ProfileSpider structures the data visible on the page. Fields the directory does not publish may remain empty.
- 4
Run the extraction
Start the extraction. ProfileSpider turns the repeated staff listings on the page into structured rows. A normal page scrape uses one credit.
- 5
Save the staff to a list
Save the extracted rows to a new or existing list. Use tags or notes to record the organization, department, or research project.
For example, save rows to a list named “University X - Engineering faculty” or “Acme Corp - Sales staff”.
- 6
Enrich and export the staff list
Review the rows, remove anyone outside your target, and enrich missing details where useful. Export the saved list as CSV, Excel, or JSON for research or outreach.
Schema
What ProfileSpider Extracts
Default fields for this workflow. Add or remove columns before you extract.
- NameThe staff member or employee name shown in the directory listing.
- Role / TitleJob title, position, or role when the directory exposes it.
- DepartmentDepartment, team, faculty, or unit when shown, such as Sales, Engineering, or Cardiology.
- EmailAn email address if it is visible on the directory page. Missing emails can be handled later with email finding where available.
- PhoneA phone or extension number if the directory lists one.
- LocationOffice, campus, building, or city location when present.
- Profile URLA profile or bio page link when the directory provides one.
- Source URLThe URL of the staff directory page, useful for verification and deduplication.
Output
Example Output
What a downloaded file looks like. Real exports are saved as .csv, .xlsx, or .json.
| Name | Role | Department | Phone | Location | Profile | Source | |
|---|---|---|---|---|---|---|---|
| Maria Chen | Head of Engineering | Engineering | maria.chen@example.org | +49 30 123456 | Berlin Office | example.org/staff/maria-chen | example.org/staff |
| James Patel | Sales Manager | Sales | j.patel@example.org | London Office | example.org/staff/james-patel | example.org/staff | |
| Aisha Carter | Professor of Physics | Physics | a.carter@example.edu | +31 20 654321 | Amsterdam Campus | example.edu/people/aisha-carter | example.edu/directory |
Troubleshooting
Common Problems
The directory is split across departments
Open each department or filter, run the extraction, and save each batch to the same list with a department tag so the full directory is captured in one place.
Emails are missing or masked
Some directories hide or obfuscate emails. Save the visible data first, then use email finding where available and appropriate once you have a name and organization.
Names and roles are inside images
If staff details are embedded in images instead of live page text, extraction may be limited. Use pages where the information is rendered as normal web content.
The same person appears in multiple departments
Some staff hold cross-functional roles. Review duplicates inside the saved list and keep the source URL column for verification.
The directory uses pagination or A-Z filters
Extract each page or letter group and save each batch to the same list, then deduplicate before export.
Questions