A quarterly SharePoint site health review helps owners keep content accurate, links functional, access appropriate, and site usage aligned with business needs. This practical audit covers the checks to perform, the evidence to record, and the warning signs that should trigger action.
Overview
A SharePoint site can remain technically available while becoming difficult to trust. Pages may contain outdated instructions, document libraries may have unclear ownership, navigation may point to retired resources, and permissions may no longer reflect the team that uses the site. A site health check turns those issues into a repeatable governance process rather than an occasional cleanup exercise.
The review should be proportionate to the site. A small project site may need a short owner-led checklist. A departmental SharePoint intranet or hub-connected site may require input from communications, records management, security, and business representatives. The objective is not to make every site look identical. It is to confirm that each site has a clear purpose, accountable owners, usable content, and controls appropriate to its audience.
Use a simple scorecard for each review. Rate each area as green (healthy or no action required), amber (an issue has an owner and due date), or red (a material risk or urgent correction). Keep the previous scorecard so that changes can be explained over time.
What to track
1. Purpose, ownership, and contacts
Confirm the site title, description, business purpose, audience, and relationship to any associated team, hub, or communication channel. Verify that at least two people understand their site owner responsibilities and that the listed contacts still work in the relevant department. A site without a reachable owner is a governance gap, even if its pages appear current.
Record the last review date, the next scheduled review, the content approver where one is required, and the escalation contact for access or security concerns. If the site was created for a temporary project, check whether it should be archived, retained, or closed.
2. Content freshness and accuracy
Review the home page, high-traffic pages, news posts, guidance pages, forms, and key documents. Look for expired dates, references to former teams or systems, obsolete screenshots, duplicate instructions, and documents that no longer match current processes. “Recently modified” is not the same as “still accurate,” so ask a subject-matter owner to confirm content that affects policy, safety, finance, legal obligations, or customer service.
Use a content review sheet with these fields: URL or library path, content owner, business purpose, last reviewed date, decision, replacement or archive location, and due date. Possible decisions are keep, revise, merge, archive, or delete. For document libraries, also check whether metadata, views, folders, and content types still support the way users work. The guide to SharePoint document libraries can help structure that assessment.
3. Links, navigation, and findability
Test the main navigation, prominent buttons, quick links, page links, images with links, and links inside frequently used documents. Record broken links separately from links that technically work but lead to an unexpected destination. Check both the page and the user journey: can someone reach the form, policy, or library they need without knowing the site’s internal structure?
Review search terms and common tasks where usage information is available. If users search for a document but repeatedly open an unrelated result, improve titles, descriptions, metadata, synonyms, or page content. Search governance should be connected to the site’s taxonomy rather than handled only through navigation. See the SharePoint search best practices guide for a broader findability review.
Check accessibility as part of navigation and content quality. Keyboard access, headings, link text, image alternatives, color contrast, readable tables, and usable forms affect whether people can complete basic tasks. A separate SharePoint accessibility audit checklist provides a focused companion review.
4. Usage and user experience
Review available site, page, and file activity indicators using the analytics and reporting features available in your tenant. Track directional changes rather than treating a single number as a verdict. Useful questions include: Are priority pages being visited? Are users reaching the intended library or form? Has activity dropped after a redesign? Are there heavily used pages with outdated content?
Low usage may indicate that content is unnecessary, difficult to find, poorly promoted, or intended for a small audience. High usage does not prove that content is correct. Combine usage signals with owner feedback, search observations, support requests, and a short task-based test with representative users.
5. Permissions, sharing, and information risk
Check whether membership and access groups still match the site’s purpose. Look for former employees, inactive project members, broad sharing, unique permissions that are no longer documented, and sensitive content stored in a general-purpose library. Avoid changing permissions during the audit without an agreed owner and rollback plan.
Separate access problems from content problems. A page may be accurate but inaccessible to its intended audience; a document may be widely accessible but inappropriate for that audience. For records, retention, and sensitive information, coordinate with the organization’s Microsoft 365 compliance and security processes rather than relying on a site owner’s judgment alone.
Cadence and checkpoints
A quarterly review is a useful default for active departmental sites, intranets, and sites containing operational guidance. Smaller or lower-risk sites may use a less frequent schedule if the organization’s governance model allows it. High-risk sites, sites with frequent membership changes, and sites supporting major business processes may need monthly checks for ownership, access, and critical links.
Use a three-stage workflow:
- Prepare: export or copy the previous scorecard, gather usage indicators, confirm reviewers, and identify recent organizational or process changes.
- Inspect: test key journeys, review priority content, verify owners and permissions, inspect libraries, and log every issue with a decision and due date.
- Close: assign actions, communicate material changes, record unresolved risks, and schedule the next review.
For a portfolio of sites, use a central register with the site URL, purpose, owner, sensitivity, last review, next review, health rating, open actions, and retirement status. A consistent register makes it easier for an administrator or governance group to identify sites with missing owners, repeated overdue reviews, or growing numbers of exceptions. Site provisioning standards can also help ensure that new sites begin with owners and review dates; compare this process with the SharePoint site provisioning workflow.
How to interpret changes
Do not treat a lower usage figure, a higher document count, or an increased number of search visits as an automatic failure. Interpret the change against events and user tasks. A redesign may temporarily alter navigation patterns. A reorganization may make an owner list inaccurate while leaving content useful. A new collaboration space may move activity away from a traditional site without eliminating the site’s records or reference value.
Prioritize issues using impact and effort. Broken links to critical forms, inaccurate operational guidance, unknown owners, and inappropriate access deserve faster action than cosmetic inconsistencies. If several pages answer the same question differently, resolve the source-of-truth issue before editing every copy. If a library is growing rapidly, investigate version history, retention, storage, and cleanup controls; the SharePoint storage management checklist covers related safeguards.
Look for patterns across quarters. Repeated amber ratings often indicate a process problem, such as unclear publishing responsibility, no content owner network, or site creation without a retirement path. Repeated red ratings may justify consolidation, restricted access, migration, or formal closure. Document the reasoning so a future owner can understand why a decision was made.
When to revisit
Revisit this review at least quarterly for active sites and update the checklist when Microsoft changes analytics terminology, page diagnostics, link-checking capabilities, sharing controls, or reporting locations. The exact labels and navigation in Microsoft 365 can change, so confirm the current tenant experience before publishing step-by-step instructions for a wider audience.
Run an additional review after a leadership change, merger, reorganization, major migration, site redesign, permission incident, compliance assessment, or launch of a new intranet experience. Also review a site before transferring ownership or retiring a related system. These events can invalidate contacts, navigation, permissions, and content assumptions even when the site has not been edited recently.
To make the next review easy, finish each audit with three actions: update the scorecard, assign no-owner issues immediately, and set the next review date in a shared register or approved governance system. Start the next cycle with unresolved items rather than repeating the entire audit from memory. That small discipline turns a SharePoint site health check into an ongoing control for trustworthy content, manageable permissions, and a more dependable Microsoft 365 workplace.
