Redirects
The Redirects plugin controls Joomla’s Redirects component: creating, testing and fixing redirects, and handling collected 404 errors.
These tools cover the Redirects component (com_redirect) and require Senso MCP 1.6.0 or later. They are only offered to the assistant if this component is enabled on the site. Every action requires access to the Redirects manager (core.manage), as in the administrator area, in addition to the permission indicated in the “Required permissions” column. Two separate permissions are offered when signing in: reading redirects and managing them.
Diagnostics
Understand what happens when a visitor opens a URL.
| Tool | Function | Required permissions (ACL) |
|---|---|---|
get_redirect_status | Overview: whether the System - Redirect plugin is enabled, 404 collection, advanced mode, number of rules by status and pending 404s | Admin access — core.manage |
list_redirects | List rules and collected 404s (filters, sorted by number of visits) | Admin access — core.manage |
get_redirect | Find a rule by its ID or source URL | Admin access — core.manage |
test_redirect | Test a URL: applied rule, final destination, chains and loops, actual server response | Admin access — core.manage |
Management
Create and correct redirects, and link 404s to the right page.
| Tool | Function | Required permissions (ACL) |
|---|---|---|
create_redirect | Create a redirect, then verify that it actually works | Admin access + Create — core.manage + core.create |
create_redirects_bulk | Create up to 200 redirects at once, with an optional simulation | Admin access + Create — core.manage + core.create |
update_redirect | Modify a rule (only the fields provided are changed) | Admin access + Edit — core.manage + core.edit |
set_redirect_state | Enable, disable, archive or move to the trash | Admin access + Edit State — core.manage + core.edit.state |
resolve_404s | Send collected 404s to the right page | Admin access + Edit — core.manage + core.edit |
Cleanup
Clear things up in two stages: a preview first, then execution after you approve it.
| Tool | Function | Required permissions (ACL) |
|---|---|---|
delete_redirects | Permanently delete rules in the trash | Admin access + Delete — core.manage + core.delete |
purge_collected_404s | Delete collected 404s with no destination (the noise left by bots), based on their age and number of visits | Admin access + Delete — core.manage + core.delete |
Good to know
- Joomla only redirects a URL that returns a 404 error: a rule whose old page still exists will never be triggered.
test_redirectandcreate_redirectcheck this and issue a warning. - The source URL is stored as a lower-case path (
/old-page): the rule works with or without www, on a development copy and regardless of the capitalisation entered by the visitor. - A 404 already collected for the same URL is reused, along with its visit count, instead of being duplicated.
- Loops are rejected. If the destination is itself redirected, the assistant flags it, or points directly to the final URL with the
flattenoption. - A code other than 301 (302, 307, 410…) requires advanced mode, which must be enabled in the Options of the Redirects manager.
- A live check counts as a visit to the URL being tested.
- Creations, modifications, status changes and deletions appear in Joomla's action log.
Prompt examples
“List the 20 most visited 404 URLs and suggest a destination page for each.”
“Why isn't the redirect from /old-catalogue working?”
“Delete the collected 404s that are more than 30 days old and have only had one visit.”