A company deletes a page.
The page disappears.
So... is it gone?
Not necessarily.
The URL is still out there.
Someone may have bookmarked it. A blog may still link to it. An old email may still contain it. It could still appear in search results, a social post, a PDF, or even a printed QR code.
This is the part of deleting a webpage that is easy to overlook:
Deleting a page does not delete every place that points to its URL.
And depending on what happens next, those old links can either lead people somewhere useful—or nowhere at all.
A deleted page can still receive visitors
Imagine a company has this page:
example.com/pricing-2024
A year later, the company launches a new pricing page and deletes the old one.
The old URL might still exist in:
- Old blog posts
- Customer emails
- Social media posts
- Search results
- Partner websites
- Bookmarks
- Sales documents
- Advertisements
The company may have forgotten about the URL.
The internet hasn't.
Someone can still click it.
And if nothing has been configured, they may simply see a 404 Not Found page.
A 404 is not automatically a disaster. In fact, when content is genuinely gone and there is no useful replacement, Google recommends returning a proper 404 or 410 response.
The important question is not:
“Is a 404 bad?”
The better question is:
“Should this particular URL really lead to nothing?”
Not every deleted page should be redirected
This is where things get more interesting.
Suppose a company deletes:
example.com/old-product
because the product was discontinued.
There may be a completely different product that replaced it.
If the new product genuinely serves the same purpose, redirecting the old URL to the new product can make sense.
But if there is no meaningful replacement, sending visitors to the homepage just because it is available isn't necessarily helpful.
Google specifically advises against redirecting lots of unrelated old URLs to one destination such as the homepage.
A redirect should answer the visitor's original question.
If someone clicked an old article about website migrations, they should not suddenly land on a company's pricing page.
That isn't fixing the old link.
It's just moving the confusion somewhere else.
Think of an old URL as an old entrance
A useful way to think about deleted pages is to imagine a physical store.
A company closes one entrance.
But people still have the old address.
You have a few choices:
1. There is a new entrance nearby.
Put up a sign pointing people there.
2. The entrance is permanently gone and there is no replacement.
Tell people clearly that it is closed.
3. You don't know what happened to the entrance.
That's when things start getting messy.
Websites have the same problem.
A deleted page isn't just a piece of content.
It's an old entrance to your website.
What should happen to an old URL?
There are three simple questions to ask.
1. Did the content move?
If the page has a clear new home, redirect the old URL to the new one.
For example:
/old-guide → /new-guide
A permanent redirect tells browsers and search engines that the page has moved.
2. Did the content disappear completely?
If there is no useful replacement, letting the old URL return a proper 404 or 410 can be the right choice.
There is nothing wrong with telling visitors:
This page no longer exists.
The mistake is pretending there is a replacement when there isn't one.
3. Does the old URL still matter?
This is the question companies often skip.
An old URL might have traffic, backlinks, campaign clicks, or references across the web.
Before deleting it, it is worth asking:
Who might still be using this URL?
You may discover that a page you considered "dead" is still an entrance people use.
The bigger problem: companies forget about old URLs
Deleting one page is easy.
Managing thousands of old URLs is not.
This becomes especially noticeable after:
- Website redesigns
- Domain changes
- Rebrands
- Product changes
- Website migrations
- Content cleanups
- Large-scale URL restructuring
A company may create hundreds or thousands of redirects during a migration.
Everything works on launch day.
Six months later, someone deletes one of the new destination pages.
Now an old URL can still redirect correctly—but the visitor eventually lands on a missing page.
The redirect itself works.
The journey doesn't.
That's an important distinction.
A redirect can work while the destination is broken
Consider this:
oldsite.com/guide
→ redirects to
newsite.com/guide
The first step works perfectly.
But what if newsite.com/guide later returns a 404?
From a basic redirect check, the old URL may look healthy because the redirect still exists.
For the visitor, however, the experience is broken.
This is why managing old URLs shouldn't end when redirects are created.
They need to be checked over time.
That becomes especially important for high-value pages, campaign links, website migrations, branded links, and other URLs that may stay in circulation for years.
A simple rule for deleting pages
Before deleting a page, ask:
Does this URL have somewhere useful to go?
If yes → redirect it.
If no → let it properly return a 404 or 410.
If you're not sure → investigate before deleting it.
And after creating redirects, don't assume they'll work forever.
Destinations can disappear.
Pages can move again.
Domains can expire.
SSL certificates can fail.
A redirect that worked perfectly when it was created can eventually lead somewhere broken.
The URL outlives the page
That's the part worth remembering.
A webpage might have a short life.
Its URL can have a much longer one.
It can live inside someone's bookmark, an old article, a marketing campaign, a search result, or a document long after the original page has been removed.
So when a company deletes a page, it shouldn't only ask:
“Do we still need this content?”
It should also ask:
“What happens to everyone who still has this URL?”
That's the real problem to solve.
And once old URLs are redirected, keeping an eye on where those redirects actually lead becomes just as important as creating them in the first place.
For a deeper look at checking redirects and the pages they eventually reach, see Redirect Monitoring & Destination Health.
Top comments (0)