Native module · Redirects
Keep your links. Native website redirect management.
SGEN runs URL forwarding as a real rules engine inside your admin. Set each rule to 301 or 302, order rules by integer priority so a specific rule wins over a broad one, flip Stop Processing to short-circuit the rest, and dry-run any URL in the built-in Test URL simulator before you publish.
Every rule tracks its own Hits counter and Last Matched time, so you see which redirects are doing work. Draft a rule inactive, test it, then flip it live, and bulk-import an existing map by CSV or JSON when you arrive. It lives in the Redirects module, between Popups and Custom Fields, not in a plugin that breaks on the next update.
Inside the module
Add, order, test, and import, all from the admin.
The Redirects module is a rules engine, not a flat list. Each rule carries a type, a priority, a stop-processing switch, and its own usage counters, and the whole thing reads and writes from one admin screen, the same screen where you manage the rest of your site.
301 or 302 per rule
Choose the type on each rule from a Type select. A 301 passes ranking signals to the new URL, a 302 keeps the old URL in the index for a short detour. You decide per rule, not per site.
Priority ordering
An integer Priority field, default 0, sets precedence: rules evaluate by priority descending, then target ascending, so a specific rule beats a broad one. It is a real ordering engine, not first-match-wins by accident.
Stop Processing
A per-rule Stop Processing switch, on by default, short-circuits the remaining rules once a match lands. Your map stays predictable because one rule can end the chain.
Test URL simulator
Paste a URL and the admin dry-runs the exact match logic, returning "Matched rule: TARGET to DESTINATION", "No rule matched", or "Invalid URL format", without performing the redirect. Confirm a rule before you publish it.
Hits and Last Matched
Every rule carries its own Hits counter and a Last Matched timestamp, so you retire dead rules and confirm the live ones. Lightweight redirect analytics, built into the table.
Bulk actions and search
Multi-select rules and Move to Active, Move to Inactive, or Delete Permanently through Action For Selected and Apply. Search the list by partial source path to find a rule fast.
Dry-run before you publish
Test any URL against your rules before one redirect goes live.
The Test URL field runs your URL through the same matching logic the rules engine uses, then tells you exactly which rule catches it and where it sends the visitor, without performing the redirect. The dry-run is part of the Redirects module, included on every plan.
The simulator reports the would-be match at config time. Use it to confirm the target and destination before you flip a rule active.
Built-in redirect analytics
Every rule keeps its own Hits and Last Matched, so you retire the dead ones.
The rules table is not write-only. Two of its ten columns are an audit trail: a Hits counter that increments each time the rule catches a request, and a Last Matched timestamp shown as a timeago. Sort the list and the rule that earns its keep is obvious, the one that has never fired is just as obvious. Both columns are part of the rule schema, so they travel in the JSON export too.
Counters are usage telemetry inside the manager. Use them to keep your redirect map honest, alongside the Analytics module's traffic reporting.
Pick the right code
301 for a permanent move, 302 for a temporary one.
The two HTTP codes mean different things to search engines, and the module lets you set either per rule. Pick the code that matches the change you are making to your URLs.
301 · Permanent
A move that should stick
Search engines treat the new page as the canonical one and transfer the source URL's ranking signals to the destination. Use a 301 when a page has permanently changed address.
302 · Temporary
A detour for now
Search engines retain the original URL in the index and treat the redirect as short-term. Use a 302 when you are sending traffic elsewhere for a campaign or a maintenance window, then bringing the page back.
Bring your map with you
Import an existing redirect map by CSV or JSON.
SGEN imports your redirect rules from a CSV or JSON file through a drag-and-drop dropzone, then reports total, imported, skipped, and failed counts plus the first errors. The file input accepts .csv and .json. Import adds new rules and skips duplicate targets, so the workflow is import once, then edit in the UI. Export the other direction with two buttons, Export CSV and Export JSON, to back up before a launch or move a map between sites.
One honest note: import writes immediately, there is no preview-then-confirm step, and imported rows arrive active. Treat it as fast bulk import, and review the result in the table after.
Rules that do not collide
Two rails keep your map clean: no duplicate targets, no rule live by accident.
A redirect map goes wrong in two predictable ways: two rules fighting over the same source path, and a rule going live before you meant it to. The module guards both. Saving a rule whose Target already exists is rejected as a conflict instead of silently shadowing the first rule, and a CSV or JSON import adds new rules while skipping any target it already holds. New rules you add in the form start as an inactive draft, Status off, so you build and test before you flip it live.
One module, the whole job
One module. The whole redirect stack, built in.
SGEN ships redirect management in the platform itself. Add a rule, set 301 or 302, give it a priority, test it, then flip it live, all from the Add New form. The module ships with the platform, updates with the platform, and adds nothing to install or maintain.
301 / 302 per rulePriority orderingTest URL dry-runCSV / JSON import
The platform behind the module
In the box on every plan.
2
redirect types, 301 or 302, choosable per rule
10
column rules table: every rule fully observable
23
native modules included on every plan
Questions
Questions about Redirects
Does SGEN support wildcard redirects? +
SGEN matches a class of URLs with regex pattern rules via the Is Regex? toggle, rather than a separate star-wildcard syntax. For a single old-URL-to-new-URL move, use a plain 301. Test any pattern rule in the Test URL simulator before you rely on it, so you confirm the rule catches what you expect.
Do redirects carry my link equity? +
Use a 301 for a permanent move: it is the redirect type that passes the source URL's ranking signals to the destination, which is why search engines treat the new page as canonical. Use a 302 for a short-term detour, since it keeps the original URL in the index. This is standard HTTP-code behavior, you pick the code per rule.
Can I bulk-import my existing redirects? +
Yes. Upload a CSV or JSON file in the Import / Export panel through the drag-and-drop dropzone. Import adds new rules and skips duplicate targets, so it is import once then edit in the UI. Two honest notes: import writes immediately, there is no preview-then-confirm step, and imported rows arrive active, unlike rules added in the form, which start inactive. The import reads the redirect rules from your file, the rules only, not the pages they point to.
If I rename a page's slug, does the redirect happen automatically? +
No. The redirect manager is a separate tool from the page editor, so renaming a slug does not auto-create a rule. The best practice is to add a 301 from the old slug to the new one in the Redirects panel right after you make the change, so the old URL keeps working.
How do I know a rule will catch the right URL? +
Use the Test URL field. It dry-runs your URL against the live match logic and returns "Matched rule: TARGET to DESTINATION", or "No rule matched", without performing the redirect. You confirm the matched rule and its destination before you publish. It is a config-time check that reports the would-be match.
Can I stage a redirect before it goes live? +
Yes. New rules added in the form default to Status off, an inactive draft, so you can build and test the rule, then flip Status on to activate it. Bulk Move to Active and Move to Inactive let you flip several at once. The one asymmetry to know: imported rules default to active, unlike rules you add in the form.
Redirects, included
Your redirect map, managed in the admin. From $39/mo.
Redirects is one of 23 native modules included in every plan, nothing to add on. Plans are priced by how many live sites you run, not by feature. Build and test your rules on the free Sandbox before you pay anything.
From $39/mo, billed annually. $47 monthly. 2-week trial, cancel anytime. Every module included.