Glossary · Glossary

Redirect

A redirect sends users and crawlers from one URL to another when content moves or route variants need consolidation.

A redirect sends users and crawlers from one URL to another. It is used when a page moves, when an old route should resolve to a new route, or when duplicate URL variants need to consolidate around a preferred destination.

Redirects are part of route hygiene. They help users avoid dead ends and help search systems understand what happened to a URL after a migration, rename, protocol change, trailing-slash cleanup, or content consolidation.

Why it matters

Without redirects, old links break. Users hit errors, crawlers waste requests, analytics split across outdated paths, and search systems may keep discovering URLs that no longer represent the site’s current structure.

For Geolyze-style static content, redirects matter whenever glossary slugs change, guide URLs are renamed, locale paths are reorganized, or old campaign paths need to resolve to durable editorial pages.

How it differs

A redirect changes the URL journey. A canonical URL leaves the page accessible while suggesting which URL should represent duplicate or similar content. A noindex directive asks search engines not to show an accessible page in results.

If users and crawlers should always land somewhere else, a redirect is usually cleaner than relying on a canonical tag. If a variant page must remain accessible for users but should consolidate signals, canonicalization may be more appropriate.

Examples

A simple static redirect rule can map an old path to a current path:

/old-glossary/canonical/ /glossary/canonical-url/ 301

The HTTP response then tells the client where to go:

HTTP/1.1 301 Moved Permanently
Location: https://www.geolyze.org/glossary/canonical-url/

Permanent redirects are for moves that should remain in place. Temporary redirects are for short-lived routing, testing, or temporary availability changes. The choice should reflect the actual intent.

How teams use it

Teams use redirects during site migrations, content consolidation, slug cleanup, protocol changes, and route repairs. A practical review asks:

1. Does each old URL redirect directly to the best current URL?
2. Are permanent moves using permanent redirects?
3. Are internal links updated to point to the final URL?
4. Do sitemap entries list final canonical URLs, not redirecting URLs?
5. Are redirect chains and loops removed?

Common misunderstanding

A redirect is not the same as a canonical tag. A canonical tag is a representative-URL hint. A redirect changes the request path for users and crawlers. Using the wrong one can leave duplicate pages accessible, send users through unnecessary hops, or make search systems choose a different representative URL than intended.