Launch day is when most businesses relax, and it is also the moment they have the most leverage. The final invoice is not yet paid, the agency still has every login at its fingertips, and nobody has forgotten where anything is. Six months later, getting a missing password or an unlisted license can take weeks.
Seahawk maintains thousands of WordPress sites, and many of them come to us with something missing from the handover: a domain registered to a former freelancer, a premium plugin licensed to an agency that no longer exists, or analytics owned by someone’s personal Google account. This checklist is designed to prevent all of that. Print it, take it to your launch meeting, and do not sign off until every box is ticked or has a written reason why not.
When to use this checklist
Use it twice. Before you sign the contract, attach it to the proposal and ask the agency to confirm that the handover will include everything on it. Our guide to writing a website scope of work shows where it fits. At launch, go through it item by item with the agency on a call.
One rule applies throughout: logins should be your own accounts, using your business email address, not shared logins and not the agency’s accounts. Store every credential in a password manager, not in an email or a spreadsheet.
1. Domain name
Whoever controls the registrar account controls your website and your email. This is the single most important item on the list. Our guide to registering a domain name covers the basics.
- The domain is registered in my business name, with my email as the registrant contact
- I have my own login to the registrar account (or the domain has been moved to my account)
- Auto-renew is on and the payment method on file is mine
- I know the renewal date and annual cost
- I know who to contact at the registrar if I am locked out
If the domain was registered or transferred recently, note that a move to another registrar is usually blocked for 60 days afterward. That is normal and not a reason to delay the handover.
2. Hosting
- The hosting account is in my business name, or the agency has given me a written exit process
- I have my own login to the hosting control panel
- I know the plan, its monthly or annual cost, and its renewal date
- I know what the plan includes: backups, SSL certificate, staging site, support
- The SSL certificate is active and set to renew automatically
If you are unsure whether the host is a good fit, see how to choose a web hosting company, our list of the best WordPress hosts for small business, and independent reviews on HostList.
3. Builder, theme, and plugin licenses
Free WordPress themes and plugins need no license. Premium ones do, and the license determines who receives updates and security fixes. A license in the agency’s name stops working for you the day the relationship ends.
- I have a written list of every paid theme, page builder, and plugin on the site
- Each paid license is in my business name, or has been transferred to me
- Each license key is entered on the site so updates arrive automatically
- I know each license’s renewal date and cost
- Nothing on the site depends on a proprietary builder that only the agency can edit
4. WordPress admin access
- I have my own Administrator account using my business email
- Other staff have accounts with the lowest role they need (Editor or Author, not Administrator)
- The agency’s accounts are listed, and we have agreed whether they stay or are removed
- Two-factor authentication is turned on for Administrator accounts
- I have logged in myself, before sign-off, and confirmed it works
5. Backups
- Automatic backups are running, covering both files and the database
- I know where backups are stored, and at least one copy is stored away from the web server
- I know how often backups run and how long they are kept
- I have received one complete backup of the site at launch
- Someone has shown me, or documented, how a backup is restored
6. Code repository
This applies if the agency wrote a custom theme, a custom plugin, or any other code.
- All custom code is in a repository (for example on GitHub or GitLab) that I own or have been given admin access to
- The contract confirms I own the custom code on final payment
- There is a short README explaining how the code is built and deployed
7. Analytics, Search Console, and tracking
Analytics and search data are years of history you cannot recreate. Make sure they belong to you.
- Google Analytics (or another analytics tool) is set up in an account I own, with the agency added as a user if needed
- Google Search Console is verified for my domain, and I am an Owner
- Any tag manager, advertising pixels, and conversion tracking are in accounts I own
- Form submissions go to an email address or system I control
8. Email and DNS records
Your domain’s DNS records decide where your website, your email, and several third-party services point. A mistake here can stop email without anyone noticing for days.
- I know where my DNS is managed (registrar, host, or a DNS service) and I have a login
- I have an export or screenshot of every DNS record after launch
- Mail (MX) records point to my email provider and email is working
- SPF, DKIM, and DMARC records are in place so website and business email is not marked as spam
- Any old records from the previous site or host have been cleaned up
9. Editing the site going forward
A site you cannot update yourself turns every small change into an invoice.
- I have had a training session, and it was recorded
- I have written documentation for common tasks: editing a page, adding a post, changing a menu, updating a form
- I know which changes are safe to make myself and which ones should go to a developer
- I have a list of every page template and reusable block, and what each is for
10. Ongoing care and costs
WordPress core, themes, and plugins release updates all year. Someone needs to apply them, check nothing broke, and watch for problems. See do you need a WordPress maintenance plan for how to decide.
- We have agreed who handles updates, backups, and security monitoring after launch
- If the agency offers a care plan, I have the price and what it includes in writing
- I know what is not covered and how extra work is priced
- I have a single total of my yearly running costs: domain, hosting, licenses, and care
11. Warranty period
Most agencies fix defects in their own work for a set period after launch.
- The warranty period is written down, with a start and end date
- I know what counts as a defect (their mistake) versus a change request (new work)
- I know how to report a problem and how quickly they respond
12. Final sign-off
- Every item above is ticked or has a written reason why not
- All credentials are stored in my password manager
- I have tested the contact form, checkout, or booking flow myself on a phone
- The final invoice is paid only after the above is complete
If something is missing
Ask for it in writing before you pay the final invoice, and name a date. Most gaps are oversights rather than bad intent, and a good agency will fix them quickly. If the agency refuses to hand over your domain, licenses, or admin access, that is one of the agency red flags to note for next time, and it is worth getting help before the relationship ends completely.
Who looks after the site now
If your agency does not offer ongoing care, or you would rather keep build and maintenance separate, WP Care plans from WP Services start at $29 a month and cover updates, backups, and monitoring. Seahawk works with more than 1,000 agency and hosting partners and maintains thousands of WordPress sites. You can also compare options in our list of the best WordPress maintenance services.