Use Growth to review the tenant’s public address, metadata, sitemap, and indexation controls. Use Website Builder to make the page itself useful before optimizing the metadata.
Farin also publishes structured information about supported public sites and ordering catalogs. Start with catalog setup if product names, categories, prices, or availability still need work.
Quick facts
Start here
- Use a stable, human-readable catalog path for sharing and search; location selection can remain a checkout decision when several locations serve the catalog.
- Each important catalog and product should have a useful name, description, image, price, category, and availability state.
- Keep addresses, hours, service areas, and policies in visible page content as well as structured metadata.
- Agent-assisted ordering still requires customer confirmation and the same payment and fulfillment rules as a human checkout.
Step 1: Give customers a useful canonical path
- Link to the tenant website page customers understand first, such as
/menu,/catering, or/order. - Use the catalog parameter only when a page needs to select among multiple catalogs. Do not make a customer decode an internal catalog ID.
- Use product-level pages for high-value products only when the product has enough unique content to justify a search result. A thin page for every variation adds noise rather than discoverability.
- 1 Growth contains the tenant address, metadata, sitemap, and discoverability controls.
- 2 Use the top metrics to see traffic, search visibility, form responses, ordering clicks, and review health at a glance.
- 3 The organic growth plan turns the site’s conversion goal into concrete actions.
- 4 Connect Search Console to bring search queries and landing-page performance into the workspace.
Step 2: Make the content answer real questions
- Write headings and descriptions that include what the product is, who it serves, and when it can be ordered.
- Include location names, addresses, hours, pickup or delivery coverage, minimums, dietary notes, and ordering cutoffs on the relevant page.
- Use genuine tenant photography with meaningful alt text. Avoid duplicate or generic images that make products hard to distinguish.
Step 3: Verify machine-readable access
- Open the public tenant
robots.txtand sitemap from the same tenant address after publishing. - Check the tenant’s
llms.txtresource when you are testing an AI discovery integration. - Run one real end-to-end test from a public link: choose a location, add an item, review modifiers, complete checkout, and confirm the order status in Retail orders.
