Turn approved URL moves into rules your hosting actually applies.
A URL map identifies the destination; the delivery platform must execute the move. ImbaHub can implement a defined redirect ruleset against approved targets, then test precedence and unaffected addresses. The scope follows your actual CDN, hosting and application setup, with deployment agreed separately.
- Map
Approved targets and exceptions are explicit.
- Rule layer
The right platform applies the intended match and order.
- Response
The request follows the decision without unintended captures.
A rule's position in a file alone does not establish its effective precedence.
The hosting rule is correct but the CDN sends the request elsewhere. Which controls the result?
The actual execution chain. Identify the earlier terminating action and retest after an agreed correction.
Start with approved targets and real execution layers
Each affected address needs an agreed destination or another explicit outcome. Unresolved content choices go back to the owner rather than defaulting to the homepage. Record addresses that must keep working unchanged, too.
Identify CDN, hosting, application and legacy redirect settings. A local static server cannot prove the behavior of a different hosting layer. We establish where the first response originates and which configurations can compete.
Translate the matching rules for your platform
Exact paths, patterns and exceptions need the syntax and execution order of the selected platform. A rule at the top of a repository file may never run if an earlier CDN action already terminates the request.
For a fictional example, an old article section moves while one archive page stays available. A broad pattern can capture both unless the exception has effective precedence. Test an intended article move and the archive that must stay put.
| Part | Decision before configuration | Evidence |
|---|---|---|
| URL map | Which target is approved? | Expected target remains independent of observed errors |
| Execution layer | Where is the response decided first? | Active layer identified |
| Matching | Exact address or justified pattern? | Intended and unintended matches tested |
| Parameters | Which values are kept or changed? | Functional values follow the decision |
| Rollback | Which configuration can be restored? | Previous version and owner recorded |
Protect function and language during the move
The target must serve the intended task and language. Define query string, host variant and trailing slash handling where relevant. A parameter that controls functionality must not be discarded as though it were merely an analytics label.
Form endpoints, APIs and static assets need protection from broad page rules. Request methods and environments may require separate exceptions. We implement the agreed boundary and document dependencies outside it.
Hand over configuration with test evidence
A first scope can cover one approved URL group, one platform and a repeatable test selection. Choosing new content targets, rebuilding applications and migrating the whole site are separate pieces of work. The proposal follows a review of your map and infrastructure.
The handover records configuration, positive and negative cases, observed responses and rollback responsibility. Passing a test does not guarantee rankings or authorize deployment. The actual hosting configuration needs verification for an agreed launch.
Sources and further reading
Questions, answered
Is a redirect line in the repository enough?
No. Confirm that it reaches the active hosting configuration and controls the response.
Can rules be copied across hosting providers?
Check syntax, matching and execution order first. Translate the decision for the actual environment.