If a WordPress administration email change stays pending, verify the new recipient and mail delivery before submitting the change repeatedly. The site administration address and your individual user-profile address are separate settings, and changing one does not automatically change the other.
Start while you still have an authorized administrator session and hosting access. A mailbox handoff is easiest to resolve before the old address is retired. Do not disable login protection or publish a confirmation link to make troubleshooting easier.
Identify the address you are changing
Review Settings > General and the pending change notice. Separately inspect your user profile's email field. The General settings reference distinguishes site administration settings from account settings.
Write down the intended business-owned mailbox and verify that its owner can receive ordinary external mail. Avoid personal addresses belonging to a departing contractor. A shared mailbox can be appropriate if access is controlled and someone is responsible for time-sensitive notices.
Trace one confirmation attempt
Use one deliberate change request and record its time and timezone. Check junk, quarantine, alias routing and mailbox rules. If you use an email delivery provider, search its logs for the recipient around that time without copying the private confirmation URL into a public ticket.
Distinguish no sending attempt, provider rejection, delivery acceptance and actual arrival. An accepted message may still be filtered by the recipient's organization. A generic SMTP test reaching your own address does not prove this specific notification reached the proposed administrator address.
No sending event: Inspect WordPress mail routing and suppression. Rejected: Use the specific delivery error and message ID. Accepted but missing: Ask the receiving organization to trace it. Confirmed: Active address correct; pending notice resolved. Original explanatory guide, not a customer test result.
Investigate the sending layer
If there is no provider event, inspect the WordPress mail integration and application logs for the attempted notification. A mail plugin may rewrite recipients, suppress system notifications or use different settings on staging. Confirm you are changing the production site, not its clone.
If the provider reports rejection, give the mail administrator the message identifier, time and rejection reason. Keep authentication details out of the ticket. If delivery is accepted but the message is missing, ask the recipient organization to trace that identifier and inspect quarantine.
Do not keep clicking resend while another administrator is changing the same setting. Agree on one intended address and one operator. Check the current pending state before opening an older message, particularly after correcting a typo.
Keep emergency recovery separate
If the site is broken and you are waiting for a Recovery Mode notification, use the missing Recovery Mode email guide. That is a different workflow from confirming an address change.
An authorized hosting administrator may have a supported emergency configuration procedure when the mailbox is inaccessible. Verify business ownership first, preserve the previous configuration, and document any direct change. Do not use an unreviewed plugin that globally bypasses confirmation across every account.
Confirm the handoff is complete
Reopen General settings and verify the intended address is active and the pending notice is resolved. Check the separate user account address if that also needs a handoff. Retest a harmless notification and confirm who monitors the new inbox.
Ask for mail-delivery troubleshooting when the application and mail provider disagree. Provide the sanitized delivery trail, not a password or a private recovery link. Keep the old mailbox available until the new notification path has been verified.
Sources checked October 1, 2026. Instructions and visuals are explanatory, not claims of customer tests.