SEO, sitemaps, PWA and public routes

Understand service-worker scope and caching

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

Keep caching confined to safe public shop assets/content.

Audience: Store administrators, SEO teams and developersPermission: Public access when store enabled; Manage settings/catalogue for contentModule v1.0.0 · code-inspected

Jump to steps

Where to go/shop and public route endpoints

What this guide helps you do

Keep caching confined to safe public shop assets/content. This section documents canonical URLs, metadata, XML sitemaps, web app manifest, service worker and offline fallback.

Follow these steps

Go to /shop and public route endpoints and open the workflow that matches “Understand service-worker scope and caching”. Confirm the page or record context before making a change.
Set store/category/product SEO fields.
Go to canonical shop, category and product URLs.
Check title, description, canonical and structured data.
Go to the sitemap index and child sitemaps.
Check manifest and service worker over HTTPS.
Test the offline fallback without allowing checkout to appear successful offline.

Fields and options

Guide focus: Keep caching confined to safe public shop assets/content.
Store, category and product metadata
Canonical links
Robots noindex controls
Sitemap index/categories/products pages
manifest.webmanifest
service-worker.js
/shop/offline

Rules and limits

Search-result pages use noindex,follow.
Product seo_noindex can prevent product indexing.
Product sitemap pages are segmented by numeric page.
The service worker is scoped to the shop and provides an offline-safe page.
Checkout/order commits require live server validation; offline mode does not create orders.

Check it worked

The specific outcome described by this guide is visible and remains tenant-scoped.
Search engines can discover eligible canonical catalogue URLs.
Installable PWA metadata is served from the tenant store.
Offline browsing fails safely without pretending to submit commerce transactions.

Safety checks and troubleshooting

Keep only public-safe metadata in pages/sitemaps.
Test canonical host/protocol in production.
Do not cache personalised checkout/order/API responses.

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.

Was this guide useful?Your response is stored only in this browser.