Blog / Web management /

A maintenance calendar for a Shopify and WordPress portfolio

A website portfolio rarely breaks all at once. One site misses a plugin update, another throws an expired certificate warning and a third has nobody who owns backups. Each issue looks small until someone needs the site to work in a busy week.

A maintenance calendar turns scattered reminders into accountable work. For a portfolio of Shopify and WordPress sites, it should reflect the difference between hosted commerce operations and self-managed site components rather than push one generic checklist everywhere.

Start with an inventory

List each site with its purpose, platform, domain, business owner and technical contact. Record where hosting, DNS, email, analytics and important integrations are managed. Keep passwords and recovery codes out of a shared calendar; use an approved access manager and note where access is controlled.

Capture what’s known about backups and recovery. Shopify and WordPress carry different responsibilities and recovery options, and details vary with apps, hosting and configuration. Confirm the actual process for each site instead of copying assumptions from another environment.

Note dependencies such as payment services, forms, feeds, custom apps, scheduled exports and third-party scripts. Identify which changes could affect revenue, customer data or search visibility. That helps you prioritise maintenance windows and assign the right reviewer.

Choose recurring work by risk

Some tasks need regular review; others should happen when a change creates the need. The calendar can include access reviews, backup verification, domain and certificate checks, update reviews, form testing, analytics validation and content accuracy checks. Set the frequency by the system, vendor guidance and business risk.

For WordPress, review core, theme and plugin changes in a controlled way. Check compatibility, release notes and available backups before applying updates. A version number doesn’t tell you whether a component is safe or needed. Remove extensions only after confirming the site no longer relies on what they do.

For Shopify, include theme and app changes, storefront journeys, checkout-related configuration within your team’s permissions, product data and domain settings. Shopify manages much of the underlying platform, but the merchant still owns decisions about apps, content, access and store configuration.

Make calendar entries actionable

A reminder that says “check site” creates work without saying what good looks like. Name the task, owner, evidence and escalation route. A form review should say which form, what a successful submission looks like and who receives it. A backup check should point to the verified recovery procedure, not ask whether a backup exists.

Separate preparation from execution. A high-impact update may need a staging review, a scheduled window, stakeholder notice and post-change testing. A routine content check may need only an editor and a record of corrections. Don’t burden simple work with a release process nobody follows.

Give recurring tasks an accountable role, not just a name, so they survive staff changes. Keep one person responsible for completion and name a backup for absences.

Connect maintenance to change management

The calendar doesn’t replace a change log. Record significant updates, the reason, the approver, the affected site and the verification result. If a problem appears later, the team can compare it with recent changes instead of relying on memory.

Before a release, decide which journeys to check. Include a representative product or service page, navigation, search, forms and other paths important to that site. Check mobile as well as desktop when the change could affect layout or interaction. Search-critical changes may also need a look at redirects, canonical output, indexation and internal links.

After a change, capture follow-up and update the calendar if the procedure changed. A task that keeps exposing the same gap should lead to a better process, not just another reminder.

Plan for incidents and recovery

A maintenance schedule should make incidents easier to handle. Keep the incident contact list, provider support routes and decision authority where the team can find them. Define how to report an outage and how to talk to affected people.

Test recovery in an agreed, safe environment. A backup is only useful if the team knows what it contains and can restore the required service. For a commerce site, think about the relationship between storefront content and changing business records; restoration choices need the right technical and operational owners.

Don’t promise every incident can be reversed instantly. Record expected dependencies and escalation steps based on the actual provider arrangements. If the recovery procedure has never been exercised, say so and schedule a review.

Review the calendar itself

Every quarter, or when the portfolio changes, check whether tasks are still relevant, owners still have access and evidence is being kept. Retire obsolete reminders. Add new sites and integrations before they become invisible dependencies.

The goal isn’t a crowded calendar. It’s a reliable way to notice risk while there’s still time to respond.

Keep platform responsibilities distinct

A portfolio calendar shouldn’t imply every platform is maintained the same way. Shopify’s managed service and WordPress’s mix of hosting, themes and extensions create different change paths. Put the actual owner beside each task and link to the provider’s current instructions. If a task belongs to an external provider, the calendar should say how the site owner verifies completion rather than pretend to control that work.

Include the business checks technical reminders miss. Confirm pricing, contact details, delivery information and support routes are still accurate. Assign someone who can confirm the operational facts; the technical administrator may not know a policy has changed. When I manage several sites, I want each entry to say what evidence closes it, such as a successful test submission or an approved access review.

As a portfolio grows, group common checks but keep site-specific exceptions visible. One shared template can describe the process while a per-site record captures the provider and owner.

Pick one site in your portfolio. Could a teammate complete its next calendar task without asking you what “check the site” means?