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 uploads, each at most 2 MB / 5,000 URLs; explicit row decisions.
Content scan	At most 1,000 posts/pages, 500 destinations and 5 retained source pages per destination; no rendered dynamic content.
Link cleanup	One eligible classic HTML page per approval; InnoDB and native revisions required.

Missing coverage is not a clean bill of health. Lexical matching is not semantic understanding and does not prove 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.

Free counts default to seven days and 1,000 distinct missing paths per day; Pro can adjust retention to 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.