💍 WeddingWire Couples & Wedding Website Scraper

🚀 Enrich a name into public wedding details in seconds. Type a partner's name, get back the couple's public wedding-website details: both partners' names, wedding date, city and state, countdown, and the public website link. Up to 20 couples per search term.

🕒 Last updated: 2026-07-08 · 📊 14 fields per record · Structured JSON/CSV/Excel/XML · Public WeddingWire wedding-website data only

This Actor is an enrichment tool for the public wedding-website data that couples themselves publish on WeddingWire. You provide a name (a first name, last name, or full name of one partner) and it returns the matching couples' publicly listed wedding-website details. It does not create or invent contact data, and it only reads information couples chose to make public in WeddingWire's open wedding-website directory.

Coverage: Each search term returns up to 20 public couples from WeddingWire's directory. Supply several names to cover more couples. Every record carries both partners' names (when the listing shows two), the wedding date and countdown, the couple's city and state, the public wedding-website URL, and the couple's cover photo when available.

🎯 Target Audience	💡 Primary Use Cases
Wedding vendors (venues, photographers, planners, caterers)	Confirm a couple's public wedding date and city before outreach
Registry and gifting services	Match a known couple to their public wedding website
Guests and family	Find a couple's public wedding website by name
Market researchers	Analyze aggregate public wedding timing and geography

📋 What the WeddingWire Couples Scraper does

• Searches WeddingWire's public wedding-website directory by name.
• Returns up to 20 couples per search term, each with structured fields.
• Parses the couple names into separate first and last names for both partners.
• Reads each couple's public wedding-website header for their city and state and welcome message.
• Outputs clean JSON, CSV, Excel, or XML you can pipe anywhere.

🎬 Full Demo (🚧 Coming soon)

⚙️ Input

Field	Type	Required	Description
mode	select (search / discover)	No	Run mode. search (default) looks up names you provide. discover browses WeddingWire's public wedding-website directory with optional state and date filters.
searchTerms	array of strings	For search mode	One or more names to search (a partner's first name, last name, or full name). Each term returns up to 20 public couples. Applies to search mode.
startWebId	integer	No	Discover mode only. Optional website ID to start from.
randomizeStart	boolean	No	Discover mode only. When on (default), starts from a fresh point so each run surfaces different couples.
usState	string	No	Discover mode only. Two-letter US state filter, e.g. FL.
weddingDateFrom	string	No	Discover mode only. Earliest wedding date to include (YYYY-MM-DD).
weddingDateTo	string	No	Discover mode only. Latest wedding date to include (YYYY-MM-DD).
maxScan	integer	No	Discover mode only. Budget: the maximum number of directory IDs to walk in a run.
maxItems	integer	No	Cap on total records. Free plan is limited to 10.
fetchDetails	boolean	No	When on (default), also reads each couple's public website for the welcome message and any public location. Turn off for a faster, names-only run.
onlyComplete	boolean	No	Only complete leads. When on, keeps only couples that have a partner name and a wedding date; sparse records are skipped and counted in the run log rather than silently dropped. Off by default.

Example 1 - enrich a last name

{
    "searchTerms": ["Smith"],
    "maxItems": 5,
    "fetchDetails": true
}

Example 2 - several names, names only

{
    "searchTerms": ["Garcia", "Nguyen", "Patel"],
    "maxItems": 60,
    "fetchDetails": false
}

⚠️ Good to Know: This Actor reads only publicly available wedding-website data that couples published on WeddingWire. It returns up to 20 couples per search term, and does not return venue, guest lists, RSVP data, or any private information. A couple's location appears only when the couple made it public.

🔀 Two modes

• search (default): look up a name you already have. Provide searchTerms and get back the matching couples' public wedding-website details. Best when you know who you're looking for.
• discover: no name needed. Walks WeddingWire's public wedding-website directory so you can browse it with optional usState and weddingDateFrom / weddingDateTo filters. It walks the newest public website IDs downward, so the most recent and upcoming weddings come back first. randomizeStart keeps runs fresh, and maxScan sets how many directory IDs a run is allowed to walk (your budget). onlyComplete pairs well with discover to drop sparse listings as you browse. Best when you have no name yet.

{ "mode": "discover", "usState": "FL", "maxScan": 5000, "maxItems": 500 }

📊 Output

Each record contains the following fields:

Field	Description
🖼 imageUrl	Couple's public cover photo (when set)
💑 coupleNames	Full couple names as published, e.g. "Dionna Smith & Reginald Smith Sr"
🧑 partner1FirstName	First partner's first name
🧑 partner1LastName	First partner's last name
🧑 partner2FirstName	Second partner's first name (when listed)
🧑 partner2LastName	Second partner's last name (when listed)
📅 weddingDate	Wedding date (MM/DD/YYYY)
⏳ daysUntilWedding	Days remaining until the wedding
📍 location	Couple's public city and state
💬 welcomeMessage	Couple's public welcome message
🔗 weddingWebsiteUrl	Public wedding-website URL
🆔 webId	WeddingWire website ID
🔎 searchTerm	The search term that returned this record
🕒 scrapedAt	Collection timestamp (ISO 8601)

Real sample records (from a live searchTerms: ["Smith"] run):

[
  {
    "imageUrl": "https://cdn0.weddingwire.com/user/9530/1_1/320/jpg/gu_37800359.jpeg",
    "coupleNames": "Dionna Smith & Reginald Smith Sr",
    "partner1FirstName": "Dionna",
    "partner1LastName": "Smith",
    "partner2FirstName": "Reginald",
    "partner2LastName": "Smith Sr",
    "weddingDate": "08/18/2029",
    "daysUntilWedding": 1136,
    "location": "Coon Rapids, Minnesota",
    "welcomeMessage": "We are getting married!",
    "weddingWebsiteUrl": "https://www.weddingwire.us/website/W37800359",
    "webId": "W37800359",
    "searchTerm": "Smith",
    "scrapedAt": "2026-07-08T19:03:17.266Z",
    "error": null
  },
  {
    "imageUrl": null,
    "coupleNames": "Cameron Smith",
    "partner1FirstName": "Cameron",
    "partner1LastName": "Smith",
    "partner2FirstName": null,
    "partner2LastName": null,
    "weddingDate": "11/01/2027",
    "daysUntilWedding": 480,
    "location": "West Chester, Pennsylvania",
    "welcomeMessage": "We are getting married!",
    "weddingWebsiteUrl": "https://www.weddingwire.us/website/W43768094",
    "webId": "W43768094",
    "searchTerm": "Smith",
    "scrapedAt": "2026-07-08T19:03:17.429Z",
    "error": null
  },
  {
    "imageUrl": "https://cdn0.weddingwire.com/user/8859/1_1/320/jpg/gu_45369588.jpeg",
    "coupleNames": "Madeline Smith & Madeline Smith",
    "partner1FirstName": "Madeline",
    "partner1LastName": "Smith",
    "partner2FirstName": "Madeline",
    "partner2LastName": "Smith",
    "weddingDate": "06/27/2027",
    "daysUntilWedding": 353,
    "location": "Indianapolis, Indiana",
    "welcomeMessage": "We are getting married!",
    "weddingWebsiteUrl": "https://www.weddingwire.us/website/W45369588",
    "webId": "W45369588",
    "searchTerm": "Smith",
    "scrapedAt": "2026-07-08T19:03:17.557Z",
    "error": null
  }
]

✨ Why choose this Actor

• Structured output. Couple names are pre-split into first and last for both partners.
• Public data only. Reads WeddingWire's open wedding-website directory, no login.
• Honest scope. Returns exactly what is public: names, date, city and state, website link.
• Fast. A five-record enrichment finishes in a few seconds.
• Any format. JSON, CSV, Excel, or XML.

📈 How it compares to alternatives

Approach	Setup	Structured fields	Public-only	Maintenance
Manual directory lookup	None	No	Yes	High effort per name
Generic HTML scraper	High	No	Depends	You maintain parsers
This Actor	Minutes	Yes	Yes	Managed for you

🚀 How to use

1. Create a free Apify account at https://console.apify.com/sign-up?fpr=vmoqkp.
2. Open the WeddingWire Couples & Wedding Website Scraper.
3. Enter one or more names in searchTerms.
4. Set maxItems and choose whether to fetchDetails.
5. Run the Actor and export results as JSON, CSV, Excel, or XML.

💼 Business use cases

Wedding vendors	Registry & gifting
Verify a couple's public date and city before a personalized pitch.	Match a known couple to their public wedding website and registry link.

Market research	Guests & family
Study aggregate public wedding timing and geography by name cohort.	Locate a couple's public wedding website when you only know a name.

🔌 Automating WeddingWire Couples Scraper

Connect runs and datasets to Make, Zapier, Slack, Airbyte, GitHub, and Google Drive through Apify's integrations to push new records into your CRM, spreadsheet, or messaging channel automatically.

🌟 Beyond business use cases

• Research: aggregate public wedding-date and location trends.
• Personal: find a friend or relative's public wedding website by name.
• Non-profit: understand seasonal wedding geography for community planning.
• Experimentation: learn structured web-data extraction with a clean, public dataset.

🤖 Ask an AI assistant

Paste your exported dataset into ChatGPT, Claude, Perplexity, or Microsoft Copilot and ask it to summarize wedding timing, group couples by state, or draft personalized outreach.

❓ Frequently Asked Questions

Is this only public data? Yes. It reads WeddingWire's open wedding-website directory, which couples chose to make public. No login, no private data.

Does it return the venue? No. Venue, guest lists, and RSVP details are not available through the public directory, so they are not returned.

What fields do I get? Both partners' names (split into first and last), wedding date, days until the wedding, city and state, welcome message, public website URL, website ID, and a cover photo when available.

How many couples per search? Up to 20 per search term. Add more terms to cover more couples.

Can it find a couple with no name? Yes, with the optional discover mode. It browses WeddingWire's public wedding-website directory with state and date filters, so no name is required. It still reads only public pages and does not sell or provide contact data. Use the default search mode when you already have a name.

Why is location sometimes empty? The city and state appear only when the couple made them public on their website.

Why is partner2 sometimes empty? Some listings show only one partner's name.

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

Does the free plan work? Yes, limited to 10 records per run.

Is this affiliated with WeddingWire? No. It is an independent tool that reads only publicly available data.

🔌 Integrate with any app

Every run writes to an Apify dataset you can pull via API, webhook, or scheduled export into your own systems.

🔗 Recommended Actors

• Registry and gifting data enrichment Actors from ParseForge
• Directory and listing enrichment Actors from ParseForge
• Contact and profile enrichment Actors from ParseForge

💡 Pro Tip: browse the complete ParseForge collection.

🆘 Need Help? Open our contact form

⚠️ Disclaimer: independent tool, not affiliated with WeddingWire. Only publicly available data collected.