💍 Zola Wedding Website & Couple Enrichment Scraper

🚀 Turn a name into public wedding details in seconds. Type a couple's name, get their public Zola wedding-website facts back: both partners' names, wedding date, city and state, venue, plus website and registry links. Up to 28 structured fields per couple, up to 50 matches per name.

🕒 Last updated: 2026-07-08 · 📊 Up to 28 fields per record · up to 50 couples per name query · US and international couples

This Actor is an enrichment tool for information couples have already chosen to publish on their public Zola wedding website. You give it a name, it looks that name up in Zola's own public "Find a Couple" directory and returns the public details Zola already shows to any wedding guest: partner names, the wedding date, the location, and the venue. It does not invent lists of people and it never touches private, passcode-protected sites.

Couples print their Zola website URL on save-the-dates and invitations precisely so guests can find these details. This Actor reads that same public page and hands the facts to you as clean CSV, Excel, JSON, or XML instead of copy-paste.

🎯 Target Audience	💡 Primary Use Cases
Wedding vendors (venues, florists, photographers, planners)	Confirm and enrich a couple's public wedding details from a name
CRM and event teams	Fill in wedding date, city, and venue for a known lead
Registry and gifting services	Resolve a couple to their public registry and website link
Researchers and analysts	Study public wedding trends (dates, venues, locations)

📋 What the Zola Wedding Website Scraper does

1. Takes one or more names you already have (a surname such as smith, or a partner's first last).
2. Queries Zola's public couple directory (the same search behind the "Find a Couple" page) and returns up to 50 matching public couples per name.
3. Optionally opens each couple's public wedding website and enriches the record with location, venue, split partner names, and the wedding headline.
4. Skips any passcode-protected (private) wedding site automatically. Only publicly visible data is collected.
5. Exports every record as CSV, Excel, JSON, or XML.

🎬 Full Demo (🚧 Coming soon)

⚙️ Input

Field	Key	Type	Required	Description
Mode	mode	select (search, discover)	❌ No	How the run finds couples. search (default) looks up names you provide. discover browses Zola's public wedding directory.
Search Terms (couple names)	searchTerms	array of strings	✅ In search mode	One or more names to look up. A surname or a partner's first + last name. Each term returns up to 50 public couples. Used in search mode.
US State	usState	string	❌ No	Discover mode only. 2-letter state filter, for example CA, to limit the directory to one US state.
Wedding Date From	weddingDateFrom	string (YYYY-MM-DD)	❌ No	Discover mode only. Only include couples with a public wedding date on or after this date.
Wedding Date To	weddingDateTo	string (YYYY-MM-DD)	❌ No	Discover mode only. Only include couples with a public wedding date on or before this date.
Max Scan	maxScan	integer	❌ No	Discover mode only. Cap on how many directory pages a run walks, so a run stays within a set budget and does not run too long.
Randomize Start	randomizeStart	boolean	❌ No	Discover mode only. When on (default), the run starts from a random point in the directory so each run returns a fresh set of couples.
Max Items	maxItems	integer	❌ No	Cap on records returned. Free plan is limited to 10.
Enrich with wedding-website details	enrichDetails	boolean	❌ No	When on (default), opens each public wedding site for location, venue, split names, and headline. Turn off for a faster names-and-links-only run.
Only complete leads	onlyComplete	boolean	❌ No	When on, returns only couples that have both names, a wedding date, and a city. Skips records with missing fields instead of returning blanks.

Example 1: enrich a single surname

{
  "searchTerms": ["haley"],
  "maxItems": 5,
  "enrichDetails": true
}

Example 2: resolve several known names, links only (faster)

{
  "searchTerms": ["smith", "garcia", "nguyen"],
  "maxItems": 50,
  "enrichDetails": false
}

⚠️ Good to Know: This Actor enriches names you already hold. It matches against Zola's public directory, so a very common surname can return many unrelated couples. Use a first + last name to narrow results. Passcode-protected wedding sites are private and are skipped by design.

🔀 Two modes

The Actor can run in two ways, set by mode:

• Search mode (default): look up a name you already have. Provide searchTerms and the Actor resolves each name against Zola's public "Find a Couple" directory. This is the behavior described above.
• Discover mode: when you do not have a name yet, browse Zola's public wedding directory instead. Optional filters narrow the browse: usState (2-letter US state), plus weddingDateFrom and weddingDateTo for a date window. maxScan caps how many directory pages a run walks, and randomizeStart (on by default) starts from a random point so each run returns different couples. As in search mode, only publicly published pages are read and passcode-protected private sites are skipped. Turning on onlyComplete pairs well with discover mode, keeping only fully-populated leads that have both names, a wedding date, and a city.

{"mode":"discover","usState":"CA","weddingDateFrom":"2026-01-01","weddingDateTo":"2026-12-31","maxScan":5000,"maxItems":500}

📊 Output

Each record contains up to 28 fields. Key fields:

Field	Key	Description
🖼 Image	imageUrl	Couple photo, when the couple made one public
💍 Couple	title	Couple display title (for example "Morgan & Haley")
🌐 Website	weddingWebsiteUrl	Public Zola wedding-website URL
🎁 Registry	registryUrl	Public Zola registry URL
👤 Owner First / Last	ownerFirstName / ownerLastName	First partner's name
👥 Partner First / Last	partnerFirstName / partnerLastName	Second partner's name
📅 Wedding Date	weddingDate	Wedding date (ISO, when public)
🏙 City / State	city / stateProvince	Couple's stated location
🏛 Venue	venueName	Venue name from the public schedule
📍 Venue Address / City / State	venueAddress / venueCity / venueState	Venue location details
🎉 Event	eventName	Public event name (Ceremony, Reception, and so on)
👗 Attire	attire	Dress code, when published
🗺 Map	googleMapUrl	Google Maps link to the venue
🎁 Has Registry / 🌐 Has Website	hasRegistry / hasWebsite	Whether the couple published each
🕒 Scraped	scrapedAt	Collection timestamp
❌ Error	error	Null on success

3 real sample records (from a live run on the name haley):

{
  "imageUrl": "https://s3.amazonaws.com/registry-images/setzerbain/95134dc3-7c35-4db7-baa1-13e8656e780d.jpg",
  "title": "Morgan & Haley",
  "weddingWebsiteUrl": "https://www.zola.com/wedding/setzerbain",
  "registryUrl": "https://www.zola.com/registry/setzerbain",
  "ownerFirstName": "Morgan",
  "ownerLastName": "Setzer",
  "partnerFirstName": "Haley",
  "partnerLastName": "Bain",
  "weddingDate": "2027-09-24",
  "city": "Connemara",
  "stateProvince": "Ireland",
  "venueName": "Cashel House Hotel",
  "venueCity": "Cashel",
  "venueState": "County Galway",
  "eventName": "Ceremony & Reception",
  "hasRegistry": true,
  "hasWebsite": true
}

{
  "title": "Bailey & Enrique",
  "weddingWebsiteUrl": "https://www.zola.com/wedding/haleysgethitched",
  "registryUrl": "https://www.zola.com/registry/haleysgethitched",
  "ownerFirstName": "Bailey",
  "ownerLastName": "Fabian",
  "partnerFirstName": "Enrique",
  "partnerLastName": "Haley",
  "weddingDate": "2027-06-18",
  "city": "Rockford",
  "stateProvince": "WA",
  "venueName": "The Greenhouse on Harvard",
  "venueAddress": "18602 S Harvard Rd",
  "venueCity": "Rockford",
  "venueState": "WA",
  "eventName": "Our Wedding",
  "weddingHeadline": "We're getting married!",
  "hasRegistry": true,
  "hasWebsite": true
}

{
  "title": "Katelin & Dylan",
  "weddingWebsiteUrl": "https://www.zola.com/wedding/agnewhaleywedding",
  "registryUrl": "https://www.zola.com/registry/agnewhaleywedding",
  "ownerFirstName": "Katelin",
  "ownerLastName": "Agnew",
  "partnerFirstName": "Dylan",
  "partnerLastName": "Haley",
  "weddingDate": "2026-12-12",
  "city": "Martinsville",
  "stateProvince": "VA",
  "venueName": "The Legacy at Hatcher Farm",
  "venueAddress": "163 Hatcher Farm Rd",
  "venueCity": "Martinsville",
  "venueState": "VA",
  "eventName": "Ceremony",
  "attire": "Casual attire",
  "hasRegistry": true,
  "hasWebsite": true
}

✨ Why choose this Actor

• Name in, facts out. Built as an enrichment step: give it a name you already have, get the public wedding details back.
• Clean, split fields. Both partners' first and last names are separated, not a single blob.
• Real venue data. Venue name, address, city, state, and a Google Maps link straight from the couple's public schedule.
• Public only. Private, passcode-protected sites are detected and skipped. No logins, no paywalls.
• Fast and light. Runs on plain HTTP, no browser and no proxy needed, so runs are quick and cheap.
• Any format. CSV, Excel, JSON, or XML in one click.

📈 How it compares to alternatives

Approach	Split partner names	Venue and location	Public-only, private skipped	Structured export
Manual copy-paste from a wedding site	Manual	Manual	You decide	❌
Generic HTML scraper	❌ Usually one blob	Hit or miss	❌	Needs cleanup
Zola Wedding Website Scraper	✅	✅	✅ Automatic	✅ CSV/Excel/JSON/XML

🚀 How to use

1. Create a free Apify account using this sign-up link.
2. Open the Zola Wedding Website & Couple Enrichment Scraper.
3. Enter one or more names under Search Terms (a surname, or a partner's first + last name).
4. Set Max Items and leave Enrich with wedding-website details on for full location and venue data.
5. Click Start, then download your results as CSV, Excel, JSON, or XML.

💼 Business use cases

Wedding venues and planners

Goal	How this Actor helps
Confirm an inbound lead's date and city	Enrich the name they gave you into a public wedding date and location
Understand a couple's plans	See their public venue, event names, and attire

Florists, photographers, and caterers

Goal	How this Actor helps
Prioritize by wedding date	Sort enriched leads by public wedding date
Route by geography	Filter on public city and state

Registry and gifting services

Goal	How this Actor helps
Resolve a couple to their registry	Get the public registry URL and website link
Verify a couple exists on Zola	Check the has-registry and has-website flags

CRM and operations teams

Goal	How this Actor helps
Fill gaps on known records	Add wedding date, venue, and location to a name you already hold
Keep data clean	Ingest structured CSV or JSON instead of manual entry

🔌 Automating Zola Wedding Website Scraper

Run this Actor on a schedule and pipe results anywhere with Apify integrations:

• Make and Zapier for no-code workflows
• Slack notifications when a run finishes
• Airbyte to load results into a warehouse
• GitHub Actions to trigger runs
• Google Drive to archive exports

🌟 Beyond business use cases

• Research: study public wedding trends such as popular dates, venues, and regions.
• Personal: find a friend's public wedding website or registry link from their name.
• Non-profit: understand event-planning patterns for community programs.
• Experimentation: a clean, real-world dataset for data and ML practice.

🤖 Ask an AI assistant

Paste your exported data into any assistant and ask away:

• ChatGPT
• Claude
• Perplexity
• Microsoft Copilot

Example prompts: "Group these couples by state" or "List venues with weddings after June 2026".

❓ Frequently Asked Questions

1. What does this Actor actually do? It enriches a name into public wedding-website details. You give it a name, it looks that name up in Zola's public couple directory and returns the public facts.

2. Is this a way to discover or buy a list of couples? There is an optional discover mode that browses Zola's public wedding directory and can filter by US state and wedding date, so you can use it without a name in hand. It still reads only publicly published wedding pages and skips private, passcode-protected sites. It does not sell or provide contact data. Search mode remains the default and simply enriches names you already provide.

3. Does it collect private or contact data? No. It collects only what a couple has chosen to publish publicly on their Zola wedding website. It does not collect emails, phone numbers, guest lists, or RSVPs, and it skips passcode-protected private sites.

4. Do I need a Zola login? No. Only publicly available pages are read. There are no logins or paywalls.

5. How many couples can one name return? Up to 50 public matches per name. Use a first + last name to narrow a common surname.

6. Which fields are always present? The slug, website and registry URLs, both partners' names, and the has-website and has-registry flags are consistently present. Location and venue appear when the couple published them.

7. Why are some venue or location fields empty? Because that couple did not publish them. The Actor never guesses; empty means not public.

8. What formats can I export? CSV, Excel, JSON, and XML.

9. Does it use a proxy or a browser? No. It runs on plain HTTP, which keeps runs fast and inexpensive.

10. How current is the data? Every record includes a scrapedAt timestamp and reflects the public page at run time.

11. Can I enrich many names at once? Yes. Pass an array of names under searchTerms and the Actor processes each in turn.

12. Is this Actor affiliated with Zola? No. It is an independent tool that reads publicly available data.

🔌 Integrate with any app

Every run produces a dataset you can pull via the Apify API, webhooks, or the built-in integrations above, so results flow straight into your CRM, sheet, or warehouse.

🔗 Recommended Actors

• Google Maps Scraper for venue and vendor business details.
• Instagram Profile Scraper for public vendor social profiles.
• Website Content Crawler for general public-site extraction.
• Contact Details Scraper for public business contact info.

💡 Pro Tip: browse the complete ParseForge collection.

🆘 Need Help? Open our contact form

⚠️ Disclaimer: This is an independent enrichment tool and is not affiliated with, endorsed by, or sponsored by Zola. It collects only publicly available data that couples have chosen to publish on their public wedding websites, and it skips private, passcode-protected sites. It does not provide contact details or private information. Use the data responsibly and in compliance with applicable laws (including privacy and data-protection rules) and Zola's terms.