Web Hosting for Funeral Homes

The obituary is the page

Everything else on a funeral home website is background. The preplanning page, the history of the firm, the list of services, the map. Useful, occasionally read, not what brings people to the site.

Obituaries bring people to the site. One notice goes up, the family sends the link to a group chat, somebody posts it to Facebook, and it moves outward through a network you have no visibility into. A cousin in Arizona opens it. A woman who worked with him in 1988 opens it. Somebody sees the shared post and forwards it to four more people.

That is not marketing traffic. It is a family relying on you to hold a piece of information at the moment they are least able to deal with a problem. If the page is slow, or worse, if it is not there, the failure is not technical. It is the family refreshing a blank screen while relatives text them asking whether the link is broken.

What that means for how the page is built

• The obituary must be real web text on your own domain, not an image of a printed notice and not a post that lives only on a third-party memorial platform.
• The service times, the address of the church or chapel, and the visitation hours belong in the text where a search engine and a screen reader can both find them.
• Photographs should be resized before they go up. A single unresized portrait straight off a phone can be several times the weight of everything else on the page.
• The page needs a stable address that does not change. People bookmark these and come back to them years later.

If your obituaries live on a supplier's platform under their domain, the sharing still works, but the traffic and the long-term record are theirs. Keep at least a copy of every notice on the site you own.

Online condolences and the guest book

Nearly every funeral home site has a place for people to leave a message. It is one of the genuinely valued things a website does in this trade, and it is also the only part that lets a stranger publish words under a family's name.

Most of what arrives is exactly what you would hope. A proportion of it is spam, because an open form on a public page is found by machines within days of going live. And a very small proportion is a person who should not be posting on that page, which the family will see before you do if nothing sits in between.

1. Hold everything for review

   Nothing appears until a person at the funeral home approves it. This is the single decision that matters, and it costs a few minutes a day. A family should never be the first to read a message on their own father's page.

2. Ask for less

   A name, a message, and an email address you do not publish. Every extra field is another thing to store, another thing to get wrong, and another reason for somebody to abandon the form.

3. Put a quiet spam check on the form

   A hidden field that humans never see and bots fill in stops most of it without asking a grieving visitor to identify traffic lights in a grid.

4. Decide in advance how you remove a message

   Sooner or later a family will ask you to take one down, usually within the hour. Know who can do it and how, before the call comes.

5. Make sure the notification email arrives

   A moderation queue nobody is told about is a queue that fills up. Send the alert to an address at your own domain that someone actually watches. There is more on that on the business email page.

One more thing that is easy to miss. Condolence messages are personal data about living people, and they sit on your site indefinitely. Have a plain answer for how long you keep them and what happens if somebody asks you to delete theirs. If that touches anything you are unsure of, check with your own adviser rather than guessing.

Who should not spend more than the minimum

If you are a cemetery, a monument company, or a memorial products business, most of this page does not apply to you and you should not be paying for what it describes.

You do not publish obituaries. Nothing on your site gets shared to a thousand people in an hour. Your traffic is steady, small, and made of people looking up your hours, your section map, your price list or your phone number. That is one of the least demanding websites there is, and an entry shared plan covers it comfortably.

• You do not need capacity sized for a spike that will not happen.
• You do not need a managed plan for a handful of pages that change a few times a year.
• You do not need extra storage unless you are hosting large plot maps or scanned records, and even then the answer is usually to compress them.
• You do not need a moderation workflow, because you have no guest book to moderate.

The same goes for a single-location funeral home that publishes notices on a supplier's platform rather than its own site. In that case your site is a brochure, and it should be priced like one.

Where spending more is genuinely warranted: you run several locations from one site with a shared obituary archive, you have years of notices going back and want them all kept and searchable, or you take preplanning enquiries with personal details attached, which puts you in certificate and website security territory rather than plan-size territory. Volume of services alone is not a reason.