Zola Wedding Couples Scraper

Zola Wedding Couples Scraper

Scrape wedding couples from Zola's public directory by name or discover them directly from sitemaps. Each record returns partner names, wedding date, city, venue, and website URL. No login required. Export to CSV, JSON, Excel, or XML.

Zola does not offer a public API for its wedding couple directory, and manually browsing tens of thousands of registry pages is slow and unreliable. This Actor reads the public couple listings and wedding websites directly, pulling names, dates, locations, and venues in a consistent structure. Run it with a list of names you already have, or let it discover new couples from Zola's own sitemaps with filters for state and date range.

Who uses it	What they scrape Zola for
Wedding photographers	Build a prospecting list of engaged couples in a target city or state with a known wedding date.
Event planners	Understand upcoming wedding volume in a region and find couples with public venue and date details.
Market researchers	Analyze wedding date distribution and venue popularity by geographic area.
Registry analysts	Track which couples and locations are active across Zola's public directory over time.

What it does

This Actor collects Zola wedding couples by name search or sitemap discovery and returns each matched couple as a flat row with partner details, event data, and location.

• 🔍 Search by name: Provide a list of surnames or first-plus-last names and get up to 50 matching couples per term.
• 🗺️ Discover from directory: Pull couples straight from Zola's wedding sitemaps with no seed list, filtering by US state, date range, and scan budget.
• 🎲 Randomized scanning: Each discover run starts at a random sitemap and offset so repeated runs cover the whole directory and avoid duplicates.
• 🗓️ Date range filter: Set a lower and upper wedding date bound in discover mode to target couples marrying in a specific window.
• 🇺🇸 State filter: Enter a full state name or two-letter code to keep only couples located in that state during discover runs.
• ✅ Complete-leads filter: Drop records missing partner names, a wedding date, or a city so your dataset stays clean and actionable.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Zola data

📸 Build a local prospect list for a photography studio.

A wedding photographer runs discover mode with a state filter and a date range, exports the dataset, and contacts couples marrying nearby in the next six months.

📍 Map wedding venue demand by US region.

A market researcher runs discover mode weekly with different state filters and aggregates venue and date data to spot regional trends.

🔎 Enrich a list of leads with wedding website details.

A planner uploads a list of surnames, runs search mode with enrichment on, and gets back split partner names, city, venue, and date for each couple.

🗓️ Monitor upcoming wedding activity for a vendor fair.

An event organizer runs discover mode with a narrow date window to identify couples most likely to attend a local bridal show.

🔄 Maintain a rolling fresh dataset for ongoing outreach.

A sales team runs discover mode on a schedule with randomized start to collect new couples each week without overlap.

Why choose this scraper

	What you get
Flat row output	One couple per row with partner names, wedding date, city, state, venue, and website link, no nested JSON to unpick.
Two collection modes	Search matches names you already hold, discover pulls fresh couples from the whole directory.
Enrichment on demand	Pull full wedding-website details including venue and split partner names, or skip enrichment in search mode for speed.
Skipped-record logging	When a filter drops a couple it is counted in the log, not silently lost, so you know your scan reach.
Reproducible runs	Override the random start with a fixed sitemap and offset to replay the same scan path.
Large-scale friendly	Built to handle up to a million couples per run with configurable scan budgets and limits.

How it compares

The Wedding Vendor Scraper covers Zola for vendor profiles, not couples. This Actor is purpose-built for the wedding couple directory and the data a couple leaves behind.

Feature	ParseForge	Wedding Vendor Scraper - 7 Sites
Scrapes Zola wedding couple directory	Yes, both search and discover modes	Not listed
Returns partner names, date, and location	Yes, enriched from wedding websites	Not listed
Sitemap-based discovery without seed names	Yes, via discover mode	Not listed
State and date range filter for couples	Yes	Not listed
Scrapes Zola vendor profiles	Not listed	Yes
Covers other wedding sites	Not listed	The Knot, WeddingWire, ISPWP, Honeyfund, Junebug, Azazie

Configure the run

Drive the Actor with couple names in search mode or let it walk Zola's wedding sitemaps in discover mode, and filters run as each couple is read so only matches reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
 "searchTerms": [
 "smith"
 ],
 "maxItems": 10,
 "maxScan": 2000
}

A larger pull:

{
 "searchTerms": [
 "smith"
 ],
 "maxItems": 200,
 "maxScan": 2000
}

Pricing

Pay-per-result: $0.006 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$0.60
1,000 results	$6.00
10,000 results	$60.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the Zola Wedding Couples Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to Zola through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/zola-couples-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results in discover mode?

Your state or date filter may be too narrow for the couples scanned within the maxScan budget. Increase maxScan, remove filters one at a time, or widen your date window and run again.

Why are some fields empty in my results?

Not every couple has a public wedding website. When enrichment is enabled, fields that are not present on the couple's site will be empty. Run without the 'only complete leads' filter to include those records.

Why does my search term return no matches?

Zola's search returns only public couples. Try using only a surname, or different partner name combinations. Check for typos, and note that very common surnames return up to 50 matches but some names may not appear in the directory.

What does the 'only complete leads' filter skip?

It drops any couple missing a partner name, a wedding date, or a city. Skipped couples are counted in the run log so you can see how many were removed.

I see duplicate couples across runs. Is that expected?

When using the default randomized start, runs can overlap if they happen to sample the same sitemap region. Set a fixed start sitemap and offset and pair it with a date or state filter to control coverage precisely.

FAQ

Question	Answer
What is the difference between Discover and Search mode?	Discover mode walks Zola's wedding sitemaps and pulls public couples without needing any seed list. Search mode looks up couples by name and returns up to 50 matches per term you provide.
Does this Actor require a Zola login or API key?	No. It reads only publicly visible couple directory pages and wedding websites, so no account or application is needed.
What fields does enrichment add?	Enrichment visits each couple's public wedding website and returns city, state, venue name, wedding date, and splits a combined partner name into two separate fields.
Why am I getting fewer results than my maxItems setting?	In discover mode a state or date filter drops non-matching couples after they are fetched, and the maxScan budget limits how many are examined. Check the run log for skipped counts.
How does the randomized start work?	Discover mode begins at a random sitemap (1 to 17) and a random offset inside it so each run pulls different couples. Turn it off and set fixed sitemap and offset values for repeatable runs.
Can I scrape only couples in a specific US state?	Yes. In discover mode fill in the US State field with a full name or two-letter abbreviation. The Actor fetches couples then keeps only those with a matching location.
Does this Actor scrape wedding vendors or registries?	No. It collects couple profile and wedding-website details only. Vendor data is not included in the output.
What is the maxScan budget and how should I set it?	maxScan is the hard ceiling on how many couples discover mode will fetch and inspect. If your filters are narrow, set it higher than the target result count so the scan has room to find matches.
How do I get the list of sitemaps to use a fixed start?	The Actor logs which sitemap it uses in each run. You can copy a sitemap number from a previous run log and paste it into the Start Sitemap field for exact reproduction.
Is enrichment available in Discover mode?	Enrichment is always on in discover mode so you receive location, venue, and date details for every couple that has a public wedding website.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Zola, Inc. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.