Draw the execution chain before testing collisions
List every layer that can issue a redirect, such as CDN, hosting and application. Read the platform's execution model and identify where a matching action ends processing. Do not assume all layers share first-match or last-match behavior.
In a fictional example, a specific archive address stays while a broader article tree moves. Write the intended winner for that collision before running the request. Include an ordinary path that should match only the broad pattern.
Choose positive and negative matching cases
Include an exact source address, a valid pattern member and a similar address outside the intended scope. Add the protected exception, a relevant language path and an asset or API route that must remain untouched.
Try slashes, encoded characters and query values where these affect the rule. Change one dimension at a time so a failure has an explainable cause. Use prepared test addresses within the agreed scope.
| Case | What it isolates | Expected decision |
|---|---|---|
| Exact special case | Precedence over broad pattern | Approved exact action wins |
| Ordinary pattern member | Intended coverage | Broad rule selects the right target |
| Similar unaffected address | Overmatching | No unintended move |
| Protected resource path | Pages versus APIs or files | Agreed delivery stays intact |
| Address in two layers | CDN versus hosting or app | Identified layer returns the intended response |
Observe the active rule and first response
Request without automatically following redirects and record status and destination. Use platform tracing where available to identify the active rule. A final destination alone can hide an earlier layer's incorrect choice.
Reorder or narrow a rule only against a documented decision, then rerun the affected collision cases. Do not revise an expected target just to fit the current error. Also check whether the target can match again and create a loop.
Keep precedence as a maintenance requirement
When a new general rule arrives, retest its intended members and existing exceptions. Record why each exception exists and where it belongs. A future maintainer should be able to understand the order without guessing.
Record configuration version, layer, test address, possible matches, actual winner and retest. Continue with the migration protocol for complete status chains and destination content. An isolated precedence test neither authorises production deployment nor proves how search engines will treat the move.