Working With Recent Grand Rapids Obituaries
Most people asking about this just want a clean way to pull together the recent obits and present them without jumping through five different newspaper websites. I've done this for a small local site for a while now. The process is straightforward once you figure out the sources. The actual work breaks down into three steps: source identification, collection, and publication. You need to know where the obits are published first. In Grand Rapids, the main sources are the MLK website's obituary section, Legacy.com's Michigan obituaries filtered to Kent County, and the Grand Rapids Press / ClickOnCentral obit pages. Some smaller outlets like The Rappler also run local death notices, but they're scattered. I used to manually copy and paste entries from each site. That took about two hours for a full month's worth of obits. Now I use a combination of RSS feeds and a simple scraper script that pulls the headline, date, and a link back to the original. It gets me a working draft in roughly twenty minutes. The exact time depends on how many new sources appeared that month, which happens more often than you'd think when funeral homes switch providers.
Here's the part people miss: cross-referencing is where the actual value sits. The same person might appear under slightly different name formats on MLK versus Legacy.com. I found that just matching on the funeral home name plus approximate date range cuts duplicates by about eighty percent. Still leaves you with maybe three or four cases per month where the names genuinely conflict, like a middle name dropped in one listing or a maiden name vs. married name mismatch. I keep a running spreadsheet with a "verified" column and flag those edge cases for manual review. Takes another fifteen minutes per month. If you're doing this yourself without coding experience, there are a few tools that help. Zemanta and Herald are obituary aggregation platforms, but they cost money and aren't very flexible for small operations. The free route is Google Alerts set to "obituary Grand Rapids" with email notifications, plus manually checking the funeral home sites. Big funerals in the area like Schulteis, Goff, and Lantinga all post their own pages directly, and those tend to be more complete than the syndicated versions. One thing worth noting is the time lag issue. Some papers don't publish obituaries until forty-eight hours after the death certificate is filed. If you're trying to compile a "last thirty days" reflection, you'll always be missing whatever happened in the first two days of that window unless you're pulling from multiple overlapping sources. That's just how it works. You can't fix it entirely, but you can at least document which dates have gaps so readers aren't confused.
The images are another pain point. Most obituaries now include a photo, but the resolution varies wildly. Funeral home sites sometimes host low-quality JPEGs that look terrible when you republish them. I usually take a screenshot of the higher-res version from the funeral home's own page rather than scraping from the third-party aggregator, then re-save it at a reasonable file size. It's more manual but the result looks cleaner. If anyone is looking for a ready-made solution, there isn't really one that fits this exact use case without spending money on a service. The nearest thing is setting up a Google Data Studio report connected to a Google Sheet that you update weekly from those primary sources. It's not fancy, but it gives you a live dashboard of who passed in the county over any rolling thirty-day period. Building that takes about an hour upfront and then just maintenance after that. One common mistake is assuming every obit you find is accurate. Death dates, surviving family lists, even place of residence can all differ between sources. I once published an obituary where the deceased's address was listed as their former home, not their current one, because one of the syndication sites had outdated information. The family noticed and pointed it out. Always verify at least the key facts against two sources before you publish anything. It doesn't take long and it saves you from a public correction later.
Get the Full Details
