What Actually Happened With Kneb Obits
I got pulled into the Kneb Obits thing about eighteen months ago when a friend was running a memorial ecommerce shop. The whole concept is basically taking the traditional obituary format and turning it into a marketing channel. You publish death notices, memorial pages, and tribute content that links back to products or services people need when they are dealing with loss. It sounds weird until you look at the numbers. The model works because grief is a buying moment. People need urns, flowers, memorial jewelry, and estate services right after someone dies. Traditional funeral homes capture the initial search traffic, but Kneb Obits sits one step downstream. You build the tribute content, get the organic clicks from people searching for death notices in specific towns, and route them toward affiliates or your own store. The key insight nobody mentions upfront is that Google treats memorial pages differently than normal ecommerce. They rank for local queries without needing backlinks. I spent three weeks fighting a ranking problem on a memorial page for a small town in Ohio. Nothing moved. The workaround was adding the person's full name with the year of birth and death in the h1 tag, then embedding a genealogy-style family tree widget below the fold. Page went from position forty-two to the top three within fourteen days. The widget mattered more than the copy. Setting this up does not require a huge budget. You need a CMS that handles dynamic pages well, a template system for obituary formats, and a content pipeline that can produce localized notice pages at scale. I use a headless setup with Next.js on the frontend and a postgres database for the notice records. The template engine pulls fields like full name, age, town, date of death, survivor names, and service details. You pair that with structured data markup for obituary schemas and Google starts picking up the pages fast. Most people skip the schema part. That mistake costs you the rich results that drive the actual click-through rate.
Monetization happens through affiliate links to funeral supply vendors, direct store sales for custom memorial products, and display ads once you hit decent traffic volumes. I found that the ad revenue per session on memorial pages is roughly double what you get on regular blog content. People are engaged and browsing multiple pages. The downside is that conversion rates drop hard if you push sales too aggressively. I learned that the hard way. Placed a buy button directly under the photo of the deceased on a test page and the bounce rate spiked to sixty-eight percent. Moved the commercial elements to a separate sidebar that only appears after scrolling past the tribute text. Conversion stayed flat but bounces dropped to twenty-one percent. The page length matters more than you would think. Memorial pages that hit around twelve hundred words with a mix of biographical text, survivor listings, and service information perform best in search. One counter-intuitive thing about this space is that newer domains can outrank established funeral directory sites if the local signal is strong enough. Google's local intent algorithms favor fresh content tied to specific geographic queries. A brand new site covering obituaries for a single county can beat a national competitor by focusing exclusively on that area and posting daily. I ran an experiment across four counties in Iowa. One domain, four separate content hubs, each with its own local landing page. Within five months, the Iowa hub was pulling twelve thousand monthly searches combined. The trick is maintaining accuracy. Wrong dates or misspelled names get flagged fast and destroy trust. I built a verification step into the workflow where each notice gets cross-referenced against the local newspaper archive before publishing. It adds about twenty minutes per page but prevents the kind of error that makes people report your site to Google. The biggest bottleneck people hit is content creation speed. You cannot manually write thousands of memorial pages and stay competitive. I use an automated ingestion pipeline that scrapes public death records, matches them against existing notice formats, and generates draft pages with extracted survivor information and service times. A human editor reviews each one for accuracy and sentiment before it goes live. The automation cuts production time from an hour per page down to about eight minutes for routine cases. Complex pages with unusual formatting or missing data still take longer, but the volume work gets handled quickly.
If you are thinking about building something like this, start small. Pick one state or region and create a functional prototype before expanding. Test the schema markup, check how pages render in search, and measure which notice formats get the most engagement. The market is growing because digital death notices are replacing print versions faster than most people realize. Funeral homes and cremation societies are pushing this transition, and the search demand is following. The technology to run a proper Kneb Obits platform is straightforward. The challenge is staying accurate and keeping the tone appropriate. Those two things separate the sites that last from the ones that get abandoned after a few months.
Get the Full Details
