Your obituary page is your most important page

Where everyone actually goes

Families visit your obituary page to find a service time. Neighbors visit it to check a name they heard at church. Search engines visit it because it is the only page on most funeral home sites that changes weekly — and freshness is a ranking signal. AI assistants lean on it because it is evidence the funeral home is active, local, and current.

Follow one obituary for a week and the traffic tells the story. The daughter shares the link with her out-of-state brothers, who each open it twice to re-check the service time. A coworker of the deceased searches the name on Tuesday, lands there, and forwards it to the old department. The church prayer chain passes it along. By Saturday, a single obituary has quietly been opened by more people than visited your homepage all month — and every one of them now knows your home’s name, because the page carried it.

Meanwhile the machines are doing their own visiting. A search crawler that finds something new on your domain every week learns to come back often. An AI assistant asked “tell me about [your funeral home]” leans on the most current, most local, most factual pages it can find — and nothing you publish is more current, local, or factual than this week’s obituaries.

What a strong obituary page does

It loads fast on a phone. Each obituary has its own address on YOUR domain — not buried on a third-party host — with the name, dates, and service details in real text a machine can read, not an image of text. It is linked plainly from the homepage: “Obituaries,” not “Tributes & Legacies” behind a menu.

Each of those requirements earns its place. Fast on a phone, because nearly everyone arriving is holding one, often in a hallway or a parking lot. Its own address per obituary, because a link that can be shared is a page that travels — “ourfuneralhome.com/obituaries/jane-ellison” gets texted, posted, and printed in a bulletin, and every share is your domain in another hand. Real text, because a scanned newspaper clipping or a photo of the program is invisible to every machine that indexes the web: the name, the dates, the service time at the chapel on Thursday at ten — those need to be typed words on the page, not pixels in an image.

And the plain “Obituaries” link matters more than it seems. A visitor who cannot find the obituaries in five seconds leaves for the newspaper’s site; a machine that cannot find them from your homepage may conclude you do not publish any. Sentiment has its place, but navigation is not it.

The compounding effect

Each obituary is a small, honest, local page: a name people search, a date, a place. Dozens of them a year, on your own domain, teach every system that indexes the web what your home is and where it serves. No advertising buy replicates that record — and it is made of work you already do.

Think of what a year of them adds up to. Sixty obituaries is sixty pages that each say, in machine-readable plainness: this funeral home operates in this town, served this family, held a service at this address. When an assistant is asked which funeral home to call, that accumulated record is much of what it has to go on. The funeral home with years of obituaries on its own domain has been writing its case daily; the home that publishes elsewhere has an empty file.

The mistake to stop making

Publishing obituaries only to a case-management portal or a newspaper site gives your most valuable content to someone else’s domain. Publish on your own site first; syndicate second. The page you already update every week is quietly your best marketing asset — treat it like one.

The check takes one minute: search the name from your most recent service. If the first result is a newspaper, a legacy portal, or an aggregator — anyone but you — then the traffic, the freshness signal, and the machine-read evidence of that family’s trust all just accrued to a domain you do not own. Nothing stops you from syndicating a copy afterward; the point is the original lives at home. Starting Monday, that is a workflow change, not a budget line: publish to your own obituary page first, then let the others carry the echo.