Domain: SEO¶
The SEO domain covers the organic search visibility of the Zwerfkei storefront: how pages are discovered, rendered, and indexed by search engines and AI crawlers, and how technical implementation choices — client-side rendering, asynchronous data loading, pagination, and structured data — affect that visibility.
This domain does not own product, price, or category data itself (that data is owned by the Product domain); it owns the technical delivery guarantees that make that data discoverable by crawlers.
Features¶
-
Non-JS Crawler Support for Product Listings
How the Product Listing Page can serve real, crawlable product links to devices and crawlers that don't execute JavaScript, or that don't wait for the asynchronous Algolia response — plus the impact on SEO.
Responsibilities¶
- Guaranteeing that the raw (pre-JavaScript) HTML response of every crawlable page contains real, canonical
<a href>links to the content it lists — independent of client-side rendering timing. - Providing structured data (schema.org / JSON-LD) that accurately reflects what is visible on the rendered page, per Google's structured data policies.
- Providing correct pagination signals (
rel="canonical",rel="prev",rel="next") so that paginated listings are fully crawlable, not only their first page. - Monitoring index coverage and render health for key templates (PLP, PDP) in Google Search Console.
Open Action Items¶
Technical elaboration required: Product Listing Page for non-JS / non-waiting crawlers
See the Product Listing Overview organism — the Zwerfkei PLP currently renders its product grid exclusively client-side via Algolia InstantSearch inside a VueJS component. A technical design still needs to be produced for how product links are exposed to crawlers that do not execute JavaScript, or that do not wait for the async Algolia XHR response to resolve.
Connection to other domains¶
- Product — source of the category and product data that must be exposed to crawlers.
- Product Listing Overview — the front-end organism most directly affected; its results grid is populated entirely through client-side Algolia InstantSearch.