Site Launch Workshop / GUIDE
The handover folder a website buyer needs
Prepare a transferable asset while the website is still easy to understand.
Separate accounts from files
A ZIP of HTML files is only one part of a handover. Inventory the domain, hosting, source, analytics, mailing tools and any paid licenses. Note whether each account or license is transferable. Keep credentials in an appropriate password manager, not in a public downloads folder.
Document the publishing process
Write the exact path from editing a page to seeing it live. Include where backups go, how a release is verified and how a prior version is restored. Test those notes with someone unfamiliar with the project. Missing steps are easier to fix before a sale introduces a deadline.
Show evidence responsibly
Keep traffic exports, revenue statements and expense records with their date ranges and definitions. A page-view count from an ad platform is not interchangeable with an Analytics user count. Separate estimates from settled payments and revenue from profit. Never turn a domain appraisal into a claim about operating earnings.
Inventory rights and obligations
List image sources, content permissions, affiliate agreements and software subscriptions. A buyer needs to know what can move and what must be replaced. Remove personal datasets from examples and record any contractual restrictions. Obtain qualified advice for the actual sale rather than treating a checklist as a purchase agreement.
Rehearse the technical move
Create a temporary copy, check internal links and confirm the domain can be pointed at its intended destination. Plan the order of account transfers and DNS updates. Keep the previous service available until verification is complete. A small, documented site is often simpler to hand over than one dependent on a large collection of undocumented plugins.
Prepared with AI assistance. Examples are constructed for explanation, not reported client results. Corrections are welcome.