| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nTitle\n\n | \n\nInternal name of the page. Use the title to search for a page in the Service Portal Designer.\n\n |
| \n\nID\n\n | \n\nA unique ID for the page. The ID is what you use to assign a page to a portal. It also determines the URL for the page, for example `https://instance name.service-now.com/doc_portal/?id=doc_page`, where doc\\_page is the page ID.\n\n |
| \n\nApplication\n\n | \n\nThe application scope.\n\n |
| \n\nPublic\n\n | \n\nEnables the page to be accessed without the need for authentication. If **Public** is selected, all users can view the page no matter the roles listed.\n\n |
| \n\nDraft\n\n | \n\nMark a page as draft to limit user ability to view the page while you’re still creating it. Only users with the admin role can view a page in draft, all other users see a 404 page.\n\n |
| \n\nRoles\n\n | \n\nLimit user access to a page by role.\n\n |
| \n\nShort description\n\n | \n\nDescribes the portal page. This field isn’t public facing.\n\n |
| \n\nPage Specific CSS\n\n | \n\nUnless a page has Page Specific CSS, the page inherits CSS from the Theme and Branding. If you need a page to look different, the Page Specific CSS overrides the inheritance from the Theme and Branding.\n\n |
| \n\nDynamic page title\n\n | \n\nCreate variables to generate descriptive titles depending on the content loaded into a page.\n\n For more information, see [Add dynamic titles to a page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/service-portal/add-page-title.md).\n\n |
| \n\nClone Page\n\n | \n\nEnables you to make a copy of a page that can be modified. If you copy a base system page, a new widget instance is created for each widget on the page.\n\n |
| \n\nUse SEO script\n\n | \n\nOption to enable a script include that adds SEO tags for canonical URLs and hreflang tags.\n\n For more information, see [Enable SEO for localized versions of a portal page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/service-portal/seo-header-tags.md).\n\n |
| \n\nSEO script\n\n | \n\nScript include to apply to the page. By default, the system uses the SPSEOHeaderTags script include, which includes the default implementation for the canonical URL and hreflang tags for Service Portal Analytics pages.\n\n |
| \n\nHuman readable URL structure\n\n | \n\nAdd human readable keywords to the page URL to improve search engine optimization \\(SEO\\) and click-through rates for public pages. Human readable URLs also help users understand what to expect on a page for public and non-public pages. For example, `https:// |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nName\n\n | \n\nInternal name of the container.\n\n |
| \n\nOrder\n\n | \n\nThe order in which the containers appear on a page. To set a container to appear above all other containers, give the container the lowest number in the **Order** field.\n\n |
| \n\nPage\n\n | \n\nThe page that includes the container.\n\n |
| \n\nScreen reader title\n\n | \n\nThe title used by a screen reader.\n\n |
| \n\nSemantic tag\n\n | \n\nThe semantic HTML tag that includes the container. Options include:- None: All content on the page between the header and footer is included in the **<main>** tag.\n- Main: The **<main>** tag includes only the container and its contents. The **<main>** tag is a semantic HTML element that contains the main content of the page. It should be applied to content that is unique to the page and should be configured for only one element on the page.\n\n**Note:** The **<main>** tag can be applied to a container, row, or column. For more information, see [Configure the main tag on a page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/service-portal/configure-main-tag-on-page.md).\n\n- Header: The <header> tag is used as introductory content. It can be used multiple times per page, including inside an <article> tag.\n- Nav: The <nav> tag is used in page-level navigation. It can be used multiple times in each page.\n- Section: The <section> tag groups related content under a common heading or theme.\n- Article: The <article> tag is self-contained content that can stand alone or be reused.\n- Details: The <details> tag can be used in expand/collapse sections, and intended for FAQs.\n- Summary: <summary> tag is the first child of <details> and acts as the clickable label.\n- Time: <time> tag is for dates, times, and durations. Add for machine-readable values.\n- Fig caption: <figcaption> tag is only valid as a child of <figure> and provides the caption for a figure.\n\n\n |
| \n\nApplication\n\n | \n\nThe application scope.\n\n |
| \n\nWidth\n\n | \n\nWidth of the container. Options include: - Fixed\n- Fluid\n\n\n |
| \n\nParent class\n\n | \n\nParent CSS class for the container.\n\n |
| \n\nCSS class\n\n | \n\nThe CSS classes for the container. Overwrites page-specific CSS.\n\n |
| \n\nBackground color\n\n | \n\nThe background color of the container.\n\n |
| \n\nBackground image\n\n | \n\nBackground image for the container.\n\n |
| \n\nBackground style\n\n | \n\nThe display style of a background image. Options include: - Default\n- Cover\n- Contain\n- Repeating\n\n\n |
| \n\nBootstrap alternative\n\n | \n\nSelecting this field removes the standard Bootstrap grid classes and disables the Bootstrap grid system in the container. If selected, the following aren’t applied: - The **Width** field in the container record.\n- Standard Bootstrap class in the row record within the container.\n- The **Size - xs**, **Size - sm**, **Size - md**, and **Size - lg** fields in column records within the container.\n Only select this field if you plan to provide custom CSS classes and CSS for the container, row, and column records.\n\n |
| \n\nMove to header\n\n | \n\nWhen selected, the container sticks to the header and doesn’t scroll. Use this option to create a subheader.\n\n |
flight_land
`\n\n"}}