A website address is a small thing that carries a lot of weight. People bookmark it, save it in a document, paste it into an email, or type it from memory. Search engines record it, associate it with the value of a page, and send visitors to it for years. So when the addresses on a site are about to change, and they change more often than most people expect, it is worth treating that change with care.
URLs change for good reasons. A redesign reorganizes how content is grouped. A growing site outgrows its old structure and needs clearer sections. A move away from an older content management system brings a different way of building paths. None of these are problems. They are healthy signs that a site is being looked after. The goal is simply to carry the value of the old addresses forward, so the change is invisible to the people and the search engines that relied on them.
Here is how we approach a URL change so that search traffic and saved links keep working, calmly and without drama.
An address is a promise someone is relying on
Every published URL is, in effect, a small promise. Somewhere out there, someone has saved it. Another site has linked to it. A search engine has spent time learning what lives at that address and how much to trust it. When the address disappears without a plan, all of that quietly breaks. The visitor lands on a page not found, the link from another site leads nowhere, and the search engine slowly stops sending people to a page it can no longer find.
The reassuring part is that none of this has to happen. A URL change handled properly keeps every one of those promises. The old address still leads somewhere sensible, the search engine understands that the page has moved, and the person who bookmarked it two years ago never notices anything at all.
The redirect map comes before anything moves
Before we change a single address, we make an inventory. We list the URLs that exist today, note which ones carry traffic or attract links, and decide where each one should point in the new structure. This is the redirect map, and it is the quiet backbone of a smooth migration.
Most old pages have a clear new home. An about page moves to a tidier path, a product page lands in a better-organized section. Occasionally a page has no direct equivalent, and then we make a deliberate choice: send it to the closest relevant page rather than dropping people on the homepage, which tells a visitor nothing about where they were trying to go. Doing this thinking up front, on paper, is far easier than discovering gaps after the new site is live.
Permanent redirects, because the move is permanent
When a page moves for good, we use a permanent redirect, the kind commonly known by its status code, 301. It tells a browser and a search engine the same thing: this page has a new home, update your records. Over time, search engines transfer the reputation a page earned to its new address, which is exactly what we want. The distinction matters, because a temporary redirect signals the opposite, that the move is only for now, and search engines treat it accordingly.
Getting this right is not complicated, but it is easy to overlook. So we make it a standard part of the work rather than an afterthought, and we check that each redirect returns the right signal rather than assuming it does.
Old paths stay alive
A redirect is not a one-time favor you can remove once the new site settles in. It is a permanent bridge. Links on other sites do not update themselves, bookmarks live in browsers for years, and search engines revisit old addresses long after a change. So the redirects we put in place are meant to stay in place.
This is one of those maintenance details that is invisible when it works and painfully obvious when it does not. Removing a redirect a year later, to tidy up, quietly breaks every link and bookmark that still pointed through it. We would rather keep the bridge standing. It costs nothing to leave in place, and it keeps a promise you made without thinking about it.
Internal links and sitemaps, updated to match
Redirects catch the traffic arriving from outside, but a site should also be tidy on the inside. If the pages on the new site still link to old addresses, every one of those clicks takes an unnecessary detour through a redirect. It works, but it is slower and less clean than it should be. So we update the internal links to point straight at the new addresses.
The same goes for the map a site hands to search engines. An XML sitemap should list the addresses that actually exist now, not the ones that used to. Keeping it current helps search engines discover the new structure quickly and understand that the change was intentional. These are small, unglamorous tasks, and they are the difference between a migration that feels clean and one that leaves loose ends trailing for months.
Why Drupal makes this manageable
A lot of what makes a URL change smooth comes down to having good tools for it, and this is an area where Drupal is genuinely strong. It manages clean, readable addresses, keeps a proper record of redirects, and can generate one automatically whenever the address of a page changes, so the old path keeps working the moment the new one goes live. It also produces the sitemap that search engines read.
Having all of this in one place, rather than scattered across separate services, means a URL change is a controlled, reviewable process instead of a scramble. We can see the full list of redirects, confirm each one points where it should, and keep that record as the site grows. It is one of the reasons we are comfortable restructuring a site when the content calls for it, rather than leaving an awkward structure in place out of a fear of breaking things.
Measured, then watched
After the addresses change, the work is not quite over. We watch. Search engines take a little time to notice a move and update their records, so we keep an eye on how they are crawling the site, look for any address reporting a problem, and fix anything the map missed. A URL change is rarely perfect on the first pass, and the point of watching is to catch the small gaps before they matter.
Done this way, changing the addresses on a site stops being something to dread. Rankings hold, saved links keep working, and the people visiting your site never know the ground moved under them. If you are planning a redesign or a restructure and the thought of the URL change is giving you pause, that is exactly the kind of thing we are glad to talk through.