—UTC,8:01 AM

Oct 28, 2026

IN /

Guides

5 min read

Website maintenance checklist: what are you paying for?

Review what your website care plan covers, who handles faults and what shows the checks happened. A practical checklist for small business owners.

Carbon Black Digital

If your monthly website bill arrives and you couldn't say what was checked, start with the care agreement. Before renewing or cancelling, ask for a list of the work, who handles it and what evidence you'll see.

In a Reddit discussion about website costs, someone joining a small Canadian plumbing business questioned its hosting and maintenance fees. They later said the provider was responsive when asked for help, but the site rarely changed and they didn't understand what the maintenance covered.

The thread can't settle whether that bill was fair. The missing piece is an agreed list of what the fee covers.

Use this website maintenance checklist to agree what your current provider is looking after. It's advice, not a report of work CBD completed for the business in the thread.

Start with the platform you actually have

A WordPress site with plugins needs a different care agreement from a site hosted on Framer. Ask your provider which parts the platform handles and which parts they handle themselves.

For example, Framer says it generates and renews SSL certificates automatically. That is part of its hosting. It doesn't tell you whether the phone number on your contact page is current or who will fix a broken booking link.

On WordPress, updates and recovery need their own explanation. Its backup guidance says a typical site needs both its files and database for a full restore. A folder of images is not the same thing.

Get these responsibilities written down

Account access and renewals

Record who controls the domain registration, website platform and hosting account. Check that the business can recover access and knows where renewal notices go. Ask what access and files you would receive if you changed providers.

Keep passwords out of the report. Record who can recover each account, and how you will keep access when staff or providers change.

Updates and recovery

Ask what gets updated, how often it is checked and who deals with an update that breaks something. WordPress's upgrade instructions call for a backup first and checking that it is usable.

If the plan says "backups included", ask what is covered, how long copies are kept and when a restore was last demonstrated. For a hosted builder, ask the equivalent questions about version history and recovery. Framer says its version-history retention depends on the plan.

Have a technical person demonstrate recovery on a separate test copy where the platform allows it. Don't restore over your live site just to tick the box. External booking or payment records need their own recovery arrangements.

The jobs customers use the site for

Agree a short test route: open a service page on a phone, try its contact button, then check the enquiry form or booking route you rely on.

Use your own contact details and clearly label any test enquiry. Check the test enquiry arrived in the right inbox or system, and that the person responsible can find it. A thank-you message on screen is only one part of that check.

Repeat the relevant test after a form, recipient address or booking connection changes. Set the routine around how often the site changes and what a broken step would interrupt. A checkout needs its own test route.

If the form is already failing, use the website traffic but no enquiries guide to trace the missing step.

Content changes and fault response

Ask what "small edits" means. Does changing a phone number count? What about replacing a service page or adding a gallery? Agree what is included, what needs a quote and how to request it.

Then separate the time to acknowledge a fault from the time to fix it. Check the support hours and who handles an urgent failure. A quick acknowledgement doesn't establish a repair deadline.

A record you can use

Ask for a short care record with a check date, evidence, a named person and the next due date. An unresolved problem needs an action and a person responsible for it.

Keep SEO work on a separate line in the agreement. If you're paying for content or search improvements, ask what was changed and how it will be assessed. A list of software updates doesn't answer that question.

Try the four-field care record

Care-record worksheet with four fields: check and date, evidence of the result, person responsible, and next due date or retest trigger.

Original CBD care-record worksheet. Fill in the actual result for your site.

Use these fields for each recurring check:

  • Check: what was tested, and when?

  • Evidence: what showed it worked, or failed?

  • Person: who handles any follow-up?

  • Next due: when will it be checked again, or what change triggers a retest?

A hypothetical form-test record could say: "Quote form tested; labelled enquiry received in the nominated inbox; office manager to check it; retest after the recipient address changes." Add the actual date and result when you run it. If it fails, record the fault and who is fixing it.

This is an original CBD worksheet, not a client result. Keep it with the invoice so you can ask about a missed check or a fault that is still open.

Decide what you want someone else to own

Fill in the checklist with your current provider before changing the arrangement. A task the platform handles may still need someone to check the business details. A task you can do yourself still needs a place in the diary.

CBD's website design and care offer includes hosting and updates, with small text changes also available. Bring the gaps from your checklist so we can agree the scope for your site. Checks, recovery work and response times need to be agreed explicitly; don't assume every item here is included in a starting price.

Oct 28, 2026

IN /

Guides

5 min read

Website maintenance checklist: what are you paying for?

Review what your website care plan covers, who handles faults and what shows the checks happened. A practical checklist for small business owners.

Carbon Black Digital

If your monthly website bill arrives and you couldn't say what was checked, start with the care agreement. Before renewing or cancelling, ask for a list of the work, who handles it and what evidence you'll see.

In a Reddit discussion about website costs, someone joining a small Canadian plumbing business questioned its hosting and maintenance fees. They later said the provider was responsive when asked for help, but the site rarely changed and they didn't understand what the maintenance covered.

The thread can't settle whether that bill was fair. The missing piece is an agreed list of what the fee covers.

Use this website maintenance checklist to agree what your current provider is looking after. It's advice, not a report of work CBD completed for the business in the thread.

Start with the platform you actually have

A WordPress site with plugins needs a different care agreement from a site hosted on Framer. Ask your provider which parts the platform handles and which parts they handle themselves.

For example, Framer says it generates and renews SSL certificates automatically. That is part of its hosting. It doesn't tell you whether the phone number on your contact page is current or who will fix a broken booking link.

On WordPress, updates and recovery need their own explanation. Its backup guidance says a typical site needs both its files and database for a full restore. A folder of images is not the same thing.

Get these responsibilities written down

Account access and renewals

Record who controls the domain registration, website platform and hosting account. Check that the business can recover access and knows where renewal notices go. Ask what access and files you would receive if you changed providers.

Keep passwords out of the report. Record who can recover each account, and how you will keep access when staff or providers change.

Updates and recovery

Ask what gets updated, how often it is checked and who deals with an update that breaks something. WordPress's upgrade instructions call for a backup first and checking that it is usable.

If the plan says "backups included", ask what is covered, how long copies are kept and when a restore was last demonstrated. For a hosted builder, ask the equivalent questions about version history and recovery. Framer says its version-history retention depends on the plan.

Have a technical person demonstrate recovery on a separate test copy where the platform allows it. Don't restore over your live site just to tick the box. External booking or payment records need their own recovery arrangements.

The jobs customers use the site for

Agree a short test route: open a service page on a phone, try its contact button, then check the enquiry form or booking route you rely on.

Use your own contact details and clearly label any test enquiry. Check the test enquiry arrived in the right inbox or system, and that the person responsible can find it. A thank-you message on screen is only one part of that check.

Repeat the relevant test after a form, recipient address or booking connection changes. Set the routine around how often the site changes and what a broken step would interrupt. A checkout needs its own test route.

If the form is already failing, use the website traffic but no enquiries guide to trace the missing step.

Content changes and fault response

Ask what "small edits" means. Does changing a phone number count? What about replacing a service page or adding a gallery? Agree what is included, what needs a quote and how to request it.

Then separate the time to acknowledge a fault from the time to fix it. Check the support hours and who handles an urgent failure. A quick acknowledgement doesn't establish a repair deadline.

A record you can use

Ask for a short care record with a check date, evidence, a named person and the next due date. An unresolved problem needs an action and a person responsible for it.

Keep SEO work on a separate line in the agreement. If you're paying for content or search improvements, ask what was changed and how it will be assessed. A list of software updates doesn't answer that question.

Try the four-field care record

Care-record worksheet with four fields: check and date, evidence of the result, person responsible, and next due date or retest trigger.

Original CBD care-record worksheet. Fill in the actual result for your site.

Use these fields for each recurring check:

  • Check: what was tested, and when?

  • Evidence: what showed it worked, or failed?

  • Person: who handles any follow-up?

  • Next due: when will it be checked again, or what change triggers a retest?

A hypothetical form-test record could say: "Quote form tested; labelled enquiry received in the nominated inbox; office manager to check it; retest after the recipient address changes." Add the actual date and result when you run it. If it fails, record the fault and who is fixing it.

This is an original CBD worksheet, not a client result. Keep it with the invoice so you can ask about a missed check or a fault that is still open.

Decide what you want someone else to own

Fill in the checklist with your current provider before changing the arrangement. A task the platform handles may still need someone to check the business details. A task you can do yourself still needs a place in the diary.

CBD's website design and care offer includes hosting and updates, with small text changes also available. Bring the gaps from your checklist so we can agree the scope for your site. Checks, recovery work and response times need to be agreed explicitly; don't assume every item here is included in a starting price.

Oct 28, 2026

IN /

Guides

5 min read

Website maintenance checklist: what are you paying for?

Review what your website care plan covers, who handles faults and what shows the checks happened. A practical checklist for small business owners.

Carbon Black Digital

If your monthly website bill arrives and you couldn't say what was checked, start with the care agreement. Before renewing or cancelling, ask for a list of the work, who handles it and what evidence you'll see.

In a Reddit discussion about website costs, someone joining a small Canadian plumbing business questioned its hosting and maintenance fees. They later said the provider was responsive when asked for help, but the site rarely changed and they didn't understand what the maintenance covered.

The thread can't settle whether that bill was fair. The missing piece is an agreed list of what the fee covers.

Use this website maintenance checklist to agree what your current provider is looking after. It's advice, not a report of work CBD completed for the business in the thread.

Start with the platform you actually have

A WordPress site with plugins needs a different care agreement from a site hosted on Framer. Ask your provider which parts the platform handles and which parts they handle themselves.

For example, Framer says it generates and renews SSL certificates automatically. That is part of its hosting. It doesn't tell you whether the phone number on your contact page is current or who will fix a broken booking link.

On WordPress, updates and recovery need their own explanation. Its backup guidance says a typical site needs both its files and database for a full restore. A folder of images is not the same thing.

Get these responsibilities written down

Account access and renewals

Record who controls the domain registration, website platform and hosting account. Check that the business can recover access and knows where renewal notices go. Ask what access and files you would receive if you changed providers.

Keep passwords out of the report. Record who can recover each account, and how you will keep access when staff or providers change.

Updates and recovery

Ask what gets updated, how often it is checked and who deals with an update that breaks something. WordPress's upgrade instructions call for a backup first and checking that it is usable.

If the plan says "backups included", ask what is covered, how long copies are kept and when a restore was last demonstrated. For a hosted builder, ask the equivalent questions about version history and recovery. Framer says its version-history retention depends on the plan.

Have a technical person demonstrate recovery on a separate test copy where the platform allows it. Don't restore over your live site just to tick the box. External booking or payment records need their own recovery arrangements.

The jobs customers use the site for

Agree a short test route: open a service page on a phone, try its contact button, then check the enquiry form or booking route you rely on.

Use your own contact details and clearly label any test enquiry. Check the test enquiry arrived in the right inbox or system, and that the person responsible can find it. A thank-you message on screen is only one part of that check.

Repeat the relevant test after a form, recipient address or booking connection changes. Set the routine around how often the site changes and what a broken step would interrupt. A checkout needs its own test route.

If the form is already failing, use the website traffic but no enquiries guide to trace the missing step.

Content changes and fault response

Ask what "small edits" means. Does changing a phone number count? What about replacing a service page or adding a gallery? Agree what is included, what needs a quote and how to request it.

Then separate the time to acknowledge a fault from the time to fix it. Check the support hours and who handles an urgent failure. A quick acknowledgement doesn't establish a repair deadline.

A record you can use

Ask for a short care record with a check date, evidence, a named person and the next due date. An unresolved problem needs an action and a person responsible for it.

Keep SEO work on a separate line in the agreement. If you're paying for content or search improvements, ask what was changed and how it will be assessed. A list of software updates doesn't answer that question.

Try the four-field care record

Care-record worksheet with four fields: check and date, evidence of the result, person responsible, and next due date or retest trigger.

Original CBD care-record worksheet. Fill in the actual result for your site.

Use these fields for each recurring check:

  • Check: what was tested, and when?

  • Evidence: what showed it worked, or failed?

  • Person: who handles any follow-up?

  • Next due: when will it be checked again, or what change triggers a retest?

A hypothetical form-test record could say: "Quote form tested; labelled enquiry received in the nominated inbox; office manager to check it; retest after the recipient address changes." Add the actual date and result when you run it. If it fails, record the fault and who is fixing it.

This is an original CBD worksheet, not a client result. Keep it with the invoice so you can ask about a missed check or a fault that is still open.

Decide what you want someone else to own

Fill in the checklist with your current provider before changing the arrangement. A task the platform handles may still need someone to check the business details. A task you can do yourself still needs a place in the diary.

CBD's website design and care offer includes hosting and updates, with small text changes also available. Bring the gaps from your checklist so we can agree the scope for your site. Checks, recovery work and response times need to be agreed explicitly; don't assume every item here is included in a starting price.

Oct 28, 2026

IN /

Guides

5 min read

Website maintenance checklist: what are you paying for?

Review what your website care plan covers, who handles faults and what shows the checks happened. A practical checklist for small business owners.

Carbon Black Digital

If your monthly website bill arrives and you couldn't say what was checked, start with the care agreement. Before renewing or cancelling, ask for a list of the work, who handles it and what evidence you'll see.

In a Reddit discussion about website costs, someone joining a small Canadian plumbing business questioned its hosting and maintenance fees. They later said the provider was responsive when asked for help, but the site rarely changed and they didn't understand what the maintenance covered.

The thread can't settle whether that bill was fair. The missing piece is an agreed list of what the fee covers.

Use this website maintenance checklist to agree what your current provider is looking after. It's advice, not a report of work CBD completed for the business in the thread.

Start with the platform you actually have

A WordPress site with plugins needs a different care agreement from a site hosted on Framer. Ask your provider which parts the platform handles and which parts they handle themselves.

For example, Framer says it generates and renews SSL certificates automatically. That is part of its hosting. It doesn't tell you whether the phone number on your contact page is current or who will fix a broken booking link.

On WordPress, updates and recovery need their own explanation. Its backup guidance says a typical site needs both its files and database for a full restore. A folder of images is not the same thing.

Get these responsibilities written down

Account access and renewals

Record who controls the domain registration, website platform and hosting account. Check that the business can recover access and knows where renewal notices go. Ask what access and files you would receive if you changed providers.

Keep passwords out of the report. Record who can recover each account, and how you will keep access when staff or providers change.

Updates and recovery

Ask what gets updated, how often it is checked and who deals with an update that breaks something. WordPress's upgrade instructions call for a backup first and checking that it is usable.

If the plan says "backups included", ask what is covered, how long copies are kept and when a restore was last demonstrated. For a hosted builder, ask the equivalent questions about version history and recovery. Framer says its version-history retention depends on the plan.

Have a technical person demonstrate recovery on a separate test copy where the platform allows it. Don't restore over your live site just to tick the box. External booking or payment records need their own recovery arrangements.

The jobs customers use the site for

Agree a short test route: open a service page on a phone, try its contact button, then check the enquiry form or booking route you rely on.

Use your own contact details and clearly label any test enquiry. Check the test enquiry arrived in the right inbox or system, and that the person responsible can find it. A thank-you message on screen is only one part of that check.

Repeat the relevant test after a form, recipient address or booking connection changes. Set the routine around how often the site changes and what a broken step would interrupt. A checkout needs its own test route.

If the form is already failing, use the website traffic but no enquiries guide to trace the missing step.

Content changes and fault response

Ask what "small edits" means. Does changing a phone number count? What about replacing a service page or adding a gallery? Agree what is included, what needs a quote and how to request it.

Then separate the time to acknowledge a fault from the time to fix it. Check the support hours and who handles an urgent failure. A quick acknowledgement doesn't establish a repair deadline.

A record you can use

Ask for a short care record with a check date, evidence, a named person and the next due date. An unresolved problem needs an action and a person responsible for it.

Keep SEO work on a separate line in the agreement. If you're paying for content or search improvements, ask what was changed and how it will be assessed. A list of software updates doesn't answer that question.

Try the four-field care record

Care-record worksheet with four fields: check and date, evidence of the result, person responsible, and next due date or retest trigger.

Original CBD care-record worksheet. Fill in the actual result for your site.

Use these fields for each recurring check:

  • Check: what was tested, and when?

  • Evidence: what showed it worked, or failed?

  • Person: who handles any follow-up?

  • Next due: when will it be checked again, or what change triggers a retest?

A hypothetical form-test record could say: "Quote form tested; labelled enquiry received in the nominated inbox; office manager to check it; retest after the recipient address changes." Add the actual date and result when you run it. If it fails, record the fault and who is fixing it.

This is an original CBD worksheet, not a client result. Keep it with the invoice so you can ask about a missed check or a fault that is still open.

Decide what you want someone else to own

Fill in the checklist with your current provider before changing the arrangement. A task the platform handles may still need someone to check the business details. A task you can do yourself still needs a place in the diary.

CBD's website design and care offer includes hosting and updates, with small text changes also available. Bring the gaps from your checklist so we can agree the scope for your site. Checks, recovery work and response times need to be agreed explicitly; don't assume every item here is included in a starting price.

(CBD — 11)

Field notes

More articles

More articles

More articles

Plain-English notes on calls, admin
and websites — from real builds.

  • Plain English, no jargon

  • Fixed price before we build

  • You stay in control

  • Built on the Gold Coast

  • Most first builds live in 30 days

VALUES • VISION • BELIEF •VALUES • VISION • BELIEF •
VALUES • VISION • BELIEF •VALUES • VISION • BELIEF •

(CBD — 15)

NEXT STEP

Talk to
Josh

No call centre, no runaround —
you talk to the person who builds it.

No call centre, no runaround —

you talk to the person who builds it.

Let’s find the first
job to automate.
Tell us where the
work gets stuck and
we’ll map a first step.

Let’s find the first job to automate. Tell us where the work gets stuck and we’ll map a first step.

Let’s find the first job to automate. Tell us where the work gets stuck and
we’ll map a first step.

No preparation needed. Call 07 5690 5300
or send a quick message.

No preparation needed. Call 07 5690 5300 or send a quick message.

(CBD — FINAL)

GET IN TOUCH

Let’s talk

Call 07 5690 5300 or email info@carbonblackdigital.com.au.
Gold Coast based, working Australia-wide.

Studio
Studio
Systems
Systems
Work
Work
Insights
Insights
About
About
Contact
Contact

Legal

001.

PRIVACY POLICY

002.

ABN 15 676 829 477

003.

RESOLVE HOLDINGS PTY LTD

©

2026 Resolve Holdings Pty Ltd

·

Gold Coast, QLD

Carbon Black Digital designs brands and websites and builds AI systems
for Australian small businesses.

Carbon Black Digital designs brands and websites and builds AI systems
for Australian small businesses.

(CBD — FINAL)

GET IN TOUCH

Let’s talk

Call 07 5690 5300 or email info@carbonblackdigital.com.au.
Gold Coast based, working Australia-wide.

Studio
Systems
Work
Insights
About
Contact

Legal

001.

PRIVACY POLICY

002.

ABN 15 676 829 477

003.

RESOLVE HOLDINGS PTY LTD

©

2026 Resolve Holdings Pty Ltd

·

Gold Coast, QLD

Carbon Black Digital designs brands and websites and builds AI systems for Australian small businesses.