Schema markup generator for wedding planners

Wedding planners don’t have a dedicated schema.org type, so ProfessionalService is a sound choice. Fill in the form and I’ll build valid JSON-LD you can paste into your site.

Your details

One or two factual sentences. The same words as your homepage intro work well.
International format: +1-403-…
A real photo of you, your team or your space.
Comma-separated, e.g. Mo-Fr 09:00-17:00, Sa 10:00-14:00
Optional. A symbol range like $ or a short text range.
Comma-separated cities or regions.
What you plan and coordinate. (knowsAbout)
Languages you plan in. (knowsLanguage)
How couples pay. (paymentAccepted)
One URL per line: Google Business Profile, LinkedIn, Instagram, directories.

ProfessionalService JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfessionalService",
  "@id": "https://kananaskisweddings.example/#business",
  "name": "Kananaskis Weddings & Events",
  "description": "A Calgary wedding planner organising full-service and day-of coordination for mountain and city weddings.",
  "url": "https://kananaskisweddings.example/",
  "telephone": "+1-403-555-0142",
  "email": "hello@kananaskisweddings.example",
  "image": "https://kananaskisweddings.example/images/photo.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Example Street SW",
    "addressLocality": "Calgary",
    "addressRegion": "AB",
    "postalCode": "T2P 1J9",
    "addressCountry": "CA"
  },
  "openingHours": [
    "Mo-Fr 09:00-17:00"
  ],
  "priceRange": "$",
  "areaServed": [
    "Calgary",
    "Airdrie",
    "Cochrane",
    "Okotoks"
  ],
  "knowsAbout": [
    "Full-service wedding planning",
    "Day-of coordination",
    "Mountain weddings",
    "Destination weddings"
  ],
  "knowsLanguage": [
    "English",
    "French"
  ],
  "paymentAccepted": "E-transfer, Credit card",
  "sameAs": [
    "https://www.instagram.com/kananaskisweddingsevents",
    "https://www.linkedin.com/company/kananaskisweddingsevents"
  ]
}
</script>

Paste this into your page’s head, then test it with Google’s Rich Results Test and validator.schema.org. The example values are made up: replace every one.

Want this added to your planning business’s website?

Send me your site and I’ll check your current structured data and send back corrected JSON-LD for it. Free.

No newsletter. Just what you asked for, from me. Privacy

The properties that matter for wedding planners

Type: ProfessionalService. Every property below is a real schema.org property.

Key schema properties for wedding planners
PropertyWhy it matters
knowsAboutFull planning and day-of coordination are different services. Naming them helps couples and AI tools find the right fit.
areaServedMountain and destination weddings mean travel. Name the places you plan in, like Canmore and Banff.
imageA real wedding you planned shows your style better than a logo.
priceRangePlanning fees vary a lot. A range helps couples self-select.
sameAsLink Instagram and your wedding directory profiles so your identity is joined up.

Common mistakes

  • Marking up each wedding as an Event. Private weddings aren’t public events; describe them on portfolio pages instead.

  • Showing a home office address you don’t want visited. Leave the street out and use areaServed.

  • Marking up testimonials as review stars. Google won’t show self-serving review stars for a LocalBusiness.

How to add it to your site

  1. Replace every example value in the form with your own details. They should match your Google Business Profile exactly.
  2. Copy the code and paste it into your page’s <head>. Most site builders have a custom code field. On a hand-built site, it goes in the template.
  3. Test the live page with Google’s Rich Results Test and validator.schema.org, and fix anything they flag.
  4. Add the same facts to the visible page. Structured data should describe what visitors can see. My website checklist for wedding planners covers the rest.
FAQ

Schema for wedding planners: questions

  1. It is a reasonable fit, since there isn’t a dedicated wedding planner type. Your description and knowsAbout explain the rest.

  2. Mention them in page content, and in areaServed if they are places you cover. Don’t add venue websites to sameAs.

  3. Event markup belongs to the event organiser’s page. You can mention it on your site in plain text.

Keep reading

Let’s begin

Let’s build something you’re proud to share.

Let’s Talk