Know the scope before a large change
Practical limits for rules, local analysis, checks, approvals and retained data.
Rules and requests
RedirectNest handles GET/HEAD requests that reach WordPress. Server/CDN redirects, caches and other plugins can affect responses outside it. The limit is 5,000 rules including at most 200 advanced rules, with uploads below 2 MB. Exact paths are case-sensitive and trailing slashes distinct by default. Local rule tests make no HTTP request.
Request conditions use temporary 302/307 responses and require source-path cache exclusions. Login/role conditions were introduced in Free 0.6.2; additional request conditions in Free 0.7.0. They are not access controls. Use the current matched pair and test real visitor contexts.
Local analysis and content coverage
| Tool | Scope |
|---|---|
| Smart repair | At most 3 lexical candidates from 500 public pages; up to 500 reviews and 25 decisions per approval batch. |
| Auto-Mapper | Two local UTF-8 XML urlset uploads, each at most 2 MB and 5,000 URLs. No sitemap-index expansion. Explicit suggested or custom-target decisions; 25 rows per review page. |
| Content scan | Each scope: up to 1,000 public password-free posts/pages, 500 targets, five source examples per target and 2 MB of state, so it may stop earlier. Continue into later scopes. At most 512 KB per post and 2,000 anchors per worker slice. Stored content only; no rendered dynamic content. |
| Link cleanup | One eligible classic HTML page or supported stable core paragraph, list and button blocks per approval. At most 512 KB and 200 exact matching anchors. InnoDB and native revisions required. |
Missing coverage is not a clean bill of health. Suggestions compare words and paths; they do not prove content relevance. None of these tools estimates revenue, unique people or match confidence.
Plan around retention and stale approvals
Deletion reviews (100 maximum), repair queues, mapper reviews, scans and cleanup records expire after 30 days. Repair and content-approval previews expire after 15 minutes. Lifecycle intentions expire 90 days after their latest edit or requested review date. Migration preflight checks expire after 24 hours; changed rules or relevant content can invalidate evidence sooner.
Retention, daily path limits, noise filtering and ignored prefixes are included in Free. Seven days and 1,000 distinct missing paths per day are the defaults; retention can be set to 7, 30 or 90 days. There are ten saved migration workspaces, ten previous-project reports and twenty rule snapshots. History and migration cleanup uses a 90-day retention period. Keep WordPress cron working, and manage exported files, native revisions and backups separately.
Use the right kind of recovery
A ruleset snapshot replaces the entire current ruleset; it cannot restore content, server configuration or caches. Link cleanup restores one exact unchanged result through its verified revision. Independent backups cover broader WordPress recovery. After the 0.7.1 storage upgrade, do not downgrade either edition below 0.7.1.
Read HTTP check limits, privacy controls and rule recovery before relying on a large automated workflow.
Review queues and care history
Free retains up to 1,000 per-path 404 review decisions for 30 days; ignoring is a review filter, not a logging exclusion. Auto-Mapper retains one review for 30 days within 4 MB. Content scans retain ten scope summaries for 30 days and at most 50 dated target observations per scope within a 2 MB archive. Monitoring retains up to 90 run summaries for 90 days within 1 MB, with 25 failure details per run. Storage bounds can remove older detail before the time limit.
Manual scan continuation needs request authorization. Optional recurring content scans are off by default, offer daily or weekly intervals and use WordPress cron, which can run late. External-target authorization remains separate. These scans do not add email alerts. Stopping discards in-flight results. Rule monitoring and its existing optional alerts are configured separately.
Proposal and reversal limits
Up to 100 exact-rule proposals are retained for 90 days within 512 KB. A proposal-only user needs view and proposal capabilities and cannot edit live rules. A different administrator reviews and publishes. Existing edit grants continue to allow direct editing; proposal access does not turn them into an approval-only role.
Pro retains up to 20 change-batch receipts for 90 days, but reversal also requires both original snapshots, which may expire earlier. Later changes to affected rules or loops block reversal. The administrator-, site- and generation-bound preview expires after 15 minutes. This is bounded rule reversal, not unlimited undo.
These guides describe Free 1.1.2 and Pro 1.1.2. Current downloads and availability.