Content audits: a quarterly framework

Most B2B tech content audits are one-off exercises. The marketing team commits to a “full content audit” once every two years, blocks out a fortnight, exports everything from Search Console into a spreadsheet, makes a pass at colour-coding it and then loses interest by row 200. The audit produces a tab in Notion that nobody opens again until the next two-year exercise.

The fix is not a better one-off audit. It is a quarterly rhythm that is small enough to actually finish. Here is the framework we use across our content marketing clients.

Why quarterly beats annual

A quarterly content audit fits inside a normal planning cycle. It runs in the same rhythm as the editorial calendar, the SEO reporting and the sales review. The team does the work in two days, ships decisions, then gets back to publishing.

An annual or biennial audit, by contrast, accumulates so much surface area that the team never finishes. By the time row 400 of the spreadsheet is colour-coded, the colour-coding on row 50 is already out of date. We have watched this happen at three different clients before settling on the quarterly approach.

The other reason is that content rots faster in B2B tech than in other categories. A piece on Microsoft licensing that was right in 2024 is wrong in 2026. A pricing comparison written six months ago is missing the latest entrant. The longer the audit cycle, the more wrong content the site is carrying at any one time.

What the quarterly audit covers

Each quarter, the audit covers one segment of the site. We rotate the segments across the year so that every piece of content is touched at least once every 12 to 18 months.

The split is a default. For a smaller site, the whole content estate might fit into a single quarter. For a larger one, we split each quarter further. The discipline is doing one slice properly, not all of it badly.

The five decisions

For every page in scope, the audit makes one of five decisions. Not 12. Five.

1. Keep. The page is doing its job. No action other than noting the decision.
2. Refresh. The page is fundamentally right but needs new data, links or examples.
3. Rewrite. The page is on the right topic but the structure or angle needs reworking.
4. Merge. The page overlaps with another and the two should be combined into one.
5. Retire. The page is not earning its keep and is not worth saving. 301 redirect to the closest relevant page.

The reason we keep it to five is that “maybe” decisions are how content audits stall. If a page is on the borderline between refresh and rewrite, we default to refresh and review again next quarter. Forcing a decision now beats keeping the page on a watchlist that will be forgotten by Q3.

The data we look at

For each page, we pull a short set of metrics. We resist the temptation to pull more.

• Organic clicks over the last 12 months from Search Console.
• Ranking positions for the page’s primary queries, including the trend over the last six months.
• Engagement metrics from GA4, principally average engagement time and conversion contribution.
• Internal links pointing in, from a crawl using Screaming Frog, Ahrefs or Semrush.
• Backlinks, separately, from Ahrefs or Semrush.
• The most recent update date.

The combination matters. A page with strong rankings but no backlinks might still be doing its job. A page with strong backlinks but no rankings might be carrying authority that a rewrite could redirect. A page with neither is a candidate for retirement.

Our note on the technical SEO audit checklist covers the technical side of the audit, which runs in parallel. We try not to mix the two together because the decisions are different. A technical audit produces engineering tickets. A content audit produces editorial tickets.

The retirement decision is the hardest

The single hardest decision in any content audit is retirement. Marketing teams are reluctant to retire content because somebody wrote it, somebody approved it and removing it feels like an admission of failure. We push back hard on that instinct.

A page that has produced 30 clicks over 18 months, has no backlinks, ranks nowhere meaningful and does not show up in any sales conversation is actively costing the site. It dilutes topical focus, gets indexed as low-quality coverage and crowds out the better pages on the same topic. Retiring it is the right move.

The right way to retire is a 301 redirect to the closest relevant page on the site, not a 404 and not a “page not found” with a soft message. The redirect preserves whatever link equity the page accumulated and sends any residual traffic somewhere useful. If there is no relevant target, the page can be redirected to the relevant pillar or service page.

How to handle a piece that is partly working

The most common case in any audit is the partly-working page. It ranks for one query but not the others it should. It gets reasonable engagement but no conversions. The traffic is up year on year but the rankings are not. These are the pages where the refresh and rewrite decisions live.

The question we ask is whether the structural problem is at the topic level or the page level. If the page is on the wrong topic, no amount of refreshing fixes it and a rewrite, merge or retirement is the right call. If the page is on the right topic but structured badly, a refresh that adds the missing sections, fixes the internal linking and updates the data is usually enough.

For pages that need a refresh, we work to a 60-minute time budget per page. If the page needs more than an hour of attention to be fit again, it is a rewrite, not a refresh. Time-boxing the refresh stops the audit drifting into a rolling rewrite project.

Internal linking as part of the audit

Every audit pass also looks at the internal linking of the segment in scope. The questions:

• Is each pillar still being fed by the right cluster posts.
• Are new posts published since the last audit linked into the existing structure.
• Are there orphan pages with no inbound internal links.
• Are there pages that have accumulated too many inbound links and become a bottleneck.

This work matters more than most teams realise. A small change in internal linking can move rankings several places without any change to the content itself. Our internal linking for tech sites post covers the mechanics, and the pillar page structure post explains how the cluster wiring should be set up in the first place.

Where the audit feeds back into the calendar

The output of every audit is two lists. One is the list of pages to refresh, rewrite, merge or retire. The other is the list of gaps. Topics the team is not covering. Long-tail queries the cluster is missing. Cases where a competitor has a stronger page on a topic the site should own.

Both lists go straight into the next quarter’s editorial calendar. The audit is not a separate activity sitting next to the calendar. It is the input that feeds the calendar. Our note on editorial calendars for tech marketing teams covers how the two pieces fit together.

The role this plays in measurement

A regular audit is also what makes longer-term measurement honest. Without an audit, the team is reporting on a content estate that has been quietly aging for two years. The numbers might look fine in aggregate while the pages doing the lifting are getting older and the new pages are not picking up the slack.

The audit gives the team a quarterly check on whether the programme is compounding or coasting. Our measuring content marketing ROI post and our content marketing service both lean on the audit cadence as part of the reporting rhythm.

If you have a content estate that has been growing for years without ever being properly audited, drop us a line. We are happy to talk through what a first quarterly pass would look like.