ARTICLES & GUIDES

WordPress redirects.
Practical guides.

Practical notes on redirects, migration checks
and looking after the links people still use.

Migration notes

Before you change a URL

A short checklist for giving an old link a sensible new home.

Read the note ↗

Field guide

What a verification report can tell you

Understand passed, mismatched and unverified results before signing off a migration.

Read the note ↗

WordPress redirect tutorials

301, 302, 307, 308 or 410: choose a WordPress redirect response

Choose the right response for a permanent move, temporary change or retired page. Learn how redirect methods and browser caching affect testing.

Read the note ↗

WordPress redirect tutorials

WordPress query parameters: preserve them or match them?

Understand the difference between carrying query parameters to a destination and using query conditions to select a redirect in RedirectNest Free and Pro.

Read the note ↗

WordPress redirect tutorials

Import WordPress redirects from CSV: a safe checklist

Prepare a small CSV, inspect the import preview, handle duplicate sources and verify the resulting redirects before importing a larger WordPress migration.

Read the note ↗

WordPress redirect tutorials

How to troubleshoot WordPress redirect loops and chains

Trace each redirect hop, check competing WordPress and hosting rules, and distinguish cached responses from current configuration before changing a live site.

Read the note ↗

WordPress redirect tutorials

A WordPress domain migration redirect checklist

Plan old-to-new URL mappings, check destination pages and preserve a rollback path before moving WordPress content to a different domain.

Read the note ↗

WordPress redirect tutorials

WordPress 404 errors: redirect, repair or return 410?

Decide whether a missing WordPress page needs a relevant redirect, a repaired link or an intentional 410 response instead of a blanket homepage redirect.

Read the note ↗

LOOKING FOR THE HOW-TO?

Less theory.
More next steps.

Follow a task from start to finish in the documentation.

Find a guide ↗