Need to know what to include in a website handover document? Use this complete checklist to deliver websites like a pro, with logins, assets, instructions & more.
💡 Introduction
Delivering a website without a proper handover document is like giving someone a car with no keys or manual. If you’re a web developer, agency, or freelancer, it’s critical to know what to include in a website handover document to avoid endless post-launch headaches.
This post is your complete, SEO-optimized checklist to make sure your website delivery is clean, professional, and future-proof.
🧩 Why a Website Handover Document Matters
When you deliver a website, you’re handing over control — but also responsibility. A detailed website handover document:
✅ Protects you legally and professionally
✅ Educates your client (less support burden later)
✅ Shows you’re a pro who takes quality seriously
This is why it’s essential to understand exactly what to include in a website handover document — and do it right.
📦 What to Include in a Website Handover Document
Here’s the full breakdown of what to include in a website handover document to avoid confusion and set your client up for success.
1️⃣ Admin Login Credentials 🔐
Provide access details for:
CMS (e.g., WordPress, Webflow, Shopify)
Hosting panel (e.g., cPanel, SiteGround)
FTP/SFTP login
Email management (if setup included)
🛡️ Tip: Tell clients to change passwords after handoff.
2️⃣ Domain & Hosting Info 🌐
Include:
Hosting provider name + URL
Domain registrar info (GoDaddy, Namecheap, etc.)
DNS records or nameservers
Renewal dates
🧾 Optional: attach a TXT file with backup DNS config.
3️⃣ Website Structure Overview 🧱
Your client should understand how the website is laid out:
Main pages and subpages
Navigation/menu structure
Important post types or collections
Login URL
📌 Bonus: Add a flowchart or diagram of the structure.
4️⃣ Theme & Plugins List 🧩
Clearly list:
Theme name + version
Custom theme or builder used (Elementor, Divi, etc.)
Plugins (free and premium)
Licensing status or renewal dates
🔔 Let the client know what must be kept updated.
5️⃣ Branding & Design Files 🎨
Include:
Logo files (PNG, SVG, EPS)
Fonts used (plus download links if licensed)
Any design source files (Figma, PSD)
📁 Deliver in a clean ZIP folder or Google Drive link.
6️⃣ Website Operation Guide 🧠
This is where you shine as a professional. Include:
How to update pages/posts/products
How to add blog posts
How to manage users
How to back up the website
How to contact you (or not, if you’re done)
🎥 Want to go next level? Add Loom walkthroughs.
7️⃣ SEO & Analytics Details 📊
Help the client understand the SEO foundation:
SEO plugin used (Yoast, Rank Math)
Sitemap URL (
/sitemap.xml)GA4/Google Tag Manager access
Any schema setup or custom tags
Robots.txt or .htaccess updates
🔍 Bonus: Add a quick PageSpeed test link for proof.
8️⃣ Security Recommendations 🔒
Protect your client (and yourself):
Recommend regular updates
Suggest a security plugin (e.g., Wordfence)
Two-factor authentication (2FA) options
Hosting-level firewalls or backups
🧯 Explain what to do in case of a security issue.
9️⃣ Maintenance Plan or Offer 🧹
Most clients need ongoing support but don’t realize it.
Explain typical monthly maintenance tasks
Offer your own support package
Link to a care plan or retainer offer
Add upsell options like SEO, hosting, etc.
💸 This is a great time to secure long-term income.
🔟 Final Checklist & Sign-Off 📝
Make the handover official:
“Client accepts final website as delivered”
Signature or digital acknowledgment
Any remaining payment terms
Support window (e.g., 7–14 days post-handover)
📌 Keeps your boundaries clear. You’re not on-call forever!
🧠 10 Common FAQs – Website Handover Document
1. What is a website handover document?
A website handover document is a detailed file that includes credentials, instructions, and resources a client needs after a website is delivered.
2. Who prepares the website handover document?
Usually the web developer, freelancer, or agency that built the website.
3. What’s the most important thing to include?
Login credentials, hosting access, and a user guide are critical.
4. Should I include plugin license keys?
Yes — or at least tell the client which ones need renewing and how.
5. Do I need to offer post-launch support?
It’s optional, but you should define a support window in the document.
6. What if the client breaks the site later?
Your document should disclaim future responsibility unless you’re on retainer.
7. How do I deliver the handover file?
PDF format + ZIP folder for assets. Google Drive works well too.
8. Should I explain SEO basics?
Yes — give them a list of tools and tips to maintain rankings.
9. Can I upsell a care plan?
Absolutely. A handover doc is a perfect time to introduce ongoing services.
10. How long should the handover document be?
Usually 5–10 pages, depending on the complexity of the site.
📦 Final Thoughts
If you’ve been wondering what to include in a website handover document, now you have a step-by-step guide. Delivering a clean, clear, and client-friendly handover file shows professionalism, reduces future confusion, and helps build trust.
✅ A solid website handover document = happy clients, fewer problems, more referrals.
📥 Want a Free Website Handover Template?
👉 Download a done-for-you, editable Google Docs handover template at DigitalExpertWorld.com
