FFAS Redirection Manager

Description

FFAS Redirection Manager lets site administrators create URL redirects without manually editing server configuration files.

Each rule contains a source URL, a destination URL and a redirect type. Source and destination values can be entered as complete URLs or as paths such as /old-page and /new-page. Relative paths are converted to URLs for the current site.

Standard URL redirects

Use a standard rule when a page has moved, a URL has changed or visitors should be sent to a different destination.

• Choose 301 – Permanent when the old URL has permanently moved.
• Choose 302 – Temporary when the move is temporary.
• Set a start date/time and an end date/time for a 302 rule. Leave the start blank to begin immediately; an end is required when saving a 302 rule.
• Review, edit or delete existing rules from the same dashboard page.

Redirects are matched against the requested path, ignoring a trailing slash. When the source includes a query string, that query string must also match. A source entered as a full URL is limited to that host. Destinations may be on the current site or an external website selected by an administrator.

WordPress installations in a subdirectory are supported. On a site at https://example.com/wordpress, both /old-page and /wordpress/old-page resolve to the same source without adding the subdirectory twice.

Dates use the WordPress site timezone shown next to the start field. A scheduled 302 is inactive before its start and stops at its end. The original page then resumes its normal behaviour. Legacy imported rules without dates remain compatible; edit them to add an end date. Redirect responses send cache-control headers to avoid retaining a scheduled redirect past its end. A 302 is a different HTTP status from a 301 even without a schedule.

First-login redirects

Enable Only apply on first login to use a rule as a one-time destination for a user’s first detected login.

The plugin records login state in WordPress user metadata. When a qualifying user logs in, the first enabled and unexpired first-login rule is applied once and then marked as completed for that user. Tracking begins after the plugin is activated, so the first login detected by this plugin is treated as the user’s first login for this feature.

First-login rules can be useful for sending a new user to an onboarding page, account instructions or another administrator-selected destination. They do not replace WordPress role and capability controls.

Settings export and import

The Export / Import screen can download this plugin’s redirect rules as a JSON settings file and restore a compatible FFAS Redirection Manager settings file on another site. Review imported destinations before using them on a production website.

The plugin stores its rules in the WordPress database. It does not write redirect rules, robots.txt or LLMS.txt files into the WordPress installation directory.

Privacy

The plugin does not send redirect rules or login-tracking data to FFAS or any external service. Rules are stored in the WordPress database. First-login state is stored as user metadata on the website.