SEO Content Audit: A Practical Worksheet
An SEO content audit is a decision about each existing page: keep it, improve it, combine it with another page, or remove it carefully. The output should be a short worklist with an owner and a reason, not a spreadsheet full of scores nobody acts on.
You can start with a sitemap, Google Search Console's Performance report, and your website analytics. Search Console supplies impressions, clicks, queries, and average position; analytics can show what visitors do after landing. Neither number, by itself, says whether a page helps a customer.
Build one row per canonical page
Export your live article URLs and add these columns. The template works for a small blog or one section of a larger site:
URL | Primary reader question | Search clicks | Search impressions | Qualified actions | Last fact check | Overlapping page | Decision | Owner | Next review
Use the same date range for every row. For a first pass, compare the most recent 90 complete days with the prior 90; check seasonality before interpreting a decline. A page about a holiday may move because demand changed, not because its copy became worse. Record pages that have never earned impressions too, but check indexing and internal links before judging their content.
Add the query that actually brings people to each URL. A page titled “Best planters for small rooms” may receive impressions for “how to repot a monstera”; that mismatch tells you more than its average position. Search Console groups data by dimensions, and its latest numbers can still be preliminary, so look for a pattern rather than treating a one-day change as proof.
Make the decision with evidence
| Decision | Evidence to look for | Action |
|---|---|---|
| Keep | The answer is accurate, distinct, and serves a relevant reader | Leave the URL alone; set a future review date |
| Refresh | The question still matters, but facts, examples, links, or the opening answer are weak | Edit the existing page and verify its claims |
| Merge | Two pages answer nearly the same question and split the useful material | Choose the stronger destination, combine what is unique, then redirect the retired URL |
| Remove | The topic no longer helps your audience and no suitable replacement exists | Check links and traffic first; then remove and return an appropriate status |
| Expand | The page works but a separate, meaningful reader question remains unanswered | Plan a genuinely distinct new page and link the two where useful |
Do not delete a page merely because it has few clicks. It may support a buyer late in the journey, earn links, or answer a narrow question that matters. Equally, do not keep a stale page because it once had a good month.
Here is an illustrative four-row audit. The URLs and observations are examples, not RankPine customer results:
| Page | Observation | Decision | Next action |
|---|---|---|---|
/blog/daypack-size-guide |
Useful visits, current sizing advice | Keep | Review after next product-range change |
/blog/2022-backpack-care |
Search demand remains, cleaning advice and links are dated | Refresh | Verify material-care claims; update links |
/blog/choosing-a-daypack |
Substantially overlaps the size guide | Merge | Combine distinct advice; redirect old URL |
/blog/packing-for-a-day-hike |
Readers also ask about water planning, not covered here | Expand | Brief a separate water-planning guide |
Handle consolidation carefully
Before merging, compare the queries and links for both pages. Keep the URL whose topic and existing signals best fit the final answer; there is no automatic rule that the older or higher-traffic URL wins. Preserve unique examples, update links that point to the retired page, and test the final destination on mobile.
When a URL really moves, Google recommends a permanent server-side redirect where possible. Its canonical guidance explains how redirects, canonical tags, and sitemap entries signal the preferred URL. A canonical tag is not a substitute for a useful merged page, and a redirect to an unrelated homepage is not a meaningful replacement.
If you remove a page without a replacement, do not silently send every old link to the homepage. Make sure the old URL returns an appropriate response and remove it from navigation and the sitemap. Check important external links before making that call.
Turn the audit into a short production queue
Sort first by business relevance and the size of the problem, then by effort. A page with qualified visitors and outdated product facts may need attention before a higher-impression page with no meaningful conversion path. Give each task one owner, a specific edit, and a check date.
For a small team, the first week could look like this:
- Refresh two pages with clear demand and verifiable factual gaps.
- Merge one overlapping pair and test the redirect.
- Add descriptive internal links from relevant kept pages.
- Brief one new article only where the audit found a distinct unanswered question.
RankPine helps with that last step: researching relevant topics and producing new articles through an editing and publishing workflow. It is not a substitute for checking your existing URLs and deciding which ones to merge or remove; those changes still need to happen in your CMS. If your audit identifies new questions worth covering, see how RankPine plans content and how it publishes articles.
Repeat the audit on a sensible cadence and when products or services change. Check the edited URLs later in Search Console and your analytics, using comparable periods and noting what else changed. A better page can improve a reader's experience immediately; rankings and conversions need separate evidence.