What WordPress Maintenance Actually Includes (2026 Checklist)
If you run a WordPress site, “maintenance” is easy to postpone until something breaks. An update sits unapplied. A backup exists only on the same host as the site. A domain renewal email lands in an inbox nobody checks. None of those failures announce themselves with a countdown on your homepage—they just fail.
Last updated: November 10, 2026. Added where to find each check in wp-admin, how to test a backup restore without touching the live site, and a monthly maintenance log you can copy.
A WordPress maintenance checklist is the list of jobs that keep a site secure, working and recoverable, grouped by how often they need doing. Every day, something should watch uptime, SSL and domain expiry and security alerts, and a person should read those alerts. Every week, back up the site off the host, take a snapshot, update WordPress core, plugins and themes, and test your forms. Monthly, quarterly and yearly checks catch the slower problems: malware, broken links, slow pages, old plugins and admin accounts, backups nobody has tested, and renewals that are about to lapse.
If you run a WordPress site, “maintenance” is easy to postpone until something breaks. An update sits unapplied. A backup exists only on the same host as the site. A domain renewal email lands in an inbox nobody checks. None of those failures announce themselves with a countdown on your homepage—they just fail.
This post is a practical checklist of what WordPress maintenance actually includes in 2026, who should own each task (you or a care plan), and how that maps to Revive Guard plans—Monitor, Guard, and Shield—using what’s on our live pricing page. No fake rankings. No invented install counts. Just the work that keeps a site alive. If you’d rather hand these jobs to a team, see our WordPress maintenance service.
The checklist on one screen
Short version first. Each row links to the full table for that cadence, which explains why each task matters and who usually owns it.
| How often | What to do | Full list |
|---|---|---|
| Daily (automated) | Uptime monitoring, SSL and domain expiry alerts, security alerts, and a person who reads them the same day. Stores, bookings and membership sites also need a daily backup. | Daily checks |
| Weekly | Back up the site off the host, take a snapshot, apply core, plugin and theme updates, then check key pages and forms. | Weekly checks and the safe-update routine |
| Monthly | Read a health report, scan for malware, fix broken links, check page speed, clean up the database, check Site Health and Search Console, and remove plugins you no longer use. | Monthly checks |
| Quarterly | Run a restore drill, do a deeper security review, check your PHP version, audit who has admin access, and spot-check accessibility. | Quarterly checks |
| Yearly | Confirm renewals (domain, hosting, SSL, premium licences), review your recovery plan, and check whether your plan still fits what the site earns. | Yearly checks |
If your site takes orders, bookings or payments, add the extra checks for stores and booking sites.
Not sure where these jobs live in your dashboard? See where to find each check in wp-admin, and copy the monthly maintenance log to record what you did.
What “WordPress maintenance” means (vs hosting)
Hosting keeps the server running. WordPress maintenance is application-layer care: the CMS, themes, plugins, certificates, domain renewal awareness, backups you can actually restore, and someone answering when a check fails.
Your host may offer snapshots or “daily backups.” That helps—until the same failure that takes the site also takes the host’s copy. Maintenance, done properly, assumes the host can fail and still leaves you with an independent recovery path. That’s why Revive Guard stores backups off-host, encrypted, with access limited to the team protecting your site. We built that habit after years of restoration work at Wayback Revive—the parent practice behind Revive Guard (Wayback Revive LLC)—where preventable disasters showed up as emergency recoveries.
If you’re comparing tools vs humans: a maintenance plugin gives you buttons. A care plan transfers responsibility. If you are not sure where that line sits, here is what a WordPress care plan covers and what it usually leaves out. This checklist is written so you can see the difference task by task.
The WordPress maintenance checklist (by cadence)
Use this as an ownership map, from daily checks to the once-a-year jobs that are easiest to forget. Rows marked with plan coverage use only live Revive Guard plan bullets from pricing; rows marked “owner task” stay with you on any plan.
Automate vs escalate. Checks, backups, and alerts should run on their own. Decisions should not: a failed update, a malware hit, or a site that won’t load needs a person to decide between a fix, a rollback, and a restore. As you read each bucket, ask two questions per row: does this run without me, and who acts when it fails?
Daily (and always on)
Daily work should be almost entirely automated. Your job is to make sure someone reads the alerts the same day they fire.
| Task | Why it matters | DIY owner | Revive Guard coverage |
|---|---|---|---|
| Uptime monitoring | Downtime you don’t know about is downtime you can’t fix | You or a monitor tool | All plans — checks every 5 minutes; alert after two failed checks, with a human notified |
| SSL certificate watch | Expired HTTPS breaks trust and SEO signals overnight | You (calendar + hosting panel) | All plans — alerts at 60 / 30 / 7 days |
| Domain expiry watch | Quiet expiry can hand your address to someone else | You (registrar emails) | All plans — same 60 / 30 / 7 day alerts |
| Vulnerability / malware awareness | Unpatched plugins are a common breach path | You (newsletters, scanners) | Guard & Shield — weekly malware scans; Monitor does not include malware scanning |
| Same-day alert triage | An alert nobody reads is the same as no monitoring | You (inbox or phone, every day) | All plans — a human is notified after two failed uptime checks |
| Daily backup for high-change sites (stores, bookings, memberships) | A weekly backup can lose days of orders or sign-ups | You — if your host or a plugin runs it off-host | Shield — daily backups, kept 180 days |
Weekly
| Task | Why it matters | DIY owner | Revive Guard coverage |
|---|---|---|---|
| Core, plugin, and theme updates | Most “hacked site” cleanups we see were missing a fix that already existed | You — with time to test | Guard & Shield — weekly updates |
| Snapshot before every change + rollback path | A routine update that can’t be undone becomes a rebuild | You — if you have a real recovery point | Guard & Shield — fresh snapshot before every change; auto-rollback if something breaks |
| Off-host backup + verify it exists | A backup you can’t restore isn’t a backup | You — preferably off the host | Monitor — weekly off-host backup, kept 30 days · Guard — off-host backups with 90-day retention · Shield — daily backups, kept 180 days |
| Backup verification | “File written” ≠ “site restorable” | You — periodic restore test | All plans that include backups — every backup is verified restorable (live standard) |
| Test forms and email delivery | A contact or booking form can stop sending after an update while the site still loads fine | You — send a test entry and confirm it reaches the inbox, not spam | Owner task |
Monthly
| Task | Why it matters | DIY owner | Revive Guard coverage |
|---|---|---|---|
| Plain-language health report | You need a record of what changed without digging logs | You — if you keep notes | All plans — monthly health report + private portal |
| Broken-link hygiene (where relevant) | Dead links waste leads and frustrate visitors | You or an SEO tool | Guard & Shield — monthly broken-link audit (Guard+) |
| Page speed check | New plugins, images and scripts slowly add weight until pages feel slow on mobile | You — run your key pages through PageSpeed Insights and note the trend | Owner task · one-time speed optimization audit available as an add-on ($99, see pricing) |
| Database cleanup | Old post revisions, spam comments and expired temporary data build up month by month and slow the site down, faster on stores | You — take a backup first, then clear them with a cleanup plugin or WP-CLI and note the database size. Expired temporary data (transients) should clear on its own: since version 4.9, WordPress removes it in a daily scheduled task, so a pile-up usually means scheduled tasks are not running, which Site Health reports as a failed loopback request | Owner task |
| Site Health and Search Console check | WordPress flags critical problems under Tools > Site Health, and Google Search Console shows crawl, indexing and security issues before visitors report them | You — fix anything marked critical, then look for new 404 errors or key pages dropping out of the index | Owner task · Shield — quarterly security + SEO health audits |
| Support for odd breaks | Content quirks, plugin conflicts, “it looks wrong” tickets | You or a freelancer | Guard — 2 human support requests/month · Shield — unlimited priority support · Monitor — monitoring-first; one-time restore available as add-on |
Quarterly (or deeper cadence)
| Task | Why it matters | DIY owner | Revive Guard coverage |
|---|---|---|---|
| Deeper security / health audit | Surface checks miss drift over months | You or an agency sprint | Shield — quarterly security + SEO health audits |
| Plugin prune / unused software | Abandoned plugins enlarge the attack surface | You | Best-effort under Guard/Shield update workflow; Shield audits raise the bar |
| PHP version check | An old PHP branch stops getting security fixes, and newer plugin releases may stop supporting it | You — check the PHP version in your hosting panel and plan upgrades with a snapshot first | Owner task |
| Admin and user access review | Former staff, agencies, and freelancers often keep admin logins long after the work ends | You — remove old users, make sure every admin is a named person (no shared “admin” login), reset shared passwords, turn on two-factor login | Owner task |
| Accessibility spot check | Theme updates, new content and new forms can quietly break keyboard access, contrast or image alt text | You — tab through your key pages and forms using only the keyboard, then run an automated checker such as Lighthouse or WAVE (automated tools catch only part of the problems) | Owner task |
| Content edits / small site changes | Busy owners still need copy and image updates | You | Shield — 2 hours of content edits/month |
| Restore drill | The only proof a backup works is a restore you have actually watched succeed | You — restore a recent backup to a test copy and click through key pages (how to do it safely) | All plans that include backups — every backup is verified restorable (live standard) |
| Account continuity | Who do you call when revenue is on the line? | You | Shield — dedicated account manager |
Annual
Once a year, step back from the routine and check the things that only break on a calendar date or a staff change.
| Task | Why it matters | DIY owner | Revive Guard coverage |
|---|---|---|---|
| Domain, hosting, and SSL renewals | Turn on auto-renew, confirm the card on file, and make sure renewal emails reach an inbox someone reads | You (registrar + host) | All plans — domain and SSL expiry alerts at 60 / 30 / 7 days |
| Premium plugin and theme licences | A lapsed licence quietly stops updates for that plugin or theme | You — renew or replace before expiry | Owner task |
| Recovery plan review | Know where backups live, who restores them, and how much downtime the business can tolerate | You — write it down and share it with whoever covers for you | Guard — priority restore, typically same-day · Shield — written 4-hour emergency restore SLA |
| Stack and plan fit | Sites grow; a brochure site that now takes orders needs more than it did a year ago | You — review plugins, hosting, and what the site now earns | Shield — quarterly security + SEO health audits; not sure which fits now? Start with a free evaluation |
Keep an evidence log. Whatever cadence you run, write down what was done and when: updates applied, backups confirmed, the date of your last restore drill. If something breaks, that log is the first thing anyone helping you will ask for. Revive Guard clients get this as a monthly health report and a private portal showing backups, updates, and alerts.
A monthly maintenance log you can copy
Paste this into a document or spreadsheet and fill in one copy per month. The right-hand column shows the kind of entry each line needs; it is an example, not data from a real site.
| Field | What to write (example) |
|---|---|
| Month and who did the work | March, done by the site owner |
| WordPress version before and after | From Dashboard > Updates, for example “6.x.1 to 6.x.2” |
| Plugins and themes updated | Name and new version of each one |
| Updates held back, and why | “Booking plugin held: changelog mentions a payment change, testing on staging first” |
| Latest off-host backup | Date, where it is stored, and that you opened the file list to check it is complete |
| Last restore test | Date, and whether the copy loaded and logged in (see how to test a restore safely) |
| Site Health | Critical issues found in Tools > Site Health, and what you did about each |
| Forms and email | Test entry sent from each key form, and whether it reached the inbox |
| Uptime and alerts | Any downtime or security alerts this month, and how they were handled |
| Users removed or changed | Old accounts deleted, passwords reset, two-factor turned on |
| Next action | The one thing to fix or check before next month |
Soft checkpoint: If half these rows already feel like homework you won’t finish this month, compare plans on /pricing/ or start with a free evaluation—written findings in 48 hours, no card required.
Where to find each check in wp-admin
Most of the checks above start in your WordPress dashboard. These are the default menu locations in current WordPress; some hosts and security plugins add their own screens on top.
| Check | Where in wp-admin | What to look for |
|---|---|---|
| WordPress core updates | Dashboard > Updates | A new WordPress version, plus the plugin and theme updates waiting for you |
| Plugin updates and unused plugins | Plugins > Installed Plugins | “Update available” notices, and inactive plugins you can delete |
| Unused themes | Appearance > Themes | Themes you no longer use; Site Health recommends removing inactive themes |
| Critical problems | Tools > Site Health (Status tab) | Anything listed under critical issues, such as an outdated PHP version, plugins waiting to update, or a failed loopback request |
| PHP version and database size | Tools > Site Health > Info (Server, and Directories and Sizes) | The PHP version your host runs, and how large the database has grown since last month |
| Admin accounts | Users > All Users, filtered to Administrator | People who no longer work on the site, and shared logins |
| Spam comments | Comments > Spam | Use “Empty Spam” once you have checked nothing real is in there |
| Search engine visibility | Settings > Reading | “Discourage search engines from indexing this site” must be unticked on your live site |
| Indexing and security issues | Outside wp-admin, in Google Search Console | The Pages report for pages dropping out of the index, and the Security issues report |
The locations come from WordPress.org’s Site Health screen guide and the default admin menus.
Before you update anything: a safe-update routine
A broken update is usually easy to undo if you did things in the right order, and painful if you didn’t. If you run updates yourself, use the same routine every time. (If an update has already broken your site, follow what to do when a plugin update breaks WordPress instead.)
- Confirm a recent backup exists off the host. Check the date on it. A backup from last month won’t help if this update breaks today’s orders.
- Take a snapshot right before you start. That gives you a restore point from minutes ago, not days ago.
- Update one thing at a time. Start with security releases, then the rest. If something breaks, you’ll know which update caused it.
- Check what earns money after each update. Load the homepage and your key pages, submit a test form, and test login or checkout if the site has them.
- Roll back if anything looks wrong. Restore the snapshot, hold that update, and check the plugin’s changelog or support forum before trying again.
- Write it down. Note what you updated, when, and anything you held back. That log saves hours when something goes wrong later.
If your host offers a staging copy, testing there first adds another safety net. On Guard and Shield, our team runs this routine for you: weekly core, plugin and theme updates, a fresh snapshot before every change, and automatic rollback if something breaks.
How to test a backup restore safely
A restore test proves your backup works, but done carelessly it can email real customers, take real payments or show a duplicate site to Google. Use a separate copy and switch off anything that talks to the outside world first.
- Restore to a separate copy, never over the live site. Use your host’s staging tool or a password-protected subdomain.
- Hide the copy from search engines. Tick “Discourage search engines from indexing this site” under Settings > Reading on the copy, and keep it behind a password if your host allows.
- Stop outgoing email. Turn off sending in your mail or SMTP plugin on the copy, so order, booking and password emails don’t reach real people.
- Put payments in test mode. Switch payment gateways to their sandbox or test setting, and pause anything that syncs with outside services, such as subscription renewals or CRM and mailing-list connections.
- Click through what matters. Load the homepage and key pages, log in, open a recent post or order, and send a test form to an inbox you control.
- Record it, then clean up. Write the date and result in your maintenance log, then delete the copy or keep it locked.
WordPress.org’s backup guide covers what a full backup has to contain. If a restore test fails, fix the backup before you need it. On every Revive Guard plan that includes backups, each backup is verified restorable.
Why plugins are where the risk sits
Patchstack, a WordPress security company, publishes a yearly report on vulnerabilities across the WordPress ecosystem. Its State of WordPress Security in 2026 report (updated 25 February 2026, covering 2025) found:
- 11,334 new vulnerabilities in the WordPress ecosystem in 2025, a 42% increase on 2024.
- 91% were in plugins and 9% in themes. Only 6 were reported in WordPress core, and those were low priority.
- 46% did not receive a fix from the developer in time for public disclosure.
- For the most heavily exploited vulnerabilities, the weighted median time to first exploit was about 5 hours, and roughly half of high-impact vulnerabilities were exploited within 24 hours.
- Only four of the ten most-attacked vulnerabilities in 2025 were published that year. The rest were older flaws, still being exploited on sites that hadn’t updated.
The same report includes Monarx malware data showing malicious file uploads nearly tripled in November and December 2025, when traffic is high and fewer people are watching. If your site matters over the holidays, the weeks before them are a good time to work through this checklist.
What this means in practice: keep fewer plugins, update promptly, and never rely on updates alone. When almost half of disclosed flaws have no fix yet, monitoring, malware scans and a backup you can restore are what get you through. Patchstack sells security services, so read its framing with that in mind; the counts above are its own published data.
Extra checks if your site takes orders, bookings or payments
A store or booking site can fail while looking fine. The homepage loads, so an uptime monitor stays green, but the payment step throws an error or the confirmation email never arrives. If your site sells or books work, add these to the cadence above:
- After every update session: place a test order from product page to confirmation. Check the cart total, shipping, tax and any coupon, the payment step, and that both you and the customer receive the order email. Use your payment provider’s test mode, or buy a low-value product and refund it.
- Every payment method you offer: card, PayPal, wallet buttons and bank transfer can each break on their own. Test each one in turn, and run at least one test on a phone.
- Weekly: compare orders with a normal week and look for failed or pending payments in your payment provider’s dashboard. A sudden drop in orders is often the only sign that checkout has broken.
- Monthly, on WooCommerce: open WooCommerce > Status. According to WooCommerce’s System Status documentation, the Templates section shows theme files that override WooCommerce templates and notes if they are outdated, the Scheduled Actions tab lists background tasks such as subscription renewals and some customer emails (including any that failed to run), and the Logs tab keeps fatal errors.
- Backups: daily rather than weekly, because every order and sign-up since the last backup is at risk.
On Revive Guard, Guard and Shield take a fresh snapshot before every change and roll back automatically if something breaks, and Shield adds daily backups kept 180 days. Test orders and payment-dashboard checks are owner tasks on every plan; they are not part of the plan list on our pricing page. If you are not sure how much of this you want to hand over, the DIY vs care plan decision table has a column for sites that sell, book work or bring in leads.
What “good” maintenance looks like
A useful maintenance practice has three non-negotiables. They match how we run protection day to day (how it works):
- Restore-tested, off-host backups. Encrypted copies stored independently of your host. On Revive Guard, a backup that isn’t verified restorable doesn’t count. Retention grows with plan level (30 / 90 / 180 days).
- Snapshot before updates, with a rollback path. We take a fresh snapshot before every core, plugin, or theme change. If an update breaks the site, we restore to how it was—usually within minutes—and hold the update until a fix exists. Activity shows up in your portal. (We do not describe this as “staging” unless your stack already has one; the live guarantee is snapshot + rollback.)
- A human when checks fail. Tools can page you. Someone has to decide whether it’s a false positive, a malware incident, or a restore. On Monitor you’re alerted immediately and can buy a one-time restore. Guard prioritizes restore (typically same-day). Shield includes a 4-hour emergency restore SLA in writing.
Visibility matters too. Clients see uptime, backups, updates, and alerts in a private portal—so “taken care of” isn’t a black box.
DIY reality check (short)
You can own this checklist yourself. Many site owners do—until travel, a busy season, or a single missed renewal email. The risk isn’t ignorance; it’s discipline under distraction. Hosting dashboards, registrar portals, plugin changelogs, and backup logs all compete with running the business the site is supposed to support.
If you’re weighing DIY vs paying for care, our DIY vs WordPress care plan guide covers that decision directly, and our WordPress maintenance cost guide explains what different price levels usually buy. For now: be honest about which rows above already slipped last month. That honesty is more useful than any generic “hours per month” estimate.
How Revive Guard approaches maintenance
Revive Guard is the prevention product of Wayback Revive LLC / Wayback Revive. We spent years restoring hacked, expired, and broken sites. The patterns were uncomfortable: domain expiry, host-only backups, and unapplied updates showed up again and again. Care plans exist so those recoveries become rare.
Path for new clients
- Request a free evaluation — about two minutes: URL + biggest concern.
- A real person reviews your site within 48 hours and sends written findings (and an honest plan suggestion) whether or not you join. We check CMS/update status, plugins and known vulnerabilities, hosting context, SSL, domain expiry, and existing backups.
- If you accept, your invite activates the portal. Install a lightweight plugin; monitoring starts; the first backup runs overnight. Onboarding is meant to take under ~10 minutes of your time (how it works).
Capacity note: We accept a maximum of 26 new clients a month—roughly one proper onboarding per working day. That’s a quality constraint, not a countdown timer. At capacity, you join a waitlist and we tell you where you stand.
Plan fit (honest summary)
- Monitor · $49/mo — Know when something’s wrong. Uptime, SSL/domain watch, weekly off-host backup (30 days), monthly report. No WordPress updates or malware scans. Extra sites +$29/mo. One-time restore available for $99 if you need it.
- Guard · $99/mo — Fully managed for business sites. Everything in Monitor, plus weekly WP/plugin/theme updates with snapshot + rollback, weekly malware scans, 90-day backup retention, monthly broken-link audit, 2 support requests/month. Extra sites +$49/mo. Priority restore, typically same-day.
- Shield · $179/mo — Revenue-critical. Everything in Guard, daily backups (180 days), written 4-hour restore SLA, 2 hrs content edits/month, dedicated account manager, unlimited priority support, quarterly security + SEO health audits. Includes up to 3 sites; extra +$59/mo.
No setup fee. Cancel anytime. 7-day money-back when you start. Full matrix: /pricing/.
Wayback Revive alumni get a personal invite path and skip the public queue—we already know the stack. Everyone else starts with the evaluation.
FAQ
What does WordPress maintenance include?
At minimum: uptime, SSL and domain monitoring; regular backups stored off the host; core, plugin and theme updates with a way to roll back; malware scanning; and someone who acts when a check fails. Beyond that come broken-link and speed checks, access reviews, restore drills, and renewals. The tables above list each task by cadence.
What should I check on a WordPress site every month?
Once a month, read your health report or maintenance log, run a malware scan, fix broken links, check the speed of your key pages, clean up the database after taking a backup, deal with anything marked critical in Tools > Site Health, look for new errors in Google Search Console, and remove plugins you no longer use. Restore drills, PHP version checks and admin access reviews are quarterly jobs; the monthly and quarterly tables show who usually owns each one.
What is not part of WordPress maintenance?
Maintenance keeps the site you already have secure, up to date and recoverable. Redesigns, new pages or features, writing content, and SEO or advertising campaigns are usually separate projects with their own quote, even when the same team does them. Small content edits sit in between: some plans include a set number of hours and others bill them separately, so check the plan wording. On Revive Guard, Shield includes 2 hours of content edits a month.
How often should I update WordPress?
Check for updates at least weekly, and apply security releases as soon as you safely can, since Patchstack’s data shows heavily targeted flaws can be attacked within hours of disclosure. Take a snapshot first and update one item at a time. On Guard and Shield, we run updates weekly with a snapshot before every change and automatic rollback.
How often should I back up a WordPress site?
Weekly is a reasonable floor for a site that rarely changes. Stores, booking sites and membership sites usually need daily backups, because a week-old copy can lose orders or sign-ups. Whatever the schedule, keep at least one copy off your host and test a restore every quarter. On Revive Guard, Monitor keeps weekly off-host backups for 30 days, Guard keeps backups for 90 days with point-in-time restore, and Shield runs daily backups kept for 180 days.
Are hosting backups enough?
Usually not as your only copy. Host backups often live on the same infrastructure as the site; the failure that takes one can take both. Independent, encrypted off-host backups mean recovery doesn’t depend on the company that just failed you. That’s why every Revive Guard plan that includes backups stores them separately from your host.
Do you use staging, or snapshot-before-update?
Live protection emphasizes a verified snapshot before every change and automatic rollback if something breaks. That’s the workflow we commit to in product copy. If your host already offers staging and you want it in the loop, say so in the evaluation—we’ll be honest about what fits your stack rather than overselling a lab environment we don’t claim by default.
Can I cancel anytime?
Yes. Month-to-month, no annual lock-in, plus a 7-day money-back guarantee at the start. On cancellation, we’ll hand you your most recent full backup on request.
Why an evaluation instead of instant signup?
Because we take responsibility for sites we protect. A person reviews every website before we commit. You get written findings within 48 hours free—whether or not you join—so the process works in your favor either way.
Which plan do most business sites need?
Many business sites land on Guard (updates, malware scans, longer retention, human support). Brochure or portfolio sites that mainly need eyes on uptime and renewals may be fine on Monitor. Revenue-critical sites that need a written restore clock and a dedicated manager belong on Shield. We’ll say if the cheaper plan is enough after we see your site.
How long does WordPress maintenance take each month?
Published estimates vary a lot. Kinsta’s maintenance routine puts a typical small business site at around 15 to 30 minutes a week and 1 to 2 hours a month, on hosting where backups and monitoring already run automatically. Artimization estimates two to four hours a month for a small site, and Toimi roughly 6 to 8 hours a month once staged updates and restore tests are counted. All three sell hosting or maintenance, so treat these as their estimates, not ours. Stores and membership sites take longer, and a broken update or a malware cleanup comes on top. To put a price on your own hours, see how much time DIY takes, then compare paying by the hour with a monthly plan in our pricing models table.
Where do I find Site Health in WordPress?
In your dashboard under Tools > Site Health. The Status tab lists critical issues and recommended improvements; the Info tab shows your WordPress and PHP versions, database size and server details. Fix anything marked critical first. The wp-admin locations table lists where the other monthly checks live.
How do I test a WordPress backup without breaking my live site?
Restore it to a separate staging copy, not over the live site. Before you click around, hide the copy from search engines, stop it sending email, and put payments in test mode. Then load key pages, log in and send a test form. The step-by-step list above covers each part.
Next step
If you want a clear picture of where your site stands—without a sales script—request a free evaluation. Two minutes to submit. Within 48 hours, a real person sends written findings. If you already know you want coverage compared side by side, start at /pricing/ and come back to the evaluation when you’re ready.
Maintenance isn’t a badge. It’s a list of jobs that either get done on schedule or become tomorrow’s emergency. This checklist is the list. Who owns each row is the decision.
For the systems view—watch, back up, update, restore—see WordPress security, updates, backups & uptime for busy owners.
Not sure which side you’re on?
We’ll review your site and send written findings — usually within 48 hours. Free, no setup fee.
Get free evaluation ↗