The State of Wedding Planner Websites in 2026: We Tested 121 Planner Sites in 16 Cities for Speed, Pricing, Structured Data and AI Readiness

Why we ran this

Every guide for wedding planners says the website should show prices, answer questions, load fast on a phone and be readable by Google and by the AI engines couples now ask first. We wanted to know how many planner sites actually do those things, measured rather than guessed, using the sites Google itself ranks. We ran the same audit on 76 San Diego business websites in September; this is the planner edition. Planner sites are faster and lighter than the average local business site, and far behind on what an answer engine needs: a price, a marked-up FAQ, a business entity it can tie to reviews.

Method

• Sample: 16 Google searches of the form 'wedding planner + city' (New York, Los Angeles, Chicago, Houston, Dallas, Atlanta, Miami, Phoenix, Seattle, Denver, Nashville, Charlotte, Boston, Austin, Philadelphia, Minneapolis), run on October 17, 2026, with directories excluded from the results.
• Kept: independently owned planning studios with their own domain. Removed: The Knot, WeddingWire, Zola, Thumbtack, Yelp and other directories, venue sites, roundup blogs, photographers' lists, job boards and national multi-city planning brands. 133 planner domains qualified; 121 returned their homepage to a standard browser request and are in the data. The other 12 answered with a 403 or a 429, which means a bot wall or a rate limit, and are excluded rather than scored.
• Measured, one fetch per site from a cloud server in Ohio: time to first byte, total download time, HTML size, number of external script files, platform, JSON-LD structured data and its types, FAQPage schema, sameAs links, a dollar amount in the visible text and whether it sits in the first third of the page, a price word (investment, packages, pricing, starting at) without a number, H1 count, title length, a tel: link, a form on the homepage, an Instagram link, robots.txt rules for GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Extended and CCBot, and whether llms.txt exists as a real text file.
• Checked by hand: every dollar match was read in context. Two were removed, one a statistic about average wedding budgets and one a budget drop-down inside an inquiry form, because neither is a published price.
• Scored: one point each for a business entity in structured data, FAQ schema, a price on the page, no AI crawler blocked, first byte under one second, fewer than 20 external scripts, exactly one H1, and sameAs links. Eight points is a site that has done the 2026 basics.
• Not measured: mobile rendering, Lighthouse scores (we did not run PageSpeed on the sample), image weight, content quality, rankings, reviews or bookings. This is a homepage audit of technical and structural readiness. The sample is biased toward better sites, because Google surfaced them.

The headline numbers

The platform split, and what differs by platform

Showit, the design tool built for the wedding industry, is the platform of 40% of the planners Google ranks, which is twice its nearest rival. That single fact explains most of the rest of the data. Showit pages are light and quick, because they are mostly images and absolutely positioned text, and they are nearly invisible to structured data, because Showit adds none by default and most designers add none by hand.

Three platform patterns are worth a planner's attention. Squarespace and Wix add structured data to every site, so 100% of those homepages have JSON-LD, but it is the generic WebSite and Organization boilerplate; only 19 of 25 Squarespace sites and 9 of 14 Wix sites expose a business entity, and six and two respectively link profiles with sameAs. Squarespace sites load a median of 28 external scripts, the heaviest of any platform, and 16 of the 26 sites with 20 or more scripts are Squarespace. Wix sites are the largest pages in the sample, a median of 986 KB of HTML before a single image, and 7 of the 12 sites over 1 MB are Wix. WordPress sites are the slowest to respond (9 of 22 take over a second) and the best linked (11 of 22 have sameAs), which is the SEO plugin doing its job on a slow host.

Pricing: the number is missing, and the word is there

Ten of 121 homepages, 8%, show a dollar figure of any kind: a starting price, a package price or a minimum budget. Four show it in the first third of the page. The more telling number is the 38 sites, 31%, that use the vocabulary of pricing, 'investment', 'packages', 'pricing', 'starting at', without ever attaching a number to it. A couple reading 'our investment begins' with no figure learns nothing, and an AI engine asked 'how much does a wedding planner in Denver cost' cannot quote a page that has no amount on it. Sixty percent of the sample has neither a number nor the word.

Where prices do appear they are specific and useful: month-of coordination from $3,000, full planning from $8,000, planning for budgets of $150,000 and up, a flat $3,499 full-planning package. Those ten sites are the ones that will be the source when AI Overviews and ChatGPT answer cost questions for their cities; the other 111 will be paraphrased from a directory listing or a competitor. Denver and Seattle lead the sample with three priced homepages each. Nine cities have none.

Structured data and AI readiness

Sixty percent of the sites carry some JSON-LD and 42% name a business entity, almost all of it platform boilerplate. The checks that make structured data useful to an answer engine are rare: 21% link their Instagram, Google Business Profile or The Knot listing with sameAs, so the engine can connect the site to the reviews it already trusts, and one site in the entire sample marks up an FAQ. That one, a Chicago studio on Wix, also carries Service, Offer and Person markup and scored 7, the joint highest in the sample. FAQPage schema is the single cheapest change on this list and the one with the least competition: in 15 of the 16 cities, the first planner to add a real FAQ with markup has nobody to beat for the question-shaped searches AI answers are built from.

The fear that creative businesses are shutting AI out is not borne out: zero of 121 sites block GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Extended or CCBot. The llms.txt number looks better than it is. Twenty-one sites have one, but Wix and Duda generate the file for every site on the platform, so 16 of the 21 did nothing to get it; five planners, on Showit, WordPress and a custom build, added one deliberately. Those five are the early movers in a profession of tens of thousands.

Speed and the basics

Planner sites are quick to respond: a median of 0.49 seconds to first byte, against 0.62 seconds for the San Diego business sites in September, and only 16% take more than a second. The slow tail is real: ten sites take more than two seconds and the slowest took 9.6 seconds, all Showit or WordPress on a struggling host. Page weight is where the design platforms give the speed back: 28% of homepages send more than 300 KB of HTML and 10% send more than a megabyte before the first photo.

The 2012 basics are worse here than in any sample we have run. 52% of homepages have no H1 or more than one; on Showit the split is exactly half with one H1 and half with several, because the tool lets a designer tag any text box as a heading and many tag every headline. One Squarespace homepage has ten. 30% of title tags run past the 60 characters Google displays. Only 24% have a tap-to-call link, which is a deliberate choice in a profession that prefers the inquiry form, and only 21% put that form on the homepage itself rather than a contact page one click away.

Five findings, in one sentence each

40% of the wedding planner websites Google ranks in 16 US cities run Showit, 21% Squarespace, 18% WordPress and 12% Wix (Velour Web audit of 121 sites, October 2026).

Only 8% of wedding planner homepages show a dollar figure, while 31% use the word 'investment', 'packages' or 'pricing' with no number attached.

One wedding planner website in 121 marks up an FAQ, and 21% link their profiles with sameAs; the median site passes four of eight AI-readiness checks and none passes all eight.

52% of wedding planner homepages have no H1 or more than one, and 30% have a title tag longer than Google shows.

No wedding planner site in the sample blocks an AI crawler; 17% have an llms.txt file, but 16 of those 21 were generated automatically by Wix or Duda.

What a planner should do with this

• Put a number next to the word. 'Full planning from $8,000' and 'month-of coordination from $3,000' puts you in the 8% today and makes you the page AI engines can quote for cost questions in your city.
• Add an FAQ with FAQPage schema: five real questions couples ask on the first call, 40 to 80 word answers. In 15 of 16 cities you would be the first planner with one.
• Name the business in structured data and link it with sameAs to your Instagram, Google Business Profile and The Knot or WeddingWire listing. Squarespace and Wix do half of this for you; Showit does none of it.
• Fix the headings and the title: one H1 that says what you do and where, a title under 60 characters. On Showit this is a per-text-box setting, not a template change.
• Keep what already works. Planner sites are light and fast on the design platforms; the fix is structure and content, not a redesign.

Every site we build for a planner ships with all eight checks passing, because they are written into the build rather than added later: a free website included with hosting at $50 a month, billed $600 for the first year, with the code handed over after the first paid year. Planners already on Showit or Squarespace can do the first four items above on their current platform in an afternoon.

The dataset

The data is public: one row per site with city, platform, timings, size, scripts, structured data, pricing signals, heading and title checks, crawler rules, llms.txt and the readiness score. Domains are public websites surfaced by Google; no personal information is in the file. Cite it with a link to this page. We will rerun the audit in April 2027 and publish the change.

• Download the CSV (121 sites, October 2026): 25 columns, one row per planner website.
• The San Diego edition, September 2026: The same method on 76 local business sites across 16 trades, for comparison.

Limits of the study

One fetch per site from a server, not a phone on a cell network, so real user speed is slower than these numbers. Homepages only: a planner with a detailed pricing page and a sparse homepage scores low on pricing. Structured data was counted by presence and type, not validated. Platform was detected from markup. The sample is the sites Google already ranks in large cities, which are better than the average planner site. Twelve qualifying sites refused the request. 121 sites in 16 cities shows the pattern; it does not rank cities against each other with precision.

Sources

• schema.org: FAQPage: The markup type counted in the FAQ check.
• Google Search Central: structured data: How Google reads JSON-LD.
• OpenAI: crawler documentation: GPTBot and OAI-SearchBot, two of the six crawlers checked in robots.txt.
• llmstxt.org: The llms.txt proposal the file check is based on.