Page Properties
Update the page name in the following fields:
- Basic
- Title (fix in both language-masters and live copy; break inheritance in live copy for this field only and manually edit)
- Page Title (changing this text may impact SEO)
- Description (changing this text may impact SEO)
- Breadcrumb (used on page and in sitemap web page link)
- Tags, if applicable (refer to Tag Management for more info) (edits may be needed to Tag Label and Tag Path before addressing in this step)
- Card Properties
- Card Title
- Subhead - to add the "Formerly Known As Old Product Name" text, if applicable (for product pages only)
- Card Description
- Alt Text, if applicable for card image
Page Body
- Update the H1 (changing this text may impact SEO)
- Add an Announcement banner below the Top Banner, if applicable (for product pages only)
- Update any other applicable page name references within the body copy
Page URL
"Move" the page to change the URL of the page to reflect the new page name.
Page Redirect
If a redirect is needed to address the URL change, refer to Redirect Process for more info.
Page Tag
Determine if the existing tag can be overwritten or if a new tag needs to be created to address the name change.
- If a new tag is created, then it will need to be applied within the Basic tab of Page Properties of the applicable pages
- Get the new tag translated, add those translations to the Tag interface, and bulk publish the affected language sites to push the changes throughout the language sites
- If an existing tag is overwritten, bulk publish all sites to push the changes throughout the language sites
- Retranslate the existing tag to reflect the new name, adjust the tag translations in the Tag interface, and bulk publish the affected language sites to push the changes throughout the language sites
Refer to Tag Management for more info.
Please note: Tag changes have impacts to integrations between AEM and these other systems as a minimum, so do not change tags until all systems are scheduled to update the same tags in their respective systems:
- MediaValet - for assets
- Mulesoft - for workflow used to send assets between MediaValet and AEM
- Ektron - for 2022 and 2023 presentations
- Salesforce - for Events search
- Marketo - for form submissions initiated on AEM
After tags are updated in their respective systems, run the workflows between the systems to verify that the tag changes are synced successfully.
Header
Review the header to determine if link text or URLs need to be updated to reflect the page name changes.
Bulk Publishing
URL changes and tag changes require bulk publishing to be done to push the updates throughout all aveva.com sites.
Sitemap Web Page
Review the sitemap web page to ensure the new page name is reflecting.
In most cases, link text is derived from the Breadcrumb field, but the name may be manually authored if a Fixed List is used, and then it will need to be edited manually.
- https://www.aveva.com/en/sitemap/
- https://www.aveva.com/de-de/sitemap/
- https://www.aveva.com/es-es/sitemap/
- https://www.aveva.com/fr-fr/sitemap/
- https://www.aveva.com/pt-br/sitemap/
- https://www.aveva.com/ja-jp/sitemap/
- https://www.aveva.com/ko-kr/sitemap/
- https://www.aveva.cn/sitemap/
Sitemap.xml
Review the sitemap.xml to ensure the new page URL is reflecting, if the page in indexed.
- https://www.aveva.com/sitemap.xml
- https://www.aveva.com/sitemap_de.xml
- https://www.aveva.com/sitemap_es.xml
- https://www.aveva.com/sitemap_fr.xml
- https://www.aveva.com/sitemap_pt.xml
- https://www.aveva.com/sitemap_ja.xml
- https://www.aveva.com/sitemap_ko.xml
- https://www.aveva.cn/sitemap.xml
Coveo Search
Verify the changes are reflected in Coveo search:
- Look in the actual search results (Page Label, Page Title, Description, URL)
- Look at the facets if there has been a tag change
International Sites and Translation
Any content changes made in the English site should be reviewed to determine the impacts to the international sites and then be scheduled for implementation in the international sites as well.
Reports and Audits
- Run an Oncrawl report to identify any 301s or 404 generated on the site as a result of changing the page URL.
- Run an ACS Commons report to identify any Card Carousels or Card 2x2 Section Layouts that likely have broken as a results of the tag label or tag path changes. (A copy down from Prod to Stage may be needed to access the latest data.)