ShadowX canonical and redirect matrix

List expected URL variants

Record HTTP, HTTPS, trailing-slash and obsolete path variants for representative templates. Define one expected final page for each equivalent resource.

Do not invent redirects for unrelated missing content.

Trace the response chain

Capture every status and Location header until the final response. Prefer one direct HTTP-to-HTTPS redirect and avoid loops or unnecessary intermediate hosts.

The final page should return 200 and remain within the intended information property.

Compare page-level signals

Match the HTML canonical, Open Graph URL, internal links and sitemap entry to the final URL. Fix contradictions in the shared template rather than one page at a time.

External ShadowX destinations are not canonical targets for editorial pages.

Test after deployment

Check the homepage, guide index, article, policy page and missing path. Confirm that the custom 404 remains a real 404.

Notify Bing about only the canonical pages whose public signals changed.

Frequently asked questions