Update risk changes with the site
A five-page brochure site with six plugins is not maintained the same way as a WooCommerce store with payment, shipping and inventory extensions. Update frequency and testing are matched to business risk.
WORDPRESS MAINTENANCE / PERTH, WA
Scheduled WordPress care for businesses that need the site to keep taking enquiries, bookings or orders without gambling on unattended updates. We maintain the WordPress layer: updates, backups, restore readiness, security checks, uptime, forms, database health and routine functional testing.
backup -> update -> verify -> reportforms / checkout / SSL checkeduptime + security signals monitoredrestore path tested before it is needed MAINTENANCE IS RISK CONTROL, NOT A PLUGIN UPDATE BUTTON
The maintenance job is not simply to install the newest versions. The job is to make controlled changes, know what changed, verify the customer journey still works and keep a recoverable copy if something fails.
A five-page brochure site with six plugins is not maintained the same way as a WooCommerce store with payment, shipping and inventory extensions. Update frequency and testing are matched to business risk.
We keep off-site copies and include scheduled restore checks by plan. A backup that has never been opened or restored is not a complete recovery strategy.
Forms, call links, booking handoffs and checkout steps are checked on the plans where those actions are business-critical, so a silent failure is less likely to sit unnoticed for weeks.
Updates, issues found, actions taken and next priorities are recorded. That history makes recurring faults easier to diagnose and prevents each support visit from starting from zero.
CONTROLLED CHANGES, NOT BLIND AUTO-UPDATES
Updates are grouped by risk, backed up first and checked after deployment. Security releases can be accelerated; major plugin, theme or WooCommerce changes get a more cautious path.
Minor and security updates are reviewed promptly. Major WordPress releases are assessed against the theme, plugins and PHP environment before they are applied to a business-critical site.
Payment, forms, caching, security, SEO and page-building plugins can affect different parts of the site. Updates are not treated as one identical batch when the dependency risk is different.
Theme updates can alter templates, CSS, JavaScript or builder behaviour. Key page types are checked after changes so an update does not quietly damage navigation, forms or responsive layouts.
WooCommerce and payment or shipping extensions need stronger checks than a normal brochure site. Commerce Care includes checkout-path verification after update cycles.
RECOVERY SHOULD BE BORING
Backup frequency is matched to how quickly the site changes. A brochure site may be safe with daily copies; a busy store needs shorter recovery gaps. The plan also defines retention and when a restore test is performed.
MONITOR THE SIGNALS THAT PRECEDE A CUSTOMER COMPLAINT
Monitoring cannot prevent every incident, but it shortens the time between a failure and someone knowing about it. We watch the WordPress layer for availability, suspicious change and security risk, then separate an alert from a confirmed incident before acting.
Automated checks flag when the site stops responding so downtime does not depend on a customer telling you first.
Core, theme and plugin exposure is reviewed as part of the maintenance cycle, with higher-risk updates prioritised.
Security scans and change signals help surface suspicious files or modified code that deserves investigation.
Certificate and HTTPS problems can block forms, trigger browser warnings or disrupt payment handoffs.
Administrator accounts, obvious abandoned users and access hygiene are reviewed where the plan and access allow it.
Alerts are triaged so the client is contacted about an actual issue or required action, not every automated warning.
MAINTENANCE SHOULD ALSO REMOVE DRAG
Maintenance is not a one-off speed project, but routine care can stop avoidable performance debt from accumulating. We watch for database growth, expired transients, oversized logs, cache problems and update-related regressions.
THE SITE CAN BE ONLINE AND STILL BE BROKEN
An uptime monitor only proves that a URL responded. It does not prove the enquiry arrived, the booking handoff worked or the checkout could complete. Functional checks focus on the business actions that matter.
For a Subiaco consultancy, the critical path may be a consultation form; for an Osborne Park supplier, it may be a quote upload; for a Fremantle hospitality venue, a booking link; for a Cannington or Rockingham retailer, cart and checkout. We document the important path before maintaining it.
Submit agreed contact or quote forms and confirm the expected success state. Email-delivery troubleshooting beyond the site is separated from a WordPress form fault.
Commerce Care verifies cart, checkout and agreed payment handoffs after maintenance cycles without creating unnecessary live orders.
Confirm administrator access remains available after updates and that normal editing workflows have not been blocked by a plugin or security change.
Review agreed key page types after update cycles for obvious mobile or layout regressions affecting calls to action and navigation.
Where GA4 or Tag Manager is in scope, confirm the code is still present after theme or plugin work. Deeper analytics audits are scoped separately.
Business-critical scheduled actions, webhooks or integrations are checked at the level included in the selected plan.
A REPEATABLE MONTHLY OPERATING RHYTHM
Each cycle follows the same controlled sequence so maintenance is inspectable: review risk, create recovery point, apply agreed changes, verify customer paths, record what changed and queue anything that needs a separate development scope.
Review pending updates, uptime/security alerts, backup status and any client-reported issues before changing production.
Risk list + maintenance queueConfirm a current backup exists before the scheduled maintenance window and that the retention policy is healthy.
Known rollback pointApply core, theme and plugin updates according to plan cadence and risk, using staging when the site or update warrants it.
Documented version changesCheck the critical paths included in the plan: forms, key templates, checkout, tracking or other agreed actions.
Post-update verificationComplete the scheduled database, security, uptime and performance checks included in the selected care level.
Health observationsRecord what was completed, what needs attention and what should be quoted separately rather than hiding extra work inside maintenance.
Maintenance report + prioritiesCARE PRICING BASED ON BUSINESS RISK
The monthly plan defines the routine work and the first response when maintenance uncovers a fault. It does not pretend that every hack, hosting failure or custom-code bug can be fixed inside a small care fee. Recovery work outside the included allowance is diagnosed and approved before extra billing.
Published Australian maintenance guidance in 2026 places small-business care broadly around A$200–A$800/month and WooCommerce care around A$500–A$2,500+/month; Perth examples also advertise basic monthly care around A$189. Our guide ladder starts at A$119/month and scales with update, recovery and transaction risk.For brochure and lead-generation sites with a modest plugin stack and no business-critical ecommerce transaction flow.
Monthly maintenance cycle · 30-day notice to cancelFor active service, professional and marketing sites where forms, tracking, uptime and faster maintenance response matter.
Fortnightly risk review + monthly reportingFor WooCommerce, bookings or other transaction-led sites needing tighter backup intervals, checkout checks and priority maintenance handling.
Weekly risk review + priority maintenance pathGuide prices are in AUD. Hosting, domain renewal, premium plugin or security licences, paid backup storage, third-party monitoring costs, malware cleanup, hacked-site forensics, major development work and vendor charges are excluded unless specifically written into the plan. Backup frequency also depends on hosting and tooling access. GST treatment is confirmed in the final proposal.
Additional approved maintenance / support work: A$72/hrA REPORT SHOULD TELL YOU WHAT CHANGED AND WHAT TO DO NEXT
Maintenance creates useful operational data. The report records the work completed, risks found and recurring issues, then separates routine care from improvements that need their own estimate.
Need a One-Off Fix Instead? →See which maintenance cycle ran, whether backups were healthy and which major version changes were intentionally deferred.
Broken forms, checkout anomalies, layout regressions or integration warnings are recorded with the action taken or recommended next step.
If the same plugin, hosting limit or custom-code fault keeps returning, the report makes the pattern visible rather than repeatedly patching the symptom.
Performance, UX or technical changes outside routine care are listed separately so you can prioritise them without losing visibility.
CARE PLAN QUESTIONS BEFORE YOU HAND OVER ACCESS
These answers focus on what a maintenance plan should actually cover, what it does not cover and how often a business WordPress site needs attention.
Our current guide plans are A$119/month for Essential Care, A$359/month for Business Care and A$749/month for Commerce Care. The right tier depends on update risk, transaction volume, backup frequency, critical forms or checkout paths and how much hands-on support the site needs.
A business site should be reviewed on a predictable schedule because WordPress core, themes, plugins, PHP environments and security exposure keep changing after launch. The exact cadence can be monthly, fortnightly or more frequent depending on site risk.
Automatic updates can be useful for low-risk components, but they do not understand whether checkout stopped working, a form stopped sending or a theme change damaged a template. A care process adds backup, change control and post-update verification.
The plan includes a retention and restore-testing schedule. Essential Care targets quarterly restore checks, while Business and Commerce Care target monthly restore tests, subject to the hosting and backup tooling available.
We first use the agreed rollback or restore path and identify the component that caused the fault. Small remediation can use the plan's included troubleshooting allowance; larger plugin, theme or custom-code repairs are scoped before additional work.
Routine security scanning and risk review are included by plan, but confirmed malware cleanup, hacked-site forensics and deep recovery are separate incident work because the effort can range from a short cleanup to a full credential and code compromise.
Yes. We normally start with a takeover health check covering access, versions, plugin/theme condition, backup reality and obvious risk. If the site has severe technical debt, we explain that before placing it under routine care.
Yes. Commerce Care is designed for transactional sites and includes tighter backup targets plus cart and checkout verification after scheduled update cycles. Complex ERP, inventory or payment-gateway incidents may need separate support time.
Not by default. Keeping hosting in the client's name avoids unnecessary lock-in. We can work with suitable existing hosting and recommend a move only when the hosting itself prevents reliable backups, staging, performance or security.
Maintenance is delivered remotely across Perth metro, including Perth CBD, West Perth, Subiaco, Osborne Park, Joondalup, Fremantle, Cannington, Midland, Wanneroo and Rockingham, and can also cover WordPress sites elsewhere in Australia.
START WITH THE SITE HEALTH, NOT A CONTRACT
Send the WordPress site you want kept reliable.
Share the URL, hosting provider, whether the site takes enquiries, bookings or payments, and anything that has been neglected or unstable. We will recommend the smallest care level that matches the operational risk.