Redirects

The SG-Admin Redirects module — URL redirect rules, patterns, types, hit measurement.

The Redirects module in the admin is the per-site surface for URL redirect rules. Operators configure source patterns that map to destination URLs; the platform applies the redirects at request time. This page is the Reference definition.

What is this for?

Read this page when you want the structural definition of redirect handling — rule types, pattern matching, and hit measurement.

Good use cases

• You are migrating URLs from a previous platform.
• You are restructuring site URLs and need to preserve external links.
• You hit a "where do I add a 301?" question.

What NOT to use this for

• Step-by-step procedures — open the relevant Guide.
• Per-release shipped change — open What's New or Changelog.

How this connects to other features

• SG-Admin Overview — parent surface.
• Pages — page route changes often need a redirect from the old route.

Where to find it

Open SG-Admin for the active site. Redirects is in the sidebar under the configuration or SEO group. The rule list, add-redirect form, and per-rule hit counters are all reachable from this section. Admin access is required to add or remove redirect rules.

Definition

A redirect rule maps an incoming source URL pattern to a destination URL with a defined redirect type. The platform evaluates redirect rules at request time before serving the requested URL.

The defining property is request-time evaluation. Redirects do not require page or content changes; they intercept the request directly.

Purpose

Define the Redirects module as a Reference layer.

Scope

Covers rule types, pattern matching, hit measurement. Does not cover per-step procedures (Guides) or per-release shipped change.

Rule types

301 (permanent)

Source URL has permanently moved to destination. Search engines update their index.

302 (temporary)

Source URL has temporarily moved. Search engines retain the source URL for indexing.

307 / 308

Method-preserving variants of 302 / 301 used for non-GET requests.

Pattern matching

Redirects support exact-match (literal source URL) and pattern-match (wildcard or regex source) modes. Wildcard patterns capture portions of the source URL for substitution into the destination.

Hit measurement

Each rule carries hit counters per defined window. Operators review hit counts to identify redirects that are no longer needed (zero hits over a long window) or rules that need adjustment (very high hits suggest the redirect should be replaced with the destination becoming the canonical URL).

Constraints and boundaries

Redirects is a Reference area for URL redirect rules.

Do not use for: per-step procedures (Guides), per-release shipped change.

Public boundary

This page is intentionally public-safe.

Examples

Example 1 — Operator migrates URLs from a previous platform

After a site migration, operator adds 200+ 301 rules mapping old URLs to new ones. Search engines update; external links continue working.

Example 2 — Operator restructures blog URL pattern

Operator adds a wildcard 301 mapping /blog/category/* to /blog/topic/$1. All category URLs now redirect to the new topic structure.

Example 3 — Operator audits redirect hits

Operator reviews 30-day hit counts, identifies redirects with zero hits (safe to retire) and very high hits (should the destination become the canonical URL).

Documentation guidance

Use this page as the structural definition for the Redirects module.

Reading order

Open this page when scoping URL changes or migrations.

Related reading

• SG-Admin Overview — parent surface.
• Pages — page route changes.

Vocabulary cross-reference

• Redirect is one source-to-destination mapping rule.
• Source pattern is the incoming URL the rule matches against.
• Destination is the URL the platform redirects to.
• Redirect type is one of 301 / 302 / 307 / 308.

Maintenance discipline

When Redirects changes across releases (new pattern syntax, new redirect type, new hit-measurement surface), update this Reference.

Related reading