Wedding Vendor Scraper — The Knot + WeddingWire

Scrape wedding vendor profiles from The Knot and WeddingWire in a single run. Returns vendor name, contact info, social handles, ratings, awards, price range, and capacity — across both directories, in one flat schema.

---

Wedding Vendor Aggregator Features

• Crawls both The Knot and WeddingWire in one pass. Same input, same output schema. Deduping is on you.
• Pulls vendor email and website from The Knot profiles where the vendor has chosen to expose them. WeddingWire gates these behind a contact form, so those fields stay blank for WW records.
• Captures social handles from both platforms — Instagram, Facebook, Pinterest, X, YouTube — pulled out of structured profile data, not screenshot OCR.
• Extracts awards (Best of Weddings years, Hall of Fame, Couples' Choice) as a clean array of human-readable strings.
• Returns ratings, review count, price range, and venue capacity for every record. Vendor description is included as the marketing bio.
• Mix Knot category URLs and WeddingWire category URLs freely in searchUrls. The scraper picks the right path per host.

---

Who Uses Wedding Vendor Data?

• Wedding-industry SaaS — feed Honeybook / Dubsado / Aisle Planner outreach with verified vendor contacts and category context.
• Photo & video delivery platforms — pull photographers and videographers by city, then route into onboarding sequences.
• Insurance and payments brokers — score vendor categories by rating and review volume to size the addressable market before outreach.
• Market research — count vendors per category per region, or compare price-tier mix across cities. Numbers, not vibes.
• Agency lead-gen — build city-by-category prospect lists with social handles already attached, so the cold-DM step is one less manual step.

---

How Wedding Vendor Aggregator Works

1. Pick category or city URLs from The Knot, WeddingWire, or both. Drop them into searchUrls.
2. The scraper paginates each search URL up to maxPagesPerSearch, harvests vendor profile links, and fetches each profile.
3. The Knot path parses the inline vendor JSON the site embeds in its SSR HTML (full contact data). The WeddingWire path parses Schema.org LocalBusiness JSON-LD plus the social-link block.
4. Records are flushed to the dataset as they come in. The run stops when maxItems is reached.

---

Input

{
  "searchUrls": [
    { "url": "https://www.theknot.com/marketplace/wedding-photographers-austin-tx" },
    { "url": "https://www.weddingwire.com/c/tx-texas/austin/wedding-photographers/615-10-rca.html" }
  ],
  "platforms": ["theknot", "weddingwire"],
  "maxItems": 100,
  "maxPagesPerSearch": 3
}

Field	Type	Default	Description
searchUrls	array	required	Category or city pages on The Knot or WeddingWire. Mix freely — the scraper detects the platform from the host.
maxItems	integer	15	Cap on total records returned across all search URLs.
maxPagesPerSearch	integer	5	How many paginated pages to fetch per search URL. The Knot is ~33 vendors per page; WeddingWire is ~50.
platforms	array	["theknot", "weddingwire"]	Filter which platforms to keep. Useful when a search list contains both and you only want one.

The Knot only

{
  "searchUrls": [
    { "url": "https://www.theknot.com/marketplace/florists-nashville-tn" }
  ],
  "platforms": ["theknot"],
  "maxItems": 200,
  "maxPagesPerSearch": 7
}

WeddingWire only

{
  "searchUrls": [
    { "url": "https://www.weddingwire.com/c/ca-california/los-angeles-county/wedding-djs/803-7-rca.html" }
  ],
  "platforms": ["weddingwire"],
  "maxItems": 100,
  "maxPagesPerSearch": 5
}

---

Wedding Vendor Aggregator Output Fields

One record per vendor. Same flat schema across both platforms — platform tells you the source.

{
  "vendor_name": "Ashton Gardens Atlanta by Walters Wedding Estates",
  "category": "Reception Venues",
  "city": "Sugar Hill",
  "state": "GA",
  "postal_code": "30518",
  "phone": "(404) 885-8503",
  "email": "concierge@waltersweddingestates.com",
  "website": "https://waltersweddingestates.com/venues/ashton-gardens-atlanta/",
  "instagram": "https://www.instagram.com/ashtongardensatl/",
  "facebook": "https://www.facebook.com/ashtongardensatl/",
  "pinterest": "https://www.pinterest.com/agardensatlanta/",
  "twitter": "",
  "youtube": "",
  "rating": 4.8,
  "review_count": 142,
  "price_range": "$$$ – Moderate",
  "capacity": "251-300",
  "description": "Ashton Gardens is the Atlanta area's premier wedding venue...",
  "awards": ["Best of Weddings 2025", "Best of Weddings 2024", "Best of Weddings 2023"],
  "facets": ["Settings: Ballroom", "Settings: Garden", "Venue Service Offerings: Bar & Drinks"],
  "profile_url": "https://www.theknot.com/marketplace/ashton-gardens-atlanta-by-walters-wedding-estates-sugar-hill-ga-435421",
  "platform": "theknot",
  "vendor_id": "435421",
  "scraped_at": "2026-04-27T12:55:29.000Z"
}

Field	Type	Description
vendor_name	string	Vendor business name as displayed on the profile.
category	string	Vendor category (Reception Venues, Photographers, Florists, etc.). Normalized across both platforms.
city	string	City the vendor is headquartered in.
state	string	Two-letter US state abbreviation, or province / region label.
postal_code	string	ZIP / postal code.
phone	string	Vendor phone number, normalized to US format when 10 digits.
email	string	Vendor public email. The Knot only — WeddingWire gates email behind a contact form, so this is blank for WW.
website	string	Vendor's external website URL. The Knot only — WeddingWire routes outbound URLs through a redirect.
instagram	string	Instagram profile URL.
facebook	string	Facebook page URL.
pinterest	string	Pinterest profile URL.
twitter	string	X (Twitter) profile URL.
youtube	string	YouTube channel URL.
rating	number | null	Overall star rating (0-5).
review_count	integer | null	Number of reviews on the source platform.
price_range	string	Price tier label, e.g. $$ – Affordable, $$$ – Moderate.
capacity	string	Guest capacity tier for venues, e.g. 151-200. Empty for non-venue categories.
description	string	Vendor's marketing description / bio.
awards	array of strings	Awards and badges (Best of Weddings YYYY, Hall of Fame, Couples' Choice).
facets	array of strings	Attribute tags from the platform (settings, ceremony types, business attributes).
profile_url	string	Canonical URL to the vendor profile.
platform	string	theknot or weddingwire.
vendor_id	string	Source platform's internal vendor ID.
scraped_at	string	ISO 8601 timestamp when the record was captured.

---

FAQ

How do I scrape The Knot and WeddingWire vendor data?

Wedding Vendor Aggregator does both at once. Drop your category or city URLs from either site into searchUrls and the scraper paginates them, pulls every vendor profile, and writes flat records to the dataset. No code, no separate runs.

How much does Wedding Vendor Aggregator cost to run?

Wedding Vendor Aggregator runs on Apify's pay-per-event model — a small fixed start fee plus a tiny per-record fee. 100 records is roughly $0.20. 1,000 records is roughly $1.10. You only pay for records we actually deliver.

Can I get vendor email addresses?

Wedding Vendor Aggregator returns vendor email when it's publicly exposed on The Knot, which is most paid-tier listings. WeddingWire intentionally gates email behind a contact form to capture leads on its own platform, so WW records will have a blank email field. Same for website — Knot exposes it, WW doesn't.

Does it cover all 50 states or just one city?

Wedding Vendor Aggregator scrapes whatever search URLs you give it. The Knot has city-and-category index pages for every major US metro (e.g. wedding-photographers-austin-tx); WeddingWire uses region IDs in its URLs. To cover the country, add one URL per metro per category. There's no built-in nationwide crawl by design — that turns into millions of requests fast.

Does this need proxies?

Wedding Vendor Aggregator runs through Apify's US datacenter proxy by default, which both sites accept at modest concurrency. No CAPTCHAs to solve, no Cloudflare to clear. Both targets sit behind Akamai, but neither escalates to managed challenges at the volumes this actor runs at.

Why are awards labeled "BOW2025" sometimes in raw data?

Wedding Vendor Aggregator decodes The Knot's award codes for you. BOW2025 becomes Best of Weddings 2025, HOF becomes Hall of Fame. The output is human-readable. Unknown codes pass through verbatim so nothing gets silently dropped.

---

Need More Features?

Need extra fields, a different city / category mix, or a same-day variant scoped to one platform? File an issue or reach out through the actor's Apify page. We add fields and tune selectors regularly.

Why Use Wedding Vendor Aggregator?

• Two directories, one schema — most competing actors target only The Knot or only WeddingWire. This one normalizes both into a single flat record set so you don't have to merge later.
• Real contact data where it exists — pulls email and website directly from The Knot's embedded vendor JSON, which is more than card-only scrapers do, and labels the WeddingWire gaps honestly instead of returning empty profiles.
• Pay per record — ~$0.001 per vendor, fixed start fee. Nothing to subscribe to and no minimum commitment.