Search-optimized website

A published website with search metadata and CMS content. When AI response is enabled, connect it to the website inquiry entry point.

Acceptance

Verify the public URL, indexing controls, content updates and selected chat connection.

Boundary

The published site is the deliverable. Entity content management and AI inbound messaging can serve other channels independently.

Compose a website with Entities

[blocked]

Store wording and images in Entities.

Starting conditions and inputs

Have the intended Entities and website editing permission.

Edit Entity content and translations

Values for this task

entry_url, organization_id, section_ids, entity_ids, locale, preview_url

Command sequence

text

open "$entry_url" && snapshot -i
click "$page_entity" && snapshot -i
get text body
# Outside browser: The page implementer binds the Entity and product references in the page composition. This does not assume a visual page editor.
open "$preview_url" && snapshot -i
get text body
click "$application_link" && snapshot -i
get text body

open "$entry_url" && snapshot -i
click "$page_entity" && snapshot -i
get text body
# Outside browser: The page implementer binds the Entity and product references in the page composition. This does not assume a visual page editor.
open "$preview_url" && snapshot -i
get text body
click "$application_link" && snapshot -i
get text body

Ref targets and expected results

#	Command / ref	Target and verification
1	`click` `$page_entity`	Entity record used by the page
2	`get text`	Read content and localized values.
3	Outside browser	The page implementer binds the Entity and product references in the page composition. This does not assume a visual page editor.
4	`open`	Preview URL for the configured page
5	`get text`	Compare rendered title, content and products with their sources.
6	`click` `$application_link`	Customer application link on the page
7	`get text`	Check the destination form and product.

Check the result

Order and content match, with no required area left empty.

Resuming after interruption

Read the same IDs again. Preserve correct settings and update only differences.

[blocked]

Separate content from layout

Store wording and images in Entities. Store page paths and layout in sections. Reuse one Entity for the same service description on the home and detail pages. Editing shared content affects its consumers.

[blocked]

Configure pages and sections

Open Sections in Settings and check each page path and display order. Choose the section type and layout, then adjust the number of items. Distinguish the home path from detail paths. Check heading order and action buttons.

[blocked]

Connect Entity content

Open Content and edit the Entity name, localized label, slogan, and description. Connect it to the section and order its children. Set a slug when the item needs a page. Use catalog-backed product sections for prices.

[blocked]

Preview devices and languages

Open home and detail pages at wide and narrow viewport sizes. Switch languages and check headings, text, images, and actions. Test destination forms and pages. Check other pages that reuse the edited Entity.

Connect a domain and check search visibility

[blocked]

Identify the domain owner or DNS administrator.

Starting conditions and inputs

Have domain administration access and a website ready to publish.

Values for this task

entry_url, organization_id, domain, public_url, locale

Command sequence

text

open "$entry_url" && snapshot -i
# Outside browser: The deployment operator confirms the domain and version, then publishes it.
open "$public_url" && snapshot -i
get text body
click "$application_link" && snapshot -i
get text body
# Outside browser: The publisher checks canonical, robots, sitemap and search-tool collection state. Ranking improvement is evaluated separately.

open "$entry_url" && snapshot -i
# Outside browser: The deployment operator confirms the domain and version, then publishes it.
open "$public_url" && snapshot -i
get text body
click "$application_link" && snapshot -i
get text body
# Outside browser: The publisher checks canonical, robots, sitemap and search-tool collection state. Ranking improvement is evaluated separately.

Ref targets and expected results

#	Command / ref	Target and verification
1	Outside browser	The deployment operator confirms the domain and version, then publishes it.
2	`open`	Published public page URL
3	`get text`	Compare the public title and content with the published version.
4	`click` `$application_link`	Customer application link
5	`get text`	Check the application target and language.
6	Outside browser	The publisher checks canonical, robots, sitemap and search-tool collection state. Ranking improvement is evaluated separately.

Check the result

Metadata matches public content. This does not establish search-engine indexing.

Resuming after interruption

Read the same IDs again. Preserve correct settings and update only differences.

[blocked]

Connect the domain

Identify the domain owner or DNS administrator. Choose the hostname and apply the DNS values supplied by your connection contact. Preserve unrelated email and service records. Check connection and certificate status before using the public address.

[blocked]

Set search information

Write each page title and description to match the offered service. Check localized content and the representative image. Distinguish pages by the questions they answer. Search services can rewrite displayed snippets.

[blocked]

Choose public content

Decide which pages are public and which are excluded from search. Keep private customer information out of public Entity descriptions. Check URLs, the sitemap, and crawler access. Separate test domains from production search targets.

[blocked]

Check the published site

Open the domain, language routes, key pages, and forms while signed out. Check redirects and missing pages. Publication and search indexing are separate results. Measure search visits over a consistent period after release.