Website maintenance

AI can help build a website. Who looks after it afterwards?

The website looks ready. Your logo is in place, the service pages sound convincing, and a contact button sits exactly where you’d expect it. With AI helping, you’ve reached this point much faster than you anticipated.

A customer says their enquiry never arrived. Your booking tool asks you to renew a subscription. Someone suggests updating a plugin, but you’re unsure whether that will affect the layout you’ve just approved.

Who handles those jobs?

Before choosing an AI website builder, commissioning an AI-assisted build or accepting a finished site, ask that question. The answer affects your time, your costs and what happens when customers need to reach you.

Building the pages is one part of the job

Used with a clear brief, AI can help draft copy, suggest layouts and generate code. You can explore different headlines without waiting for another meeting, or turn rough notes into a service description that you can edit.

A finished page doesn’t tell you whether its contact form delivers messages reliably. Nor does it establish who owns the domain, where backups are stored, or which person will investigate a payment failure.

Consider a small gardening business. Its new site might need only five pages, a quotation form and photographs of completed work. Once launched, someone still needs to replace the winter opening hours, check enquiries arrive and renew the domain.

For a shop taking orders, the responsibilities extend further: payment tests, delivery settings, stock information and recovery arrangements that account for recent purchases.

Start with what your website actually does. That gives you a sensible maintenance brief, without paying for tasks your business doesn’t need.

Find out what you’ve actually bought

“Built with AI” describes part of the production process. It doesn’t explain the support arrangement.

A hosted website builder may manage its underlying software and infrastructure. You’ll still need to check your content, account access, subscriptions and any connected booking or payment services. Read the plan details: support for the platform may exclude problems inside an external tool.

With a self-hosted WordPress website, responsibility can be divided between the hosting company, the developer, plugin suppliers and you. Some hosting plans include particular updates or backups; others leave those tasks to the website owner.

The agreement should spell out what your host covers and which tasks your business needs to arrange.

A custom website generated with AI brings another question: can someone understand and maintain its code? Before accepting it, establish where the source files live, how changes are released and whether another developer could take over.

None of these arrangements is automatically wrong. What matters is knowing which services you have, which you don’t, and whom to contact when a specific function fails.

Five jobs that continue after launch

1. Checking that customers can contact you

Use your phone, complete the form and follow the message through to the inbox where you normally answer customers. Check the confirmation screen too: does it explain what happens next?

A visible form isn’t proof of delivery. If messages stop arriving, the cause could involve the form, email configuration, filtering or a connected service. Someone needs to investigate the complete route.

Repeat the check after relevant changes. For a booking business, also test the appointment confirmation. For a shop, agree a suitable test purchase process, including how test payments are handled.

2. Updating software and checking the result

On WordPress, core software, themes and plugins need attention. An update can address a fault or security issue, while also changing behaviour that your website depends on.

Decide who will review and apply updates, how they’ll handle urgent issues and what they’ll test afterwards. For bigger changes, a staging site gives you a separate copy to test before touching the live website.

Before a major update, make sure you have a recent backup and know how to restore it.

During a recent round of WordPress updates, we found a site running a version of PHP that its page builder’s new release did not support. We left the existing plugin version active and flagged the PHP upgrade as a separate job. That compatibility check is worth making before anyone clicks Update.

After an automatic update, run a test booking or send an enquiry through the quotation form. Check that the booking completes and that the enquiry reaches the right inbox.

3. Making backups you can restore

“We have backups” needs a follow-up question: has anyone tested a restore?

For a typical WordPress website, a complete recovery needs both its files and database. WordPress’s official backup guidance explains that distinction. Copying photographs and theme files alone won’t preserve everything stored in the database.

Choose backup frequency around the information you could afford to lose. A brochure site changed monthly has different needs from a shop recording orders throughout the day.

Your backup record should show where copies are stored, how long they’re kept and who can retrieve them if you lose access to your hosting account. Write down the recovery steps while the site is working.

4. Keeping the business information accurate

AI can produce confident wording from incomplete instructions. Read every service claim before launch, especially promises about response times, qualifications, coverage and prices.

Whenever your services, prices or business details change, review the relevant pages. Remove services you’ve stopped offering, replace expired promotions and make sure staff details remain correct.

For example, a consultant who no longer offers free introductory calls shouldn’t leave that promise beside the booking button. A visitor may reasonably expect the offer to be honoured.

Give one person responsibility for approving business information. Your developer can make the change, but they can’t know your new terms unless somebody tells them.

5. Protecting access and arranging renewals

Your business should have appropriate control of the domain registration, renewal payments and recovery arrangements. Apply the same scrutiny to hosting, the website administrator account and essential subscriptions.

Use individual accounts where supported, enable multifactor authentication where available and remove access when someone no longer needs it. Store recovery information securely, with a clear arrangement for authorised access.

Write down renewal dates and the person responsible for payment. A website can depend on several separate services, and your maintenance provider may not manage every subscription.

What AI can help with after launch

After launch, AI can help you prepare a monthly checklist, explain an unfamiliar error message, draft revised service copy or summarise a maintenance report for your review.

Give it boundaries. When sharing an error, remove passwords, access tokens and customer details. Treat suggested technical changes as proposals requiring checks, particularly if they affect payments, personal information or access permissions.

A generated fix can sound plausible while overlooking something specific to your site. Ask whoever implements it to explain the change, test the relevant customer journey and confirm how it could be reversed.

Choose support around the work you need

You may be comfortable managing a simple website yourself. That’s a reasonable choice if you understand the tasks, have access to the necessary accounts and can set aside time.

If you can only deal with website maintenance at weekends, consider which problems can reasonably wait. A team photo can usually wait until Saturday. Make a plan for who can respond sooner if checkout fails.

When comparing maintenance providers, ask about the actual scope. Does the plan include backup restoration, functionality checks and help investigating faults? Are content changes extra? What are the response arrangements outside normal working hours?

Distinguish acknowledging a request from resolving it. A reply within an hour doesn’t necessarily mean the fault will be fixed within an hour.

Also ask whether the provider supports your platform and any custom code. Don’t assume that a WordPress care plan covers an application created in a different system.

Your handover checklist

Before calling the project finished, get clear answers to these questions. Keep them somewhere your business can access independently of the person who built the website.

  • Ownership: Who controls the domain, hosting and website accounts?
  • Documentation: Where are the instructions, source files and subscription details?
  • Updates: Who applies changes and checks the affected functions?
  • Backups: What is saved, how often, and who tests recovery?
  • Enquiries: Who checks forms, bookings and payment journeys?
  • Content: Who approves prices, claims and service information?
  • Support: Who receives a fault report, and what happens next?
  • Costs: Which renewals, fixes and changes fall outside the agreed fee?

Vague answers deserve another conversation. You don’t need to become a developer to ask who owns a job, how it’s checked or what it costs.

Make the first month a proper handover

Book a review for a few weeks after launch. By then, you’ll have had time to use the editor, receive enquiries and discover which instructions need explaining.

During the first month, keep a snagging list that separates faults from requests for new features. A contact button leading to the wrong page is a fault; adding a new quotation calculator is additional work. Agreeing that distinction early makes conversations about charges more straightforward.

During the review, open the website on your phone and walk through the tasks customers actually perform. Check the published telephone number, submit the enquiry form and follow any booking link through to its confirmation.

Then ask for a demonstration of the tasks you’ll manage yourself. Changing a price while someone explains the steps is more useful than receiving a folder of instructions you haven’t opened.

The handover should also explain what happens if you decide to change suppliers. Confirm whether the website can be transferred, which licences belong to your business and whether moving away would require rebuilding any features.

If you use a hosted builder, ask which parts of the website you can export. Check whether a new supplier could use the export to recreate the site and what they would have to rebuild.

Finally, assign a cover contact. If the person responsible is away, someone else should know how to report a fault and reach the relevant provider. They don’t need technical expertise; they need the account reference, the contact details and a clear description of what’s failing.

Put these details in your handover record. When a problem happens, you can report it promptly instead of searching emails for the person who arranged everything.

Give the finished website an owner

AI may help you reach launch sooner. Take that benefit, then make a deliberate decision about what happens afterwards.

Choose who handles routine checks, who approves changes and who responds when something stops working. Record the arrangement. Review it when you add a shop, booking service or other feature that changes the website’s responsibilities.

Test your enquiry form today, locate your domain account and find out when your last backup was checked.

Knowing who is responsible for your website could save you hours of frustration when something goes wrong.

Need help deciding who should look after your WordPress website?

Let’s discuss the checks your site needs. Whether AI helped build it or not, the support arrangement should be clear.

Ace Web Studio’s WordPress care plans