UrlEdge
Core Features

Redirect Types Explained

Choosing the right HTTP status code is critical for SEO. It tells search engines and browsers how to handle redirected content.

301 Moved Permanently

Status: Permanent • Cacheable

This is the standard redirect for SEO. It passes most ranking power to the new URL and browsers cache it aggressively.

docsLayout.ui.useWhen:

  • • Migrating a domain permanently
  • • Merging two websites
  • • Fixing a typo in a URL structure
  • • Switching from HTTP to HTTPS

docsLayout.ui.avoidWhen:

  • • Running a temporary promotion
  • • A/B testing pages
  • • Geo-targeting (unless permanent)
  • • You might revert the change soon

302 Found / 307 Temporary

Status: Temporary • Non-Cacheable

These codes tell search engines the content has moved temporarily, but the original URL should remain canonical.

docsLayout.ui.note:
Why 302 vs 307? 307 preserves the HTTP method explicitly, while 302 is broader and more widely supported. For most link routing use cases, both work similarly in practice.

308 Permanent Redirect

The modern version of 301. It guarantees that the HTTP method (POST, PUT, etc.) is preserved during redirection.

docsLayout.ui.recommendation: Use 308 for API redirects where preserving POST data matters. Use 301 for standard page redirects when maximum compatibility is preferred.

Advanced Response Types

Masked

IFrame Masking

Show the destination content while keeping your custom domain in the browser address bar.

Proxy

Reverse Proxy

Serve upstream content through UrlEdge while keeping full control over the public-facing URL.

Custom

Custom Response

Return a static HTML or JSON response directly from the edge for maintenance pages or light APIs.