PLANNING & MAINTENANCE · 3 MIN READ

Website Redesign Without Losing Important URLs and Content

Plan a website redesign around existing URLs, useful content, redirects, internal links, and launch checks so a visual refresh does not discard value.

A redesign changes how a website looks and how people move through it. It should also account for existing pages that customers, search engines, and external websites already know.

Before drawing the new navigation, create a record of what exists and what should happen to it.

01

Inventory the useful pages

Collect the current URLs, page purposes, important content, and known entry points. Where authorized data is available, review search and usage information alongside business priorities.

Do not remove a page solely because it is old or has a design you dislike. A small technical resource may answer an important customer question even if it does not resemble a sales page.

For a hypothetical consultancy, an older integration guide may attract the right readers and support a current service. It could deserve an update and a clearer path to that service rather than deletion.

02

Map the new structure

For each existing URL, decide whether it stays, changes, merges into another page, or is retired. Record the intended destination when a meaningful equivalent exists.

Google's site-move guidance recommends preparing URL mappings, implementing redirects, and monitoring the transition. A move can involve changes to paths as well as domains. If URLs do not change, do not create unnecessary changes merely to make the redesign feel new.

Avoid sending every removed page to the homepage. The destination should make sense for a person following the old link.

03

Preserve meaning, not every sentence

Review the purpose and evidence behind the content. Improve confusing wording, remove obsolete claims, and retain useful explanations. A shorter page is not automatically better if it drops the information that answers the visitor's question.

Check titles, headings, descriptions, and links as part of the content review. Do not treat metadata as a substitute for a useful page.

04

Verify the transition technically

Check representative redirects, internal links, canonical URLs, sitemap entries, and indexing settings. Ensure staging restrictions are not unintentionally carried into a site intended for public indexing.

Test forms and important user journeys too. Preserving URLs is of limited value if the redesigned contact process no longer works.

05

Monitor after launch

Review broken URLs, unexpected redirects, indexing signals, and important business journeys. Compare changes in context rather than assuming every traffic movement has one cause.

A careful plan reduces avoidable mistakes, but cannot guarantee unchanged rankings or traffic. The practical deliverable is a documented content map and verified transition, with clear ownership for issues found after launch.

06

Discuss the implementation

Explore website redesign and WordPress development.

KEEP EXPLORING

Sources & further reading

Official documentation for the topics discussed. Check implementation details against the versions and services used by your project.

WRITTEN BY MARKO ARNAUTOVIC

Practical thinking.
Hands-on engineering.

I build AI automation, web platforms, and mobile applications for businesses. These notes share the decisions behind that work.

Meet the engineer behind ArnautCode

PUT THE IDEAS TO WORK

Need help with
the implementation?

Explore the approach and scope for website redesign.

Explore the service
Chat on WhatsApp