Customer work, connected.

Help & supportMyAccount
Public store, catalogue browsing and cart

Understand public search noindex behaviour

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

This guide explains that search results use noindex,follow to avoid indexing result combinations.

Audience: Customers, clients and public-store administratorsPermission: Public access when store enabled; catalogue/settings permissions for administrationModule v1.0.0 · code-inspected
Jump to steps
Where to go/shop

What this guide helps you do

Know search results use noindex,follow to avoid indexing result combinations. This section documents public catalogue eligibility, category/product pages, cart handling and route behaviour.

Follow these steps

  1. Go to /shop and open the workflow that matches “Understand public search noindex behaviour”. Confirm the page or record context before making a change.
  2. Go to /shop while the store is enabled.
  3. Browse categories or search products.
  4. Go to a canonical product page.
  5. Add a valid quantity to the session cart.
  6. Update or remove items.
  7. Check recalculated stock, promotions, tax, shipping and totals before checkout.

Fields and options

  • Guide focus: Know search results use noindex,follow to avoid indexing result combinations.
  • Public category and product slugs
  • Search query and page number
  • Session cart product IDs and quantities
  • Coupon code
  • Default stock location
  • Availability and backorder status
  • Canonical, meta and structured data

Rules and limits

  • Disabled stores return 404.
  • Public product lists use 24 items per page.
  • Search-result pages use noindex,follow.
  • The cart accepts at most 100 distinct product IDs.
  • Each quantity is positive and no more than 100,000.
  • Non-weighed quantities must be integers.
  • Cart totals are recalculated server-side.

Check it worked

  • The specific outcome described by this guide is visible and remains tenant-scoped.
  • Only eligible products/categories are displayed.
  • Cart changes persist in the visitor session.
  • Canonical URLs and metadata match the requested public item.

Safety checks and troubleshooting

  • Do not rely on client-side totals or product data.
  • Do not expose internal stock/audit details.
  • Use HTTPS and privacy/terms links for production.
Stay within the supported module flow

Use the supplied UI, host module lifecycle and documented endpoints. Do not bypass tenant filters, permissions, CSRF, idempotency, rate limits, audit evidence or transaction checks. A stored table or field does not imply that version 1.0.0 exposes a management screen for it.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page