Key Takeaways
- A URL list is the starting point of a content audit, not the finished result.
- Comparing several URL sources produces a more reliable inventory than relying on one report.
- Each reviewed page should receive a clear next action, such as keep, update, combine, redirect, archive, or remove.
- Traffic matters, but it is only one signal of a page’s value.
- An effective audit ends with assigned priorities, owners, and deadlines.
Table Of Contents
- Why a URL inventory matters
- Where to find website URLs
- How to build a clean inventory
- How to find missing and orphan pages
- How to review content
- Six practical content decisions
- How to prioritize findings
- Common mistakes and review timing
A website can accumulate years of articles, landing pages, product details, help content, downloads, campaign URLs, and pages that no longer appear in the navigation. Learning how to find all pages on a website is important, but discovery alone does not tell a team whether each page is accurate, useful, connected, or worth maintaining.
A content inventory records what exists. A content audit goes further by evaluating purpose, quality, performance, and the action each page needs next. That distinction helps teams avoid a common outcome: a large spreadsheet that documents a problem without creating a practical plan to improve the site.
Why a URL inventory matters
Menus, category pages, and on-site search rarely reveal every public URL. An old landing page may still receive visitors from a bookmark, an email campaign, or an external link even though it is no longer linked from the main site. A complete inventory supports redesigns, migrations, accessibility checks, search reviews, and editorial planning because it gives the team a shared view of what must be considered before changes are made.
For a useful review process, record each page’s purpose rather than treating every URL as interchangeable. A checkout page, policy page, comparison guide, blog post, and support article may require very different measures of success.
Where to find website URLs
No single source provides a perfect picture. A crawler finds pages reachable through internal links, while an XML sitemap lists URLs the site presents for discovery. A CMS export can reveal published, scheduled, draft, or archived content, but it may exclude pages managed by a separate store, help center, or application.
Build your list from several places: a crawl, XML sitemaps, CMS records, analytics landing-page reports, search performance data, server logs where available, and backlink reports. The practical guidance for listing pages and recording their purpose is especially valuable when a site contains many formats and sections.
How to build a clean content inventory
Create one working sheet or database with a row for each meaningful page. Useful fields include:
- URL, page title, content type, and website section
- Canonical URL, HTTP status, and indexability
- Publication date and last meaningful update
- Internal links pointing to the page
- Organic visits, impressions, backlinks, and conversions where relevant
- Content owner, review notes, recommended action, and priority
Clean the list before reviewing content. Normalize protocol, capitalization, and trailing-slash variations. Separate pages from images, feeds, files, tracking URLs, and filter parameters. Group duplicate versions under their canonical destination, flag redirects and errors, and note the source where each URL was found. URLs that appear in only one source deserve closer inspection.
How to find missing and orphan pages
Compare the crawl list with the sitemap, CMS, analytics, search data, and backlink data. A URL found in one of those sources but absent from the internal-link crawl may be an orphan page. It exists, but visitors cannot reach it through the site’s normal link structure.
An orphan page is not automatically a problem. It may be a limited campaign page or a deliberately unlinked resource. Still, it can also reveal a publishing oversight, a weak content pathway, an outdated page that should be retired, or an important page that needs links from a relevant hub or service page.
How to review each page
Review the page as a person would use it, then assess its technical and business context. Ask who the page serves, which question or task it addresses, whether the information remains accurate, and whether it overlaps with another page. Check that headings match the content, links and forms work, media is relevant, and visitors have an appropriate next step.
Use five review categories
- Accuracy: Verify dates, names, prices, policies, claims, screenshots, and contact details.
- Usefulness: Decide whether the page gives enough context and practical guidance for its intended visitor.
- Structure: Check headings, internal links, related content, and the page’s place in the wider journey.
- Performance: Consider visits, impressions, engagement, conversions, and backlinks in context.
- Technical health: Review status codes, canonicals, redirects, index rules, and mobile usability.
Six practical content decisions
Keep, update, or expand
Keep pages that are accurate, relevant, and serving a clear purpose. Update pages with outdated facts, broken links, weak examples, or unclear wording. Expand pages that answer part of a visitor’s question but omit important instructions, evidence, examples, or follow-up answers.
Combine, redirect, or archive, and remove
Combine pages that target the same need or substantially repeat one another, choosing the strongest destination before moving useful material. Redirect or archive pages that have a relevant replacement or a valid historical role. Remove content only after checking its links, traffic, business value, and any replacement path. Content audit work is fundamentally about assessing content against its purpose, not simply counting pages, as the broader definition of a content audit reflects.
How to prioritize audit findings
Use a simple rating for user value, risk, opportunity, and effort. Start with broken, misleading, or high-risk pages. Next, protect pages with strong traffic, links, conversions, or an essential role in a customer journey. Then repair important orphan pages, consolidate overlapping topics, refresh outdated but valuable content, and plan new material only after existing high-priority pages are in good condition.
Do not delete a page solely because it has low traffic. Some pages support narrow but important tasks, receive visitors through email or external links, help prospects make decisions, or provide necessary legal and service information.
Common mistakes and review timing
Common errors include trusting the sitemap as the full inventory, reviewing only blog posts, changing URLs without redirect planning, judging quality by word count, and failing to assign ownership. Test changes after publication, including redirects, internal links, page status, forms, and important user paths.
Use a light recurring process. Check new pages, broken links, and major changes monthly. Review priority content and orphan-page candidates quarterly. Complete a full inventory before a migration, compare old and new URLs after a redesign, and conduct a broader annual review. The goal is not a permanently perfect spreadsheet. It is a smaller, clearer, more accurate, and better-connected website that helps people complete real tasks.
