What happens to your old blog posts and pages during a redesign

The default outcomes: keep, merge, cut, or archive

You've got years of blog posts sitting on the current site. Maybe a hundred product pages, service descriptions someone spent real hours writing back when the business was smaller.

Then a redesign gets scheduled and a quiet worry sets in: does all of that just vanish? It's a reasonable thing to wonder and an oddly awkward thing to say out loud, so plenty of people just assume the worst and never ask directly.

It doesn't disappear. A redesign is a new look and structure for the site, not a blank document someone starts typing into. Every existing page gets sorted first. Nothing gets deleted by default, and nothing should be.

Every page you already have ends up in one of four buckets. Keep means the page carries over close to as-is, restyled to match the new design. Merge means two or three thin, overlapping pages get combined into one stronger page instead of competing with each other.

Cut means a page that's outdated, duplicate, or simply never read gets dropped for good. Archive means it's removed from navigation and search but the content stays saved somewhere, in case you need it later for reference.

A lot of sites end up with pages in all four buckets by the end of this process. That's completely normal. It isn't a verdict on how good the old site was to begin with.

What decides which bucket a page falls into

A few honest questions sort most pages fast. Does anyone actually read this page? Does it bring in search traffic, or answer a real question customers search for before they call? Is the information still accurate, or does it describe a service you quietly stopped offering two years ago?

A page with steady traffic that answers a real question is a keep, even if the writing itself is dated and needs a light edit before it goes live again. A page almost nobody visits, covering something two other pages already do better, is a cut or a merge candidate. Neither of those is a hard call once you actually look at the numbers.

This sorting deserves to happen on purpose, with someone actually looking at each page, rather than being left to whoever's building the new site to guess at halfway through construction.

Keeping the same URL for content that survives

When a page survives the redesign, keeping its web address exactly the same matters more than most people expect going in. Search engines, other websites linking to you, and even your own old social posts all point at that specific address. Change it without a plan and every one of those links quietly breaks, sending people to a dead page instead of your content.

If the address genuinely has to change, because of a new site structure or a full platform switch, that old address needs to redirect to the new one automatically. Nothing complicated about the idea itself. It just has to be tracked, page by page, so none of them get missed in the shuffle.

What a redirect map is and why your redesign needs one explains exactly how that tracking gets done so nothing slips through unnoticed.

What happens to images and media specifically

Images and video get overlooked easily, because they're not text anyone sits down and proofreads in a document. They live as separate files, and depending on how the old site was built, moving them cleanly to a new platform isn't always a simple drag and drop between systems.

Someone needs to confirm that every image on a kept or merged page actually made the trip, at a size and format that still looks sharp on a modern screen. A page that reads fine but shows broken image icons where photos used to be looks noticeably worse than no image at all.

This check is tedious and easy to skip, which is exactly why it gets skipped on real projects. Put it on a list somewhere with a name attached to it.

The mistake of rewriting everything just because the design changed

A new design tempts people into rewriting content that was already working perfectly fine before anyone touched it. Resist that instinct specifically for pages that already rank well in search or already convert well into calls and bookings. A visual refresh and a full content rewrite are two separate jobs, even though they get bundled together out of habit.

Doing both at once, on every single page, multiplies the number of things that could go wrong at launch for very little real gain. Save actual rewrites for pages that genuinely need them: the outdated ones, the thin ones, the confusing ones nobody understands on first read. Let the new design simply carry the pages that already do their job well.

Auditing the old site before anyone starts building

All of this depends on someone going through the existing site first, page by page, sorting it into the four buckets before design work even begins in earnest. Skip this step and decisions get made on the fly mid-build, usually under time pressure near a deadline. That's exactly how good, working pages get accidentally cut.

This audit belongs inside the overall project scope from the start, not bolted on as an afterthought once the new templates are already finished and waiting for content.

How to scope a website rebuild before getting quotes covers folding this audit into the plan from day one.

How to redesign a website without losing what works sets out where this content decision sits inside the larger project as a whole. And if keeping your search visibility through all of this is what's actually keeping you up at night, how to redesign a website without losing your google rankings is the direct answer to that specific worry.

More from the blog

All posts