Dancers Group Audition & Job Listings Scraper
JOBSLEAD GENERATION
Dancers Group Audition & Job Listings Scraper
Scrape dance audition and job listings from Dancers Group — a San Francisco-based nonprofit and one of the few freely accessible, non-paywalled aggregators for performing arts opportunities. Covers auditions, teaching jobs, residencies, and calls for submissions.
What it does
This actor crawls the Dancers Group website's category archives (/category/auditions/ and /category/jobs/), follows pagination, and visits each individual posting page to extract:
- Full description text
- Posting type (audition, job, residency, call for submissions)
- Dance style / genre
- Company or choreographer name
- Location
- Remote/virtual flag
- Posting date
- Application deadline
- Audition date and location
- Compensation details
- Requirements
- Contact email
- Apply links
Use cases
- Dance agents and casting platforms — monitor open calls across the Bay Area and beyond
- Performer job boards — aggregate non-paywalled audition data
- AI talent-matching SaaS — feed structured listings into performer-job matching pipelines
- Dance researchers — track trends in audition volume, compensation, and style demand
Output
Each record represents one posting. Key fields:
| Field | Description |
|---|---|
posting_id |
WordPress post ID |
posting_title |
Title of the listing |
posting_type |
audition, job, residency, or call_for_submissions |
dance_style |
Dance styles mentioned (e.g. ballet, contemporary) |
company_or_choreographer |
Submitting organization or individual |
location |
City / region |
is_remote |
true if the opportunity is virtual |
posting_date |
Date published (YYYY-MM-01 from URL path) |
deadline |
Application deadline (parsed from body text) |
description |
Full posting text |
contact_email |
Email address from the posting |
external_apply_url |
Application URL |
source_url |
Original posting URL |
Input
| Parameter | Type | Default | Description |
|---|---|---|---|
maxItems |
integer | 10 | Maximum number of records to return |
Notes
- Site is server-rendered WordPress — no JavaScript required
- Chrome user-agent is used automatically (bare requests return 403)
- No proxy needed: datacenter IPs with Chrome UA are accepted
- Pagination follows WP standard
/page/N/pattern — stops when no articles are found - Structured fields (deadline, compensation, requirements) are extracted via regex from free-text body; null is returned when not parseable