Free 20-point conversion & SEO audit for export stores — Free website audit — claim yours

hello@woo.one Mon–Fri · 9:00–18:00 (UTC+8)

WordPress Maintenance Checklist for Ecommerce Stores (2026 Edition)

A monthly and quarterly WordPress maintenance checklist for WooCommerce stores: updates, backups, restore tests, security, performance, SEO health and documentation.

WordPress maintenance is not a button. It is a short list of routines performed consistently by someone who will notice when something is wrong. Most compromised or broken stores we see were not unlucky — they were unmaintained.

This checklist is the one we run for client stores. Adapt the frequency to your traffic and risk tolerance, but do not skip the restore test.

Weekly

  • Confirm backups completed — files and database, stored off-site. A backup that lives on the same server is not a backup.
  • Check uptime and SSL — review monitoring alerts, certificate expiry and any downtime incidents.
  • Review plugin update queue — note security releases; schedule them for the staging window rather than clicking “update all” on a Friday.
  • Scan for malware and file changes — automated scanning plus a quick look at modified core files.
  • Check checkout health — place a test order, or review recent orders for failures and payment errors.
  • Review error logs — PHP fatal errors, database errors and 404 spikes.

Monthly

Updates

  1. Run core, theme and plugin updates on staging first.
  2. Test the homepage, a category, a product page, cart, checkout and account login.
  3. Deploy to production during a low-traffic window.
  4. Re-test the same paths and monitor errors for 24 hours.
  5. Record what changed and any rollback performed.

Backups and recovery

  • Verify the latest backup can be restored to a staging environment. Actually do it.
  • Confirm retention policy and off-site storage location.
  • Check that database size growth is not caused by expired transients or runaway logs.

Security

  • Review administrator and editor accounts; remove departed staff immediately.
  • Enforce strong passwords and two-factor authentication for all privileged users.
  • Check login attempt logs for brute-force patterns.
  • Confirm firewall and rate-limiting rules are active.
  • Review file permissions and disable file editing in production.

Performance

  • Run PageSpeed or WebPageTest on the four revenue templates.
  • Check database bloat: revisions, expired transients, orphaned meta and autoloaded options.
  • Confirm caching is working for guests and excluded correctly for cart and checkout.
  • Review image sizes and any new oversized uploads.

SEO health

  • Crawl the site and review new 404s, redirect chains and canonical conflicts.
  • Check Search Console for coverage errors, manual actions and Core Web Vitals regressions.
  • Validate structured data on a sample of product and article pages.
  • Confirm the sitemap still includes the right URLs and excludes noindexed ones.

Content and conversion

  • Test all forms and verify enquiries or orders arrive.
  • Check that policy pages (returns, shipping, privacy) are current.
  • Review top landing pages for broken links, outdated pricing or missing stock.
  • Check that analytics and conversion events still fire.

Quarterly

  • Plugin audit: list every plugin, its purpose, last update and whether anyone still uses it. Remove abandoned plugins.
  • PHP and MySQL versions: confirm you are on a supported version and plan upgrades before end of life.
  • Access review: hosting, DNS, registrar, payment gateways, analytics and Search Console ownership.
  • Disaster recovery drill: restore a full staging copy from backup and document the time taken.
  • Performance budget review: page weight, requests and third-party scripts versus last quarter.
  • SEO strategy review: category performance, indexation trends and content gaps.
  • Documentation update: architecture, plugin list, custom code, credentials ownership and escalation contacts.

Annually

  • Renew domains, SSL certificates, plugin licences and hosting contracts before expiry.
  • Reassess hosting capacity against traffic and catalogue growth.
  • Review legal pages and consent configuration against current regulations in your markets.
  • Test the full order lifecycle: refunds, cancellations, partial shipments and tax corrections.
  • Plan one meaningful improvement project — speed, checkout or SEO — rather than another redesign.

Signs your maintenance is not working

  • Nobody can name the last successful restore test.
  • Updates are applied directly to production without testing.
  • There are administrator accounts for people who left months ago.
  • The plugin list contains tools nobody can explain.
  • Checkout errors are discovered by customers, not monitoring.
  • The site has no staging environment.

Doing it in-house vs outsourcing

In-house works if you have a developer who understands the stack and has time reserved for maintenance. Otherwise, a care plan is cheaper than an incident. Our plans start at $149 per month and include tested updates, off-site backups, monitoring and a monthly report — see what is included.

If you are inheriting a store with unknown history, start with a technical audit before taking responsibility for it. It is much easier to fix the foundations first than to discover them during an outage.

S

Infrastructure and security engineer at woo.one, based in Foshan, China. Works on WordPress, WooCommerce and OpenCart systems, self-hosted mail, and the operational side of running stores for exporters.

More about the team

No pressure · No sales script

Ready for a store that sells while you sleep?

Send us your current site or product list. You will receive a fixed-scope proposal, a 20-point audit and a realistic timeline within two business days.

Reply within 1 business day NDA on request 100% code ownership
Chat with us
WhatsApp Get a quote