Skip to content
Interface language: English
Design / Signal

Moving a website without abandoning its URLs: mapping, redirects and acceptance

Inventory old URLs, map them to relevant destinations and test redirects before and after a site move. Include files and contact routes in your checks.

Article language: English

A dark blue railway carriage stands on a stone viaduct above a cloud-filled mountain valley.
In this article

The new site is live, the confetti has settled, and a link in a proposal sent last month leads nowhere. That is a migration stopped one step too early. Before rebuilding, map the old addresses, choose appropriate destinations and test redirects on the public domain. Old messages, bookmarks and search results do not move by themselves because the website has a nicer home.

No one can honestly promise that changing a site will never cause visibility to fluctuate. An inventory, appropriate destinations, tests and monitoring can reduce the risk of abandoning URLs. This workshop is about that responsibility, not a guarantee of a particular search ranking.

Gather old URLs from more than one place

Start with the current sitemap, navigation and article list. Add downloads, campaign URLs, language versions and pages no longer in the menu. If available, review traffic and error data. No single source necessarily covers the entire historical site.

Record the complete URL, including domain, protocol and relevant parameters. An old subdomain may need its own handling. Do not automatically discard parameters before understanding them: some measure campaigns, while others select content, a language or a document.

For each address record its title, material type, status and importance to the visitor. Connect this work with the information architecture of the new site (in Polish). Decisions about the new structure and the fate of old URLs should be made together, not in two unrelated documents.

Map each old address to a new answer

The map should contain the source URL, destination material, expected status and reason, plus the person approving it and the test result. Not every entry needs a new page. You may retain the address, move it to a suitable successor, combine content or deliberately withdraw it. For a catalogue rebuild, connect this map to the product content model so the successor represents the right item and its current information. The guide to product catalogue data (in Polish) explains how to structure those records.

Consider a hypothetical example: two old pages describe consecutive stages of one service and the new offer covers both. A shared destination can be justified. An old guide to a discontinued product is different if the new offer has nothing to do with it. Redirecting that guide to an arbitrary page does not preserve the meaning of the old link.

Google warns against unrelated redirect targets, including sending many different pages to a home page. We recommend approving difficult entries individually. A broad technical rule should not replace the editorial decision about what the content means.

Distinguish a move from an absent resource

HTTP 301 means a resource has permanently moved (source in English) and the server should provide the new URL in the Location header. For ordinary pages it is a clear way to handle the old location. Google also identifies HTTP 308 as a permanent redirect. Pay attention to request-method behaviour when moving an endpoint that receives a form submission, not just a descriptive page.

404 means the resource was not found (source in English), without deciding whether the absence is permanent. 410 describes a resource that is no longer available and whose absence is considered permanent (source in English). The choice should reflect the actual decision about the material, not a desire to hide every error in a report.

A page explaining that material is missing can help someone find the offer or search. Its appearance does not replace the correct server status. “Not found” shown with HTTP 200 differs from an actual 404. Record checks of both layers in the acceptance report.

Keep redirects direct and test exceptions

Aim for a direct path from the old URL to the correct final destination. A chain of hops is harder to inspect and adds waiting. Do not add a new rule on top of an old one without checking the full path. Record both the expected initial status and final URL in the map.

Test general rules separately: domain changes, www, extensions and slashes. An earlier pattern can capture an exception for an important article. Check for self-redirects and loops between two variants as well.

Do not put migration logic only in a script that runs after the application loads if the host can return the appropriate HTTP redirect. The visitor should receive the right response at the old address. This differs from a button leading to an offer: that button should remain an explicit link the visitor chooses.

The new site should not continually route its own links through old URLs. Update navigation, article links, the footer, cards and documents you can change. Redirects help handle history; they do not replace housekeeping in the new site. Point links directly to the approved URL.

Google describes canonical as a signal for the preferred version of similar content. It does not redirect the visitor. After migration compare canonical with the actual final URL and the sitemap entry. An old canonical can conflict with the new deployment's other signals.

Aeneia conceptual photography

When introducing language versions, do not send every old page to the Polish home page merely because the structure is simpler. Decide whether an equivalent exists or the material is withdrawn. Technical SEO before launch (in Polish) covers URL and public-content checks in more detail.

Include files and contact routes

A PDF, presentation or manual may be forwarded directly more often than the page from which it was once downloaded. Check the filename and availability, the meaning of the new version and how the old one is handled. A document covering something different should not impersonate the former material merely to make the address respond.

Check the form, calendar and submission endpoints too. The contact page may work while a click still sends a request to an old service. Acceptance of a B2B form (in Polish) requires following the whole path to the place where the message is handled, not merely looking at a success message.

When changing domains, assign responsibility for keeping the old domain. Without access to the old host or domain, even well-planned redirects can stop working. The handover should state the term and conditions of maintenance, a named owner and a renewal reminder.

Test before and after launch

Before publication, test the map in an environment that reproduces URL handling. After publication repeat the tests on the real domain. Different hosting configuration can make a local result differ from what visitors receive. Open a deep page without first visiting the home page and refresh the tab.

For each important entry record the initial status, subsequent steps, final status and title, and whether the content matches the map. A tool can traverse the list, but a person must assess the meaning of the destination. HTTP 200 does not say whether an old guide reached the right successor.

Record rollback readiness and the conditions for that decision. Not every uncertainty requires an immediate rollback of the whole site. Prepare a procedure for redirect loops, unavailable contact or widespread missing content, and make sure responsible people know it before launch.

How do you test one difficult URL?

Choose an old article with a long address and a campaign parameter. Open that exact version first, then the version without the parameter. Record whether both reach the intended content and compare the final URL with the map. Do not manually change the path halfway through the test: that would hide a defect in the real link.

Use the back button and open the old link in a new tab. Check a document or form available from the destination as well. This scenario does not replace checking the whole list, but it can reveal dependencies that one response status cannot. Keep it as an example for retesting after a fix.

Not every old address has a suitable successor. In those cases prepare a 404 page that helps recover context (in Polish). A helpful error page must work with the correct server response: a friendly message does not turn a missing page into a working one.

Monitor the history instead of deleting it after acceptance

After launch observe URL errors, contact routes and important destinations. Not every 404 proves a poor migration: some requests may concern random paths that never existed. Compare them with the map and real historical material to prioritise repairs.

Google recommends retaining redirects as long as possible, generally for at least one year. That is not an automatic deletion date after twelve months. If people still use old links, keeping them longer may be justified. This is search-provider guidance, not a promise of when migration processing will finish.

  • The map includes pages, files and historical variants.
  • Destinations are semantically appropriate, not merely available.
  • Redirects have no loops or unnecessary chains.
  • Internal links and canonical point to approved URLs.
  • Contact has passed a real delivery test.
  • Monitoring and maintenance have an owner.

Include links stored outside the site: email signatures, proposals and QR codes. Change them where you can. A printed piece cannot be corrected from the site's menu, which is a good reason to keep a meaningful response at the old path and not treat migration as one-off configuration cleanup. Separately test the journey from a printed QR code to the right page, including its destination and an alternative that does not require scanning. The article on printed QR codes (in Polish) examines that journey and its alternatives.

Combine this evidence with website acceptance (in Polish) and post-change speed measurement. The Core Web Vitals measurement guide (in Polish) sets out what to measure. Planning a rebuild? Explore Aeneia Design.

Aeneia Design

Prepare an export of old URLs and describe the scope of the migration before the old site is switched off. This lets the team plan appropriate destinations and their acceptance. Plan a rebuild with a map of the old URLs.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear