Document logins, owners, software versions, backups, content changes, and measurement settings before January. A year-end website maintenance review is a short written record of how the site stands so the next fix starts from facts. The record saves time when themes, plugins, or staff change. It also keeps project work steady when several people touch the same WordPress or Drupal site.
Table of Contents
- What belongs in your site inventory?
- Who holds access and ownership?
- What is your update and backup position?
- What changed on pages and tracking?
- What should January start with?
- Frequently Asked Questions
What belongs in your site inventory?
List the domain, host, plan level, and renewal contact. Add the content system and version, active theme, and active plugins or modules with their versions. Note custom code, key integrations, and where each item lives.
Keep one line per item with its purpose and last change date. For example, note which form tool handles contact requests and which payment tool handles checkout. Short notes beat long prose because you can scan them fast.
- Domain registrar, host, and renewal owner
- System, theme, plugins or modules, and versions
- Custom code location and what it changes
- Forms, checkout, maps, feeds, and other integrations
Who holds access and ownership?
Record who can enter the host, domain account, site admin, and ad accounts. Write the role for each person and remove accounts that staff no longer need. Confirm the business owns the domain and the main accounts, not a former contractor.
Store recovery details in a safe place, such as a team password manager. Note where the store is and who administers it. That step prevents lockouts during holiday cover.
What is your update and backup position?
Write the date of the last core, theme, and plugin or module update. Note any item you held back and why, such as a conflict with checkout or a custom layout. List known errors, failed updates, and fixes you deferred.
Record backup location, frequency, and last test restore. A backup gains value only when you know it restores. Keep the restore steps beside the backup note so January work does not guess.
- Last full backup date, location, and retention span
- Last restore test and result
- Pending updates and reason for delay
- Open defects with page name and symptom
What changed on pages and tracking?
List pages you added, removed, redirected, or rebuilt this year. Note landing pages used for ads, key forms, and front-end changes that affect layout or speed. Include menu, footer, and contact details you edited.
Record how visits, goals, and ad results are measured. Note which pages carry tracking tags, which forms count as goals, and who owns each account. Check that test and live tags do not mix.
What should January start with?
Turn the notes into a short task list with an owner and a date. Put safety work first: access cleanup, held-back updates, backup tests, and broken forms.
Then list content fixes, speed issues, and page changes tied to winter campaigns. Keep the whole file where the team already works. Assign each task an owner and a January date before you close the file.
Frequently Asked Questions
How long should the year-end record be?
One to three pages often suffices. Cover inventory, access, backups, page changes, tracking, and next tasks with brief lines.
Where should the file live?
Keep it with active project notes, beside open tasks and release notes. The team should reach it without asking for a link.
What if several vendors share the site?
Name the owner for each part: hosting, domain, code, content, and ad accounts. Write handoff steps so cover staff can act.




