Who Can See an Online Memorial Page? Privacy and Visibility Settings Explained

Detailed Explanation

Most families make one privacy decision when a memorial page goes up (public or private) and never look at the settings again. But a page that's already live usually has several more specific controls sitting underneath that first choice, and knowing they exist matters most when a particular worry shows up: an ex-partner the family doesn't want commenting, an employer who shouldn't see the funeral address, or a search result the family would rather didn't come up when someone types the deceased's name into Google. See the Online Memorials hub for how this fits alongside setting up, writing for, and moderating a page.

This page is about the settings available once a page exists, not the initial choice of whether to make it public or private in the first place. For that broader decision, see how do you announce a death and share an online memorial respectfully, which covers who to tell before anything goes live and how to choose the page's starting visibility.

The three separate layers of "who can see it"

It helps to treat visibility as three distinct settings, not one:

1. Page-level access: public, private, or invite-only. This controls who can find and open the page at all.
2. Field-level visibility: which specific pieces of information (a service address, contact details, a home town) show to everyone who can see the page versus only to people the family trusts.
3. Search engine visibility: whether the page turns up in a Google search for the deceased's name, independent of whether the page itself is public.

A public page doesn't have to expose everything, and a page can be technically public while still being effectively invisible to a search engine. Most platforms let these three settings be configured independently.

Public, private, and invite-only: what each actually restricts

• Public means anyone with the link, or anyone who finds it through search, can view the page. This gives the widest reach, useful when the family wants distant relatives, old colleagues, and long-lost friends to find and contribute to it, and it's the setting that surfaces stories the immediate family never knew.
• Private means only people the administrator has explicitly approved, usually by email invitation or an approved list, can view the page at all. Everyone else, including someone who has the direct link, is turned away.
• Invite-only sits between the two on some platforms: viewable by anyone with the link (so it isn't discoverable through search or browsing), but posting requires an invitation or approval. The exact meaning of "invite-only" varies by platform, so it's worth checking what a given service actually restricts under that label rather than assuming.

None of these settings is inherently more respectful than another. The right choice depends on the family's own comfort with a wide, semi-public audience versus a closed circle, and it can be changed later if circumstances shift.

Hiding specific details without hiding the whole page

A public page doesn't require every field on it to be public too. Most platforms let a family hide sensitive details from general view while still keeping the page open for tributes and memories:

• Service address and timing. Some families want a public tribute page but a private funeral, or they're wary of an unwelcome person showing up uninvited. Hiding the address from the public page, and sharing it separately with people actually attending (by direct message, a printed order of service, or a separate invite-only section), keeps the tribute open while keeping the event itself controlled.
• Contact details. A phone number or email left on a page for coordination purposes doesn't need to stay visible to every stranger who lands on it.
• Cause of death or other sensitive details. Where the family has chosen to share this at all, it can often be restricted to logged-in contributors or a private section rather than shown to anyone who opens the page.

This matters most where the family wants the widest possible reach for the tribute itself (so old friends and distant relatives can find and contribute) while still protecting the practical details of an actual event from being fully public.

Keeping a page out of search results

A page being public and a page being indexed by Google are two different things, even though people often assume they're the same. Some families want a memorial to stay reachable by anyone with the link, so it can be shared freely with family and friends, but they'd rather it didn't come up when someone searches the deceased's name directly. Common reasons include keeping the page away from an employer who shouldn't be the one to find out this way, or from an estranged relative or ex-partner who the family would rather didn't stumble across it.

Where a platform offers this as a separate setting (sometimes labelled "hide from search engines," "exclude from indexing," or similar), it works by asking search engines not to include the page in their results, technically done using a noindex instruction, without restricting who can view the page if they already have the link. This differs from making the page fully private, which restricts viewing outright rather than just search visibility. Not every platform offers this as a distinct control, so if it matters to a family, it's worth checking specifically rather than assuming a public page automatically supports it.

Requiring approval before a post goes live

Some platforms let an administrator require every post to be approved before it appears publicly, rather than posting instantly. This is a setting configured in advance, and it's a genuinely different tool from moderating a page after a difficult post has already appeared. Pre-approval prevents an upsetting or inappropriate post from ever being visible in the first place; moderation is what happens once something is already live and a family has to decide whether to remove it. Families expecting a genuinely difficult contributor, or simply wanting peace of mind during an already hard week, often turn pre-approval on for the first few weeks and relax it once the page has settled into a steady, trusted rhythm.

The trade-off is a small delay: contributions don't appear the instant someone writes them, which can feel less spontaneous for a page meant to gather memories in real time. Most families find this a reasonable cost for the reassurance it buys during the most vulnerable period.

Blocking a specific person from posting, in advance

Separately from approving individual posts, some platforms let an administrator block a named person from posting on the page at all, set up before that person ever tries. This is worth distinguishing from removing someone's post after the fact, which is a moderation decision made in reaction to something that's already happened. Pre-blocking is a preventative setting, typically used where the family already knows, before the page goes live, that a particular person's involvement would cause real distress: an estranged parent, a person subject to a restraining order, or someone with a documented history of harassment.

This is a step worth taking sparingly. Most disagreements over who gets to contribute are better handled through page-wide settings (public versus private) or case-by-case moderation than by pre-emptively excluding a named individual, which can itself become a source of family conflict if others disagree with the decision. Reserve it for situations where the risk is clear and specific, not as a general precaution against anyone the family finds difficult.

Account-free posting versus requiring sign-in

Most memorial platforms let visitors choose whether contributing requires creating an account or simply typing a name and a message. This is primarily a spam and troll-prevention setting rather than a privacy one:

• Account-free posting lowers the barrier for genuine contributors, useful for an older relative unfamiliar with creating new accounts, or anyone who wants to leave a message quickly without friction. The trade-off is that it also makes it marginally easier for spam or a bad-faith anonymous post to appear.
• Sign-in required adds a small amount of friction but makes it harder for anonymous spam or troll posts to reach the page, and it gives the administrator a clearer record of who posted what.

Combined with requiring approval before a post appears, sign-in requirements give an administrator the most control; combined with public access and no approval step, account-free posting gives contributors the least friction. Most families land somewhere in between, based on how much they expect the page to attract a wide, sometimes anonymous audience. Platforms such as Forever In Our Hearts build these controls in at the administrator level, so a family can adjust visibility, approval, and posting settings themselves as circumstances change, rather than needing to contact support each time.

What this page doesn't cover

This page is about settings on a dedicated memorial page itself. It doesn't cover Facebook's memorialised-account settings, Google's Inactive Account Manager, or Apple's Legacy Contact, which are separate tools controlling access to the deceased's own personal accounts rather than a family-created tribute page. See what happens to your digital accounts when you die for those.

Things to Consider

• Decide these settings before sharing the link widely, not after. It's much easier to start with pre-approval and sensitive fields hidden, then relax them as the page settles, than to tighten settings after something unwanted has already happened.
• A more locked-down page isn't automatically the safer choice. The value of an online memorial comes largely from the people who find and contribute to it, including distant relatives and old friends the immediate family has lost touch with. Over-restricting visibility can quietly narrow a page that was meant to gather a whole community's memories.
• Revisit the settings once the initial rush has passed. Pre-approval and tight visibility settings that made sense in the first anxious week often aren't needed once the page has an established, trusted group of contributors.
• These settings sit alongside who administers the page, not instead of it. Visibility controls only work if someone maintains access to change them. See who inherits administrator control of an online memorial page for keeping that access secure over the long term.

Common Mistakes

• Assuming public and indexed by Google mean the same thing. A page can often be made public for anyone with the link while still being excluded from search results, if the platform offers that as a separate setting. Check rather than assume.
• Putting a full home address in the open, public part of the page. Where a service is genuinely private, or the family is wary of an uninvited attendee, keep the address in a section visible only to invited contributors rather than the whole public page.
• Reaching for pre-blocking as a first response to a family disagreement. Blocking a named person in advance is a significant, hard-to-undo-socially step. It's appropriate for a clear, specific risk, not a general precaution against someone the family simply finds difficult.
• Leaving every setting on its default. Most platforms default to the broadest, most open configuration. Deciding deliberately, even if the conclusion is to keep the defaults, is worth the ten minutes it takes.