SEOArchive edition6 min read

Handling URLs when navigation changes

Protect useful page addresses while improving labels, categories and menus.

A network of connected nodes and branching routes — Handling URLs when navigation changes
Original ARTware computational illustration.

Changing a site's navigation is often a necessary part of growing a technical publication. A new set of development services may need a clearer place in the menu, while the journal becomes easier to browse under dedicated subjects. None of those changes automatically requires a new public address. A label is a navigational decision, a category describes a relationship, and an address identifies a document. If these are treated as the same thing, a minor design change can unexpectedly create dozens of moves. The goal of a route transition is to preserve access to useful pages while making the new structure understandable to a visitor and maintainable for the publisher.

Separate the new information architecture from addresses

Suppose a business currently has a navigation item named 'Software' leading to '/software-development/'. The redesign groups that page with backend development, integration work and mobile interfaces under a menu label named 'Engineering.' Changing the label and the position of the link does not change the subject of the existing page. The route can remain intact. The new grouping might also have its own index identifying the relevant services. That index links to all the existing preferred service destinations. Creating nested addresses merely to reflect every menu relationship imposes a permanent routing consequence on what could be a reversible navigation decision.

There are cases where a route change is warranted. An old address may contain a temporary internal identifier, or several old pages may be replaced by a coherent new destination. A structural change involving languages may require explicit language-specific paths. Evaluate those cases individually. A stable URL need not match the current menu hierarchy exactly, provided that it is consistent, understandable and still identifies the relevant document. Before considering a move, write down why keeping the old address fails to serve the new structure. This often eliminates unnecessary work and reduces the number of legacy redirects that must be preserved and tested.

Capture a complete old route inventory

Create the inventory before releasing the new template. Read the old sitemap, crawl visible internal links, and consult the published content source. If suitable request or query reports exist, use them to identify older addresses no longer linked from navigation. Store the preferred route of each page, its heading and the function it served. Also retain known aliases and existing redirects. These sources can disagree. The old sitemap may contain stale paths, while a link embedded in an older article may reveal an existing document that the newer menu no longer lists. Checking all available sources helps avoid forgetting pages during the transition.

A small migration table might contain seventy-five current pages and ten obsolete routes. For each entry, assign a disposition: unchanged, moved to an equivalent document, replaced through consolidation, retired without an equivalent, or still requiring review. Use the destination column only where a meaningful destination exists. Do not mechanically fill it with the new home page. A reader requesting a detailed article about data recovery is not served by a general welcome page that does not contain the relevant information. If the subject has genuinely disappeared, a clear not-found or deliberately retired response is more honest than an apparently successful but unrelated destination.

Related reading: A sitemap that reflects the site you actually publish.

Create the redirect map before modifying navigation

For routes that really move, enter the final preferred address in the redirect configuration. A permanently replaced document normally receives a permanent status indicating that the relocation is intentional. The configuration should not depend on the address that happened to be preferred immediately before the last redesign. Suppose an article moved from '/notes/interface.html' to '/journal/interface/' and will now move to '/journal/interface-design/'. Update both older known paths to lead directly to the final address if the article remains equivalent. A redirect that points to another redirect can still work, but the chain adds requests and introduces another configuration dependency.

Check the map for cycles and collisions. A destination should not also be the source of a redirect back to the original route. A broad pattern should not conceal a more specific page that continues to exist. Rules for alternate hostnames, secure connections and directory-style paths can interact with per-page redirects, so inspect their combined behavior in the intended hosting environment. A redirect that is valid in a local preview is not necessarily implemented the same way at the edge of the deployed site. Document any relevant assumptions about how the server treats old extensions, path capitalization and trailing slashes.

Layered flowing curves with fine network-like intersections
ARTware visual study. A complementary computational composition.

Update every generated reference to moved pages

Navigation may be the visible reason for a change, but it is not the only producer of links. Article cards, breadcrumb trails, related page links and the sitemap also refer to published routes. If all of them read from one route inventory, the work is simpler: adjust the selected record and regenerate the output. If article paragraphs contain manually written addresses, inspect them separately. A link to an old address might be hidden inside a long technical example several years old. The release should point current visitors directly to the intended destination instead of relying on the redirect as a permanent repair for the site's own navigation.

The visible contents of the destination deserve review as well. Suppose two general guides about site maintenance are combined into a fuller article. Preserve the specific explanation that made each predecessor useful, and check that the new page title and main heading describe the consolidated subject. A correct redirect to a page that offers substantially less useful material than the predecessor does not fully preserve the old document's purpose. Ensure that the destination identifies its preferred address in canonical metadata and appears in the sitemap if it is part of the new published collection. The superseded path belongs only in the redirect inventory.

Verify the release with actual requests

Prepare a test set containing unchanged destinations, old addresses that should move, genuine removals and new category pages. Request each address and record the initial response. For a moved page, confirm the expected permanent redirect status and inspect its location before following it. Request the final location independently and ensure that it returns the intended successful document without another intermediate move. For an unchanged route, confirm that the redesign has not introduced an unnecessary relocation. For a missing route, inspect both its status and the error page. A generic successful response containing an error message is difficult for both people and maintenance tools to interpret.

Once routing behavior is correct, crawl the new site and compare the actual internal destinations with the expected route inventory. Internal references to old routes are worth correcting even if visitors are able to follow them through redirects. Inspect pages across the site types that share navigation, including old articles and any service pages using separate layouts. Check that the breadcrumb describes the new information architecture and that its links point at the actual index and page. Test the navigation on a small display where a menu is arranged differently from desktop. A change that appears correct at one width may still make primary destinations inaccessible at another.

Keep the migration record after the launch

A redirect mapping is part of the site's maintenance history. Keep it along with the new route convention and the list of intentional removals. When another reorganization takes place, these records help distinguish current pages from historical aliases. Review the redirects before adding new ones so that old paths continue to point to the final equivalents. Avoid casually reusing a previously published address for a completely unrelated subject if its earlier meaning may still be referenced elsewhere. Navigation and category layouts can evolve repeatedly while the core addresses remain stable. By reserving moves for genuine document transitions, the next redesign can concentrate on making the site easier to use rather than repairing needless URL churn.

Explore the implementation area: Technical SEO.