← Integrations

Static Shield + Redirection

Redirection is genuinely different from most integrations here: its whole feature is an arbitrary, site-owner-authored table of 301/302 rules checked against every incoming request URL — the opposite of a narrow, fixed endpoint. There's no single pattern to bridge the way a form's submission route has one, so rule matching is classified dynamic rather than forced into a bridge shape that doesn't fit. In practice, that means most of what Redirection actually does won't apply once static serving reduces how much WordPress ever runs for a request — unless the rule table is exported into the static host's own redirect config, or the site runs Hybrid mode so WordPress stays in the loop to evaluate rules live.

Recommended mode

Hybrid

Static behavior

Nothing directly — though a stable rule set can be exported once and baked into the static host's own redirect configuration (.htaccess/nginx rewrites) as a manual step.

Dynamic behavior

Rule matching itself: every incoming request has to be checked against a table that can change at any time in wp-admin. The rule-management screen where rules are authored is a separate, purely admin-side concern with no public exposure of its own.

Bridges & routes

None — and this is a real, structural limitation, not an oversight. Redirection's rules are arbitrary and change whenever the site owner edits one, so there's no fixed route pattern to declare as a bridge the way a form's single submission endpoint has one.

Setup

No special setup for detection — but if you rely on Redirection's rules, decide up front whether this site needs Hybrid mode (rules change often) or a one-time/periodic export to host config (rule set is stable); Static Shield doesn't perform that sync automatically.

Limitations

Static Shield does not currently auto-sync Redirection's rule table into static host configuration. Today, keeping a Fully Static site's redirects correct means manually re-exporting the rule table and updating the host's own .htaccess/nginx rewrites every time a rule changes, or running the site in Hybrid mode instead so WordPress evaluates redirects live. Under Fully Static serving with no host-config export in place, redirect rules simply won't fire for public visitors at all. This has not been behaviorally validated against a live install.