LOGUE MEDIA · WEBSITE CARE & MAINTENANCE
Give the live website a clear care routine.
Keep the routine clear. Know who owns the next action.
Updates, backups and functional checks need an owner after launch.
Agree what is covered, how work is reviewed and where support requests go.
What should a website care arrangement cover?
Website Care & Maintenance covers agreed recurring work on a live WordPress site. It can include software updates, backup arrangements, functional checks and support. The Plan states the frequency, responsibilities and limits. New pages, redesigns and custom features are scoped separately.
Why does a website need care after launch?
WordPress, themes and plugins change over time. The website also depends on hosting, access and external services. A care arrangement identifies who reviews updates and checks the important functions rather than assuming the launch build will stay unchanged.
Are backups enough on their own?
No. The arrangement needs to specify what is backed up, how often, retention, storage and restoration responsibility. Appropriate restore checks also need consideration. A backup exists to support recovery, not just to appear in a report.
Can you care for a site built elsewhere?
We can review it before agreeing a Plan. The review identifies the software, access, hosting and known problems. Significant repairs or unsupported components may need separate work before a recurring care scope is sensible.
Small maintenance gaps can become operational problems.
A successful software update message does not confirm that the enquiry form or checkout still works. A change can affect an important journey without an obvious error on the homepage. The business may discover it only after a customer reports it.
We identify the critical functions and agree the checks relevant to the site. Update work considers staging where appropriate, review and recovery arrangements. The aim is a defined routine rather than a blanket claim that every update is risk free.
Agree a care cycle that ends with a useful record.
A software update is one part of maintenance. Agree the backup, check the affected functions and record what still needs attention.
The cards appear in order. Hover, tap or focus to reveal each card’s detail.
-
Know how the site can be restored.
Confirm who manages backups, where they are stored and which recovery tasks are included. A backup indicator alone does not show whether the agreed recovery process will work.
-
Keep the change under control.
Review the agreed WordPress, theme and plugin updates. Use staging where the arrangement provides for it, and identify licence or compatibility issues before making the live change.
-
Check what customers actually use.
Test the relevant enquiry, booking or buying journey after the work. Record the result and flag issues that fall outside routine care, so the business can approve the next step.
Real content makes the design review useful.
Keep the routine clear. Know who owns the next action.
Care begins with an agreed routine and a clear owner.
Set the care scope around the way your site operates.
Business website care
A service website depends on readable pages, navigation and working enquiries.
- Inventory the WordPress theme, plugins and access.
- Agree backup and recovery responsibilities.
- Schedule the covered update and checking tasks.
- Record faults that require a separate repair quote.
- Provide a clear route for reporting a problem.
Name the critical functions and the review frequency.
WooCommerce care
An online store needs care that reflects trading activity.
- Include agreed product, checkout and order checks.
- Assess extension updates before release.
- Agree how backups support store recovery.
- Define who handles operational store requests.
- Separate new selling features from recurring care.
Separate operational checks from product entry and campaign management.
Care review & handover
Start by reviewing an existing site when software, access or maintenance responsibilities are uncertain.
- Review the site condition before promising coverage.
- Identify unsupported software and existing defects.
- Confirm hosting, backup and account ownership.
- Prioritise repairs needed before a routine starts.
- Recommend a defined care scope or development brief.
Agree unresolved issues before accepting recurring care.
Put the maintenance boundaries where everyone can see them.
Frequency and limits vary with the site. These items should be stated rather than implied by the word support.
| Care item | Detail to confirm |
|---|---|
| Updates | Covered software, frequency and applicable staging approach. |
| Backups | Scope, frequency, retention, storage and restore responsibility. |
| Checks | The agreed forms, pages or store journeys to review. |
| Support | Request channel, included tasks and response arrangements. |
| Extra work | How repairs, new features and emergencies are assessed. |
| Access | Who controls hosting, accounts and required credentials. |
Choose a recurring care Plan with a defined scope.
Website care usually costs 20% of the website build fee.
We confirm the care price after reviewing the site’s software, condition and critical customer journeys. The proposal sets out the Plan period, recurring tasks and support limits.
Hosting, licence renewals, backups and recovery responsibilities belong in the agreed scope. Repairs, migrations and new features may need a separate one-off Package.
Review website build pricing for the underlying website Package, then confirm the care arrangement for your site.
Establish the care routine before the first maintenance cycle.
Four decisions move the build forward. Hover, tap or focus on a stage to open its detail. Once opened, the detail stays available.
Identify WordPress, themes, plugins, hosting and responsible contacts. Record known faults and the forms, payments or booking journeys the business relies on.
Agree routine tasks, backup arrangements and support limits. Identify which repairs, licences and new features need separate approval.
Complete the scheduled work using the agreed backup and staging approach. Check the affected customer journeys and record anything that needs further attention.
Summarise completed updates, backup status and functional checks. Name unresolved issues and who owns the next action before the following cycle.
Website Care & Maintenance on the Central Coast.
Settle the site’s condition and responsibilities before choosing a routine.
Questions to settle before the care Plan begins.
Define the routine, access and support boundaries before accepting recurring maintenance.
Does care include adding new pages?
Only if the Plan expressly includes that work. New service pages, layout redesigns and custom functions are normally development tasks with their own brief. The care scope states any included content changes.
Do you guarantee the site will never fail?
No. Care can reduce identified risks and make recovery responsibilities clearer, but hosting, external services, software and access can still cause problems. The Plan explains the covered work and support route.
Will you fix every existing problem?
An initial review identifies known issues and suitability for care. Significant faults, malware investigation or unsupported software may require a separate repair scope. Existing problems are not automatically included in recurring maintenance.
Who pays for software licences?
The proposal identifies licence ownership and renewal responsibility. Some products or external services have their own recurring costs. These are not assumed included simply because the website is under care.
Choose the next part of the care brief.
Website DesignHover, tap or press EnterWebsite DesignFor this maintenance brief, give several real services a connected website rather than stretching one campaign page beyond its purpose.Explore Website Design →
Website DesignHover, tap or press EntereCommerce Website DevelopmentHover, tap or press EntereCommerce Website DevelopmentFor this maintenance brief, scope the catalogue and buying journey when the website must take orders, accept payment and support fulfilment.Explore eCommerce Website Development →
eCommerce Website DevelopmentHover, tap or press EnterAI WordPress & WooCommerce DevelopmentHover, tap or press EnterAI WordPress & WooCommerce DevelopmentFor this maintenance brief, define an add-on when an agreed business rule or data task needs more than the existing site settings.Explore AI WordPress & WooCommerce Development →
AI WordPress & WooCommerce DevelopmentHover, tap or press EnterTell us how your website is currently maintained.
Share the URL, platform, known issues and who currently handles updates and backups.
Prefer to talk? 0411 199 997 · info@logue.group