When a redesign or domain change alters URLs, Google’s guidance is to map old URLs to new ones, use server-side permanent redirects without chains, and keep them generally at least a year. Build that map before launch.
\nGoogle Search Central advises building a list of old URLs from sitemaps, server logs or analytics, Search Console’s links report and the content management system, including embedded images, videos, JavaScript and CSS, then deciding where each one should redirect.
\nGoogle recommends server-side permanent redirects such as 301 or 308, redirecting directly to the final destination rather than chaining, and avoiding redirecting many old URLs to one irrelevant page such as the home page, which may be treated as a soft 404. Each new URL should carry a self-referencing canonical tag, and any noindex rules used during staging must be updated.
\nA Change of Address is submitted in Search Console only for moves between domains or subdomains. Google says to keep redirects generally at least one year, submit the new sitemap, and expect temporary ranking fluctuation; a small or medium site can take a few weeks for most pages to move.
\nUse this whenever URLs change, including moves to a new CMS that generates different paths. Google notes that small and medium sites are best moved all at once, while large sites can move one section at a time.
\nDSE recommends making the old-to-new URL map a launch deliverable that must be complete and tested before a redesigned site goes live. Store the map in a reviewable file, implement it as server or CMS redirect rules, update internal links to new URLs, and plan to keep the redirects in place for at least a year.
\nBefore and after launch, run the full old-URL list through a script that records the status code and final URL, failing any chain, non-permanent redirect, 404 or unexpected home-page landing. Spot-check key URLs with the Search Console URL Inspection tool and watch indexing and traffic for both old and new URLs.
\nGoogle Search Central — Site moves with URL changes. Reviewed October 18, 2026.
", "content_text": "When a redesign or domain change alters URLs, Google’s guidance is to map old URLs to new ones, use server-side permanent redirects without chains, and keep them generally at least a year. Build that map before launch.\nSource facts\nGoogle Search Central advises building a list of old URLs from sitemaps, server logs or analytics, Search Console’s links report and the content management system, including embedded images, videos, JavaScript and CSS, then deciding where each one should redirect.\nGoogle recommends server-side permanent redirects such as 301 or 308, redirecting directly to the final destination rather than chaining, and avoiding redirecting many old URLs to one irrelevant page such as the home page, which may be treated as a soft 404. Each new URL should carry a self-referencing canonical tag, and any noindex rules used during staging must be updated.\nA Change of Address is submitted in Search Console only for moves between domains or subdomains. Google says to keep redirects generally at least one year, submit the new sitemap, and expect temporary ranking fluctuation; a small or medium site can take a few weeks for most pages to move.\nApplicability\nUse this whenever URLs change, including moves to a new CMS that generates different paths. Google notes that small and medium sites are best moved all at once, while large sites can move one section at a time.\nDSE recommendation\nDSE recommends making the old-to-new URL map a launch deliverable that must be complete and tested before a redesigned site goes live. Store the map in a reviewable file, implement it as server or CMS redirect rules, update internal links to new URLs, and plan to keep the redirects in place for at least a year.\nVerification\nBefore and after launch, run the full old-URL list through a script that records the status code and final URL, failing any chain, non-permanent redirect, 404 or unexpected home-page landing. Spot-check key URLs with the Search Console URL Inspection tool and watch indexing and traffic for both old and new URLs.\nOfficial reference\nGoogle Search Central — Site moves with URL changes. Reviewed October 18, 2026.", "content_markdown": "When a redesign or domain change alters URLs, Google’s guidance is to map old URLs to new ones, use server-side permanent redirects without chains, and keep them generally at least a year. Build that map before launch.\n\n## Source facts\n\n[Google Search Central](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) advises building a list of old URLs from sitemaps, server logs or analytics, Search Console’s links report and the content management system, including embedded images, videos, JavaScript and CSS, then deciding where each one should redirect.\n\nGoogle recommends server-side permanent redirects such as 301 or 308, redirecting directly to the final destination rather than chaining, and avoiding redirecting many old URLs to one irrelevant page such as the home page, which may be treated as a soft 404. Each new URL should carry a self-referencing canonical tag, and any noindex rules used during staging must be updated.\n\nA Change of Address is submitted in Search Console only for moves between domains or subdomains. Google says to keep redirects generally at least one year, submit the new sitemap, and expect temporary ranking fluctuation; a small or medium site can take a few weeks for most pages to move.\n\n## Applicability\n\nUse this whenever URLs change, including moves to a new CMS that generates different paths. Google notes that small and medium sites are best moved all at once, while large sites can move one section at a time.\n\n## DSE recommendation\n\nDSE recommends making the old-to-new URL map a launch deliverable that must be complete and tested before a redesigned site goes live. Store the map in a reviewable file, implement it as server or CMS redirect rules, update internal links to new URLs, and plan to keep the redirects in place for at least a year.\n\n## Verification\n\nBefore and after launch, run the full old-URL list through a script that records the status code and final URL, failing any chain, non-permanent redirect, 404 or unexpected home-page landing. Spot-check key URLs with the Search Console URL Inspection tool and watch indexing and traffic for both old and new URLs.\n\n## Official reference\n\n[Google Search Central — Site moves with URL changes](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes). Reviewed October 18, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/website-redesign-url-mapping-permanent-redirects/", "url": "https://update.dsesecurity.com/updates/website-redesign-url-mapping-permanent-redirects/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-18" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/website-redesign-url-mapping-permanent-redirects/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Map every old URL to a permanent redirect before a redesign changes the site’s addresses", "item": "https://update.dsesecurity.com/updates/website-redesign-url-mapping-permanent-redirects/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/website-redesign-url-mapping-permanent-redirects/#article", "identifier": "https://update.dsesecurity.com/updates/website-redesign-url-mapping-permanent-redirects/", "url": "https://update.dsesecurity.com/updates/website-redesign-url-mapping-permanent-redirects/", "headline": "Map every old URL to a permanent redirect before a redesign changes the site’s addresses", "description": "When a redesign or domain change alters URLs, Google’s guidance is to map old URLs to new ones, use server-side permanent redirects without chains, and…", "abstract": "When a redesign or domain change alters URLs, Google’s guidance is to map old URLs to new ones, use server-side permanent redirects without chains, and keep them generally at least a year. Build that map before launch.", "articleBody": "When a redesign or domain change alters URLs, Google’s guidance is to map old URLs to new ones, use server-side permanent redirects without chains, and keep them generally at least a year. Build that map before launch.\nSource facts\nGoogle Search Central advises building a list of old URLs from sitemaps, server logs or analytics, Search Console’s links report and the content management system, including embedded images, videos, JavaScript and CSS, then deciding where each one should redirect.\nGoogle recommends server-side permanent redirects such as 301 or 308, redirecting directly to the final destination rather than chaining, and avoiding redirecting many old URLs to one irrelevant page such as the home page, which may be treated as a soft 404. Each new URL should carry a self-referencing canonical tag, and any noindex rules used during staging must be updated.\nA Change of Address is submitted in Search Console only for moves between domains or subdomains. Google says to keep redirects generally at least one year, submit the new sitemap, and expect temporary ranking fluctuation; a small or medium site can take a few weeks for most pages to move.\nApplicability\nUse this whenever URLs change, including moves to a new CMS that generates different paths. Google notes that small and medium sites are best moved all at once, while large sites can move one section at a time.\nDSE recommendation\nDSE recommends making the old-to-new URL map a launch deliverable that must be complete and tested before a redesigned site goes live. Store the map in a reviewable file, implement it as server or CMS redirect rules, update internal links to new URLs, and plan to keep the redirects in place for at least a year.\nVerification\nBefore and after launch, run the full old-URL list through a script that records the status code and final URL, failing any chain, non-permanent redirect, 404 or unexpected home-page landing. Spot-check key URLs with the Search Console URL Inspection tool and watch indexing and traffic for both old and new URLs.\nOfficial reference\nGoogle Search Central — Site moves with URL changes. Reviewed October 18, 2026.", "datePublished": "2026-10-18T21:00:06+00:00", "dateModified": "2026-10-18T22:22:06+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/website-redesign-url-mapping-permanent-redirects/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/website-redesign-url-mapping-permanent-redirects/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Map every old URL to a permanent redirect before a redesign changes the site’s addresses" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Checklist", "Information priority" ], "genre": "Checklist", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 348, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Google Search Central — Site moves with URL changes", "url": "https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes" } } ] } }