Public website

The website tools prepare the public presentation of your application. Start from Website to review the type of site, page definitions and construction state.

Before you start — Prepare the audience, purpose and next action of the public site. Base product claims on the application’s real scope and prices on the confirmed offer. Use the publisher’s actual details for legal content rather than examples.

Review the pages to prepare

Review each page’s purpose in the visitor journey before deciding which content needs preparation.

1. Open Website and its configuration.
2. Inspect Mandatory pages, Showcase pages and Legal pages.
3. Read each page's Status and available action.
4. Open the page concerned to review its intended message.

Keep the page claims consistent with your application's real functionality. Product descriptions, prices and company information serve different parts of the visitor journey.

Prepare a page that has not started

Prepare the page’s message and supply the missing information requested by its questions.

1. Under Legal pages (or Dynamic pages on a dynamic site), find the page marked Not started.
2. Click Create this page.
3. Follow its preparation state.
4. Use Answer when content questions are requested.

The preparation produces the content definition needed for construction. It is not proof that a public page is already published. The other pages are prepared by the website construction itself.

Start and follow website construction

Launch the prepared site when the overview offers the action, then follow the existing request.

1. Return to Website.
2. Check that all your modules are shipped; until they are, the launch action stays unavailable.
3. Use Launch the website construction when the action is available.
4. Read Construction progress and the page states. When pages need clarifications, click Answer next to each one.

Follow any prerequisites shown by the screen rather than submitting the launch repeatedly.

Review the finished public page

Review what visitors can understand and do, including the transition to the next useful action.

1. In configuration, use Open for a built page.
2. Check the message, links, prices and contact path.
3. Review the page in each published language and on a narrow screen.
4. Confirm that the expected version is published in Deployment.

Use Navigation for menus, Website visuals for images and Domains for the public address.

Important — Supply the actual publisher details and business conditions for legal content. A page definition or placeholder does not establish a legal policy for your company.

A product page explains the workflow, pricing explains the offer and contact gathers the initial need. Verify that the same capabilities and conditions are described consistently across these pages. A menu link alone does not make their content coherent.

Control which bots crawl the website

Crawler rules adjust the website’s robots.txt in production. By default, production allows crawling and lists the main sitemap; development and staging always refuse crawling.

1. Open Website and select the Robots tab.
2. In the environment list, choose Production.
3. Click Add a rule.
4. Under Bot, enter a bot product token such as Googlebot, or * for all compliant crawlers.
5. Under Rule, choose Allow or Disallow, then enter a Path that starts with /.
6. Click Save. The rule is saved and published.

When production has no custom rule yet, the tab shows No custom crawler rules. Click Generate base file, then Generate the file: the base file contains User-agent: *, Allow: / and the address of the main sitemap. Generation is offered only while no custom rule exists. In development and staging, the tab shows the automatic Disallow: / rule, which cannot be edited.

To change or remove a rule, use Edit the rule or Delete the rule on its row. When the link is shown, use Open robots.txt to check the published file.

Note — Rules can be changed only while the website is available and supports automatic crawler configuration. Crawler rules control crawling; they do not protect private content.

Check the automatic sitemaps

Sitemaps are generated automatically: the main index links to one sitemap per activated country, and published pages are added or removed without a manual build.

1. Open Website and select the Sitemap tab.
2. Choose the environment.
3. Read the Main sitemap index row and the sitemap of each country, with its Type, Address and number of Entries.

If nothing has been generated yet, the tab shows No sitemap is available yet. Development and staging refuse crawler access, but their sitemap files remain available there for verification.

Manage the cookie consent box

The Cookies tab sets, for each environment, the consent box shown to website visitors and the cookie categories your website uses.

1. Open Website and select the Cookies tab.
2. Choose the environment.
3. Click Edit cookie settings.
4. Check or uncheck Show the consent box. Hiding the box also blocks optional cookie uses.
5. Under Cookie categories, enable only the categories your website actually uses: Additional features, Audience measurement or Marketing. Necessary cookies always remain active.
6. Under Notice text, optionally enter the title and text in English and French. Leave these fields empty to use the default translated notice.
7. Click Save and read Cookie settings saved.

New visitors have no optional category selected. They can accept or refuse optional cookies, or customize their choice; it is remembered for six months and can be changed from any page. A change to the notice or its categories asks visitors to confirm their choice again.

Note — Edit cookie settings appears once the website is ready; until then the tab shows The website is being prepared for cookie preferences. If saving shows These settings changed. Reload the page before saving., reload the page and repeat your change.