WordPress Site Handoff Checklist: 7 Publisher Checks
Use this WordPress site handoff checklist to verify plugin transfers, maintenance access, affiliate links, outgoing credentials, and rollback before signoff.
What Should You Compare Before Choosing?
A WordPress site handoff checklist helps publishers complete an ownership or maintenance-provider change without losing the ability to run their site. A homepage that still loads is only one part of the result. The incoming operator also needs usable accounts, maintained plugins, working revenue paths, and a clear recovery plan.
Use the seven checks below before signing off a site acquisition, developer handover, or agency exit. Complete each check against the actual site and vendor accounts involved.
Quick answer: Agree on the handoff scope, save a recoverable baseline, confirm each vendor's permitted account-change method, and test incoming maintenance access. Then verify publishing and affiliate journeys, remove outgoing access in a controlled order, and record acceptance with any unresolved exceptions.
| Check | Main question | Completion evidence |
|---|---|---|
| Scope and baseline | What is changing and what must keep working? | Agreed inventory and recovery copy |
| Vendor method | How can each subscription change hands? | Current rule or support confirmation |
| Incoming control | Can the new operator manage the site? | Independent account and recovery tests |
| Maintenance | Can the new operator keep software current? | License status and staging test |
| Revenue paths | Do publishing and affiliate journeys work? | Representative end-to-end checks |
| Outgoing access | Which permissions should end or continue? | Completed removal and retained-access record |
| Acceptance | Who owns remaining work and recovery? | Dated signoff and exception list |
When to use this checklist
Use this WordPress site handoff checklist once the parties have agreed that responsibility will change. It fits an acquired affiliate blog, a publisher leaving an agency, or a site moving from one maintenance contractor to another. A simultaneous hosting migration needs its own procedure and tests.
Start with the WordPress plugin license audit if you do not yet know which subscriptions cover the site. That review establishes the starting inventory. This guide checks whether the incoming operator can actually take over and the outgoing operator can leave safely.
These checks are a suggested operating process. Vendor instructions determine available account changes; your agreement determines payment and responsibility. A domain reassignment, subscription transfer, hosting transfer, and WordPress user change may involve different procedures.
Seven checks before the publisher accepts the site
1. Agree on the scope and preserve a baseline
List what the handoff includes: WordPress, hosting, domain services, paid plugins, custom code, backups, email delivery, and external integrations. For each component, name the incoming operator and the outgoing person who can complete the change. Identify anything explicitly staying with a service provider.
Save a recovery copy of the files and database, relevant configuration exports, and the current software versions. Verify that the incoming operator can retrieve the copy and understands the restoration method. An old archive on the outgoing developer's laptop is weak recovery evidence.
Record a few baseline journeys before making changes. For an affiliate publisher, those might include editing a review, submitting a newsletter form, and following a product link. Compare these journeys after the handoff.
2. Confirm the permitted method for each paid plugin
Ask whether the vendor permits an account transfer, an account switch on the existing site, or a new subscription owned by the publisher. Record the supported method and who must perform it. Do not treat a site sale or a contractor's promise as proof that every subscription can transfer.
Elementor's official license settings guide describes switching a client site from the developer's Elementor Pro account to the client's account. The incoming account must have an Elementor Pro license. This is a specific supported account-switch workflow, not a rule for all WordPress plugins.
If the vendor's instructions are unclear, keep that component open and obtain confirmation before removing current coverage. A WordPress site handoff checklist should capture the decision and evidence, rather than merely say that the license was included.
3. Prove the incoming operator controls the accounts
Have the new operator sign in using their own account, check recovery options, and confirm that relevant notices reach an inbox they control. Verify the exact production domain and subscription shown in each dashboard. Check hosting and billing control separately.
Use named accounts where the service supports them. Decide who should receive renewal, security, and failed-payment notices, then confirm those settings. Keep passwords and recovery codes in an appropriate protected system, with references in the handoff record rather than pasted secrets.
For example, a publisher may gain WordPress administrator access while the agency still owns the plugin account and receives all renewal messages. That is incomplete unless the parties explicitly agree to a continuing maintenance service and document its responsibilities.
4. Test maintenance access before closing old coverage
Check plugin account connections, download access, available update status, and support eligibility under the incoming arrangement. When a routine update is available and appropriate, test it on staging with a recovery path. If no update is available, record that limitation.
Use the site's actual dependencies to guide the test. Check page-builder editing, cached pages, and retained SEO configuration. Avoid combining a provider handoff with an unrelated redesign or wholesale plugin replacement.
The Elementor program listing, WP Rocket program listing, and Rank Math program listing support publisher research into relevant tools. Affiliate enrollment is separate from permission to use or maintain an installed plugin. Confirm product requirements directly before buying or changing coverage.
5. Check publishing and affiliate revenue journeys
Repeat the baseline checks as the incoming operator. Edit a test page safely, preview it, submit a test form through its intended destination, and inspect representative mobile pages. Check scheduled publishing, notifications, and integration accounts.
For affiliate links, confirm destinations and the identifiers assigned to the correct publisher. A website transfer does not establish that an affiliate account or existing tracked links can transfer. Obtain each program's current instructions before changing ownership details or replacing identifiers.
Use the affiliate link redirect audit checklist for deeper destination and redirect testing. A successful click proves a navigable path, not a payable conversion. Record separately whether commission attribution still needs confirmation from the program.
6. Remove outgoing access with explicit exceptions
Review WordPress users, hosting collaborators, deployment access, remote management services, and integration credentials. Remove access that the outgoing provider no longer needs only after replacement ownership and essential workflows are verified. Retain narrowly scoped access when ongoing support is agreed, with an owner and review date.
WordPress documents application passwords as separate credentials for API access that can be revoked individually. Review these alongside interactive logins. A provider's publishing or maintenance integration may use a credential that is not visible in a simple list of browser users.
Revoke obsolete credentials and test the integrations that should remain. If a shared secret must change, coordinate replacement before revocation. Record ended and continuing access without removing the incoming operator's recovery route.
7. Record acceptance, exceptions, and rollback ownership
Finish with a dated acceptance record covering completed changes, test results, unresolved items, and the person responsible for each next action. Agree on the support period and which failures should trigger escalation.
Write a practical rollback plan before it is needed. Identify the recoverable baseline, who can restore it, and which later edits or submissions could be lost. A backup can recover site data, but it does not automatically reverse vendor account transfers or revive revoked credentials.
Close the WordPress site handoff checklist when the incoming operator accepts the evidence. Keep any exception visible, such as an unresolved vendor transfer request or attribution confirmation. Assign a deadline and owner rather than marking the entire handoff complete because most pages look normal.
Evidence to keep in the handoff record
Use this suggested record structure in your own workspace. Store sensitive evidence separately and link to protected references.
| Area | Record to retain | Who verifies it | Keep open when |
|---|---|---|---|
| Site baseline | Version list, backup location, recovery method | Incoming maintenance owner | Recovery copy cannot be retrieved |
| Paid plugin change | Vendor method, account reference, completion date | Subscription owner | Transfer permission remains unclear |
| Account control | Named owner, recovery check, notice recipient | Publisher | Outgoing provider remains sole recovery contact |
| Maintenance | Connection status and appropriate staging results | Incoming maintainer | Updates or support access is unresolved |
| Revenue journeys | Sample pages, link IDs, form results, open questions | Publisher | Destination or ownership evidence conflicts |
| Access removal | Revoked credentials and agreed exceptions | Account owner | Necessary access has no replacement |
| Acceptance | Decision, exception owners, support and recovery scope | Both parties | Critical actions have no accountable owner |
For future software recommendations, the WordPress plugin affiliate programs guide maps tools to publishing jobs. Keep those offer comparisons separate from the evidence proving that your own site has changed hands successfully.
Key Takeaways for WordPress Site Handoff Checklist: 7 Publisher Checks
A WordPress site handoff checklist should prove that the incoming publisher can operate, maintain, and recover the site. Confirm vendor methods, test real publishing and revenue paths, then remove outgoing access and record acceptance. Assign owners to unresolved items.
Browse FindAffiliates when researching software programs for your publishing audience. Verify current provider terms and recommend tools that fit the reader's job, while keeping affiliate relationships separate from site ownership and maintenance responsibilities.
FAQ
Does changing the WordPress administrator transfer plugin licenses?
A WordPress user change does not establish that a paid plugin subscription transferred. Check the vendor's supported process and confirm incoming account access, maintenance coverage, and billing responsibility separately.
Should the outgoing developer keep administrator access?
Keep access only when the continuing support arrangement needs it. Document the purpose, permitted scope, and review date. Verify incoming control before removing the outgoing operator's access.
Can affiliate links stay unchanged after buying a website?
Check each affiliate program's rules and the account associated with the links. A site purchase does not establish permission to take over another publisher's affiliate account. Confirm the required process before changing or retaining tracked identifiers.
What proves a WordPress handoff is complete?
Evidence should show incoming account control, usable maintenance access, working publishing and revenue journeys, completed access changes, and an agreed recovery plan. Remaining exceptions need a named owner, next action, and acceptance decision.