Reviews, real weddings and vendor credits: a planner's evidence in text

Which reviews say something a reader can check?

The useful review names things: the venue, the month, the service the couple booked, and what went right, best of all something that nearly went wrong. A review that says only how lovely the planner was is kind and gives a reader nothing to check. One that names the venue and the month, and says the planner had the ceremony moved indoors before the storm arrived, tells a reader what a coordinator does on the day it counts.

Ask in a way that draws those details out. After the wedding, a question such as "what would you tell a couple deciding whether to hire us?" brings out specifics that "please leave us a review" does not. Do not script the answer and do not offer anything for it; Google's review snippet rules exclude fake reviews and undisclosed incentivized ones. And ask every couple, not only the ones you expect to be pleased, so the reviews you have describe the weddings you plan.

Where the reviews go, and what the markup rules allow

Put each review on the page it describes, quoted as text, with the reviewer's first name, the date and the platform where it was left: a day-of review on the day-of page, a review of a lakeside wedding on that wedding's page. Ask the couple before their review goes beside their photographs, because the two together identify them.

A review widget does a different job. One that draws the reviews with a script after the page loads can leave a fetcher that runs no scripts with an empty box, because the words sit on the platform's servers and not in your HTML. In our audit of 9,483 small business websites (40 trades, 90 metros, late August to early September 2026), 64.7% showed no review signal a crawler could read, neither rating markup nor a review quoted in the page text, and only 8.9% carried rating markup. Both figures cover every trade together; the audit published no planner cut of them.

The markup follows Google's rules for review snippets. Ratings have to be sourced directly from users, and reviews or ratings from other websites are not to be aggregated, so a platform's reviews and its star average stay out of your JSON-LD. When a LocalBusiness or an Organization controls the reviews about itself, whether on its own site, in markup or through an embedded widget, Google calls that self-serving and the page is not eligible for review stars. Google's local business documentation recommends aggregateRating only for sites that capture reviews about other businesses.

So put no aggregateRating on your business node, and build no Review markup from a platform's reviews. If couples leave reviews through a form on your own site, review markup for those states a true fact, and it still earns no stars. The quoted text on the page is the part any reader, a person or a crawler, can use.

References: the couples a prospect can call

A prospective couple may ask to speak to someone you have planned for. That conversation happens off the site, and the details stay off it too: never publish a reference's name, phone number or email address. The site can say that references are available and, with each reference's agreement, what kind of wedding they had: "References from couples married in [season and year] at [kind of venue], for [number] guests, on request."

Corporate references work the same way with one more step. A company's name goes on your site only with its written permission, and some events are covered by confidentiality terms. Where you cannot name the client, describe it by type, size and place: "a three-day sales kickoff for a software company, [number] attendees, [city], [year]".

A real-wedding or event page, written with permission

A real-wedding page is a case study: what the couple asked for, what you did and how it went, published only with the couple's written permission. Documenting reference projects sets out the general method for any trade. For a planner, the page states the venue and the town, the month and year, the guest count, the service level, the style or format, the scope of your work, what was hard, the vendors, and the couple's own words if they agreed to be quoted.

Write the opening paragraph so that it still makes sense when it is quoted without the rest. A template, with every bracket your own:

[Business name] planned [first names, if the couple agreed]'s wedding at
[venue], [town], in [month year]: [service level] for [number] guests,
starting from [what was already booked] and running to the last dance.

We sourced [which vendors], built the timeline and the floor plan, and
ran the day with [number] coordinators. [What was hard, and what you did.]

Vendors: [venue], [photographer], [florist], [caterer], credited as
each asked. Photographs by [photographer], used with permission.

"[The couple's words, as they wrote them]", [first names], [month year]

Credit the photographer on every image, and use the images only with their permission and the credit line they ask for. A corporate event takes the same page with the client's permission, or anonymized as above, and its fields become the format, the headcount, the agenda and what you sourced. Link each write-up from the service page and the style page it belongs to, as the article on ceremony and style pages describes, and from the venue's line on your venues page.

Vendor credits and venue lists: pages elsewhere that name you

Other businesses' pages can name a planner in several ways. A photographer's post about a wedding credits the planner, a florist's portfolio lists the team, a venue keeps a list of preferred vendors, a wedding publication runs a real wedding with every vendor named. Each is a brand mention on a page you do not control, often beside the name of a venue a couple may ask about.

What you can do is make them accurate. Give every vendor the same credit line, your exact business name and your site's address, and ask them to use it. Check the venue lists you appear on for the right name, the right service and a link that works. Credit vendors on your own pages in return, by the names they use. A credit under an old name or a misspelling is one more variant of your name, and variants are already common: across all trades in our audit, 43.1% of sites were inconsistent about who and where they are on their own three main pages.

We cannot tell you how any assistant treats a mention on a photographer's blog or a venue's list, and no operator documents it. What those pages are is plain: text on a public page, naming you beside a place and a date. Mentions and digital PR covers earning mentions in general, and directories and review portals covers the listings. If a vendor pays you a referral fee, say so on the page where you recommend them. The overview for wedding and event planners lists what the rest of your site should state.