The funeral home schema checklist
Humans read your website. Machines read the markup underneath it — and when the markup is missing, they guess. A funeral home is too easy to confuse with a florist, a chapel, a cemetery. Say what you are.
What schema is, in one paragraph
Schema markup is a small block of structured text inside your pages that names things machines care about: this is a funeral home; its name, address, phone; its hours; where it sits on the map. Search engines and AI assistants read it directly, no interpretation needed. It never shows to visitors; it exists so nothing about you has to be guessed.
Here is what one looks like, whole. This block sits invisibly in a homepage and answers, in one place, most of what a machine wants to know:
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Cedar Lane Funeral Home",
"description": "Funeral home serving Fairview, Ohio and surrounding counties.",
"url": "https://www.example.com",
"telephone": "+1-555-014-2200",
"address": {
"@type": "PostalAddress",
"streetAddress": "418 Cedar Lane",
"addressLocality": "Fairview",
"addressRegion": "OH",
"postalCode": "45501",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 40.00712,
"longitude": -83.01452
},
"openingHoursSpecification": {
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"],
"opens": "00:00",
"closes": "23:59"
}
}
The names and numbers are invented; the shape is real. If reading it feels technical, notice that every line is a fact you already publish somewhere — the markup just says it in the one dialect machines never misread. And if you’d rather not hand-write the dialect at all, we’ll write it for you: type the letterhead facts at funeralhomeaeo.com/schema and the ready-to-paste starter block arrives by email, free.
The checklist
A funeral home site needs surprisingly little to be well-marked:
LocalBusiness markup on the homepage, with “funeral home” stated plainly in its description —
and name, address, phone exactly as they appear on your Google Business Profile. Geo coordinates.
Opening hours, including whether you answer around the clock — “available 24 hours” is a fact
machines love and families need. Each obituary marked as a page about a person, with dates. And a
real FAQ page — genuine answers to what families actually ask, in plain words an assistant can
quote.
Taken one line at a time:
LocalBusiness, with “funeral home” in the words. Here is a fact your web vendor may not know: schema.org has no FuneralHome type — the vocabulary holds aCemeteryand aCrematorium, never the business itself — and a block typedFuneralHomefails validation outright. So the homepage block isLocalBusiness, and the words carry the kind: “funeral home” plainly in the name or description, with the right category on your Google Business Profile doing the classifying.- Name, address, phone — character for character. Copy them from your Google Business Profile, not from memory. The markup’s value is agreement, and agreement is exact.
- Hours, honestly. If a person answers your phone at 3 a.m., say so in the markup. “Open now” is one of the first things an assistant checks before recommending anyone for an urgent need.
- Obituaries as pages about a person. Name, birth date, death date as structured fields — the same facts your most important page already shows, restated for machines. Your website platform may already do this; it is worth asking.
- Services as events. A visitation on Thursday at ten, at your chapel’s address, is an event with a start time and a location — marked as one, it can surface directly when someone searches the name.
- A real FAQ page — content first, markup second. Google cut FAQ rich results back to
government and health sites in August 2023 — funeral homes stopped earning them then — and
retired the feature entirely in May 2026, so
FAQPagemarkup earns no special place in search. What still works is the page itself: genuine answers to what families actually ask — “what does cremation cost here,” “what do I do when a death happens at home” — in plain words. That question-shaped content is what an assistant quotes back, with or without the markup.
This is an afternoon of work for whoever maintains your site, and it is one-time work — the markup rides along quietly from then on, updating only when the facts do.
Consistency outranks cleverness
The markup’s job is agreement: site, Google profile, and directories all stating the same name, address, and phone, character for character. “Smith Funeral Home” in one place and “Smith Funeral Home & Cremation Services” in another splits your identity in half. Pick the canonical form and repeat it everywhere.
The exercise is worth doing on paper once. Write the exact string you want to be known by — your name is a query, so choose it like one — then hunt down every place a variant lives — the site footer, the Google profile, the state directory, the old chamber-of-commerce listing — and bring each one into line. A machine cross-checking your identity should find one spelling, one address format, one phone. Boring agreement is the whole trick; there is no clever version of it.
How to check your own site
Paste your homepage into Google’s Rich Results Test. If it reports nothing at all, your site is speaking only to humans — which, this decade, is speaking to half the room.
Two checks, ten minutes, this Monday: the Rich Results Test for what Google can lift, and the schema.org validator for whether the markup parses at all. Print what they report and hand it to whoever runs your website with this post attached. When both tools read back your name, type, address, phone, and hours without a warning, this piece of the housekeeping is done — and it stays done.
What markup won’t do
One honest note, so no vendor oversells you: schema is hygiene, not a growth lever. The best evidence we have — a 2026 Ahrefs study that tracked 1,885 pages adding schema against 4,000 matched control pages — found no meaningful lift in citations from ChatGPT or Google’s AI surfaces. Every page in that study was already being cited heavily by AI, so it says little about a page still trying to get found — but nobody has shown the lift the vendors promise, either. Google itself now says there is “no special schema.org markup you need to add” for its AI features. Markup keeps a machine from getting you wrong; it doesn’t get you chosen. Do it because a funeral home mistaken for a florist is a real cost — not because someone promised it would put you at the top of ChatGPT. The things that actually move AI visibility are duller and harder: a complete Google Business Profile, steady reviews, and question-shaped content on your own site.
The FuneralHomeWebsites Team