Weddingwire scraper: scrape WeddingWire vendors, profiles and reviews for wedding vendor leads

Scrape WeddingWire vendor listings, vendor profiles and reviews into clean JSON with this Weddingwire scraper. Built for wedding vendor leads, wedding market research, CRM enrichment and wedding industry data workflows, it delivers two joinable datasets (vendors and reviews) with 19 verified vendor fields. weddingwire scraper coverage focuses on US city and category pages using static HTML parsing — no browser required.

Main use cases

• Wedding vendor leads: Capture phone numbers, ratings, review counts, pricing, services, awards and profile links to enrich your CRM or sales pipeline with fresh wedding vendor data.
• Wedding market research: Track photographers, venues, caterers and other categories by US city to analyse pricing, coverage and Couples' Choice Awards trends for your target markets.
• Wedding venue pricing: Collect starting price text and profile details for wedding venues near me-style searches to benchmark rates across locations.
• Vendor reputation monitoring: Pull review text, dates, authors and ratings with includeReviews to monitor sentiment and flag changes over time.
• Wedding vendor directory enrichment: Build or validate a wedding vendor directory with structured, joinable records instead of scraping manually.

How it works

CheerioCrawler over static HTML — no browser. Based on verified behaviour (Oct 2026 validation against Common Crawl snapshots), this actor uses:

1. Embedded JSON-LD (application/ld+json, schema.org LocalBusiness) on every vendor profile (/biz/...) — primary source for name, full postal address, geo, telephone, aggregateRating (ratingValue + reviewCount), images and sample reviews. Parsed with JSON.parse with no DOM scraping for these core fields.
2. Structured listing cards (li.vendorTile) on category/location pages (/c/...-vendors.html and /shared/search?...) — each card carries data-vendor-info (vendor id, city/region/country, sector, address parts), data-ec-name, rating/review-count/location text, award flags (data-ribbon, "Award winner") and pricing text. Profile URLs come from the card's /biz/ anchor.
3. Dedicated review pages (/reviews/...) — followed for per-review text/date/author beyond the JSON-LD sample, with pagination up to maxReviewsPerVendor. Reviews embedded in JSON-LD are stored immediately when parsing the profile, so a blocked /reviews/... page costs extra reviews only — never the vendor row.

Anti-bot & reliability (verified): WeddingWire sits behind Akamai Bot Manager — direct requests from datacenter/VPS IPs return HTTP 403 ("Access Denied", AkamaiGHost). Enable Apify Proxy (residential recommended) for production runs. Without a proxy you will typically get 403s and zero rows.

Datasets: Two datasets — default (vendors) and reviews (non-default), joined on profileUrl. The actor enqueues up to ~20% extra candidates (max 25) to replace blocked profiles (profiles blocked with HTTP 403/429 after retries do not consume a maxItems slot). maxConcurrency defaults to 8 with a floor of 4 in flight so profiles and reviews keep loading while listings parse; lower if you see HTTP 403. Free-plan runs return at most 10 vendors; paid runs up to maxItems.

WeddingWire API: there is none — build WeddingWire vendor data without official API access

WeddingWire does not publish a public developer API for vendor data, reviews or search results. This actor fills that gap by extracting only publicly available served HTML and JSON-LD from US city/state category and location pages, profiles and review pages. It does not rely on internal XHR/GraphQL, Algolia-style backends or __NEXT_DATA__ blobs (verified: none present on target surfaces). Website/social/phone fields depend on what each profile publicly lists — gated contact details may be absent (returned empty rather than guessed).

Wedding market research city by city: photographers, venues, caterers and more

Scale your wedding market research with location-targeted start URLs. The verified example targets US coverage: https://www.weddingwire.com/c/ny-new-york/new-york/wedding-photographers/10-vendors.html. Supply several area/city listing URLs in startUrls for fuller coverage (pagination follows explicit "next" links only). Track wedding photographers, wedding venues near me, wedding venue pricing, wedding vendor directory coverage and WeddingWire Couples' Choice Awards trends by city, category and region.

Input Parameters

All 7 input fields from input_schema.json are documented below.

Field	Type	Required	Default	Notes
startUrls	array	Yes	(prefill provided)	Listing pages (/c/...-vendors.html, /shared/search?...), vendor profiles (/biz/...) and/or review pages (/reviews/...). Listing pages auto-enqueue their vendor profiles.
maxItems	integer	No	50	Maximum number of vendor profiles to return (1–1000). Capped at 1000. Free users are capped at 10.
includeReviews	boolean	No	true	When enabled, individual reviews (text/date/author) are scraped from profile page plus /reviews/ page and written to the reviews dataset (one row per review). When disabled, no review rows are stored (and no vendor-review charges).
maxReviewsPerVendor	integer	No	10	Cap on individual reviews stored per vendor (1–100).
maxRequestsPerCrawl	integer	No	300	Safety cap on total HTTP requests (listings + profiles + review pages) (1–5000).
maxConcurrency	integer	No	8	Pages fetched in parallel (1–20). Crawl never drops below 4 in flight; lower if WeddingWire returns HTTP 403.
proxy	object	No	{ "useApifyProxy": false }	Standard Apify proxy picker. Enable Apify Proxy (residential recommended) for WeddingWire.

Output Fields

All 19 vendor fields from dataset_schema.json (default/vendors dataset). Reviews dataset fields (non-default) are listed in context below; both datasets join on profileUrl.

Vendors (default dataset) — one record per vendor:

• name (string) — Vendor business name
• category (string) — Vendor category (e.g. Wedding Photographers)
• address (string) — Full street address
• city (string) — City
• region (string) — State/region
• postalCode (string) — Postal code
• phone (string) — Phone number (when publicly listed)
• rating (number) — Average rating 0-5
• reviewCount (integer) — Total number of reviews listed by WeddingWire
• pricing (string) — Starting price / pricing text
• services (array) — Services offered (array of strings)
• awards (array) — Award names/badges (array of strings), including WeddingWire Couples' Choice Awards indicators when present
• website (string) — Vendor website (when listed)
• socialLinks (object) — Social profile links
• about (string) — About text from profile
• location (string) — Location text from profile/card (where present)
• profileUrl (string) — WeddingWire vendor profile URL (join key with reviews dataset)
• reviewsUrl (string) — WeddingWire dedicated reviews page for this vendor (when linked)
• sourceUrl (string) — Listing page the vendor was found on
• extractedAt (string) — ISO timestamp of extraction

Reviews (reviews dataset, non-default) — one record per review (when includeReviews is true):

• vendorName (string) — Vendor business name
• profileUrl (string) — Join key to vendors dataset
• position (integer) — Review position in sequence
• text (string) — Review text
• date (string) — Review date (as published)
• author (string) — Review author name
• rating (number) — Review rating (0-5 when present)
• reviewPageUrl (string) — Source review page URL
• extractedAt (string) — ISO timestamp of extraction

Join the two datasets on profileUrl. Reviews embedded in JSON-LD are stored immediately on profile parse.

Example Input And Output

Example Input (real field names, minimal working example)

{
  "startUrls": [
    {
      "url": "https://www.weddingwire.com/c/ny-new-york/new-york/wedding-photographers/10-vendors.html"
    }
  ],
  "maxItems": 50,
  "includeReviews": true,
  "maxReviewsPerVendor": 10,
  "maxRequestsPerCrawl": 300,
  "maxConcurrency": 8,
  "proxy": {
    "useApifyProxy": false
  }
}

Example Output (vendors dataset row with real field names)

{
  "name": "Example Wedding Photographer",
  "category": "Wedding Photographers",
  "address": "123 Example St",
  "city": "New York",
  "region": "NY",
  "postalCode": "10001",
  "phone": "+1 212-555-0100",
  "rating": 4.9,
  "reviewCount": 85,
  "pricing": "Starting at $2,500",
  "services": ["Engagement shoots", "Wedding day coverage", "Photo albums"],
  "awards": ["Couples' Choice Awards 2026"],
  "website": "https://example.com",
  "socialLinks": {
    "facebook": "https://facebook.com/example",
    "instagram": "https://instagram.com/example"
  },
  "about": "Professional wedding photography serving New York.",
  "location": "New York, NY",
  "profileUrl": "https://www.weddingwire.com/biz/example-photographer/abc123",
  "reviewsUrl": "https://www.weddingwire.com/reviews/example-photographer/abc123",
  "sourceUrl": "https://www.weddingwire.com/c/ny-new-york/new-york/wedding-photographers/10-vendors.html",
  "extractedAt": "2026-10-08T12:34:56.000Z"
}

Reviews row (joined on profileUrl):

{
  "vendorName": "Example Wedding Photographer",
  "profileUrl": "https://www.weddingwire.com/biz/example-photographer/abc123",
  "position": 1,
  "text": "Amazing photos, great experience!",
  "date": "2026-01-15",
  "author": "Alex R.",
  "rating": 5,
  "reviewPageUrl": "https://www.weddingwire.com/reviews/example-photographer/abc123",
  "extractedAt": "2026-10-08T12:34:56.000Z"
}

The Knot vs WeddingWire: what this scraper covers — and what it doesn't

This actor covers WeddingWire only (US city/state pages, profiles, reviews). It does not scrape The Knot. For comparison queries ("The Knot vs WeddingWire"), this means coverage is WeddingWire-specific. Alternatives to consider: The Knot (separate platform), Zola (directory/listings differ by region). The actor extracts only publicly available pages; no login, no bypass of gated flows.

Wedding industry data for CRM enrichment and lead-gen teams

The output is structured for direct ingestion into CRMs and databases. With includeReviews on, you get review-level detail; with it off, you pay only for vendor rows (see pricing). Use cases: wedding vendor leads generation, wedding business CRM enrichment, wedding industry mailing list validation/augmentation (note: some contact fields may be gated on source), and competitive intelligence for venues, photographers, caterers and planners.

Integrations & Automation

• Apify API: Trigger runs programmatically, poll status and download datasets via the Apify API.
• Webhooks: Send run completion notifications to your system.
• Zapier: Automate workflows (e.g. push new vendors/reviews to spreadsheets, CRMs or messaging tools).
• Make: Build no-code automations to transform and route data.
• Recurring schedule: For wedding vendor leads monitoring, reputation tracking or market research, schedule runs daily/weekly (recurring usage improves Store recommendation signals). Configure in Apify Console → Schedules.

Related Actors

Exactly 5 relevant actors from the WeddingWire/Wedding vendor cluster:

1. gio21/weddingwire-vendors-scraper — WeddingWire vendors scraper (same data surface, complementary coverage)
2. quarterly_jingo/weddingwire-scraper — WeddingWire scraper focused on vendor listings/profiles
3. fortuitous_pirate/weddingwire-scraper — WeddingWire vendor and review extraction
4. hanamira/wedding-vendor-scraper — Wedding vendor scraper covering vendor details and reviews
5. jungle_synthesizer/wedding-vendor-aggregator-scraper — Wedding vendor aggregator scraper for multi-source/vendor aggregation use cases

Relevance over ownership; all are established Store actors in this topic cluster.

FAQ

Does WeddingWire have an official public developer API?

No. WeddingWire does not publish a public developer API for vendor data, reviews, or search results. This actor extracts only publicly available HTML and JSON-LD from WeddingWire pages to provide structured data.

Why use this actor instead of the official API?

Because there is no official WeddingWire API. This actor provides structured JSON (vendors + reviews, joined on profileUrl) with 19 vendor fields extracted from static HTML/JSON-LD (CheerioCrawler), with clear input controls and predictable pay-per-event pricing.

What are the alternatives to this actor / this data source?

Alternatives include The Knot (separate platform), Zola (directory/listings differ by region), and other vendor directories. This actor only covers WeddingWire (US city/state pages).

How do I scrape WeddingWire vendor data for a specific city?

Use a WeddingWire city/category listing URL as startUrls. Verified example: https://www.weddingwire.com/c/ny-new-york/new-york/wedding-photographers/10-vendors.html. Add multiple listing URLs for broader coverage (pagination follows explicit "next" links only).

Can I get wedding vendor email addresses and phone numbers from WeddingWire?

phone is extracted when publicly listed on the profile. Website and socialLinks are best-effort when present. Some contact details may be gated behind contact forms on WeddingWire; the actor does not bypass gated flows and returns empty fields rather than guessing.

How many vendors and reviews does WeddingWire have?

WeddingWire is a large wedding vendor directory (US-focused in this actor's coverage). A single run returns up to maxItems vendors (free cap 10, paid up to 1000). Review counts per vendor come from the profile (reviewCount); total stored reviews are capped by maxReviewsPerVendor and includeReviews.

How much does a wedding venue cost?

Wedding venue pricing varies by city and vendor. This actor extracts pricing (starting price/pricing text) from listing cards and profiles where present, enabling wedding venue pricing comparisons across vendors/locations.

What are Couples' Choice Awards?

WeddingWire's Couples' Choice Awards recognize vendors based on reviews/ratings in the prior year. The actor captures award badges in awards[] when present on listing cards or profiles.

Is WeddingWire US-only for this actor?

Yes — verified coverage focuses on US city/state URL patterns (/c/...-vendors.html, /shared/search?...). Only US variants are targeted by examples and supported surfaces.

SEO Keywords

weddingwire scraper, scrape weddingwire, weddingwire vendors scraper, scrape weddingwire reviews, weddingwire api, wedding vendor scraper, wedding vendor aggregator, wedding vendor leads, wedding leads, wedding vendor directory, wedding vendor data, wedding industry data, wedding market research, wedding market size, wedding venue pricing, weddingwire couples choice awards, the knot vs weddingwire, wedding business software, wedding business crm, wedding industry mailing list, wedding photographers, wedding venues near me

For AI Agents & LLM Apps

Purpose: extract structured WeddingWire vendor profiles and reviews (US city/category pages) as joinable JSON for agents/LLMs to reason over wedding vendor data.

Minimal working input JSON (real field names):

{
  "startUrls": [
    { "url": "https://www.weddingwire.com/c/ny-new-york/new-york/wedding-photographers/10-vendors.html" }
  ],
  "maxItems": 50,
  "includeReviews": true,
  "maxReviewsPerVendor": 10,
  "maxRequestsPerCrawl": 300,
  "maxConcurrency": 8,
  "proxy": { "useApifyProxy": true }
}

Output field list (real dataset field names):

• Vendors (default): name, category, address, city, region, postalCode, phone, rating, reviewCount, pricing, services[], awards[], website, socialLinks, about, location, profileUrl, reviewsUrl, sourceUrl, extractedAt (19 fields)
• Reviews (reviews dataset): vendorName, profileUrl, position, text, date, author, rating, reviewPageUrl, extractedAt

Behaviors an agent should know:

• US-only coverage: targets US city/state WeddingWire pages (/c/...-vendors.html, /shared/search?..., /biz/..., /reviews/...).
• Two datasets, joined on profileUrl: vendors default; reviews non-default (only when includeReviews true).
• Proxy required for production: Akamai Bot Manager blocks datacenter IPs (HTTP 403) — use Apify Proxy (residential recommended). Without proxy expect 403s/zero rows.
• No login/bypass: extracts only publicly available HTML/JSON-LD; gated contact details may be empty (not guessed).
• Reviews handling: JSON-LD embedded reviews stored on profile parse; /reviews/ pages followed up to maxReviewsPerVendor. Disabling includeReviews prevents review rows and vendor-review charges.
• Caps & resilience: free-plan max 10 vendors; paid up to maxItems (1000). Blocked profiles don't consume maxItems slot (up to 20% extra candidates, max 25). maxConcurrency >=4 in flight; lower on 403. maxRequestsPerCrawl safety cap.
• Join key: always use profileUrl to link vendors and reviews.

Billing (pay-per-event, verified): result $0.001 per result (vendor row), vendor-review $0.0009 per review (DIAMOND $0.00085), Actor Start $0.00005. Reviews are billed only when includeReviews is true and the reviews dataset receives rows.

Legal & Compliance Disclaimer

This actor is independent and NOT affiliated with, endorsed by, or sponsored by WeddingWire (a third-party platform owned by The Knot Worldwide). It accesses only publicly available WeddingWire pages (category/location listings, vendor profiles /biz/..., and review pages /reviews/...) and extracts data from served HTML/JSON-LD as documented. No login credentials are used and no gated flows are bypassed. Users are responsible for their own compliance with WeddingWire's Terms of Service and applicable data-protection laws (including GDPR/CCPA where relevant). If output includes personal contact data (e.g. phone numbers, author names), it must not be used for unsolicited commercial outreach in violation of applicable law.