How to Do a Website Content Audit: Spreadsheet and Scoring
Learn how to do a website content audit with a practical spreadsheet, page-scoring rubric, and clear rules for keeping, rewriting, or removing content.
What should a website content audit help you decide?
A website content audit should give every important URL a decision: keep it, rewrite it, or retire it. The output is a work queue with owners and next steps, not just a spreadsheet of traffic numbers.
Start with one business objective. You might want more qualified demo requests, fewer outdated support articles, or better visibility for product-related searches. That objective determines what counts as useful content.
A pricing page, troubleshooting guide, and blog post do different jobs. Scoring all three by organic traffic alone will produce bad decisions. A low-traffic integration guide may help buyers complete a purchase; a popular article may attract people who will never need your product.
Write your audit objective above the spreadsheet. For example: “Help small-business buyers understand our accounting software and start an appropriate trial.” Then evaluate each page against its intended role.
How do you build a complete content inventory?
Collect URLs from several places rather than relying on a single export.
Your CMS lists published content. Your XML sitemap shows URLs you have submitted for discovery. A website crawler finds pages reachable through links. Google Search Console and your analytics platform can reveal URLs that still receive visits but no longer appear in navigation.
Combine these lists into one inventory and deduplicate exact URLs. Keep redirected URLs in a separate review tab so you can inspect their destinations without scoring them as live content.
Watch for tracking parameters and URL variants. Usually, those belong under the main page URL rather than becoming separate content rows. However, record canonical conflicts or unexpected indexable variants as issues instead of silently discarding them.
Include more than blog posts. Product pages, landing pages, category pages, documentation, comparison pages, and important PDFs can all influence a visitor's decision.
For a large site, inventory everything but review in batches. Start with business-critical pages, pages losing relevant search traffic, and content that contains time-sensitive claims. Sample repetitive page templates initially, but inspect individual URLs before making removal decisions.
What columns should your content audit spreadsheet contain?
Use one row per primary URL. Separate observed facts from editorial judgments so another person can understand why you chose an action.
The following structure is a suggested template, not an industry standard. You can split grouped fields into individual columns when building the sheet.
| Column or column group | What to record | Why it matters |
|---|---|---|
| URL and page title | Primary URL and current title | Identifies the content |
| Page type | Product, article, comparison, support, category | Sets the right expectations |
| Audience and page job | Who it serves and what they should accomplish | Prevents traffic-only judgments |
| Topic and search intent | Main question or task the page addresses | Exposes overlap and mismatches |
| Status and indexability | HTTP status, canonical target, indexing restrictions | Separates content problems from technical ones |
| Last substantive update | Date the information actually changed | Flags potentially stale information |
| Search performance | Clicks, impressions, CTR, and query notes | Shows search demand and visibility |
| Visitor behavior | Entrances, relevant interactions, and exits where useful | Shows how people use the page |
| Business outcome | Trial starts, purchases, qualified inquiries, or task completion | Connects content to its purpose |
| Links and dependencies | Internal links, external links, campaign or support use | Protects pages with hidden value |
| Quality scores | Scores for the rubric below | Makes editorial review consistent |
| Evidence and confidence | Specific observations and data limitations | Makes decisions reviewable |
| Decision and next action | Keep, rewrite, or retire; exact work required | Turns findings into tasks |
| Destination URL | Merge or redirect destination, if applicable | Supports safe consolidation |
| Priority, owner, and dates | Responsible person, deadline, publication and review dates | Keeps the audit moving |
Record the measurement window in the sheet header. Use the same period across comparable pages. For seasonal content, add a comparable prior-year period rather than treating an off-season decline as failure.
Distinguish missing data from zero activity. A blank conversion field might mean tracking is absent; a zero should mean tracking was working and recorded no conversions.
Which evidence should you collect before scoring pages?
Combine performance data with a manual read. Neither is enough on its own.
Search visibility and intent
Use Google Search Console to inspect page-level clicks, impressions, click-through rate, and the queries bringing visitors. Check whether those queries match the page's actual purpose.
High impressions with weak click-through rate are a prompt to investigate, not proof that the title is bad. Position, search-result features, brand familiarity, and query mix can all affect clicks.
A format mismatch may require a larger change. Someone comparing solutions needs different content from someone ready to buy. Use this guide to when a blog post or landing page fits the search if the intended format is unclear.
Visitor behavior and business value
Use your analytics platform to check landing-page activity and relevant key events. Validate tracking before comparing results. A broken signup event can make a useful page look ineffective.
Look beyond direct conversions. Ask sales and support which pages they send to customers. Documentation, security information, and implementation guides can influence decisions without being the final page before a purchase.
Accuracy and usability
Read the page on mobile as well as desktop. Follow its links and attempt its primary task.
Check product details, screenshots, pricing references, claims, examples, and calls to action. Note the exact failure: “Instructions reference a removed settings menu” is actionable; “content feels old” is not.
SiteScoper's free website audit can help flag UX, copy, SEO, and conversion issues on a page. Use those findings as review prompts, not as a replacement for your inventory or first-party performance data.
How do you score content consistently?
Use a small rubric that makes disagreements visible. The proposed scale below assigns each dimension 0, 1, or 2 points, for a maximum of 10. These are workflow choices, not research-backed performance thresholds.
| Dimension | 0 points | 1 point | 2 points |
|---|---|---|---|
| Audience and business fit | No clear current purpose | Useful to a secondary audience | Directly supports an important audience task |
| Intent satisfaction | Misses the main question or task | Answers it partially | Gives a complete, focused answer |
| Accuracy and evidence | Material errors or unsupported claims | Mostly correct, with gaps | Current, verifiable, and appropriately supported |
| Distinct value | Duplicates another page without a reason | Some useful original detail | Provides useful examples, expertise, or functionality |
| Usability and next step | Hard to use or task path is broken | Usable, with friction | Clear structure and an appropriate next step |
Keep performance metrics beside the score, not inside it. Otherwise, strong historical traffic can disguise inaccurate content, while a new page gets penalized before it has had a fair chance to perform.
For each low score, write one observation. “Distinct value: 0 — repeats the setup guide without adding a different use case” is more useful than the score alone.
Calibrate the rubric on a small set of different page types before reviewing the whole site. If several people are auditing, score the same sample independently and discuss disagreements.
A critical factual or safety issue overrides the total. A page with a strong layout and clear audience still needs urgent correction if its instructions are materially wrong.
How do you choose between keep, rewrite, and kill?
Treat the score as a triage aid, not an automatic deletion rule. Combine quality, current purpose, performance, and dependencies.
| Decision | Choose it when | Next action |
|---|---|---|
| Keep | The page has a clear purpose and serves it well | Fix minor issues and assign a review date |
| Rewrite | The purpose is valuable, but the page fails the task | Create a focused brief and usually retain the URL |
| Merge and retire | Several pages serve substantially the same intent | Combine useful material and retire the redundant URLs |
| Remove | The content has no continuing purpose or appropriate replacement | Remove it deliberately and clean up references |
Keep does not mean ignore
A useful page may only need a corrected screenshot, updated example, or clearer next step. Record those changes without turning every audit row into a complete rewrite.
Rewrite the answer, not just the wording
A rewrite brief should identify the audience, missing information, evidence needed, sections to change, and intended outcome. “Refresh for SEO” is not a usable brief.
For example: “Explain which accounting integrations are supported, show the current setup flow, and link to the relevant trial path.” That gives the writer a task with a finish line.
Kill is an editorial decision, not a redirect instruction
Retirement can mean consolidation, deletion, or keeping a page accessible but excluding it from search where appropriate. Decide what users still need before choosing the technical treatment.
Overlapping keywords alone do not justify merging pages. A setup guide and a product page may mention the same feature while answering different questions.
What does a completed audit row look like?
Here is a hypothetical example using the proposed rubric. The scores illustrate decisions; they are not measured results from a real website.
| Page | Score | Evidence | Decision | Specific task |
|---|---|---|---|---|
| Current integration guide | 9/10 | Accurate instructions; support regularly shares it | Keep | Replace one outdated screenshot |
| Product comparison | 5/10 | Relevant queries; obsolete feature table; weak explanation | Rewrite | Verify claims and rebuild the comparison around buyer needs |
| Duplicate setup article | 4/10 | Same task as the main guide; contains one useful example | Merge and retire | Move the example, then redirect to the main guide |
| Ended promotion | 2/10 | Offer expired; no continuing user need identified | Remove | Confirm dependencies, remove the page, and update links |
Notice that the low-traffic guide survives because it performs a useful job. The comparison page gets rewritten because its purpose remains valuable. The duplicate gets consolidated only after its unique material is preserved.
How do you turn the spreadsheet into a safe work queue?
Prioritize urgent inaccuracies first, then business-critical friction, then opportunities with clear evidence. Cosmetic improvements can wait behind a broken explanation of your core product.
Add an effort estimate and confidence level. A well-supported fix that fits into an afternoon is usually easier to ship than a speculative rebuild. Avoid precise-looking priority formulas when the underlying judgments are uncertain.
Before retiring a URL, check internal links, external links, campaign destinations, customer bookmarks where known, and support references. Preserve useful material before removing the source.
Use a permanent redirect when there is a genuine replacement serving substantially the same need. Do not redirect every deleted page to the homepage. If no suitable replacement exists, a proper 404 or 410 response may be appropriate.
After changes, update internal links and the sitemap, test redirect destinations, and check that retained pages remain accessible and indexable as intended. For larger consolidations, use the website redesign and SEO migration checklist to catch technical dependencies.
How do you know whether the audit worked?
Save a baseline before publishing changes. Record the change date and what changed so later results can be interpreted.
Judge each page by its original job. For an informational article, review relevant queries and onward visits to useful resources. For a product page, review qualified inquiries or purchases. For documentation, combine task-completion signals with feedback from support.
Choose a review window that fits the site's traffic and buying cycle. Check technical implementation immediately, but allow enough time to assess search and business outcomes. Compare equivalent periods and note campaign changes or seasonality.
Do not present every improvement after publication as proof of causation. Rankings, demand, traffic sources, and product changes can also affect results.
Finish each review by updating the spreadsheet: result, remaining uncertainty, and next action. The audit becomes useful when it stays connected to published changes and observed outcomes—not when every cell is filled.
Frequently asked questions
- What is the difference between a content inventory and a content audit?
- An inventory records what content exists and where it lives. An audit evaluates whether that content is accurate, useful, and worth maintaining, then assigns an action. The inventory is the input; the decisions and work queue are the output.
- Can I do a website content audit for free?
- Yes. A spreadsheet, CMS export, Google Search Console, and your existing analytics can support a practical audit without buying another tool. The main cost is the time required to read pages, validate evidence, and implement changes.
- Should I delete blog posts that get no traffic?
- Not without checking their purpose, age, discoverability, and dependencies. A post may be new, useful to customers, or suffering from an indexing problem rather than a content problem. Remove it only when you understand what would be lost and whether a better replacement exists.
- How often should I audit website content?
- Base the schedule on how quickly your information changes and how consequential errors would be. Review pricing, product claims, and instructions whenever the underlying details change. Stable reference content can follow a less frequent schedule, with earlier reviews triggered by performance drops or user feedback.
- Should I change the URL when rewriting a page?
- Usually, keep the existing URL if the page still serves the same purpose and the address remains suitable. Changing wording or adding depth does not require a new URL. If the purpose or site structure requires a move, plan the redirect and update internal links.
Audit your site in 60 seconds
SiteScoper turns this into a single, prioritised report. Free to try.