Public site search finds posts by title and by text anyone may read. It does not search every page or product. This guide also explains navigation, archives and the public states a site can serve. To change its front page or navigation, begin with Site setup or Menus in the site admin.
Checked against the product’s code on 7 November 2026.
Praxis serves published content through its configured layout. The surrounding header, footer, archives and shopper account are separate from a page’s editable body. EmDash supplies the underlying content collections and taxonomy records.
Navigation and presentation
Section titled “Navigation and presentation”The active menu supplies links around the page. A header button has its own target and visibility rules.
- Configure the header button through Site setup.
- Configure menu links through Menus.
- Inspect the actual public addresses.
When the theme offers more than one appearance, such as light and dark, visitors see a switch in the header. Their choice changes only how the page looks to them; it does not translate or publish anything.
Listings, search and languages
Section titled “Listings, search and languages”Migrated blog content can appear in the blog index and category, tag, author or date archives. Their presence depends on the imported content and route.
How public site search works
Section titled “How public site search works”Site search looks in post titles and in the text of posts anyone may read. A members only post can be found by its title, never by its protected text. Search does not cover every page or product.
The host supports English and Spanish routes and their available alternate links. That does not automatically translate every entry or add a language switcher to every layout.
Comments depend on a collection’s settings and its public renderer. A moderation inbox alone does not establish that every page has a comment form.
Empty sites and serving delays
Section titled “Empty sites and serving delays”A site with no published page can show an unpublished site message.
After a quiet period, the first page view can take longer while the site starts. If it cannot start in time, the visitor may see an earlier copy of the page or the browser’s own error. Try again after a few seconds.
Stored copies. A visitor who is not signed in may be shown a stored copy of a page, so a change you just published can take a short while to reach them. Visitor identity, consent choices and Global Privacy Control can use separate shared copies when the page is safe to share. Sign-in, cart and other cookies that change the page bypass this cache. In a browser that runs JavaScript, a stored product page loads its stock and purchase controls again when it opens.
Visitor consent controls measurement and permitted experience changes. Restricted content has its separate reading checks. For crawl policy, sitemaps, feeds and text copies, use Machine readable site.