WordPress Site After Death: Admin Access and Preservation
A WordPress site after death can be a family archive, a public memorial, a small business asset, a client-facing website, or years of writing that nobody wants to lose. It can also be fragile. One person may know the admin login, hosting account, domain registrar, DNS settings, backup plugin, payment card, and developer relationship.
When that person dies, the site is not just "on WordPress." It is a stack of accounts and decisions. Families and executors need to preserve what matters before they change, transfer, or cancel anything.
The right plan depends on one early question: is the site on WordPress.com, or is it a self-hosted WordPress installation on another host?
WordPress.com and self-hosted WordPress are different
WordPress.com is a hosted service with its own account, support, billing, purchases, and transfer workflows. If a WordPress.com site owner dies, WordPress.com has a documented deceased site owner process. The person contacting support should provide the site owner name or email if known, the site URL, an explanation, and the desired action, such as making the site private or transferring it.
For transfer requests, WordPress.com asks for a death certificate plus a legal authority document, or a signed notarized statement with the requester's details, relationship, and requested action.
Self-hosted WordPress is different. The software may be WordPress, but the practical control sits with the hosting provider, database, files, admin users, domain registrar, DNS provider, and payment method. There may be no single WordPress support team that can transfer the whole thing. The executor may need the host, domain registrar, developer, and WordPress administrator to work together.
That distinction should be written plainly in the owner's digital estate notes.
Administrator access is powerful
WordPress roles matter. WordPress.org describes Administrator as the role with access to all administration features within a single site. Editors can manage content, but they do not have the same full site administration power.
For estate planning, that means two things.
First, a site owner should not hand out administrator access casually. An administrator can change settings, manage users, affect plugins and themes, and potentially break the site.
Second, if the site matters, someone trustworthy should know how administrator access will be handled in an emergency. That might mean a second administrator, a documented technical executor, a managed hosting account with organization access, or a sealed emergency process stored with estate records.
The right answer depends on risk. A private hobby blog may only need recovery instructions. A business site that takes payments or handles customer inquiries should not depend on a single personal login.
Map the WordPress stack before acting
Before changing anything, map the site.
Start with the visible URL. Then identify the WordPress type, owner account, administrator users, hosting provider, domain registrar, DNS host, email provider, payment method, backup location, and any developer or agency. Note whether the site uses ecommerce, forms, memberships, analytics, ad networks, donation tools, newsletter integrations, or custom plugins.
Also document the path to the WordPress admin area, but do not store broad credentials in an unsafe note. A digital estate letter can say where the password manager emergency process, 2FA backup codes, hosting credentials, or legal documents are stored without exposing them in the letter itself.
This map helps an executor avoid accidental damage. Canceling hosting can delete files. Moving DNS can break email. Deleting a plugin can remove forms or payment features. Changing the domain without understanding WordPress URL settings can leave the site pointing to the wrong place.
Preserve content before transfer or shutdown
The safest first technical step is often preservation.
WordPress includes an export tool that can create an XML file containing posts, pages, comments, custom fields, terms, navigation menus, and custom posts. That is useful, but it is not always a complete recovery plan.
For a self-hosted site, families may also need the media uploads folder, theme files, plugin list, custom code, configuration, and database. WordPress developer documentation strongly recommends backing up the database at regular intervals and before upgrades. WordPress.org also advises backing up before updating WordPress because updates can affect files and folders in the installation.
Executors should not assume a content export is enough to recreate the site exactly. A photo-heavy blog, custom theme, WooCommerce shop, membership site, or portfolio may rely on files and database records that go beyond a simple export.
Keep billing and security stable
If the site should stay online, billing matters quickly. Hosting, WordPress.com purchases, domain registration, premium plugins, security tools, and backup services may all renew separately.
Do not cancel the deceased owner's payment card until the executor understands what it pays for. Also do not leave an old card active indefinitely without estate authority and review. The practical move is to identify renewals, keep critical services paid long enough to preserve the site, then move billing to the rightful owner or close services deliberately.
Security also matters. A neglected WordPress site can become a risk if plugins, themes, or core software are not maintained. If the site will remain online, assign a technical person to review updates, backups, malware alerts, admin users, and 2FA. If no one can maintain it, archiving or making it private may be safer.
Decide the intended outcome
Access is not the same as a decision.
For each WordPress site, the owner should write what should happen:
- keep public as an archive
- add a memorial notice or final post
- transfer to a spouse, business partner, company, or nonprofit
- make private while the estate is settled
- export and archive privately
- shut down after backup
WordPress.com says a site transfer can move ownership, plans, paid upgrades, and registered domains attached to the site. That may be perfect for a site with a clear successor. For a self-hosted site, the equivalent may involve changing the hosting account owner, registrar owner, DNS access, WordPress administrator, and payment methods.
The decision should come before the technical work. Otherwise a helper may preserve a site the family wanted private, or delete a blog that held years of family history.
Be careful with domains and URLs
WordPress migration documentation notes that WordPress Address and Site Address settings control where WordPress is located and how the site appears. That becomes important when a domain is transferred, hosting changes, or a site moves to a new owner.
The domain can be separate from WordPress. The DNS provider can be separate from the domain registrar. The site files can be separate from both. A family should not assume that transferring one piece transfers the whole website.
Before changing a domain or nameserver, confirm:
- where the domain is registered
- where DNS is hosted
- where email records point
- where the WordPress site is hosted
- whether the WordPress URL settings need adjustment
- whether backups exist
This is especially important for small businesses. A domain change can break email, forms, payment callbacks, search visibility, and customer trust.
A practical owner checklist
If you own a WordPress site, prepare this while you are alive:
- Record whether the site is WordPress.com or self-hosted WordPress.
- List the site URL, admin URL, owner account, administrator users, host, registrar, DNS provider, and email provider.
- Name the person who should act if you die or become incapacitated.
- Add a second administrator or documented emergency process where appropriate.
- Store password manager, 2FA, hosting, and backup recovery details securely.
- Keep database and file backups for self-hosted sites.
- Write the desired outcome for the site.
- Review the plan after changing hosts, domains, plugins, payment cards, or business ownership.
For broader website continuity, see /en/blog/web-hosting-account-after-death.