...
What are Static Pages?
Static Pages allow publishing arbitrary web content to customers under a publicly accessible address. These will be available both on the web and native apps.
Examples of static pages include, but are not limited to: new product showcases, marketing campaign landing pages, FAQ sections, job postings, terms of service, or privacy policies.
Basics
All Static Pages contain an identifiable title and path.
...
The path must be of the /page-path-name form. Clicking the Generate button will infer a path from the localized title using the expected format.
Since the path is public and becomes the entry point to content for visitors, it’s important to keep these short and concise, use lowercase letters, separate words with hyphens, and avoid special characters.
| Info |
|---|
While the path itself doesn't have a direct impact on search engine rankings, it influences the visitor's decision making process for whether or not to click on your site. |
When the market supports multiple languages, each language can define its own custom path. If no path is defined for the current application language, there will be a fall back to the path set for the market’s default language.
...
To learn more about all the SEO capabilities, please head to SEO (Search Engine Engines Optimization).
User Acceptance
When the Requires User Acceptance toggle is enabled, the static page will be treated as a document that signed in users will need to review and accept before using the site. This is useful when willing to have users to agree legally-binding documents such as Terms of Service or Privacy Policy pages.
...