Discussion
  • Enterprise SEO

Leadership hears fewer pages as less traffic. How do you forecast the effect of removing a large volume of low-quality URLs?

Published 1 reply

Discussion starter: an enterprise SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • Niraj Raut
    Niraj Raut
    Original poster

    Forecast it with the site’s own data, in two parts. The direct effect is usually small and easy to quantify: the traffic the pages being removed actually receive, which for genuinely low-quality URLs is often close to nothing, adjusted for how much of it redirects would retain. The indirect effect, meaning any improvement in crawling, indexing or how the site is assessed as a whole, is real in some cases but uncertain, so present it as a range of scenarios rather than a promise. Then propose a staged removal on one section first, with a comparison section left unchanged, so leadership sees evidence before the full programme. That approach answers “fewer pages means less traffic” with numbers, not argument.

    Building the forecast

    1. List the candidate URLs and why each is low quality: thin, duplicate, outdated, auto-generated, never visited.
    2. Pull their performance over the last 12 months: clicks, impressions, conversions and referring domains.
    3. Calculate the direct loss: the traffic and conversions those pages produce, minus the share expected to be retained where pages are redirected or merged into better pages.
    4. Check for exceptions: pages with links or conversions should be merged or improved, not removed.
    5. Estimate the indirect effect as scenarios: no change, a modest improvement in the remaining pages’ performance, and a larger improvement if quality or crawl constraints were holding the site back.

    What leadership usually sees

    Item Typical finding on sites with bloat
    Share of URLs with no clicks in 12 months Often large
    Share of traffic from the candidate URLs Often very small
    Conversions from candidate URLs Often negligible
    Crawl share spent on candidate URLs Often much higher than their traffic share

    Presenting those four numbers side by side usually changes the conversation. The pages leadership fears losing are rarely the pages producing results.

    Framing the indirect effect honestly

    Google’s guidance during the helpful content era said that removing unhelpful content could help the rankings of a site’s other content. That guidance predates the March 2024 integration of the helpful content system into core ranking, so treat it as indicative rather than a current promise. Crawl benefits are more predictable on large sites where low-value URLs consume a significant share of crawling. Present gains as possible, not certain, and let the pilot provide evidence.

    Distinguish removal methods in the forecast

    Not all low-quality pages should be handled the same way, and the forecast should reflect that. Pages with some value but thin content can be improved; overlapping pages can be merged into stronger ones with redirects, retaining most of their traffic and links; pages with no traffic, links or purpose can be removed with 404 or 410; pages needed by users but not in search can be noindexed. Showing leadership how many pages fall into each group, and the expected effect of each treatment, makes the plan look deliberate and reduces the fear that valuable content is being thrown away.

    Staging the removal

    • Start with one section or template, and keep a comparable section unchanged as a control.
    • Redirect or merge pages with links or conversions; return 404 or 410 for pages with neither.
    • Update internal links and sitemaps so removed URLs are not linked.
    • Measure over a few months: clicks, impressions and conversions for the section, crawl distribution and indexing of remaining pages, compared with the control.
    • Scale only if the pilot matches or beats the forecast.

    Hypothetical example:

    A publisher proposes removing 40,000 tag and archive pages and 8,000 thin articles. Leadership worries about traffic. The SEO team shows that those pages account for under 2% of organic clicks and almost no conversions, while taking a large share of Googlebot’s requests. It pilots the removal on one section, merging 300 thin articles with links into stronger pages and removing the rest. After three months, the section’s clicks are slightly up while the control section is flat, and new articles in the section are indexed faster. Leadership approves the full programme.

    Watch for this:

    Selecting pages for removal by traffic alone can remove pages that earn links or serve customers in ways traffic data does not show, such as support content. Check referring domains, conversions and internal use before removing anything.

    Quantify the direct loss from your own data, present the indirect effect as scenarios rather than promises, protect pages with links or conversions, pilot on one section with a control, and scale on evidence. Most leadership concerns fade once the numbers show how little the removed pages were contributing.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.