What pages should a wedding planner website have?

Eight: home, about, services and packages with starting prices, a portfolio with a page per wedding, testimonials, an FAQ, a contact page with a qualifying inquiry form, and venue guides. The first seven turn visitors into inquiries. The venue guides are what bring visitors from Google in the first place.

What should a wedding planner inquiry form ask?

Name, email and phone; the wedding date or season; the venue if chosen; estimated guest count; a budget range in four bands; which package interests them; how they found you; and an optional message. Eight questions lets you reply with real numbers from the first message and is short enough that serious couples finish it.

Should a wedding planner website have a blog?

It should have venue guides, which do what a blog is supposed to do. One page per venue you have worked at, written from experience with your photos from it, ranks for the planner-plus-venue searches couples make once they have a date. General advice posts compete with national sites and rarely produce a local inquiry.

How many photos should a wedding planner website have?

Three to five on the home page, one per wedding on the portfolio index, and twenty to forty per real-wedding page, lazy-loaded so only the first screen loads at once. Every image under 200 KB with alt text. More photos per page than that slows the site on a phone, and slow is the most common reason planner sites lose rankings and inquiries.

What should the home page of a wedding planner website say first?

Your studio name, your city or region and your specialty, in the first sentence of real text, followed by a starting price range and one button to the inquiry form. That sentence is what Google and AI search engines use to describe you, so it should be plain: 'Full-service and day-of wedding planning in Charleston, from $2,000.'

What to Put on a Wedding Planner Website: The 23-Point Checklist

By Alexey Chasin · Updated October 17, 2026 · 9 min read

A wedding planner website needs eight pages and fifteen technical basics. The pages: home, about, services and packages with starting prices, portfolio, testimonials, FAQ, contact with a qualifying inquiry form, and venue guides. The basics run from title tags and FAQ structured data to a load time under two seconds and a linked Google Business Profile. Here are all 23 in order, with what each must contain and how to check it.

Most results for this question are printable wedding binders for couples. This is the other thing: the checklist for the website of a wedding planning business, the one that has to turn a search into an inquiry. Use it to audit a site you have or to brief whoever builds the next one. Every item is in the planner sites we build.

The eight pages

1. A home page that says who, where and what in the first sentence

Your studio name, your city or region, and your specialty in the first line of text, not in an image.
Three to five of your best photos, compressed.
A starting price range in the first screen: 'coordination from $2,000, planning from $6,000'.
One button to the inquiry form, repeated at the bottom.
Three short reasons to choose you, each one specific: a number of weddings, a venue list, a cultural specialty.

2. An about page with a real photo and a real story

A photo of you, by a photographer, on the page before the text starts.
Your name and city in the first sentence.
How you came to planning, how you work, what you are like on the day.
Training, certifications or associations, in one line.
One line on the kinds of weddings you take and the ones you do not.

3. A services page with packages and starting prices

Three or four packages with plain names.
What each includes, five to eight bullets.
A starting price on each, visible without scrolling inside the package.
One sentence on what moves the price.
A 'best for' line per package.

4. A portfolio with one page per wedding

A gallery index with one image per wedding.
A page per wedding or styled shoot with the venue, the vendor team and 150 to 300 words of what you did.
Styled shoots labeled as styled shoots.
Twenty to forty photos per wedding, lazy-loaded, each under 200 KB.

5. Testimonials with names, venues and dates

Five to ten reviews, first names and last initial, the venue and the month.
A link to the Google and Knot profiles where the reviews live.
No rating stars in structured data until the reviews are public on Google.

6. An FAQ in real text

Eight to twelve questions couples ask on calls: how far out to book, what day-of includes, whether you travel, whether you work with a venue coordinator, how payment works.
Answers of 40 to 80 words, each complete on its own.
Built as expandable text in HTML, not as an image or a PDF.

7. A contact page with a qualifying inquiry form

The eight questions below, nothing more.
Your email and your reply time.
Your service area in words: cities, counties, destinations.
Delivery to your inbox and your CRM, and a confirmation to the couple.

8. Venue guides

One page per venue you have worked at, 600 to 1,000 words from your own experience: rooms, flow, restrictions, what works there.
Your photos from that venue.
A link from the venue page to the relevant real wedding and back.
This is the item that ranks; everything above it converts.

The 8 questions your inquiry form should ask

Name, email and phone, as one block.
Wedding date, or the season and year if the date is open.
Venue, if chosen, with a free-text field.
Estimated guest count.
Budget range for the whole wedding, in four bands you choose.
Which package interests them, with 'not sure yet' as an option.
How they found you: Instagram, Google, a venue, a friend, a directory.
Anything else they want you to know, optional.

Eight is enough to write a real reply from the first message. More than ten and serious couples abandon the form; fewer than six and you spend a week on email before the first call.

The fifteen technical must-haves

Items 9 to 23: the technical checklist, with how to check each one yourself
#	Must-have	Why it matters	How to check
9	A title tag per page that says what and where	It is the headline in Google and the first thing AI engines read	Hover the browser tab, or view the page source for the title element
10	A meta description per page with a price or a specific	It is the two lines under the headline in search results	Search your studio name and read the snippet
11	Exactly one H1 per page, carrying the page's phrase	Google and AI engines use it to classify the page	Browser extension or page source; count the H1s
12	An answer-first paragraph on every page	The paragraph engines quote when they recommend you	Read the first paragraph without the design; does it answer the page's question?
13	FAQPage structured data on the FAQ	Makes your answers eligible for rich results and AI citations	Google's Rich Results Test on the FAQ page
14	Business structured data naming you, your city and service area	Tells Google and AI engines who and where you are	Rich Results Test or Schema.org validator on the home page
15	Load time under two seconds on a phone	Couples open you from a phone; slow sites lose them and rank lower	Google PageSpeed Insights, mobile tab, every main page
16	Every image compressed and sized, with alt text	Galleries are why planner sites are slow	PageSpeed Insights lists the offenders by file
17	A layout that works at phone width without side scrolling	Most visits are on phones	Open every page on your own phone
18	A tap-to-call link and a visible email	Half of couples would rather text or call than fill a form	Tap the phone number on a phone; it should dial
19	Your own domain, registered in your name	The asset is worthless on someone else's subdomain	Look up the domain's registrant; it should be you
20	A sitemap submitted to Google Search Console and Bing Webmaster Tools	It is how new pages get found and indexed	Search Console, Sitemaps report, shows pages discovered
21	A Google Business Profile linked to the site, category Wedding Planner	It is the map result and the review source	Search your studio name; the profile should appear on the right
22	A robots file that allows search and AI crawlers	If ChatGPT or Perplexity cannot read the site, they cannot recommend it	Open yourdomain.com/robots.txt; look for Disallow rules on GPTBot, ClaudeBot, PerplexityBot
23	Analytics and form tracking	You should know which page produced each inquiry	Submit a test inquiry and find it in your analytics

The event planner version

Keep all 23. Change three: the services page becomes a page per event type (corporate, social, nonprofit, party) instead of wedding packages; the portfolio is organized by event type; and the inquiry form swaps the wedding date for an event date, and adds headcount and whether a venue is booked. Corporate planners add a capabilities page with a downloadable one-sheet, which is item 24 for them.

Use it as a brief

If you are hiring a designer, send them the list and ask which items are included. If you are building it yourself, do the pages in the order above and the technical items 9, 11, 12 and 15 before anything else.

Every item on this list is in the planner site we build. Velour Web builds the same site free: it is included with hosting at $50 a month, billed $600 for the first year and month to month after that, and the code is handed over after the first paid year or on a $999 buyout. Five to ten hand-coded pages from a 30-minute interview, live in 2 to 4 weeks, under one second on a phone.