Skip to page content

In short

  1. Make sure no one is linking to your content or that you can quickly notify them of the link change
    1. in Cascade (via checking Relationships)
    2. print publications
    3. email campaigns
    4. external websites
  2. Make sure the new name meets proper naming conventions
  3. Rename the content

Rename an Asset in Cascade

There are very few reasons why you would need to rename an asset. This is partially due to the fact that your website and its contents are already known to search engines, analytics, and perhaps even other websites using your content. 

Before you consider renaming your assets, you should check the naming standards for your particular asset. For example,

if it is a faculty or staff listing, the "people" name should remain the same. If it is the homepage of a website, the "index" name should remain the same.

If the name is already concise enough, using proper extensions (if it is a file) and other naming conventions, then you should leave the name alone and contact Web Services about your naming concern.

The second pre-check you should do is check the relationships your asset has with other websites. You can start by going to More on the asset in question, selecting Relationships, and viewing the potential broken links that may be caused by your name change.

If your asset is part of your dynamic right hand navigation, you will not see it in this list. Instead, check that it is in your navigation by previewing your website and selecting each link that you think may be this page to determine if it is in your navigation.

Renaming your own pages will require you to republish your entire website. Renaming your pages that are shared by other websites will require you to contact each respective owner and ask them to publish their websites as soon as possible.

Additionally, if your asset is being used by external websites or submitted in reports for auditing purposes, you need to make sure you are not changing something that will have adverse effects on those websites and reports. If you can contact anyone to notify them of the changes you are making, then your adverse effects will lessen.

However, they don't disappear. Any renaming of an asset causes breaks in analytical data and SEO rankings. Search engines know you from your previous location and have ranked you for that address. When you change locations, search engines don't know the new location is the same asset as the old location, so it is treated as an entirely different address with different rankings. 

The same thing occurs with the analytical data tracking the usage of your old address versus the new address. It starts entirely over with the new address instead of carrying the data over because it doesn't recognize these two assets as being the same. Therefore, we cannot provide analytical reports comparing progress from period to period during the time of the switch. Truly, if an asset is already live on the Tarleton website, you should typically not be renaming it.

But in the off-chance that you do need to rename an asset, find the asset, select More, Rename, and then enter the New Asset Name, making sure to still comply with naming conventions. Since this does affect so many areas, much like Moving an asset, you will need to go through the same Unpublish Content process, checking the box for Production Server before selecting Rename.

Be mindful of renaming pages. In order to keep them organized and understandable, you need to make sure your underscore folder with the content module blocks for your page has the same name, plus the underscore character in front of the name. Therefore, renaming a page is a two step renaming process.