Could you edit your own website tomorrow?

The short answer

Before paying for website improvements, establish who controls the domain, where the site is hosted, how the content is edited and who is allowed to publish. Having paid for a website does not tell you which accounts your business controls. Review your actual arrangement with the builder.

1. Find the person who can make a change

Ask who originally built the website and whether they still support it. Was the job a one-time build, or is there an ongoing maintenance agreement? Request the scope of that agreement before assuming edits are included.

• Who should I contact to change a phone number or service description?
• How long does a normal update take?
• Is there a per-edit charge or a monthly allowance?
• Can you introduce us to the person who handles technical changes?

2. Identify the editor and hosting

Ask whether the site uses WordPress, Wix, Squarespace, Webflow or a custom application. The platform affects the editing workflow; it does not by itself establish website quality. Have your provider show you one simple content edit without publishing it.

• Can the business owner edit text, photos and opening hours?
• Who holds the administrator account?
• Who pays for hosting, and what happens if that agreement ends?
• Are booking, payment or customer-portal features connected to the site?

3. Check domain control separately

The domain registration, hosting and website editor may be managed by different companies. Ask your provider to identify the registrar, the account holder and the renewal contact. Confirm that someone authorized by your business can manage renewal and recovery.

• Where is the domain registered?
• Which business-controlled email receives renewal notices?
• Who can change the domain settings if the hosting moves?
• Are recovery methods and multi-factor authentication current?

4. Agree a safe editing route

Use an account invitation with suitable permissions rather than sharing a personal password. Before a change, agree who backs up the site, how to preview the edit and who can restore the previous version if something breaks. For a custom site, ask the developer about a staging or preview environment.

5. Separate a useful edit from ongoing IT support

A service-page update is different from hosting, security updates, backups, email administration or emergency support. Define the responsibility, response time and fee for each service you actually need. If your existing provider is responsive, working with them may be the simplest option.

A message you can send your website provider

“We are reviewing a small update to our service information. Could you confirm the platform, who controls our domain and hosting, how edits are approved, and the cost and timeline for changing one page? Please also explain the preview, backup and rollback process.”

How this fits a visibility pilot

A measurement report cannot fix an access problem. Establish the editing route before agreeing to an intervention date. Once access is clear, measure the starting point, approve one specific change and preserve a record of what was published.