Home
AVEVA Site Governance
Page Properties

Page Properties

Every page has Page Properties.

The Page Properties that get completed for each page will depend upon its page type and/or its template.

Initial Page Creation

Follow these guidelines for the Title of the page:

Remove extraneous words
Use a succinct title; this will be seen in the backend of AEM only by CMS authors

Follow these guidelines for the file name of the page (the file name is the end portion of the URL: www.aveva.com/solutions/file-name/):

No empty spaces (this causes a %20 to show up in empty space, which makes URL hard to read)
All lower case letters
Hyphen (-) between words; do not use an underscore (_)
No special characters, such as ampersand (&), comma (,), apostrophe ('), quotation mark ("), pipe (|)
English words only - no translated terms
Restrict length to 150 characters

Please note: For success stories, please do the following:

Use only the company name, or use the company name plus a product or solution keyword (this will allow for all success stories URLs to be consistently formatted across the entire site section)
Do not use the entire title of the success story in the file name portion of the URL:
- Incorrect: https://www.aveva.com/en/perspectives/success-stories/apply-sorco-embraced-new-technologies-to-win-contracts/
- Correct: https://www.aveva.com/en/perspectives/success-stories/apply-sorco/

Basic

All of the fields in the table below are required for every page, except for Vanity URL.

Please note that fallback rules have been set up within Base Page Template:

If no Card Title, then fall back to Breadcrumb
If no Breadcrumb, then fall back to Page Title
If no Page Title, then fall back to Title
If no Card Description, then fall back to Description

Basic Properties Field Governance

Field

Governance

Internal Search

Dynamic Cards

Field

Title

Governance

Used for Backend CMS Title
(use simple direct language; no TM)

Internal Search

Not applicable

Dynamic Cards

Not applicable

Field

Governance

Review which ones are required based on page type

Internal Search

Used for search facets

Dynamic Cards

Used for Card Label in Card Perspectives
(this will be first tag applied to a page)

Field

Disable Breadcrumb Nav Link

Governance

Used to remove linkability of breadcrumb

Was implemented due to Coveo search pages taking over Listing pages that used to exist; breadcrumb links were redirected, so this was negatively impacting results in OnCrawl reports

Disable Breadcrumb Nav Link in the following site sections:

/about/news/press-releases/20xx (disable in each year subfolder)
/perspectives/ (disable in each subfolder)
/info

Internal Search

Dynamic Cards

Field

Page Label

Governance

Review which ones are required based on page type

Page Label will closely match text in page URL taxonomy

For example: /products correlates to Product Page Label

Internal Search

Required for any page that is shown in Coveo search results

Use a Content Type subtag for Content Type page
Use a Topics subtag for Page Type page

Dynamic Cards

Not applicable

Field

Page Title

Governance

Used as the Meta Title

Will show as Browser Title in tab of web page; this title should include keywords

For products, Page Title should be only the product name

For success stories, Page Title should be only the company name

Internal Search

Used in internal Coveo search results for Page Types and in external search results

Dynamic Cards

Not applicable (Card Title from Card Properties tab will be used)

Field

Breadcrumb Title

Governance

Displays at top of web page

Display as link text in Sitemap Webpage

Use short, simple direct language

Do not match Page Title text because it will be too long for a breadcrumb

Breadcrumbs are not required for the following:

/perspectives/blog
/perspectives/campaigns
/perspectives/podcasts
/about/news/press-releases/20xx

Internal Search

Not applicable

Dynamic Cards

Not applicable

Field

Description

Governance

Used as the Meta Description

Internal Search

Used in internal Coveo search results for Page Types and in external search results

Dynamic Cards

Not applicable (Card Description from Card Properties tab will be used)

Field

Vanity URL

Governance

Use only if a vanity URL is required; however, it is recommended to make a permanent redirect instead of doing this in AEM because vanity URLs in AEM pages compete with their page's default URL in external search, which works against AVEVA's SEO goals

Internal Search

Not applicable (confirm this does not override page default URL)

Dynamic Cards

Not applicable (confirm this does not override page default URL)

Advanced

Redirects (learn more about short- and long-term redirect governance)
- Redirect Type
  - 301 (permanent; this is the default)
  - 302 (temporary)
- Redirect URL - Select a relative internal path or enter an absolute external URL
  (Once you save the Page Properties, you will no longer be able to access the content on the original page. Instead, you will see a message that states: This page redirects to "name of page". When you view the original page in View as Published mode, you will be taken to the page it is redirected to.)
Add This Script for Social Media Sharing component
- Apply this code to the Home page only of each language, and it will apply to the entire site
Head Tag GTM Inclusion Script (learn more about the required scripts)
Body Tag GTM Inclusion Script (learn more about the required scripts)

Site Configurations

Site Configurations are used to control the following:

Canonical Link
Fav Icon
Whether pages show up in internal/external search
Breadcrumb Configurations
Whether pages show/hide Chatbot

Site Configuration Properties Field Governance

Field

Governance

Field

Canonical Link

Governance

AVEVA's implementation is set up to default to the page's AEM URL as its canonical URL. If the Canonical URL field is completed, then it will override the page's default. There should be limited use cases for using the Canonical URL override in the current implementation.

Examples of how to use Index/No Index functionality and the Canonical Link field
- Index and No Link in Canonical Link Field (defaults to page's URL in View Source)
- Index and Link in Canonical Link Field (link overrides pages's default URL in View Source)
- No Index and No Link in Canonical Link Field (no canonical in View Source)
- No Index and Link in Canonical Link Field (no canonical in View Source)

Field

Favicon Configuration

Governance

Used in language home page only

Use asset path for ico and png file types

Field

Sitemap XML Configurations > Indexability > Index

Governance

Index = default, show page to external search engines

Used to present indexable pages to external search engines

https://www.aveva.com/sitemap.xml
https://www.aveva.com/sitemap_es.xml
https://www.aveva.com/sitemap_de.xml
https://www.aveva.com/sitemap_fr.xml
https://www.aveva.com/sitemap_pt.xml
https://www.aveva.com/sitemap_ko.xml
https://www.aveva.com/sitemap_ru.xml
https://www.aveva.com/sitemap_ja.xml
https://www.aveva.cn/sitemap.xml

Field

Sitemap XML Configurations > Indexability > No Index

Governance

No Index = use to hide page from external search engines

The following page types should be marked as "No Index" in AEM

/about/partners/global-alliances/[partner-name]/ (subpages under the partner name should be marked as "No Index")
/about/partners/login (the Partners site is external to AEM; this page exists in AEM only to generate Card Properties and Coveo internal search result)
/avevasandbox (this is internal AVEVA content, so it does not need to be found in public search)
/governance (this is internal AVEVA content, so it does not need to be found in public search)
/perspectives/articles (subpages should be marked as "No Index")
/perspectives/brochures (subpages should be marked as "No Index")
/perspectives/campaigns (no campaign pages should be indexed because traffic is driven to these pages through paid search activities)
/perspectives/datasheets (subpages should be marked as "No Index")
/perspectives/ebooks (subpages should be marked as "No Index")
/perspectives/infographics (subpages should be marked as "No Index")
/perspectives/reports (subpages should be marked as "No Index")
/perspectives/solution-briefs (subpages should be marked as "No Index")
/perspectives/webinars (subpages should be marked as "No Index")
/perspectives/white-papers (subpages should be marked as "No Index")
/search-results (this is the Coveo internal search results page, so it does not need to be found in public search)
/sitemap (this is the sitemap web page, so it does not need to be found in public search)
/support-and-success (mark these pages below as "No Index")
- AVEVA Edge Activation
- Discrete Lean Management Activation

Field

Priority

Governance

ROAST confirmed we do not need to edit this field

Field

Change Frequency

Governance

ROAST confirmed we do not need to edit this field

Field

Breadcrumb Configuration

Governance

Use "Hide Breadcrumb from Page" as needed for individual pages

Use "Hide Breadcrumb from Child Pages" option for these pages to hide on all subpages:

Use in /perspectives/blog
Use in /perspectives/campaigns
Use in /perspectives/podcasts
Use in /about/news/press-releases/20xx

Field

Coveo Search

Governance

Default = Show all pages in internal Coveo Search

Check box to override default behavior and hide page from Coveo Search

Hide the following type of pages from internal search:

home page
Coveo search pages (/search-results, /products, /events, /press releases plus each year's subfolder main page, /perspectives plus each subfolder's main page)
/perspectives/campaigns
/robots.txt
/error-pages
functional grouping pages
All /governance pages
All /avevasandbox pages
Some about/partners/global-alliances subpages

Field

Chatbot Configuration

Governance

Used in conjunction with the Connect with Us tab in Page Properties

Apply Chat to all pages in this folder

/en (home page)
/about/locations (only subsection in /about to get Connect with Us)
/contact
/industries
/partners
/perspectives/success-stories (only subsection in /perspectives to get Connect with Us)
/products
/solutions
/support
/training

Exclude this page from Chat (to override default setting at folder level)

/about (override for /about/locations)
/error-pages
/legal
/perspectives (override for /perspectives/success-stories)
/search results
/sitemap

Connect with Us

Connect with Us is the sticky button in bottom right corner of majority of pages in the site. It is used for the chatbot.

https://jira.tadigital.com/browse/AW-29

Go to Page Properties > Connect with Us of the page where chat functionality needs to be enabled
Copy the same information from the home page's Page Properties on the Connect with Us tab
Go to Site Configurations tab and then to Chatbot Configuration section to do one of the following:

Exclude Chat from Page
Exclude Chat from Child Pages

Refer to additional info in Site Configurations > Chatbot Configuration

Card Properties

Card Properties are used used to populate the following:

Coveo internal search results for Content Types
Coveo internal search results for 2 specific fields for Products search results (Card Subheading, Partner Name)
Dynamic cards used in Card Carousels (Card Images, Card Perspectives) or in Card 2x2 Section Layouts (Card Icons)

Refer to the following resources:

Reusable Content Strategies - For dynamic cards, Coveo search results, and Experience Fragments
Card Rules - For a list of Card Properties fields to complete based on card type
Card Character Counts - For Card Title and Card Description character recommendations
Image Naming Conventions - For image sizes and naming conventions for each card type
CTAs - For recommended text to use based on page type or content type (Refer to the section on "Card Properties CTA Text Governance")
Web Writing Guidelines - For guidance on when to use trademarks/registered trademarks (Refer to the section on "Trademarks")

Card Properties Field Governance

Field

Governance

Internal Search

Dynamic Cards

Field

Card Title

Governance

Used for Content Types in internal search results

Used for Dynamic Cards, regardless of page being a Page Type or Content Type

Rules for letter casing

Internal Search

Used for Content Types

Dynamic Cards

Used for Dynamic Cards

Field

Card Subheading

Governance

Used only for products that have a former name and is formatted as follows: Formerly Known As [old product name]

Internal Search

Used for products query pipeline only; does not display for products in All Content query pipeline

Dynamic Cards

Displayed in cards in Card 2x2 Section Layout

Field

Partner Name

Governance

Used only for products to attribute products to a specific vendor

For AVEVA core products or AVEVA DX products: Apply the Topics > Product > Vendor Name > AVEVA Group plc tag
For partner products: Apply the applicable Topics > Product > Vendor Name tag

Internal Search

Used for products query pipeline only; does not display for products in All Content query pipeline

Dynamic Cards

Not applicable

Field

Icon for Card Icons or Logo for Card Images with Background Layout Image

Governance

Icon for Card Icons (add sizes)

Logo for Card Images with Background Layout Image (add sizes)

Internal Search

Not applicable

Dynamic Cards

Used for Card Icons

Used for logo in Card Images with Background Layout Image

Field

Image for Card Images or for Card Perspectives with Image

Governance

Used for Image for Card Images

Used for Card Perspectives with Image

Internal Search

Not applicable

Dynamic Cards

Used for Image for Card Images

Used for Card Perspectives with Image

Field

Alt Text for Icon, Logo, and/or Image

Governance

Used for Icon, Logo, and/or Image

Internal Search

Not applicable

Dynamic Cards

Used for Icon, Logo, and/or Image

Field

Card Description

Governance

Used for Content Types in internal search results

Used for Dynamic Cards (Card Images or Card Icons), regardless of page being a Page Type or Content Type

Internal Search

Used for Content Types in internal search

Dynamic Cards

Used for Dynamic Cards (Card Images or Card Icons), regardless of page being a Page Type or Content Type

Field

Start Date

Governance

Used for Blog Posts, Webinars, Events, and Press Releases

Internal Search

Used for internal search results

Dynamic Cards

Used in Card Perspectives

Confirm if used in Card Images

Field

End Date

Governance

Used for Events if event extends beyond one day, such as a conference that spans two or more days

Internal Search

Used for internal search results

Dynamic Cards

Used in Card Perspectives

Confirm if used in Card Images

Field

CTA Label

Governance

Used for dynamic cards

Internal Search

Not applicable

Dynamic Cards

Used for all dynamic card types

Field

External URL

Governance

If completed, External URL will override default page URL

Required only for third party URLs (include https://) or AEM Assets (use relative path for AEM Assets)

If empty, URL of this page will be used by default

Internal Search

Used as link for internal search results

Should open link in a separate tab

Dynamic Cards

Used as link from CTA Text

Should open link in a sepate tab

Field

Page Weight - Not used

Governance

Not applicable

Internal Search

Not applicable

Dynamic Cards

Not applicable

Field

Display Video Card

Governance

Used only for videos; pulls in thumbnail image

Internal Search

Not applicable

Dynamic Cards

Used in Card Images, but limited to specific views

Used in Card Perspectives, but limited to specific views

Field

Video URL or Embed ID

Video Hosting Platform

Video URL

Embed ID

Governance

Used to display videos in cards

Can be hosted in either platform: Wistia (preferred) or YouTube

Can accept either a URL or embed ID

Internal Search

Not applicable

Dynamic Cards

Used in Card Images, but limited to specific views

Used in Card Perspectives, but limited to specific views

Social Media

Is AVEVA using this tab?

Defines the sharing options available on the page.

Exposes the options available to the Sharing core component.

Social Media sharing

Enables user sharing for

Facebook
Pinterest

Preferred XF variation

Define experience fragment variation used for generating metadata for the page.

Search Config

This tab controls the search field description text that is shown when a user selects the magnifying glass icon in the header to access internal search for the site. This tab should be populated in the search-results page only.

This tab used to control search autosuggestion for SOLR, but SOLR is no longer used.

Pending AAS-438 to re-add autosuggest functionality, but for Coveo instead.

Thumbnail

AVEVA is not using this tab.

Shows the page thumbnail image.

Generate Preview: Generate a preview of the page to use as thumbnail.
Upload Image: Upload an image to use as a thumbnail.
Select Image: Select an existing Asset to use as the thumbnail.
- RevertThis option becomes available after you have made a change to the thumbnail. If you do not want to keep your change, you can revert that change before saving.e.g., used on AVEVA website.

Cloud Services

Is AVEVA using this tab?

Define properties for cloud services.

For details, visit https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/extending-cloud-services/extending-cloud-config.html?lang=en

Personalization

This is used in AVEVA.

ContextHub Configurations

Select the ContextHub Path and Segments Path.

ContextHub Path

For details: https://experienceleague.adobe.com/docs/experience-manager-65/developing/personlization/ch-configuring.html?lang=en

Segments Path

For details: https://experienceleague.adobe.com/docs/experience-manager-65/administering/personalization/segmentation.html?lang=en

Targeting Configuration

Select a Brand to specify a scope for Targeting.

For details: https://experienceleague.adobe.com/docs/experience-manager-65/authoring/aem-adobe-campaign/target-adobe-campaign.html?lang=en

NOTE: This option requires the user account to be in the Target Administrators group.

Permissions

Fields in this tab are used to allow permissions for that page only to some specific users or groups.

Blueprint

Fields in this tab are used for some rollout configurations. This is used at the root level.