TECHNICAL SEO · GUIDE
Friendly URLs and redirects: protecting a redesign
A guide to descriptive URLs, replacing menu links with # and planning redirects during a website redesign.
What makes a URL useful
A clear URL describes content with a consistent structure. Paths such as /en/search-engine-optimization/ or /en/web-design-and-development/ explain a page without technical identifiers. Use readable words, hyphens and one canonical version for each content item.
The # symbol and its limitations
An address fragment identifies a section of a page and is not sent to the server as part of the path. It is valid for navigation within a page but should not replace independent pages that need indexing. A control that only opens a menu should be a button rather than an empty href="#" link.
Take inventory before changing
Collect existing URLs, internal links and URLs appearing in search engines. Identify valuable, duplicate and outdated pages. Decide whether to keep each route, redirect it to an equivalent page or retire obsolete content.
Redirect to equivalent content
When a page permanently changes address, a 301 or 308 redirect communicates the move. It should lead to equivalent content and avoid unnecessary chains. Redirecting all old pages to the homepage may confuse users and search engines. Check both the response and final destination.
Consistent links and sitemap
Update navigation, internal links, canonicals and sitemap to use the chosen addresses. Old files may remain on the server while redirects control external visits. Rules must not affect forms, applications or the blog without reviewing their routes and dependencies.
What to check at launch
Check the homepage, service pages, old destinations, 404 responses and images. A nonexistent URL must not return a valid page with a 200 response. Monitor indexing and errors after launch; migration includes follow-up beyond file uploads.