[{"data":1,"prerenderedAt":1157},["ShallowReactive",2],{"blog-posts":3,"post-\u002Fblog\u002Fwebsite-handover-checklist":301},[4,19,31,50,64,79,94,105,117,131,143,153,164,177,186,201,210,222,234,245,256,267,280,289],{"path":5,"title":6,"description":7,"date":8,"modified":8,"draft":9,"locale":10,"category":11,"image":12,"translationKey":12,"tags":13,"readingTime":18},"\u002Fblog\u002Fwebsite-handover-checklist","Website Handover Checklist: 43 Items to Hand Over at Launch (Free Template)","A website handover checklist for agencies and freelancers: accounts, domain, hosting, backups, licenses and support terms, plus a free handover document.","2026-10-29T08:00:00+00:00",false,"en","guides",null,[14,15,16,17],"website handover checklist","website handover document template","website handover process","web agency",12,{"path":20,"title":21,"description":22,"date":23,"modified":23,"draft":9,"locale":10,"category":24,"image":12,"translationKey":12,"tags":25,"readingTime":30},"\u002Fblog\u002Fclaude-code-fix-bugs","How to Use Claude Code to Fix the Bugs Your Clients Report","How to use Claude Code to fix bugs: what it needs from a bug report, how to connect it to client feedback over MCP, and how to review the fix before you resolve it.","2026-10-27T08:00:00+00:00","workflow",[26,27,28,29],"claude code fix bugs","claude code mcp","ai bug fixing","bug report",7,{"path":32,"title":33,"description":34,"date":35,"modified":36,"draft":9,"locale":10,"category":11,"image":37,"translationKey":43,"tags":44,"readingTime":49},"\u002Fblog\u002Fbest-website-feedback-tools","How to Choose a Website Feedback Tool (2026 Checklist)","How to choose the best website feedback tool in 2026: the tool types, 12 criteria, a free scoring template (Excel) and a one-week trial plan with a real client.","2026-10-07T09:00:00+00:00","2026-10-22T10:00:00+00:00",{"src":38,"card":39,"alt":40,"width":41,"height":42},"\u002Fwp-content\u002Fuploads\u002F2023\u002F09\u002Fscreencode_7_Bug_tracker_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F09\u002Fscreencode_7_Bug_tracker_GiveFeedback-400x250.jpg","Code on a screen, illustrating how to choose a website feedback tool",1200,630,"feedback-tools",[45,46,47,48],"best website feedback tool","website feedback tool free","visual website feedback tool","client feedback",8,{"path":51,"title":52,"description":53,"date":35,"modified":36,"draft":9,"locale":10,"category":24,"image":54,"translationKey":59,"tags":60,"readingTime":49},"\u002Fblog\u002Fclient-website-approval","Client Website Approval: How to Get Sign-Off Without Delays","Client website approval made simple: the 5 approval stages, a revision-limit clause, a sign-off email, a free website sign-off form (Word) and a checklist.",{"src":55,"card":56,"alt":57,"width":58,"height":41},"\u002Fwp-content\u002Fuploads\u002F2023\u002F06\u002FAutomating-Project-Management-for-Efficiency-Sized.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F06\u002FAutomating-Project-Management-for-Efficiency-Sized-400x250.jpg","Two people reviewing a printed document with a pen, ready for client website approval",1920,"client-approval",[61,62,63,17],"client approval process","website sign off","revision rounds",{"path":65,"title":66,"description":67,"date":35,"modified":36,"draft":9,"locale":10,"category":11,"image":68,"translationKey":72,"tags":73,"readingTime":78},"\u002Fblog\u002Fhow-to-collect-client-feedback-on-a-website","How to Collect Client Feedback on a Website (Step by Step)","How to collect client feedback on a website: 5 methods compared, a review round step by step, good vs vague feedback examples and a briefing email to send today.",{"src":69,"card":70,"alt":71,"width":41,"height":42},"\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_web_Designer_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_web_Designer_GiveFeedback-400x250.jpg","Web designer at a desk reviewing client feedback on a website","client-feedback",[74,75,76,77],"client feedback on website","website feedback examples","client feedback examples","website review process",9,{"path":80,"title":81,"description":82,"date":35,"modified":36,"draft":9,"locale":83,"category":11,"image":84,"translationKey":88,"tags":89,"readingTime":30},"\u002Fes\u002Fblog\u002Fanotar-capturas-de-pantalla-web","Cómo anotar capturas de pantalla de una web (Mac, Windows y online)","Cómo anotar capturas de pantalla en Windows, Mac, online o en Chrome, cómo capturar una página web entera y cómo marcar los errores para que se arreglen.","es",{"src":85,"card":86,"alt":87,"width":41,"height":42},"\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_office_colours_pc_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_office_colours_pc_GiveFeedback-400x250.jpg","Persona anotando capturas de pantalla de una web para enviarlas al equipo de desarrollo","screenshot-annotation",[90,91,92,93],"anotar capturas de pantalla","captura de pantalla","anotar captura en Mac","anotar captura en Windows",{"path":95,"title":96,"description":97,"date":35,"modified":36,"draft":9,"locale":83,"category":24,"image":98,"translationKey":59,"tags":100,"readingTime":49},"\u002Fes\u002Fblog\u002Faprobacion-cliente-proyecto-web","Aprobación del cliente en un proyecto web: cómo conseguirla","Aprobación del cliente en un proyecto web: las 5 fases, una cláusula para limitar revisiones, un email de aprobación, un formulario de aprobación gratis y una checklist.",{"src":55,"card":56,"alt":99,"width":58,"height":41},"Dos personas revisan un documento con un bolígrafo antes de la aprobación del cliente en un proyecto web",[101,102,103,104],"aprobación del cliente","rondas de revisión","presupuesto web","agencia web",{"path":106,"title":107,"description":108,"date":35,"modified":36,"draft":9,"locale":83,"category":24,"image":109,"translationKey":111,"tags":112,"readingTime":78},"\u002Fes\u002Fblog\u002Fcapturas-anotadas-en-asana","Capturas anotadas en Asana: cómo llevar el feedback web a tareas","Cómo llevar capturas anotadas y feedback web a Asana: plantilla CSV gratis, cinco métodos comparados y tareas automáticas desde el feedback del cliente.",{"src":38,"card":39,"alt":110,"width":41,"height":42},"Capturas anotadas de una web convertidas en tareas de Asana","asana",[113,114,115,116],"capturas anotadas en Asana","plantilla Asana","gestión de bugs","feedback web",{"path":118,"title":119,"description":120,"date":35,"modified":36,"draft":9,"locale":83,"category":11,"image":121,"translationKey":125,"tags":126,"readingTime":18},"\u002Fes\u002Fblog\u002Fchecklist-qa-web-antes-de-lanzar","Checklist web: más de 70 comprobaciones antes de lanzar","Checklist web con más de 70 comprobaciones por áreas: formularios, enlaces, móvil, navegadores, velocidad, SEO, accesibilidad y WordPress, con plantilla Excel gratis.",{"src":122,"card":123,"alt":124,"width":41,"height":42},"\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracker_people_pc_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracker_people_pc_GiveFeedback-400x250.jpg","Persona revisando una web con una checklist QA antes del lanzamiento","qa-checklist",[127,128,129,130],"checklist web","checklist QA web","pruebas web","lanzamiento web",{"path":132,"title":133,"description":134,"date":35,"modified":36,"draft":9,"locale":83,"category":11,"image":135,"translationKey":137,"tags":138,"readingTime":78},"\u002Fes\u002Fblog\u002Fcomo-escribir-un-informe-de-bugs","Plantilla de reporte de errores (bugs): gratis, con ejemplos","Plantilla de reporte de errores gratis en Excel, Google Sheets y Word, con un ejemplo de informe de bugs bueno y uno malo y los campos que importan en una web.",{"src":38,"card":39,"alt":136,"width":41,"height":42},"Código JavaScript en una pantalla, ilustrando cómo escribir un informe de bugs de una web","bug-report",[139,140,141,142],"plantilla de reporte de errores","reporte de errores","informe de bugs","ejemplo de reporte de errores",{"path":144,"title":145,"description":146,"date":35,"modified":36,"draft":9,"locale":83,"category":11,"image":147,"translationKey":72,"tags":149,"readingTime":78},"\u002Fes\u002Fblog\u002Fcomo-recoger-feedback-de-clientes-en-una-web","Cómo pedir feedback a un cliente sobre su web (paso a paso)","Cómo pedir feedback a un cliente sobre su web: 5 métodos comparados, una ronda de revisión paso a paso, ejemplos de feedback bueno y vago y un email para enviar hoy.",{"src":69,"card":70,"alt":148,"width":41,"height":42},"Diseñador web en su mesa revisando el feedback de clientes sobre una web",[150,151,116,152],"cómo pedir feedback a un cliente","feedback de clientes","revisión de una web",{"path":154,"title":155,"description":156,"date":35,"modified":36,"draft":9,"locale":83,"category":24,"image":157,"translationKey":159,"tags":160,"readingTime":49},"\u002Fes\u002Fblog\u002Ffeedback-web-en-notion","Bugs en Notion: gestiona el feedback de tu web paso a paso","Cómo gestionar bugs en Notion en proyectos web: plantilla gratis, propiedades, vistas tablero, rutina de triaje y cómo recibir el feedback del cliente solo.",{"src":55,"card":56,"alt":158,"width":58,"height":41},"Equipo organizando bugs y feedback de clientes de una web en Notion","notion",[161,162,163,116],"bugs en Notion","plantilla Notion","seguimiento de bugs",{"path":165,"title":166,"description":167,"date":35,"modified":36,"draft":9,"locale":83,"category":168,"image":169,"translationKey":171,"tags":172,"readingTime":78},"\u002Fes\u002Fblog\u002Fherramientas-gratis-seguimiento-bugs","Herramientas gratis de seguimiento de bugs para webs (2026)","Herramientas gratis de seguimiento de bugs para equipos web: los planes gratuitos de Jira, Trello, ClickUp, Notion, Asana, monday.com y Wrike, y una hoja de cálculo gratis.","comparisons",{"src":122,"card":123,"alt":170,"width":41,"height":42},"Equipo revisando incidencias en una herramienta gratis de seguimiento de bugs","free-bug-tracking",[173,174,175,176],"herramientas gratis seguimiento de bugs","bug tracker","gestión de incidencias","hoja de seguimiento de bugs",{"path":178,"title":179,"description":180,"date":35,"modified":36,"draft":9,"locale":83,"category":11,"image":181,"translationKey":43,"tags":183,"readingTime":78},"\u002Fes\u002Fblog\u002Fmejores-herramientas-feedback-visual-web","Cómo elegir una herramienta de feedback visual para tu web","Cómo elegir entre las herramientas de feedback visual web en 2026: tipos, 12 criterios, una plantilla de evaluación gratis en Excel y una prueba de una semana.",{"src":38,"card":39,"alt":182,"width":41,"height":42},"Código en una pantalla, ilustración de cómo elegir entre herramientas de feedback visual web",[184,116,185,151],"herramientas de feedback visual","feedback visual",{"path":187,"title":188,"description":189,"date":35,"modified":36,"draft":9,"locale":83,"category":11,"image":190,"translationKey":194,"tags":195,"readingTime":200},"\u002Fes\u002Fblog\u002Fpruebas-de-aceptacion-uat-web","Pruebas de aceptación de usuario (UAT): ejemplos y plantilla","Qué son las pruebas de aceptación de usuario (UAT), diferencias con el QA, ejemplos de escenarios, checklist para webs y plantillas gratis en Excel y Word.",{"src":191,"card":192,"alt":193,"width":41,"height":42},"\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracking_testing-man_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracking_testing-man_GiveFeedback-400x250.jpg","Cliente haciendo pruebas de aceptación UAT de su nueva web frente al ordenador","uat",[196,197,198,199],"pruebas de aceptación","pruebas de aceptación de usuario","plan de pruebas de aceptación","ejemplo pruebas de aceptación",10,{"path":202,"title":203,"description":204,"date":35,"modified":36,"draft":9,"locale":83,"category":11,"image":205,"translationKey":207,"tags":208,"readingTime":49},"\u002Fes\u002Fblog\u002Fque-es-el-feedback-visual","Qué es el feedback visual y por qué agiliza tus proyectos web","Qué es el feedback visual: comentarios sobre la propia web con capturas marcadas, vídeo o notas. Tipos, ventajas, ejemplos y qué pedirle a una herramienta.",{"src":69,"card":70,"alt":206,"width":41,"height":42},"Diseñador web revisando el feedback visual sobre una interfaz","visual-feedback",[185,116,209,151],"capturas anotadas",{"path":211,"title":212,"description":213,"date":214,"modified":36,"draft":9,"locale":10,"category":24,"image":215,"translationKey":159,"tags":217,"readingTime":49},"\u002Fblog\u002Fsupercharge-your-workflow-with-the-notion-bug-tracker-extension","Notion Bug Tracker Template (Free) for Website Projects","Free Notion bug tracker template for website projects: import the CSV, set up the properties and board views, and send client feedback into Notion.","2025-04-24T16:17:44+00:00",{"src":55,"card":56,"alt":216,"width":58,"height":41},"Team organizing website bugs and client feedback in a Notion bug tracker",[218,219,220,221],"notion bug tracker template","notion issue tracker template","bug tracking","website feedback",{"path":223,"title":224,"description":225,"date":226,"modified":36,"draft":9,"locale":10,"category":11,"image":227,"translationKey":194,"tags":229,"readingTime":78},"\u002Fblog\u002Fuser-acceptance-testing-in-software-development","User Acceptance Testing (UAT): Template, Checklist & Examples","What user acceptance testing is, UAT vs QA, test scenario examples, a UAT checklist for websites and free templates: Excel test plan and Word sign-off form.","2023-09-28T17:32:27+00:00",{"src":191,"card":192,"alt":228,"width":41,"height":42},"Client doing user acceptance testing on a new website at his desk",[230,231,232,233],"user acceptance testing","UAT testing","user acceptance testing template","user acceptance testing checklist for website",{"path":235,"title":236,"description":237,"date":238,"modified":36,"draft":9,"locale":10,"category":168,"image":239,"translationKey":171,"tags":241,"readingTime":78},"\u002Fblog\u002Fbug-tracking-tools-free","Free Bug Tracking Tools for Web Teams (2026 Comparison)","Free bug tracking tools compared for web teams: the free plans of Jira, Trello, ClickUp, Notion, Asana, monday.com and Wrike, plus a free bug tracking spreadsheet.","2023-09-21T16:56:47+00:00",{"src":122,"card":123,"alt":240,"width":41,"height":42},"Team at a computer reviewing issues in a free bug tracking tool",[242,174,243,244],"free bug tracking tools","bug tracking spreadsheet","issue tracking",{"path":246,"title":247,"description":248,"date":249,"modified":36,"draft":9,"locale":10,"category":11,"image":250,"translationKey":137,"tags":252,"readingTime":49},"\u002Fblog\u002Fwhat-to-put-in-a-bug-report","Bug Report Template (Free Excel, Word & Google Sheets) + Examples","Free bug report template for Excel, Google Sheets and Word, with a good and a bad bug report example and the fields that matter for website bugs.","2023-09-11T14:43:18+00:00",{"src":38,"card":39,"alt":251,"width":41,"height":42},"JavaScript code on a screen, illustrating how to write a bug report for a website",[253,254,255,243],"bug report template","bug report example","how to write a bug report",{"path":257,"title":258,"description":259,"date":260,"modified":36,"draft":9,"locale":10,"category":24,"image":261,"translationKey":111,"tags":263,"readingTime":49},"\u002Fblog\u002F1-way-to-get-annotated-screengrabs-into-asana","Asana Bug Tracking: Free Template and Annotated Screenshots","Asana bug tracking for website projects: a free CSV template, five ways to get annotated screenshots into tasks, and automatic tasks from client feedback.","2023-09-11T11:56:04+00:00",{"src":38,"card":39,"alt":262,"width":41,"height":42},"Annotated screenshots of a website being turned into Asana tasks",[264,265,266,221],"asana bug tracking","asana bug tracking template","annotated screenshots",{"path":268,"title":269,"description":270,"date":271,"modified":36,"draft":9,"locale":10,"category":11,"image":272,"translationKey":125,"tags":274,"readingTime":279},"\u002Fblog\u002Fspeed-up-qa-testing","Website QA Checklist: 70+ Checks Before Launch (Free Template)","A website QA checklist with 70+ checks by area (forms, links, devices, browsers, speed, SEO, accessibility, WordPress), plus a free Excel and Google Sheets template.","2023-08-19T11:32:36+00:00",{"src":122,"card":123,"alt":273,"width":41,"height":42},"Person running a website QA checklist on a laptop before launch",[275,276,277,278],"website QA checklist","website testing checklist","website qa checklist template excel","wordpress website testing checklist",11,{"path":281,"title":282,"description":283,"date":284,"modified":36,"draft":9,"locale":10,"category":11,"image":285,"translationKey":207,"tags":287,"readingTime":49},"\u002Fblog\u002Fvisual-feedback-faster-bug-testing","What Is Visual Feedback? A Guide for Web Teams","What is visual feedback? Feedback given on the website itself with marked-up screenshots, video or pinned comments. Types, examples and a tool checklist.","2023-08-09T17:41:00+00:00",{"src":69,"card":70,"alt":286,"width":41,"height":42},"Web designer reviewing visual feedback on a website interface",[288,47,266,221],"visual feedback",{"path":290,"title":291,"description":292,"date":293,"modified":36,"draft":9,"locale":10,"category":11,"image":294,"translationKey":88,"tags":296,"readingTime":30},"\u002Fblog\u002Fscreen-grab-annotation-apps","How to Annotate a Screenshot of a Website (Mac, Windows & Online)","How to annotate a screenshot on Mac, Windows, online or in Chrome, how to capture a full web page, and how to mark up website screenshots so developers fix them.","2023-08-02T23:25:13+00:00",{"src":85,"card":86,"alt":295,"width":41,"height":42},"Person at a computer annotating website screenshots for a developer",[297,298,299,300],"annotate screenshot","annotate screenshot mac","annotate screenshot windows","annotate screenshot online",{"id":302,"title":6,"body":303,"category":11,"date":8,"description":7,"draft":9,"extension":1130,"faq":1131,"image":12,"locale":10,"meta":1150,"modified":8,"navigation":497,"path":5,"readingTime":18,"seo":1151,"seoTitle":1152,"stem":1153,"tags":1154,"tldr":1155,"translationKey":12,"__hash__":1156},"blog\u002Fblog\u002Fwebsite-handover-checklist.md",{"type":304,"value":305,"toc":1107},"minimark",[306,310,316,321,324,333,336,340,343,476,479,484,530,534,561,565,598,602,635,639,666,670,697,701,728,732,753,757,778,782,815,822,826,829,892,895,899,902,983,993,997,1000,1027,1031,1034,1037,1055,1063,1066,1074,1078,1081,1104],[307,308,309],"p",{},"A website handover checklist is the list of everything a client should receive when their new site goes live, so that a year later nobody is hunting for the hosting login or discovering that the domain renewed on the agency's card. Many problems after launch aren't bugs at all: an account nobody owns, a license that lapsed, a backup that was never tested. The 43 items below are grouped into ten areas, and the free templates turn them into an Excel tracker and a Word handover document that both sides sign.",[311,312],"template-download",{"files":313,"text":314,"title":315},"Excel|\u002Ftemplates\u002Fwebsite-handover-checklist.xlsx,Word|\u002Ftemplates\u002Fwebsite-handover-document-template.docx","Excel checklist with the 43 items, Responsible and Status dropdowns and an access register (opens in Google Sheets: File > Import), plus a Word handover document with accounts, backups, renewals, support terms and signatures.","Free website handover checklist and document",[317,318,320],"h2",{"id":319},"what-is-a-website-handover","What is a website handover?",[307,322,323],{},"A website handover is the point at which the agency or freelancer who built a site transfers its ownership, access and know-how to the client, so the client can run the site without them. It has three parts: the accounts move into the client's name, the knowledge moves into a document, and the responsibilities for what happens next are written down.",[307,325,326,327,332],{},"It isn't the same as approval. ",[328,329,331],"a",{"href":330},"\u002Fblog\u002Fclient-website-approval\u002F","Client website approval"," confirms the site is right; the handover confirms the client can run it. Approval usually comes first, at the end of the review on staging, and the handover happens at launch or in the days after.",[307,334,335],{},"A handover protects the agency as much as the client. When every account is in the client's name and the support terms are signed, a call about an expired SSL certificate two years later is a quick question, not an argument about who should have renewed it.",[317,337,339],{"id":338},"what-should-a-website-handover-checklist-include","What should a website handover checklist include?",[307,341,342],{},"Ten areas: access and ownership; domain, DNS and email; hosting and environments; code and CMS; backups and security; content and SEO; analytics, tracking and legal; third-party services; training and documentation; and support and warranty. Each one prevents a specific problem that usually shows up months after launch, when nobody remembers how things were set up.",[344,345,346,362],"table",{},[347,348,349],"thead",{},[350,351,352,356,359],"tr",{},[353,354,355],"th",{},"Area",[353,357,358],{},"What the client ends up with",[353,360,361],{},"What happens without it",[363,364,365,377,388,399,410,421,432,443,454,465],"tbody",{},[350,366,367,371,374],{},[368,369,370],"td",{},"Access and ownership",[368,372,373],{},"Every account in their name, with their own login",[368,375,376],{},"Every change depends on you, or the site is stuck when you part ways",[350,378,379,382,385],{},[368,380,381],{},"Domain, DNS and email",[368,383,384],{},"Renewal date, documented DNS, working SSL and email",[368,386,387],{},"The domain lapses, or a DNS change breaks the company's email",[350,389,390,393,396],{},[368,391,392],{},"Hosting and environments",[368,394,395],{},"The hosting account and a list of environments",[368,397,398],{},"The staging copy gets indexed; nobody knows where the site runs",[350,400,401,404,407],{},[368,402,403],{},"Code and CMS",[368,405,406],{},"The source code, a plugin list and the licenses",[368,408,409],{},"An update breaks custom work nobody wrote down",[350,411,412,415,418],{},[368,413,414],{},"Backups and security",[368,416,417],{},"Backups that run and a restore that was tested",[368,419,420],{},"The backup turns out to be empty the day it's needed",[350,422,423,426,429],{},[368,424,425],{},"Content and SEO",[368,427,428],{},"Approved content, redirects, Search Console",[368,430,431],{},"Rankings drop after a redesign and nobody sees the errors",[350,433,434,437,440],{},[368,435,436],{},"Analytics, tracking and legal",[368,438,439],{},"Analytics they own; a cookie banner that matches the tools",[368,441,442],{},"The analytics history leaves with the agency",[350,444,445,448,451],{},[368,446,447],{},"Third-party services",[368,449,450],{},"Payment, CRM and newsletter accounts in their name",[368,452,453],{},"Leads from the forms land in the agency's inbox",[350,455,456,459,462],{},[368,457,458],{},"Training and documentation",[368,460,461],{},"An editing guide and a recorded session",[368,463,464],{},"Every text change becomes a support request",[350,466,467,470,473],{},[368,468,469],{},"Support and warranty",[368,471,472],{},"Written terms: what's covered, until when, how to report",[368,474,475],{},"Every request after launch turns into a discussion",[307,477,478],{},"The checks below are the same ones in the Excel file, where each item also says who usually does it: the agency, the client or both.",[480,481,483],"h3",{"id":482},"_1-access-and-ownership","1. Access and ownership",[485,486,489,500,506,512,518,524],"ul",{"className":487},[488],"contains-task-list",[490,491,494,499],"li",{"className":492},[493],"task-list-item",[495,496],"input",{"disabled":497,"type":498},true,"checkbox"," Domain registrar account in the client's name, with the client's email as the contact",[490,501,503,505],{"className":502},[493],[495,504],{"disabled":497,"type":498}," Hosting or server account owned by the client, or a written hosting agreement if you host the site",[490,507,509,511],{"className":508},[493],[495,510],{"disabled":497,"type":498}," CMS administrator account created for the client, with their own email address",[490,513,515,517],{"className":514},[493],[495,516],{"disabled":497,"type":498}," Agency accounts reduced to what the support plan needs, or removed",[490,519,521,523],{"className":520},[493],[495,522],{"disabled":497,"type":498}," Passwords shared through a password manager, never by email or in the handover document",[490,525,527,529],{"className":526},[493],[495,528],{"disabled":497,"type":498}," Two-factor authentication on the client's own accounts, with the recovery codes kept by the client",[480,531,533],{"id":532},"_2-domain-dns-and-email","2. Domain, DNS and email",[485,535,537,543,549,555],{"className":536},[488],[490,538,540,542],{"className":539},[493],[495,541],{"disabled":497,"type":498}," Domain renewal date and auto-renew setting recorded",[490,544,546,548],{"className":545},[493],[495,547],{"disabled":497,"type":498}," DNS records documented (A, CNAME, MX, TXT), and where they are managed",[490,550,552,554],{"className":551},[493],[495,553],{"disabled":497,"type":498}," SSL certificate working on www and non-www, with the renewal method noted",[490,556,558,560],{"className":557},[493],[495,559],{"disabled":497,"type":498}," Emails sent by the site arrive (SPF, DKIM and DMARC records in place)",[480,562,564],{"id":563},"_3-hosting-and-environments","3. Hosting and environments",[485,566,568,574,580,586,592],{"className":567},[488],[490,569,571,573],{"className":570},[493],[495,572],{"disabled":497,"type":498}," Live, staging and local environments listed with their addresses",[490,575,577,579],{"className":576},[493],[495,578],{"disabled":497,"type":498}," Staging site password-protected and hidden from search engines, or deleted",[490,581,583,585],{"className":582},[493],[495,584],{"disabled":497,"type":498}," Hosting plan, server software and versions recorded",[490,587,589,591],{"className":588},[493],[495,590],{"disabled":497,"type":498}," Scheduled tasks (cron jobs) and server settings documented",[490,593,595,597],{"className":594},[493],[495,596],{"disabled":497,"type":498}," Feedback or testing scripts pointed at the live domain, or removed",[480,599,601],{"id":600},"_4-code-and-cms","4. Code and CMS",[485,603,605,611,617,623,629],{"className":604},[488],[490,606,608,610],{"className":607},[493],[495,609],{"disabled":497,"type":498}," Source code delivered: repository transferred, or an archive handed over",[490,612,614,616],{"className":613},[493],[495,615],{"disabled":497,"type":498}," Theme, plugins and extensions listed with versions and why each one is there",[490,618,620,622],{"className":619},[493],[495,621],{"disabled":497,"type":498}," Premium licenses registered to the client, or a renewal plan agreed",[490,624,626,628],{"className":625},[493],[495,627],{"disabled":497,"type":498}," Custom code and settings that must not be changed are documented",[490,630,632,634],{"className":631},[493],[495,633],{"disabled":497,"type":498}," Debug mode off; test orders, demo content and test users removed",[480,636,638],{"id":637},"_5-backups-and-security","5. Backups and security",[485,640,642,648,654,660],{"className":641},[488],[490,643,645,647],{"className":644},[493],[495,646],{"disabled":497,"type":498}," Automatic backups running, stored away from the server, with the retention period noted",[490,649,651,653],{"className":650},[493],[495,652],{"disabled":497,"type":498}," One restore tested, with the date recorded",[490,655,657,659],{"className":656},[493],[495,658],{"disabled":497,"type":498}," Security settings (firewall, login protection, security plugin) documented",[490,661,663,665],{"className":662},[493],[495,664],{"disabled":497,"type":498}," User accounts reviewed: no shared logins, no unused accounts, the right roles",[480,667,669],{"id":668},"_6-content-and-seo","6. Content and SEO",[485,671,673,679,685,691],{"className":672},[488],[490,674,676,678],{"className":675},[493],[495,677],{"disabled":497,"type":498}," Final content approved: texts, images, prices and legal pages",[490,680,682,684],{"className":681},[493],[495,683],{"disabled":497,"type":498}," Redirects from old URLs in place, if this was a redesign",[490,686,688,690],{"className":687},[493],[495,689],{"disabled":497,"type":498}," Search Console verified on the client's account and the sitemap submitted",[490,692,694,696],{"className":693},[493],[495,695],{"disabled":497,"type":498}," No noindex or \"discourage search engines\" setting left on the live site",[480,698,700],{"id":699},"_7-analytics-tracking-and-legal","7. Analytics, tracking and legal",[485,702,704,710,716,722],{"className":703},[488],[490,705,707,709],{"className":706},[493],[495,708],{"disabled":497,"type":498}," Analytics property owned by the client's account, with the agency added as a user",[490,711,713,715],{"className":712},[493],[495,714],{"disabled":497,"type":498}," Conversion events tested on the live domain",[490,717,719,721],{"className":718},[493],[495,720],{"disabled":497,"type":498}," Cookie banner and privacy policy match the tools installed on the site",[490,723,725,727],{"className":724},[493],[495,726],{"disabled":497,"type":498}," Licenses for fonts, images and stock photos recorded",[480,729,731],{"id":730},"_8-third-party-services","8. Third-party services",[485,733,735,741,747],{"className":734},[488],[490,736,738,740],{"className":737},[493],[495,739],{"disabled":497,"type":498}," Payment, CRM, newsletter, maps and other service accounts in the client's name",[490,742,744,746],{"className":743},[493],[495,745],{"disabled":497,"type":498}," API keys created on agency accounts replaced with the client's own",[490,748,750,752],{"className":749},[493],[495,751],{"disabled":497,"type":498}," Form submissions go to the client's inbox or CRM, not the agency's",[480,754,756],{"id":755},"_9-training-and-documentation","9. Training and documentation",[485,758,760,766,772],{"className":759},[488],[490,761,763,765],{"className":762},[493],[495,764],{"disabled":497,"type":498}," Editing guide delivered: pages, images, menus, blog posts, forms",[490,767,769,771],{"className":768},[493],[495,770],{"disabled":497,"type":498}," Training session held, and recorded if the client agrees",[490,773,775,777],{"className":774},[493],[495,776],{"disabled":497,"type":498}," Handover document completed, signed and stored with the project files",[480,779,781],{"id":780},"_10-support-and-warranty","10. Support and warranty",[485,783,785,791,797,803,809],{"className":784},[488],[490,786,788,790],{"className":787},[493],[495,789],{"disabled":497,"type":498}," Warranty period stated, with its end date",[490,792,794,796],{"className":793},[493],[495,795],{"disabled":497,"type":498}," How to report an issue after launch, and who answers",[490,798,800,802],{"className":799},[493],[495,801],{"disabled":497,"type":498}," What counts as a bug fix and what is a change request, and the rate for changes",[490,804,806,808],{"className":805},[493],[495,807],{"disabled":497,"type":498}," Maintenance plan offered, and accepted or declined in writing",[490,810,812,814],{"className":811},[493],[495,813],{"disabled":497,"type":498}," Open issues listed with an agreed fix date",[307,816,817,818,821],{},"For the technical checks that come before all of this (forms, links, devices, speed), run the ",[328,819,275],{"href":820},"\u002Fblog\u002Fspeed-up-qa-testing\u002F"," on staging first. The handover assumes the site already works.",[317,823,825],{"id":824},"what-goes-in-a-website-handover-document","What goes in a website handover document?",[307,827,828],{},"The handover document is the written record of the site: one file the client keeps, with where each account lives, how the site is built and backed up, what it costs to run and what support comes next. The Word template has these sections:",[485,830,831,838,844,850,856,862,868,874,880,886],{},[490,832,833,837],{},[834,835,836],"strong",{},"Project details:"," live and staging addresses, contacts on both sides, go-live date, handover date and the end of the warranty period.",[490,839,840,843],{},[834,841,842],{},"Accounts and access:"," one row per service (registrar, DNS, hosting, CMS, repository, email sending, analytics, Search Console, tag manager, CDN, backups, payments) with its address, owner, who has admin access and whether two-factor authentication is on.",[490,845,846,849],{},[834,847,848],{},"Technical summary:"," platform and version, theme or framework, server versions, environments, how changes are deployed, scheduled tasks and what must not be changed.",[490,851,852,855],{},[834,853,854],{},"Plugins, extensions and licenses:"," what each one does, who owns the license and when it renews.",[490,857,858,861],{},[834,859,860],{},"Backups:"," what is backed up, how often, where, for how long, the date of the last restore test and how to restore.",[490,863,864,867],{},[834,865,866],{},"Editing the website:"," how to change pages, menus and posts, image sizes, where form submissions go, and a link to the training recording.",[490,869,870,873],{},[834,871,872],{},"Renewals and running costs:"," domain, hosting, paid certificates, premium plugins, fonts and images, with who pays.",[490,875,876,879],{},[834,877,878],{},"Support after launch:"," what the warranty covers and until when, how to report an issue, response time, how bugs and change requests are told apart, and the rate for changes.",[490,881,882,885],{},[834,883,884],{},"Open issues:"," anything unfinished, with who fixes it and by when.",[490,887,888,891],{},[834,889,890],{},"Handover sign-off:"," a short statement and signature blocks for the client and the agency.",[307,893,894],{},"One rule matters more than the rest: no passwords in the document. It gets emailed, printed and forwarded. Record where each account lives and who owns it, and share the credentials through a password manager.",[317,896,898],{"id":897},"who-should-own-the-domain-hosting-and-other-accounts","Who should own the domain, hosting and other accounts?",[307,900,901],{},"The client, wherever the client pays for the site. Accounts registered by the agency \"to save time\" cause trouble long after the handover: renewals charged to the wrong card, a client who can't move hosts, or a domain that lapses because the reminder went to a former employee's inbox. Set accounts up in the client's name from the first week of the project, and invite yourself as a user.",[344,903,904,917],{},[347,905,906],{},[350,907,908,911,914],{},[353,909,910],{},"Account",[353,912,913],{},"Owner after handover",[353,915,916],{},"Agency access after handover",[363,918,919,930,941,952,962,973],{},[350,920,921,924,927],{},[368,922,923],{},"Domain registrar",[368,925,926],{},"Client",[368,928,929],{},"Only if the support plan includes DNS changes",[350,931,932,935,938],{},[368,933,934],{},"Hosting",[368,936,937],{},"Client, or a written hosting agreement",[368,939,940],{},"Its own user, while there is a support plan",[350,942,943,946,949],{},[368,944,945],{},"CMS",[368,947,948],{},"Client administrator",[368,950,951],{},"Its own admin or editor account, removed when support ends",[350,953,954,957,959],{},[368,955,956],{},"Analytics, Search Console, tag manager",[368,958,926],{},[368,960,961],{},"Added as a user",[350,963,964,967,970],{},[368,965,966],{},"Code repository",[368,968,969],{},"Whoever the contract says",[368,971,972],{},"As the support plan needs",[350,974,975,978,980],{},[368,976,977],{},"Payments, CRM, newsletter",[368,979,926],{},[368,981,982],{},"None, or a limited user",[307,984,985,986,992],{},"Hosting client sites yourself is a valid business model. Just write down what the client gets if they leave, so the question never comes up in the middle of a dispute. Google's help on ",[328,987,991],{"href":988,"rel":989},"https:\u002F\u002Fsupport.google.com\u002Fwebmasters\u002Fanswer\u002F7687615",[990],"nofollow","managing Search Console users and owners"," shows the pattern most services follow: the client is the owner, everyone else is added as a user and removed when they no longer need access.",[317,994,996],{"id":995},"how-does-the-website-handover-process-work","How does the website handover process work?",[307,998,999],{},"It runs from kickoff to the end of the warranty period, not just on launch day. The meeting itself is short when the checklist was filled in during the build; it's long and stressful when someone tries to reconstruct three months of setup in an afternoon.",[1001,1002,1003,1006,1009,1012,1015,1018,1021,1024],"ol",{},[490,1004,1005],{},"At kickoff, write in the contract who owns which accounts and the code, how long the warranty lasts and what support costs afterwards.",[490,1007,1008],{},"During the build, create each account in the client's name and add it to the access register the day you set it up.",[490,1010,1011],{},"Before launch, run QA on staging, get the client's approval and agree the go-live date.",[490,1013,1014],{},"On launch day, switch the DNS, re-test the forms on the live domain, check SSL on www and non-www, submit the sitemap and take a backup.",[490,1016,1017],{},"At the handover meeting, go through the document and the CMS with the client, and record the session if they agree.",[490,1019,1020],{},"After the meeting, the client changes the passwords the agency set, and the agency keeps only its own named user.",[490,1022,1023],{},"Both sides sign the handover document, and each keeps a copy.",[490,1025,1026],{},"During the warranty period, collect every issue in one place. When it ends, close the project or move the site to a maintenance plan.",[317,1028,1030],{"id":1029},"how-do-you-handle-client-issues-after-the-handover","How do you handle client issues after the handover?",[307,1032,1033],{},"Agree on one way to report them, give the warranty period an end date and keep bugs apart from new requests. The first weeks after launch are when real visitors and the client's team find what the staging review missed, so the reporting channel matters more then than at any other time.",[307,1035,1036],{},"Bugs in the delivered work are covered by the warranty. A new page, a new feature or \"can we move this section up\" is a change request, quoted and scheduled separately. Saying so in the handover document, before the first request arrives, avoids the awkward conversation later.",[307,1038,1039,1040,1044,1045,1049,1050,1054],{},"The reporting channel is where it usually falls apart: a screenshot in a chat, a voice note, an email that says \"the form on the website isn't working\". A feedback button on the live site fixes that. With ",[328,1041,1043],{"href":1042},"\u002F","GiveFeedback.io",", you add one script to the site's ",[1046,1047,1048],"code",{},"\u003Chead>"," (the ",[328,1051,1053],{"href":1052},"\u002Fdocumentation-tool\u002F","install guides"," cover WordPress, Shopify, Wix, Squarespace, PrestaShop and Google Tag Manager) and a \"Give Feedback\" button appears. The client clicks it, marks up a screenshot of the page with arrows, boxes, text or numbered markers, and sends it without creating an account, from a computer, a phone or a tablet.",[307,1056,1057,1058,1062],{},"Each report arrives with the page URL, the browser and version, the operating system, the screen resolution and a log of the page's console messages, errors and failed requests. You mark reports open, resolved or archived, and you can invite the client by email to a read-only view of the project's feedback, so they see what was fixed during the warranty without asking. Reports can also go straight to the tool your team uses: Jira, Trello, ClickUp, Asana, monday.com, Wrike, Notion, Slack, Discord or email (",[328,1059,1061],{"href":1060},"\u002Fbug-tracker-tool-integrations\u002F","all integrations",").",[1064,1065],"blog-cta",{},[307,1067,1068,1069,1073],{},"If the project was set up on the staging address during the review, change its address to the live domain on launch day; the checklist has a line for it under hosting and environments. The Free plan covers 5 projects and 50 feedback reports; see ",[328,1070,1072],{"href":1071},"\u002Fpricing\u002F","pricing"," for the paid plans.",[317,1075,1077],{"id":1076},"what-are-the-most-common-website-handover-mistakes","What are the most common website handover mistakes?",[307,1079,1080],{},"Nearly all of them come from leaving the handover until launch day. The rest come from treating it as a technical task, when what the client needs is to be able to run the site and to know who to call.",[485,1082,1083,1086,1089,1092,1095,1098,1101],{},[490,1084,1085],{},"Registering the domain or the hosting on the agency's account and becoming the client's renewal reminder for years.",[490,1087,1088],{},"Sending passwords by email, or pasting them into the handover document.",[490,1090,1091],{},"Handing over with half the checklist empty and promising to \"send the rest later\".",[490,1093,1094],{},"Leaving the staging site open and indexable after launch.",[490,1096,1097],{},"Never testing a restore, so nobody knows whether the backups work.",[490,1099,1100],{},"Training only the person who signed the contract, not the people who will edit the site.",[490,1102,1103],{},"No written support terms, so every \"can you just...\" after launch becomes free work or a dispute.",[307,1105,1106],{},"Start the checklist at kickoff and fill it in as you build. On launch day, the handover is then one meeting and two signatures, and the client walks away with a site they own and know how to run.",{"title":1108,"searchDepth":1109,"depth":1109,"links":1110},"",2,[1111,1112,1125,1126,1127,1128,1129],{"id":319,"depth":1109,"text":320},{"id":338,"depth":1109,"text":339,"children":1113},[1114,1116,1117,1118,1119,1120,1121,1122,1123,1124],{"id":482,"depth":1115,"text":483},3,{"id":532,"depth":1115,"text":533},{"id":563,"depth":1115,"text":564},{"id":600,"depth":1115,"text":601},{"id":637,"depth":1115,"text":638},{"id":668,"depth":1115,"text":669},{"id":699,"depth":1115,"text":700},{"id":730,"depth":1115,"text":731},{"id":755,"depth":1115,"text":756},{"id":780,"depth":1115,"text":781},{"id":824,"depth":1109,"text":825},{"id":897,"depth":1109,"text":898},{"id":995,"depth":1109,"text":996},{"id":1029,"depth":1109,"text":1030},{"id":1076,"depth":1109,"text":1077},"md",[1132,1135,1138,1141,1144,1147],{"question":1133,"answer":1134},"What should be included in a website handover?","The accounts the site depends on, in the client's name (domain, hosting, CMS administrator, analytics, Search Console), a technical summary, the list of plugins and licenses with renewal dates, the backup setup with a tested restore, an editing guide or training, and the support terms after launch. Passwords travel through a password manager, never inside the handover document.",{"question":1136,"answer":1137},"Who should own the domain name and hosting, the client or the agency?","The client. Register the domain and the hosting account in the client's name, with their email address and their payment method, and give the agency a user of its own. If the agency hosts the site, put it in a written agreement that says what the client receives if they leave: the files, the database and help moving the domain.",{"question":1139,"answer":1140},"Should an agency hand over the website's source code?","Settle it in the contract before the project starts: who owns the custom code written for the site, and on what terms. Themes, plugins and libraries keep their own licenses either way. If the client owns the code, deliver it at handover as access to the repository or an archive of the files and the database. A lawyer can confirm what applies where you work.",{"question":1142,"answer":1143},"How long should the warranty period after a website handover be?","There's no standard length; it's whatever your contract says. A fixed period after go-live, for example 30 days, during which defects in the delivered work are fixed at no extra cost, is easy to explain. Write down the end date, what it covers (bugs, not new requests) and how the client reports issues during it.",{"question":1145,"answer":1146},"How do you hand over website passwords securely?","Through a password manager, by sharing a vault or single items with the client, or by having the client create the accounts and invite you as a user. Avoid email, chat and documents. After the handover, the client changes any password the agency set, and the agency keeps only its own named user for support.",{"question":1148,"answer":1149},"What is the difference between website sign-off and handover?","Sign-off is the client confirming that the site meets what was agreed. Handover is the agency transferring ownership, access and know-how so the client can run the site without them. Sign-off usually comes first, at the end of the review on staging; the handover follows at launch or soon after, and starts any warranty or maintenance period.",{},{"title":6,"description":7},"Website Handover Checklist + Free Document Template","blog\u002Fwebsite-handover-checklist",[14,15,16,17],"A website handover checklist lists everything a client must receive when their site goes live: every account in their own name (domain, hosting, CMS, analytics), a handover document with the technical details, working backups with a tested restore, licenses and renewal dates, an editing guide or training, and written support terms. Fill it in while you build, go through it in one meeting and have both sides sign it.","9ZuOagegevG3namTiNQH5Aex9-iQeHM5T-uup4Sp1G4",1793276291778]