Run Screaming Frog Report
- Identify terms to search for
- Have SEO vendor run a Screaming Frog report to identify pages and pdfs that may contain those terms
- Audit impacted pages and pdfs to determine what is in/out of scope for removal or updates
- Assign tasks accordingly address content
- Re-run report throughout the retirement or update process to ensure content is being handled correctly and thoroughly
Set Rules in Internal Search
- Identify what to search for (keywords, portions of URLs, file names of pdfs, etc.)
- Search by keyword(s)
- Search by a portion of the URL (do not include www.aveva.com/en/ or www.aveva.com/xx-xx/ when searching by URL; use only the end portion of the URL because that part should be identical in all the language sites because of their content hierarchy)
- Example: Search for "products/engage" instead of "www.aveva.com/en/products/engage" because the "products/engage" portion of the URL should be the same regardless of language site
- Once you get search results, then click on each search result, and read the content to identify which part(s) of the page may need to be updated:
- Look for references in the body text
- Look for references in cards or card carousels
- If the affected page appears in a dynamic card carousel, then the web publishers will need to republish the Live Copy version of the page with the card carousel, and verify on the front end to ensure the affected page has in fact been removed
- If the card is built manually, then the web publishers should remove it from the page per the normal editing process (make sure the front-end display is acceptable with the removal of a card from a section on the page)
- Search in internal search to see current user experience
- https://www.aveva.com/en/search-results/
- https://www.aveva.com/de-de/search-results/
- https://www.aveva.com/es-es/search-results/
- https://www.aveva.com/fr-fr/search-results/
- https://www.aveva.com/pt-br/search-results/
- https://www.aveva.com/ja-jp/search-results/
- https://www.aveva.com/ko-kr/search-results/
- https://www.aveva.cn/search-results/
- Consider impacted pages in search strategy
- Assess if certain pages need to be surfaced or hidden in internal search
- Define rules for internal search results experience
Unpublish/Archive Pages (Web Team)
- Search for the webpage in the AEM backend to identify other language versions in same content hiearachy
- Per governance, if the en version of a page is retired, then its corresponding language version should be retired at the same time
- Unpublish/archive page
Unpublish/Archive PDFs (Web Team)
If there are pdfs linked from the page to be retired, then confirm with the stakeholders if pdfs should also be unpublished and archived, and then unpublish and archive them in AEM Assets.
Please note: Images will be unpublished and archived or deleted when the page is deleted.
Unpublish/Archive Images (Web Team)
This step can wait until the page is approved to be deleted in AEM. At that time, the images will be audited to ensure they no longer have any references.
If there are no references, then the images can be moved to the appropriate Delete folder.
Create Redirects (Web Team)
If a page is unpublished/archived, then consider if the page is important enough to create a redirect. Make sure to redirect the international version of the page at the same time.
Redirects are created by the Web Team on a weekly basis, typically on a Thursday or Friday.
Run Oncrawl Reports (Web Team)
Once the affected page is unpublished, it will do one of the following:
- Cause a 404 error if the URL is not redirected
- Cause a 301 error if the URL is redirected
If there are any 404 or 301 links still pointing to the unpublished page that were not uncovered by the other steps above, then they should get caught by Oncrawl when it runs on the following Monday.
Caveat: This report feature works only if the unpublished page was indexed when it was live. For example, pages with /campaigns in their live URL will not be caught in this report because these pages are not indexed.
Limitation of Oncrawl: There are some issues that Oncrawl cannot catch:
- Oncrawl will catch 404 and 301 link issues, but it cannot catch text within a paragraph on a page. This is why the searches by keywords and portion of URL need to be done.
- Oncrawl will not catch broken pdf links, but Oncrawl does allow you to search by a pdf file name to determine where it was linked on the websites so the pdf link can be removed through authoring
Run Coveo Reports (Web Team)
Export reports from the various site sections, and use Find to search for terms in the metadata and Card Properties. The Screaming Frog report should also be able to catch these same issues.
Adjust Sitemap Webpages (Web Team)
If the page in question is still linked from the sitemap webpages, then edit the sitemap webpages to remove the page.
Unpublish/Delete Tags (Web Team)
If a page is unpublished/archived, then find any tags associated to the page.
Merge the tag with another tag, or delete the tag.
Remove Product from Marketo Products Dropdown (Web Team and Marketo Team)
If the affected page is a product page, then work with the Marketo team to get the product removed from their Marketo Products dropdown.
The Products dropdown is used in the Contacts forms. View inventory of impacted forms across all languages.