Getting Obituaries Online Without Losing Your Mind
Obituary publishing moved online fifteen years ago, and everyone still treats it like it's 2009. Local newspapers used to set a flat rate per inch of print space, and families had to fit their entire narrative into a constrained column. Now the barrier to entry is basically nothing, which means more people are putting death announcements on the internet, and the quality varies from helpful resource to complete mess. The shift isn't just about moving text from paper to a browser. Digital obituaries allow for multimedia, searchable archives, guest books, and syndication across platforms. Most local newsrooms I've worked with handle this through a content management system, usually something like WordPress with custom post types or a dedicated obituary module. The workflow typically runs like this: a funeral home or family member submits a form, your staff reviews it for factual accuracy, you add biographical details and a photograph, and it goes live on the news site and sometimes gets pushed to a separate obituary section or aggregators. I've managed obituary workflows for regional publications. The actual production time for a standard obituary went from about forty-five minutes in print — typesetting, verifying with the funeral home, chasing down photo files — down to maybe twelve minutes once we had a clean digital template. That sounds great until you realize nobody is spending those saved minutes on fact-checking anymore. We got sloppy. I learned that the hard way.
Here's what nobody tells you about digital obituaries: they are not news content in the traditional sense, but search engines treat them that way. Google indexes them, ranks them, and surfaces them when someone searches for a name plus a city. That means your obituary has to compete with paid memorial sites, genealogy databases, and social media posts. If your headline is just "John Michael Smith, 74," you are going to get buried. I started using structured naming conventions like "John M. Smith, retired engineer from Oakdale, dies at 74" and saw our click-through rates jump significantly because the search result actually told the reader something useful. It's basic SEO, but funeral directors rarely know about it and families certainly don't. Another thing that comes up more than you'd expect: name collisions. When you publish an obituary for someone named Robert Garcia from Houston, and there are three other Robert Garcias from Houston in your database from previous years, your new article can get tangled in internal linking, sitemaps, and even search results. I spent two weeks trying to untangle a mess where a living person's professional bio was getting associated with a deceased person's obituary because the CMS couldn't distinguish between them. The workaround was implementing unique slugs with dates — robert-garcia-obit-2024-03-15 instead of just robert-garcia — and using structured data markup to explicitly define each page as an obituary rather than a general biography. The structural data piece is critical. Schema.org has a specific Obits markup type, and when you implement it correctly, Google displays death dates, birth dates, and surviving family members right in the search results. It takes maybe twenty minutes to set up properly, and most newsrooms I see doing it wrong or not at all. They're dumping plain text into a blog post and wondering why they aren't showing rich snippets.
Let me be clear about what this system does not do well. It does not prevent typos. Digital publishing moves too fast for the kind of multi-layer editorial review that print used to force on you. I have seen funeral home submitters accidentally list a living person as deceased, and I have seen surviving family lists include people who passed years earlier because the submitter copy-pasted from an old obituary. You need a verification step that actually verifies. Call the funeral home. Cross-reference the death certificate if your publication has that access. It adds ten minutes per piece and saves you from publishing something you have to publicly correct later, which is embarrassing for everyone involved. There is also the question of permanence. A printed obituary was finite. It ran once, maybe twice if the family paid for an expanded version, and then it was gone. Digital obituaries persist indefinitely unless someone actively removes them. That has real consequences for families who want privacy or who later regret the level of detail included. I've had people call years after a relative's death, asking to have certain information taken down because it exposed family tensions or personal struggles that weren't meant for a permanent public record. My recommendation is to build a takedown policy into your workflow from the start. Define what you will remove, what you will edit, and what stays. Make it explicit. Otherwise you are making ad hoc decisions under emotional duress, and that is a bad place to make editorial calls. Syndication is another area where people overestimate the benefit. Sending your obituary to every aggregator and memorial platform looks efficient until you realize each one has different terms, different data practices, and different ways of handling updates. Some of them sell the data. Some of them keep your content even after you request removal. I stopped syndication outreach to third-party memorial sites after I discovered one of them was selling obituary data to a genealogy company that then used it to build paid family tree profiles without consent. Now I only syndicate to platforms my publication has direct contractual relationships with, and I review those contracts annually.
Get the Full Details
If you are starting a digital obituary program from scratch, here is what I would actually do instead of following the template most newspapers use. Start with the submission form. Make it detailed but not overwhelming. Ask for the same information print obituaries required — full name, age, city, date of death, surviving family, service details, donation preferences — but add fields for biography paragraph, photograph upload, and optional social media links. Then build a simple review checklist into your CMS workflow so no piece goes live without hitting each verification step. Keep the markup structured from day one. Do not syndicate anywhere until you understand where the data goes. And invest in a cleanup policy that is visible to both your staff and your readers. The technology is easy. The institutional habits are what take work to change.
