What You Need to Know Before Setting Up an Anthony Memorial
An online memorial is a specific type of website that exists to remember someone after they die. The Anthony Memorial is one example of this — a dedicated webpage or microsite built to preserve memories, share biographical information, host photos and videos, and sometimes accept donations in someone's name. People create these for family members, friends, colleagues, or public figures. The process isn't complicated, but there are a few practical decisions that will determine whether the memorial lasts or gets abandoned within a year. The biggest decision is where to host it. You have three realistic paths here, and each one has serious trade-offs that most people don't consider upfront. Option 1: Dedicated memorial platforms. Sites like Ever Loved, Legacy.com, or Forever Remembered give you a pre-built template designed specifically for memorials. The advantage is speed — you can have something live in under an hour. The disadvantage is that you don't own the page. If the platform shuts down, changes its pricing, or decides to remove content, your memorial disappears with it. I learned this the hard way with a client who built a memorial on a free tier of a smaller platform. Two years later the company was acquired, the free tier was eliminated, and all the content was migrated to a format that broke every photo gallery and timeline they'd built. Recovery took three weeks and about forty percent of the content was lost permanently.
Option 2: A self-hosted WordPress or similar CMS. This is what I recommend for anything you want to last more than five years. You control the domain, the hosting, and the content. The initial setup takes longer — probably two to four hours if you're doing it yourself — but the long-term stability is significantly better. You can set up automatic backups, and you can move the entire site to a different host at any time without losing anything. A basic memorial site on WordPress with a clean theme like Astra or GeneratePress costs about ten to fifteen dollars per month if you include hosting, domain registration, and a backup plugin. Not expensive, and fully under your control. Option 3: A static site hosted on GitHub Pages or Netlify. This is the cheapest option — effectively free if you already own a domain — but it requires technical comfort. You write the content in HTML or Markdown, push it to a repository, and it goes live. No database, no plugins, no update mechanism to break. The downside is that non-technical family members can't easily add new photos or stories later. If that matters to you, skip this option.
Setting Up the Site
Once you've chosen a platform, the actual build is straightforward. Here's what matters for the structure: Start with a homepage that has a clear photo of the person, their full name, dates of birth and passing, and a short paragraph of context. This is the first thing anyone sees, and it's also what shows up in search results. Make sure the title tag and meta description are written deliberately — generic titles like "Memorial Page" get lost quickly in search. Add these sections in order of importance: a biography or life story, a photo gallery, a timeline of key life events, a guestbook or comments area for people to share memories, and a donations section if applicable. Keep each section focused. Long walls of text get skipped. Use subheadings, bullet points for facts, and captions on every photo that actually say something useful instead of just repeating the filename.
Get the Full Details
One thing most people get wrong is the navigation structure. Don't create fifteen separate pages. Group related content together. A single "Life Story" page with anchor links is better than five fragmented pages that all compete for attention and split the SEO value. Search engines and human visitors both prefer concentrated, well-organized content.
Photo and Media Management
This is where most memorial sites fail in practice. People upload hundreds of photos without optimization, and the page becomes slow enough that visitors leave before anything loads. Compress every image before uploading. A tool like Squoosh or ShortPixel will reduce file sizes by sixty to eighty percent with no visible quality loss. A typical memorial with fifty photos should total under three megabytes across the entire gallery. If it's over ten megabytes, you've done something wrong. Use consistent naming for your image files too. "IMG_4829.jpg" tells nobody anything. "john-anthony-graduation-1987.jpg" is searchable and gives context. This matters for SEO and for anyone trying to find a specific photo later.
A Specific Problem and Workaround
I ran into an issue recently with a memorial site where the family wanted to accept tribute payments through PayPal, but the platform's form integration kept breaking when more than three people submitted forms within a short window. The forms would silently fail — no error message, no confirmation, just a blank screen. This meant donations were being lost without anyone noticing for about two weeks. The workaround was to switch from an embedded payment form to a direct donation link that opened in a new tab, combined with a simple email notification setup using a service like Formspree. This eliminated the form-handling bottleneck entirely and the failure rate dropped to zero. It took about twenty minutes to implement once I diagnosed what was happening.
Common Pitfalls to Avoid
There are a few mistakes that come up repeatedly and are easy to prevent: First, don't publish the memorial without a clear statement about who maintains it and how people should contact the family. Without this, every comment section and guestbook entry becomes a vector for spam, scams, or inappropriate messages. A simple contact email or moderation policy at the top of each interactive section solves this. Second, don't skip the privacy check. Some photos or documents may contain information the family didn't intend to make public — medical records, financial details, private correspondence. Review everything before publishing. Once something is online, removing it completely is nearly impossible even if you delete the source.
Third, set a recurring maintenance reminder. Check the site quarterly for broken links, outdated information, or expired hosting payments. I've seen multiple memorials go dormant because the domain expired and nobody renewed it. A simple calendar event every six months prevents this.
When a Memorial Site Isn't the Right Choice
Not every situation calls for a full website. If the goal is simply to share a few photos and a brief message with immediate family and close friends, a private Facebook group or a shared Google Drive folder might be more appropriate. These require less technical skill, less ongoing maintenance, and they keep the content away from public search engines. A public memorial site is appropriate when you want the content to be discoverable, when there are many people who want to contribute memories, or when the person being remembered had a public profile. Otherwise, a private alternative is often the more practical choice. The Anthony Memorial and similar tribute sites serve a real purpose, but they require the same kind of practical planning that any long-term web project does. Pick the right platform, keep the media optimized, set up moderation early, and plan for maintenance from the start. The sites that survive are the ones built with those basics in mind.
