Start with a manageable page inventory
A content audit does not have to mean rebuilding your website. Its first purpose is to show what is published and what each page needs. For a small site, begin with a spreadsheet or simple table. Record each page’s title, URL, page type, intended audience, main purpose and person responsible for its content. Include pages that are easy to overlook, such as older announcements, service descriptions, frequently asked questions and downloadable resources.
You can gather URLs from your site’s navigation, content management system and any sitemap you maintain. Check the live site as well: a page may exist in the CMS without being linked from the main menu. If the list is long, audit one group at a time, such as service pages before blog posts. A complete but imperfect inventory is more useful than a detailed spreadsheet that you never finish.
Review each page as a visitor would
Open the published page, not just its editing screen. Ask whether a visitor can tell what the page is for and what to do next. Look for details that may have changed: opening hours, prices, staff names, product availability, processes, contact information and references to past events. Check whether linked pages and downloads still work and whether images and captions still support the message. Mark facts you cannot verify rather than assuming they are correct.
Then consider how usable the page is. Does the heading describe its subject? Is the important information easy to find? Are link labels meaningful outside their surrounding sentence? If a diagram or image carries essential information, is that information also available in text? These checks can reveal pages that are factually accurate but difficult to understand or use. Note specific problems in your inventory so the eventual editor knows what to change.
Give every page a clear decision
Use a small set of decisions: keep, update, combine or remove. Keep a page if it meets a current need and its information is sound. Update it when its purpose remains useful but details, structure or links need work. Combine pages when several cover the same question and leave visitors unsure which version to trust. Consider removing a page when it no longer has a useful purpose and its information does not belong elsewhere.
Do not judge a page only by its age or traffic. An older page may still answer an important question, while a recent one may contain an incorrect instruction. Likewise, a low-traffic page could be essential to a small group of visitors. Record a brief reason for each decision, especially when you plan to combine or remove content. That note will help you explain the change to colleagues and avoid repeating the same discussion later.
Prioritize the fixes that matter most
Once you can see the work, sort it by impact and effort. Correct misleading contact details, broken forms and inaccurate instructions before polishing minor wording. Give early attention to pages people rely on to complete a task, such as finding a service, requesting help or understanding what happens next. A page that is central to the site’s purpose usually deserves a closer review than an isolated post with no continuing role.
Make tasks small enough to assign and finish. “Update the services section” is vague; “confirm the eligibility text on the service page and replace the broken application link” is actionable. Put an owner and a target review period beside each task. If a fact needs confirmation from someone else, identify that person rather than letting the page sit in an undefined ‘needs work’ category.
Publish carefully and make the next audit easier
When editing, check the updated page in context. Confirm that its title, navigation links and calls to action still make sense. If you combine or remove pages, plan where visitors following old links should go; a relevant replacement page is usually more helpful than an error page. After publishing, test key links and any forms affected by the change. Record the decision and completion date in your inventory.
Treat the inventory as a working document, not a one-time report. Assign a review owner to pages with details likely to change and add a reminder to check them at a sensible interval. Encourage editors to note when they publish time-sensitive information or create a page that overlaps with an existing one. The next audit will be faster if each page has a purpose, an owner and a record of its last meaningful review.
