EN
Webmail

Content Audits: Finding and Fixing the Pages That Are Quietly Losing You Traffic

A website that has been publishing for a few years usually has a shape nobody planned: a handful of pages doing most of the work, a long tail that gets almost nothing, and a few pages quietly working against the rest. A content audit is how you find out which is which — not by opinion, but by pulling the actual numbers and reading what they say.

This is different from writing new content and different from a technical SEO audit. A technical audit checks whether pages can be crawled and indexed correctly. A content audit checks whether the pages that are indexed are actually earning their place — and if they aren’t, what to do about them: rewrite, merge, redirect, or leave alone.

Why a Healthy-Looking Site Can Still Be Losing Traffic

Traffic loss rarely looks like a single dramatic post announcement. It shows up as a slow decline across several related pages, and the most common cause isn’t a penalty — it’s the site competing with itself. When five articles cover close variations of the same topic, they don’t add up to five times the visibility. They split it. Google has to decide which of the five pages best answers the query, and often it hedges by ranking all of them lower than one strong page would rank alone.

This is the exact pattern documented across the wider search industry: near-duplicate content clusters depress rankings for every page in the cluster, not just the weakest one. The fix isn’t writing a sixth article. It’s auditing the five that exist and consolidating them into the one that should have existed from the start.

What a Content Audit Actually Measures

A proper audit starts with a full export of every published page and a small number of hard metrics next to each one:

  • Organic sessions over the last 12 months, to separate pages that get real search traffic from pages that only get traffic from social or direct links.
  • Impressions and average position from Search Console, which show whether a page is being shown for the queries it was written for, or for something else entirely.
  • Backlinks, since a page with earned links carries authority that shouldn’t be thrown away even if its traffic is currently low.
  • Publish and last-updated date, because a page’s age is often the simplest explanation for outdated statistics, screenshots or product references.
  • Conversion signal — form fills, chat starts, or clicks to a service page — where available, since a page with modest traffic but strong conversion is worth more than a high-traffic page that converts nobody.

None of this requires expensive tooling. Search Console’s Performance report, exported to a spreadsheet, and a simple crawl of the site’s sitemap cover the data most audits actually need.

Sorting Pages Into Four Buckets

Once the data is in one place, every page falls roughly into one of four categories. The category — not the traffic number alone — determines the action.

Keep and Leave Alone

Pages with stable or growing organic traffic, clear intent match, and no overlap with other pages on the site. The instinct to “improve everything” causes real damage here — a page that’s working doesn’t need a rewrite, and re-optimizing a page that already ranks well is one of the more common ways to accidentally lose the ranking it had.

Update

Pages with a clear, single purpose that have lost position over time, usually because the topic evolved (pricing changed, a platform released a new feature, a statistic went stale) rather than because the page was ever badly written. These are the highest-return audit findings: an update to an existing URL with existing backlinks and existing indexing history almost always outperforms writing something new from zero.

Merge

Two or more pages that answer the same core question in slightly different words. Rather than choosing a winner and deleting the rest outright, the stronger page absorbs the useful sections of the others, the other URLs 301-redirect into it, and the combined page ends up more complete than any one of the originals — while keeping whatever backlinks and indexing signal the redirected pages had already earned.

Retire

Pages with no meaningful traffic, no backlinks, and no topic overlap worth preserving — often thin pages published early, before there was a content strategy at all. These can be redirected to the closest relevant page or, if nothing fits, left as a clean 404 rather than kept live purely to avoid admitting they didn’t work.

Signal in the dataLikely bucketTypical action
Steady or rising traffic, unique topicKeepNo change — monitor only
Declining position, single clear topic, outdated detailsUpdateRefresh facts, re-check search intent, keep same URL
Multiple pages ranking for overlapping queriesMergeCombine into one page, 301 the rest
Near-zero traffic, no backlinks, thin contentRetireRedirect to closest relevant page or remove

The Part Most Audits Get Wrong: Redirect Mapping

Merging or retiring a page without a correct 301 redirect throws away whatever authority that URL had built up, and it also breaks any existing external links or bookmarks pointing to it. The redirect target has to be the single most relevant surviving page — not just the homepage, and not a generic category archive. A redirect that lands a visitor somewhere unrelated to what they clicked on will bounce them just as fast as a broken link would, and a chain of redirects (old page to merged page to another merged page) should always be flattened to a single hop before it goes live.

This is the same discipline that applies to everyday internal linking: an internal link that passes through a 301 on its way to the real destination loses some of its value and adds an unnecessary hop for the visitor. When rebuilding a site’s internal link structure after an audit, every link should point straight at the final URL, not at a redirect.

How Often to Run One

A full audit once a year catches most of the drift that accumulates from normal publishing. A lighter, quarterly check of just the pages that dropped the most in the last Search Console data is usually enough to catch problems early, before five near-duplicate pages become nine. The practice of reading an SEO analysis report regularly is what surfaces these drops before they compound — a content audit is really just what you do once that report has told you where to look.

Google’s own guidance on creating helpful, reliable content is explicit that depth and usefulness on a single page consistently outperforms splitting the same information across several thin ones — which is the underlying reason audits pay off more than most businesses expect going in.

Auditing a Multilingual or Multi-Product Site

For a site publishing across services and multiple products, the audit needs one extra step: checking overlap not just within one language or one product line, but across them. A services business that also publishes product content should watch for the same near-duplicate pattern between, for example, two articles both aimed at “reducing cart abandonment” — one written from a live-chat angle and one from an AI-assistant angle. They can coexist if each targets a genuinely distinct angle and audience, but if either drifts into repeating the other’s argument, it’s the audit’s job to catch that before search engines do.

A well-planned SEO strategy treats the audit as ongoing maintenance, not a one-time cleanup project — the same way a website needs maintenance after launch, not just at launch.

FAQ

How is a content audit different from a technical SEO audit?

A technical audit checks whether pages can be crawled, rendered and indexed correctly — broken links, slow load times, missing tags. A content audit assumes the page is indexable and asks whether it’s actually performing: is it getting traffic, ranking for the right queries, and not competing with another page on the same site.

Should underperforming pages always be deleted?

No. Deleting a page with any backlinks or historical traffic without a redirect throws that value away. Most underperforming pages are better served by a 301 redirect into a stronger, related page, or an update rather than a removal.

How many similar articles is too many?

There’s no fixed number, but the practical test is: if a reader landing on any one of them would be satisfied without needing to read the others, they’re probably fine as separate pages. If a searcher would need to open two or three of them to get a complete answer, that’s a signal they should be one page.

Does merging pages hurt SEO in the short term?

There’s often a brief adjustment period as search engines process the redirects and consolidate signals, typically resolving within a few weeks. The medium-term result — one strong page instead of several competing ones — is usually a net gain within one to two months.

What tools are needed to run a content audit?

Search Console for performance data, a basic site crawler or sitemap export to list every published URL, and a spreadsheet. Paid content-audit tools add convenience at scale but aren’t required for a site of a few dozen to a few hundred pages.

Who should decide which page “wins” in a merge?

Whichever page has the stronger combination of current ranking, backlink profile, and completeness — not necessarily the newest or the one with the better title. The data should decide, not preference for one draft over another.

The Bottom Line

A content audit isn’t a cleanup task for a slow month — it’s the mechanism that stops a growing site from quietly competing against itself. The data almost always sorts pages into the same four buckets: keep, update, merge, retire. Getting the redirects right when merging or retiring is what protects the authority those pages already earned, and doing this once or twice a year keeps a handful of near-duplicate articles from ever reaching the point where untangling them costs more than writing them did in the first place.