Website Portfolio Management: A Practical Operating Checklist

Manage the operating system behind the websites

A portfolio becomes difficult to manage when decisions live in separate inboxes and nobody has a complete view of the work. A redesign may improve one website, but it does not resolve unclear ownership, missed renewals or an editorial backlog across the rest of the portfolio.

Start with a shared operating checklist. Its purpose is to make the next action visible: what needs attention, who owns it and what evidence will show that the work is complete. The checklist below is a planning framework, not a report of a particular client’s results.

1. Maintain a website inventory

Record each domain, its business purpose, audience, content platform and responsible owner. Keep hosting and domain renewal dates visible. Note where backups are stored and who can authorise a restore. Store passwords in an appropriate credential manager, separately from the working inventory.

Include the relationships between properties. Two websites may use the same hosting account or depend on the same editor. Those shared dependencies matter when planning maintenance and deciding what happens if a person or service is unavailable.

2. Give every property a clear role

Write one sentence explaining why each website exists. A publication, a lead-generation website and a tool platform need different priorities. Avoid treating every site as a container for the same articles. A clear audience and purpose make editorial decisions easier.

For each property, identify its most important visitor journey and the pages supporting it. If those pages are outdated, improving them may be more useful than expanding the publishing calendar. Link useful supporting content to the relevant service, tool or resource.

3. Separate editorial planning from publication

An editorial calendar should show more than a target date. Give each item a brief, reviewer, publication owner and update responsibility. Record any evidence or permissions needed before publishing case studies, statistics or third-party material.

Use a small set of understandable statuses, such as brief, draft, review and ready to publish. Define what each status means. An article in review should have a named reviewer and an expected decision, rather than remaining in an indefinite queue. See our digital publishing approach for related scope.

4. Plan maintenance and recovery together

Assign responsibility for software updates, form checks, backups and restore verification. A backup notification is useful evidence that a job ran; it is not proof that the website can be restored successfully. An isolated restore test belongs in the operational plan.

Keep a change log for significant releases. Record the affected site, what changed and how it was checked. This helps a maintainer distinguish a recent regression from an older issue. Discuss the required support boundaries through website care.

5. Review a small, consistent set of measures

Choose measures appropriate to each property: search impressions, useful visits, successful enquiries or completed editorial work. Keep the date range and source consistent when comparing periods. A third-party traffic estimate should not be presented as equivalent to first-party analytics.

Do not turn every movement into a success story. Record releases and external events alongside the figures, and distinguish a technical check from a business outcome. If measurement is incomplete, make that gap visible before drawing conclusions.

6. Prioritise across the portfolio

Hold a regular review of urgent risks, important improvements and work that can wait. Limit the active workload to what the team can review and maintain. A portfolio with thirty simultaneous initiatives can be harder to improve than one with a short, owned priority list.

A useful starting brief contains the website list, current responsibilities, recurring bottlenecks and your preferred review cycle. Explore website portfolio management or discuss your portfolio to clarify a practical scope.