A website maintenance plan is an operating agreement, not just a calendar of plugin updates. Changing it can alter who owns releases, how failures are detected, how evidence is retained, and how quickly the site can be restored. Preserve evidence that lets a future maintainer distinguish the old plan, the authorized change, the live result, and any unresolved risk.
Save the live baseline before changing the plan
Record the canonical domain, hosting and deployment owner, repository or source location, production branch, runtime, content system, certificate status, DNS provider, analytics property, Search Console property, monitoring, backup location, retention, restore owner, and emergency contacts. Do not copy credentials into the maintenance document; link to the approved access process.
Capture a dated list of important URLs and their expected status, canonical, title, structured data, forms, downloads, and redirects. Include desktop and mobile screenshots for the homepage, contact path, a representative content page, and any critical transaction path. Save the current public sitemap and robots file.
Retain technical evidence safely
For a representative page, keep response headers, rendered HTML where appropriate, console errors, and a network trace. Chrome's Network panel guidance documents sanitized HAR export that excludes Cookie, Set-Cookie, and Authorization headers by default. Prefer sanitized evidence and still inspect it before sharing, because URLs, request bodies, and responses may contain sensitive data.
Record the tool version, test conditions, URL, time, cache state, device profile, and network conditions. A performance score without those details is not a reliable before-and-after comparison. Preserve several runs when variability matters.
Document search and index state separately
Search evidence needs two timestamps: what the search engine previously indexed and what the site serves now. Google's URL Inspection documentation distinguishes indexed information from a live URL test and explains that the live test does not cover every condition for appearing in search results.
For priority pages, record the inspected URL, last crawl when available, index status, selected canonical, rendered screenshot or HTML, loaded-resource issues, structured-data result, and live-test result. Do not describe a successful live test as proof that the page is indexed or will rank.
Preserve the old and new operating contracts
Keep the previous schedule and the proposed schedule side by side. For each task, record cadence, trigger, owner, backup owner, evidence produced, pass condition, escalation threshold, rollback, and retention. Cover updates, dependency review, security advisories, content review, accessibility, link checks, forms, backups, restore drills, analytics, search visibility, domain and certificate renewal, privacy, and incident response.
Mark removed checks explicitly with a rationale. If a weekly task becomes monthly, show the observed risk and the compensating monitoring. If automation replaces a manual check, retain the automation's scope, permissions, alert destination, failure signal, and a periodic human verification.
Prove releases and recovery
Run a small acceptance set before and after the change: expected status codes, canonical URLs, private-route denial, form behavior without sending real messages, core navigation, sitemap retrieval, a representative accessibility check, and a backup restore in an isolated location. Keep hashes or release identifiers for the exact tested build and independently confirm the live version.
The final evidence package should contain the authorization, baseline, old and new plans, test record, exceptions, incident contacts, backup and restore evidence, and next review date. Add an evidence index with file names, capture dates, environment, reviewer, and retention date so screenshots and traces do not become anonymous artifacts. Note every unavailable check as unavailable rather than passing it by omission.
The plan is ready when a successor can identify the current owner, reproduce a health check, see what changed, locate the last verified backup, and roll back a failed release without guessing.
Sources
- Network features reference — Chrome for Developers
- URL Inspection tool — Google Search Console Help