Skip to main content
web60

SEO & PageSpeed

Deleting Old Pages for SEO: The Clear-Out That Cost a Business Its Best Page

Ian O'Reilly··12 min read
Flat illustration of a stack of teal, navy and grey page shapes with the top page lifting away beside a broad curving teal ribbon on a warm off-white background

Consider a composite case, assembled from a pattern that turns up every time Google ships a core update. An upholsterer in Offaly has kept a blog for the best part of a decade: fabric guides, before-and-after photos, a long post on re-covering drop-in dining chairs, a few lines about a craft fair years ago. In the middle of November the enquiries feel quieter. The owner opens Google Search Console, finds the Page indexing report, and sees dozens of old posts listed as "Crawled - currently not indexed".

A forum thread makes the fix sound obvious. Delete the thin content and Google will think better of the site. So one Sunday evening the owner ticks forty-odd posts, moves them to the Trash, and empties it to be thorough.

By the following weekend the quote form has gone almost silent. The dining chair post, it turns out, was the page a local heritage group had linked to for years, and the page most new customers arrived on. It now returns "Page not found". No copy of it exists anywhere. Nothing about that evening felt reckless, and every click felt like tidying. That is exactly why it is worth walking through slowly.

What "Crawled - Currently Not Indexed" Actually Means

The Page indexing report in Search Console lists the URLs Google knows about on your site and sorts them into indexed and not indexed, each with a reason. Google's help page defines this particular status in one plain line: the page was crawled by Google but not indexed [3]. The same page says Google does not guarantee that every page will make it into its index, and that only your key pages need to be there [3].

That changes how the list should be read. As a status report. Not a to-do list.

Plenty of the URLs in it will be tag archives, attachment pages, old drafts that were briefly public, or near-copies of better pages. Some will be posts that deserve to be found and are not. None of them are doing harm simply by appearing in the report, and none of them were the reason the upholsterer's enquiries had slowed. Deleting them could not lift the site, because the clear-out was aimed at a problem the site did not have.

What Google said this week

On 10 November, Google's John Mueller was asked on Bluesky about a site with a high share of crawled or discovered but not indexed pages. As Search Engine Roundtable reported, he said this is usually a sign that Google's quality systems are unconvinced about the site, and added that just making the site smaller does not significantly raise its overall quality [4].

Read that second part twice. It is the opposite of the forum advice. A site Google is unconvinced by does not become convincing by having fewer pages; the pages left behind are judged on the same terms as before. Improvement comes from making the remaining pages more useful to the people who land on them, which is slower work and the only kind that counts.

Why a Core Update Makes the Delete Key So Tempting

Timing plays its part. Google released its November 2026 core update on 10 November, and the Google Search Status Dashboard says the rollout may take up to two weeks [1]. During that window rankings shift for sites of every size, and an owner who opens Search Console mid-rollout sees lines moving and wants to do something.

Google's guidance for that moment is unusually direct. Its documentation on core updates says there is no need to take drastic action for a small drop, and recommends waiting at least a full week after an update completes before analysing your site in Search Console [2]. On removals it is blunter still: "Deleting content is a last resort, and only to be considered if you think the content can't be salvaged" [2].

The same page warns that improvements can register within a few days but may take several months, and sometimes not until the next core update [2]. So the feedback loop is slow. A bulk delete on a Sunday shows no result by Friday, good or bad, and that silence is what tempts people to go back and delete more.

Diagnose before you delete

If your traffic has already moved, work out what really caused the drop in Google traffic before changing anything. Most drops have a cause that has nothing to do with old blog posts, and finding it first saves a great deal of undoing.

Flat illustration of a grid of grey page cards joined by navy lines, with one card in the centre highlighted in teal and surrounded by small teal dots
Most sites have a few pages doing far more work than the rest. Find them before you remove anything.

The Page That Was Quietly Carrying the Business

Every website has a handful of pages doing more work than all the others put together. On most small business sites nobody knows which ones they are, because nobody has looked.

The dining chair post was one of those. It had links from the heritage group's site and from a couple of furniture restoration forums. People searching for chair re-covering found it, read it, and filled in the quote form at the bottom. None of that showed in the Page indexing report, because the post was indexed and doing its job. It simply sat in the same blog as the forty flagged posts, and the bulk selection swept it up with them.

What a 404 does to a page with links

Once a page is deleted, WordPress serves a 404 error at its address. Google's Page indexing documentation says a 404 is not necessarily a problem when a page was removed with no replacement [3]. True. Also the trap. This page had a job that still needed doing, and every link pointing at it now leads to an error, for visitors and for Google alike.

That is where the cost lands. A reader of the heritage group's newsletter clicks through to find out about having a grandmother's chairs re-covered. What loads is "Page not found". Nobody emails to ask what happened. The visitor searches again and rings whichever upholsterer appears next, and the owner never learns the enquiry existed.

Finding your own carrying pages

Search Console can show you which pages are doing that work before you touch a single one. Two reports matter:

  • Links report, Top linked pages. This lists the pages on your site with the most links from other websites. Google describes it as a sample rather than a complete record, but the top of the list is what you need.
  • Performance report, Pages tab. Set the date range to the longest available, sixteen months, and sort by clicks. Pages that earn their keep in spring will not show up if you only look at November.

Any page near the top of either list is not a deletion candidate, however dated it looks. The broader picture of how a site's pages, speed and hosting work together is covered in our complete WordPress performance guide for business owners, but for this decision those two reports are enough.

Getting a Deleted Page Back

Recovery depends on how far the deletion went.

If it is still in the Trash

WordPress does not erase posts and pages straight away. They go to the Trash, where they stay for 30 days by default before permanent removal, according to the WordPress documentation [6]. Restoring means opening the Trash view on the Posts or Pages screen and clicking Restore.

There is a catch most owners miss. Since WordPress 5.6, a restored post comes back as a draft rather than in its previous published state, so it is not in production until someone opens it and publishes it again. Verify that each restored page loads at its old address before assuming the job is done.

If the Trash was emptied

Then the page is gone from WordPress and the only copy lives in a backup, if one exists. That is where the upholsterer stood. A site with no backup means rewriting the page from memory and hoping the old address still collects its links.

A backup restore carries a trade-off worth understanding before you press the button. Rolling the whole site back to the night before the clear-out also rolls back everything that happened since: quote requests stored by your form plugin, a new post, a changed price. On a site that takes orders, it includes the orders. The cleaner route is to restore the backup into a staging environment, copy out the pages you need, and republish them on production. Slower, yes. But it does not cost you a second week of enquiries.

What good recovery cover looks like

On any platform, the standard is the same. You want a backup you can take yourself, on demand, in the minute before any bulk change. Nightly backups should run without anyone remembering them, with a restore that does not depend on a support ticket and a few days' wait. And there should be somewhere separate from production to restore into, so you can retrieve one page without undoing a week of everything else.

Web60 meets that standard as part of the plan rather than as an extra. Manual on-demand backups sit alongside automatic nightly backups with one-click restore, a safety snapshot is taken automatically before any restore, and a one-click staging environment gives you that separate copy to work in. It is all included in Web60's €60/year managed WordPress platform, so the cover is already there on the evening you need it. For the upholsterer, it would have turned a lost week into a short, calm afternoon's work.

Flat illustration of a large curved teal arrow pointing down into the first of a row of teal folder-like shapes on a warm off-white background
A backup taken minutes before a bulk change is the cheapest rollback point you will ever have.

Reviewing Old Pages in Five Steps

Old content does sometimes need attention. The point is to change it deliberately, with a way back. This is the order we would follow on any site before removing a single page.

  1. Back up. Take an on-demand backup immediately before you start, so any mistake has a rollback point measured in minutes rather than days.
  2. Verify what each page earns. Look at the Links report and sixteen months of Performance data, and set aside any page that has outside links or regular clicks.
  3. Improve before you remove. Update the prices, photos and details on pages that are dated but still useful, in line with Google's advice to improve content in meaningful ways rather than reach for quick fixes [2].
  4. Redirect what you merge. When two posts cover the same ground, fold them into the stronger one and send the old address there with a permanent 301 redirect, which Google treats as a signal that the new page should be the one shown [5].
  5. Remove only what cannot be salvaged. A post about a craft fair that ended years ago, with no links and no clicks, can go, and a plain 404 is fine for it.

WordPress does not create that 301 for you when you delete or merge a post. A redirect plugin from the WordPress plugin directory handles it, and it is worth installing before step four rather than after. Keep a short note of what you removed and when, too. If anything moves afterwards, you will know which change to look at first.

This is also where owning your own site pays off. The person who re-covers the chairs knows which posts describe real jobs and which were filler written to keep a blog ticking over. No outside agency reviewing a spreadsheet of URLs has that knowledge, and with full WordPress access you make those calls yourself, on your own schedule.

When a Big Clear-Out Is the Right Call

Mass removal is sometimes exactly right. A site that was hacked and filled with thousands of spam pages needs every one of them gone. A shop whose filter settings have generated endless near-identical URLs needs that fixed at the source. Large publishers with tens of thousands of articles run structured content audits with enterprise SEO platforms and dedicated editorial teams, and pruning at that scale is routine work for them. That workload genuinely suits enterprise tooling and the people paid to operate it.

A ten-year-old blog on an owner-run business website is a different thing. Its old posts are a record of real work, written by the person who did it, and one or two of them are probably carrying more weight than anyone realised. WordPress, which W3Techs currently puts at roughly two in five of all websites, makes it easy to keep, edit and redirect those pages without anyone's permission. Use that freedom slowly.

Conclusion

An unindexed page in Search Console is a status, not a verdict. Google calls deleting content a last resort, and John Mueller says a smaller site is not automatically a better one. The pages most worth protecting are the ones the indexing report never flags: the indexed posts with outside links and steady clicks.

So the order matters. Back up first. Verify what each page earns. Improve what is dated, redirect what you merge, and remove only what nobody links to, visits or needs. If you are starting a new site, Web60's AI builder sets up a full WordPress site in under a minute, with nightly backups running from the first day.

When the November update settles, you will be judged on what your pages say, and you will still have every page that was saying it well.

Frequently Asked Questions

Should I delete old blog posts to improve my SEO?

Usually not. Google's guidance on core updates describes deleting content as a last resort, only to be considered if the content cannot be salvaged. Check whether a post has links from other websites or regular clicks first, improve it if it is out of date, merge it into a stronger page if it duplicates one, and only remove posts that have no links, no traffic and no use to a customer.

What does Crawled - currently not indexed mean in Search Console?

It means Google visited the page but chose not to add it to its index for now. Google says it does not index every page it finds, so the status is common and does not always need fixing. If a large share of your site shows it, Google's John Mueller has said that usually means Google's quality systems are not yet convinced by the site, which is solved by improving pages rather than removing them.

Will deleting pages help my website recover from a Google core update?

Not on its own. Google's John Mueller said in November 2026 that just making a site smaller does not significantly raise its overall quality. Google recommends waiting at least a full week after a core update finishes before analysing your traffic, taking no drastic action for small drops, and improving content in meaningful ways.

How do I restore a deleted page in WordPress?

If it is still in the Trash, open the Trash view on the Posts or Pages screen and click Restore. WordPress keeps trashed items for 30 days by default. Since WordPress 5.6 a restored post comes back as a draft, so open it and publish it again, then verify it loads at its old address. If the Trash has been emptied, the only copy is in a backup.

Should a deleted page be redirected or left as a 404?

If there is a page that does the same job, send the old address there with a permanent 301 redirect so visitors and links arrive somewhere useful. If the page has no replacement, no links and no traffic, a plain 404 is fine, and Google's documentation says such 404s are not necessarily a problem.

How long does it take to recover after a Google core update?

Google says some improvements can take effect within a few days, but it can take several months for its systems to recognise them, and in some cases recovery waits until the next core update. That slow feedback is why quick, drastic changes such as mass deletions are risky: you will not see whether they helped for weeks.

Sources

IO
Ian O'ReillyOperations Director, Web60

Ian oversees Web60's hosting infrastructure and operations. Responsible for the uptime, security, and performance of every site on the platform, he writes about the operational reality of keeping Irish business websites fast, secure, and online around the clock.

More by Ian O'Reilly →

Ready to get your business online?

Describe your business. AI builds your website in 60 seconds.

Build My Website Free →
Buy NowTry Free
Deleting Old Pages for SEO: Why It Backfires | Web60