Redirection Manager

When you delete or move a post, the old URL breaks. Redirection lets Linkilo automatically (or manually) redirect visitors from the old URL to a new one. Replaces the Redirection WordPress plugin entirely.

What this is

A redirect manager built into Linkilo. Handles 301s (permanent redirects), 302s (temporary), and regex rules. Stores them efficiently in the Linkilo database — doesn't bloat your WordPress options table the way the legacy Redirection plugin does.

Turn on auto-redirect on delete

The killer feature here: when you delete a post, Linkilo writes a redirect automatically.

1. Go to Linkilo → Settings → Redirection (under the Tools group).

One card: Auto-redirect deleted pages.

Create redirects automatically

Master toggle. When ON, every time a post or page is trashed, Linkilo writes a 301 redirect for its old URL.

Where to send visitors

Dropdown:

• Homepage — redirect to your site root
• Let it 404 — preserves the not-found behavior (no redirect created)
• Custom URL — redirect to a URL you specify

Custom URL

Full URL including https://. Only used when the dropdown above is set to Custom URL.

Send to the post category page instead

When ON, deleted posts go to their primary category page instead of the default target above. Overrides the dropdown for posts that have categories.

How long to keep each redirect

Dropdown: 1 year / 2 years / Permanent.

Click Save Settings.

View and manage redirects

Go to Linkilo → Redirection in the WordPress sidebar (top-level menu).

You'll see a table of every redirect:

• Old URL
• New URL
• Type (301 or 302)
• When created
• Action buttons (Edit, Delete)

Add a manual redirect

1. On the Redirection page, click Add Redirect.
2. Enter: – Old URL — the broken or moved URL – New URL — where to send visitors – Type — 301 (permanent) or 302 (temporary)
3. Click Save.

The redirect is live immediately.

When to use 301 vs 302

• 301 permanent — for real moves. Google updates its index to use the new URL.
• 302 temporary — for short-term moves. Google keeps indexing the old URL.

Use 301 for almost everything. 302 only when the move really is temporary (e.g., redirecting to a maintenance page for an hour).

Regex rules

For pattern-based redirects (e.g., redirect every /old-blog/ URL to /blog/), use a regex rule.

In the Add Redirect form, check the Regex box, then write your pattern in the Old URL field.

Example: redirect all /old-blog/{anything} to /blog/{anything}:

• Old URL: ^/old-blog/(.*)$
• New URL: /blog/$1
• Type: 301
• Regex: ✓

Common Questions

Will redirects affect SEO?

Done right, redirects PROTECT your SEO. When a URL changes, Google sees the 301 and transfers ranking to the new URL. Without a redirect, the old URL becomes a 404 and you lose ranking.

Will old redirects accumulate forever?

The How long to keep each redirect setting cleans them up. After the time period, auto-created redirects are removed.

Manual redirects you added yourself stay forever unless you delete them.

What happens if I delete a post and forgot to set up Auto-redirect?

The old URL returns a 404. To fix it after the fact, manually add a redirect via the Redirection page.

Can I import redirects from another plugin?

Not directly through the UI. You can export from the old plugin to CSV, then add the redirects manually through Linkilo. For large imports, contact support — there's usually a workaround.

Will Linkilo conflict with the standalone Redirection plugin?

Yes — don't run both. Disable the legacy Redirection plugin after you've migrated your rules to Linkilo. Two redirect engines fighting over the same URLs leads to unpredictable behavior.

What happens if Old URL matches an existing page?

Linkilo's redirect runs before WordPress's routing, so the redirect wins — visitors go to the new URL even if a post exists at the old URL. Useful for forcing canonical URLs.

Can I redirect from external domains?

No. Linkilo only handles URLs on YOUR site. External-to-external redirects aren't in scope.

How many redirects can I have?

No hard limit. Linkilo handles 10,000+ redirects efficiently because it uses indexed database lookups, not the bloated options-table approach of the legacy Redirection plugin.