Redirects

If you move, rename, or delete a page, you can create a 302 redirect to send users to a new page so they don’t see a 404 error page. Redirects can also be used to create short vanity URLs that send users to a deeper URL path within the site.


You can right click on any page in Sitecore and insert a new Redirect item. The folder where you insert the redirect controls the parent path, and the name of the item controls the last part of the path. Then you set the destination page using the Redirection URL field (click the Insert link button above the field to open the page selection popup).


For example, if you want to redirect the URL path /atmore/dining/starbucks-coffee to /atmore/dining/starbucks, first browse to the Atmore dining folder (/sitecore/content/Wind Creek/Wind Creek/Home/Atmore/Dining). Right click on that folder and insert a new redirect named “Starbucks Coffee”. Notice how the name of the item matches the last part of the URL you want to redirect (“starbucks-coffee”). Then click the Insert link button above the Redirection URL field and select the existing Starbucks page. Finally, publish the new item.



Sitecore also supports Redirect Pages, but these are used less frequently on the Wind Creek site. If you use a Redirect Page instead of a Redirect, Sitecore will insert a placeholder link for that page in the dynamic navigation menus (e.g. the footer links).

 

If you’re creating a redirect for an existing item, you will need to delete or rename the old item so you can create a new redirect item with the same name in that folder (this is because Sitecore requires item names to be unique within a folder). If you decide to rename instead of delete the old page, make sure you check the Never Publish box so it gets unpublished. This prevents the old pages from being crawled and indexed by search engines. Make sure you publish the new redirect item, along with all the old pages/folders that have been deleted or renamed. The easiest way to ensure all your changes have been published is to publish the parent folder.


For example, if you want to start redirecting the 2022 Atmore promo pages, rename the existing 2022 year folder to “2022 Old” (or something similar), and set it to never publish. Then create a new redirect item in the same folder called “2022” and set the destination page. Then publish all these changes by publishing the parent item (the entire Atmore promotions folder).


Note that redirect items do not automatically include all child URL paths. For example, creating a redirect for the 2022 year folder will redirect /atmore/promotions/2022, but not /atmore/promotions/2022/january/lucky-13. To accomplish this, create another redirect item called * (the asterisk character) under the 2022 redirect item. An item with this name acts as a wildcard that matches all paths under that folder.