Who is responsible for your website after launch?

A launch date is not a maintenance plan. Once the project ends, somebody needs to own the renewals, updates, forms and small changes that keep the website useful.

Write down the responsibilities

For WordPress, that includes software and backup arrangements. Hosted platforms take care of some infrastructure, but your content, integrations and customer journeys still need attention. Decide who receives alerts and who has authority to make a repair.

Define the service you are paying for

A care plan should explain its checks, response expectations and available time. “Unlimited support” is not useful if nobody knows what work is included. A clear monthly allowance helps you prioritise improvements and recognise when a separate project is needed.

A practical checklist

• Name the maintenance owner.
• Document account and licence renewals.
• Check key forms and booking routes.
• Agree response times and scope limits.

What to do next

Start with one important page and one clearly defined problem. Keep a record of the original behaviour, make a controlled change and check the result. If you are not comfortable changing the site, the record gives a developer a useful starting point and makes the scope easier to agree.

A CHD website check can add public-page evidence to that conversation. The free result includes a score and up to three findings. The full $29 teardown includes the measured findings, practical guides, a private report and a PDF. Any repair work is reviewed and quoted before payment.