# Orakel — Full LLM Site Guide

> Orakel (https://www.orakel.com) is a European manufacturer and e-commerce supplier of personalised event materials. This file expands on /llms.txt with routing, catalogue structure, SEO behaviour, and content boundaries for AI systems.

## Company summary

Orakel produces and sells event-related products including:

- Tyvek, vinyl, textile, RFID, and medical wristbands
- Plastic, wooden, biodegradable, and recycled tokens
- Lanyards, badges, and identification products
- Tickets, vouchers, drinkware, signage, and other printed event materials

Customers are primarily event organisers, venues, festivals, sports organisations, charities, and businesses ordering branded supplies online.

## Technology and content sources

The public website is a Nuxt SSR frontend backed by:

- A product information system (PIM) for catalogue, pricing, variants, stock, and product SEO fields
- A Drupal CMS for marketing pages, inspiration content, FAQ entries, jobs, and legal pages

Product URLs and CMS URLs are merged into locale-specific XML sitemaps.

## Locales and routing

The site uses locale-prefixed URLs (`/{locale}/...`). The catch-all locale for `hreflang x-default` is `en-eu`.

Active storefront locales include:

| Locale code | Audience |
| --- | --- |
| en-eu | European English (default / x-default) |
| nl-be | Belgium — Dutch |
| fr-be | Belgium — French |
| nl-nl | Netherlands |
| fr-fr | France |
| de-de | Germany |
| de-ch | Switzerland — German |
| en-gb | United Kingdom |
| en-no | Norway |
| en-za | South Africa |
| el-el | Greece |
| hu-hu | Hungary |
| it-it | Italy |
| pl-pl | Poland |
| pt-pt | Portugal |
| es-es | Spain |

Localized route names differ per locale. Examples:

| Page type | en-eu | nl-be |
| --- | --- | --- |
| Home | /en-eu | /nl-be |
| Product detail | /en-eu/products/detail/{slug} | /nl-be/producten/detail/{slug} |
| FAQ | /en-eu/frequently-asked-questions | /nl-be/veelgestelde-vragen |
| About | /en-eu/about-us | /nl-be/over-ons |
| Contact | /en-eu/contact | /nl-be/contact |
| Cart summary | /en-eu/shopping-cart/summary | /nl-be/winkelwagen/overzicht |
| Search | /en-eu/search | /nl-be/search |

Use sitemap files for authoritative URL discovery rather than guessing localized slugs.

## Key public pages (en-eu)

- [Homepage](https://www.orakel.com/en-eu)
- [Company information](https://www.orakel.com/en-eu/about-us)
- [FAQ overview](https://www.orakel.com/en-eu/frequently-asked-questions)
- [Contact details and forms](https://www.orakel.com/en-eu/contact)
- [Inspiration hub](https://www.orakel.com/en-eu/get-inspired)
- [Sustainability information](https://www.orakel.com/en-eu/orakel-works-green)
- [Privacy policy](https://www.orakel.com/en-eu/privacy-policy)
- [Cookie policy](https://www.orakel.com/en-eu/cookie-policy)
- [Terms and conditions](https://www.orakel.com/en-eu/terms-and-conditions)
- [Return policy](https://www.orakel.com/en-eu/return-policy)

Equivalent pages exist under other locale prefixes with translated slugs.

## Product catalogue structure

### URL pattern

Product detail pages follow:

`/{locale}/{localized-products-segment}/detail/{product-slug}`

Optional variant selection may appear as:

`/{locale}/{localized-products-segment}/detail/{product-slug}/{option-slug}`

### Data available on product pages

When configured in the PIM, product pages expose:

- Product and option-level titles, subtitles, and descriptions
- Meta title and meta description
- Media galleries with alt text
- Configurable options (colour, material, print type, etc.)
- Variant stock and availability signals
- Pricing or “cheapest from” pricing where calculable
- Supplement options
- Product-specific FAQ pairs
- Related products

Structured data emitted as JSON-LD `Product` includes name, description, image, brand, SKU/code, category when available, canonical URL, and offer price when price data exists.

### Major CMS category landing pages (nl-be examples)

These category hubs link into the product catalogue:

- /nl-be/polsbandjes — wristbands
- /nl-be/jetons — tokens
- /nl-be/lanyards-badges — lanyards and badges
- /nl-be/sport — sport products
- /nl-be/drukwerk — print work
- /nl-be/promotiemateriaal — promotional materials

## FAQ content

FAQ overviews render question and answer pairs from the CMS. When present, pages emit JSON-LD `FAQPage` with plain-text answers stripped from HTML.

Product detail pages may also include variant-level FAQ blocks from the PIM.

## Structured data emitted by the frontend

Global on most public pages:

- `Organization` — brand name, site URL, logo, email, phone from translations
- `WebSite` — site name and URL

Page-level when applicable:

- `Product` — product detail pages
- `BreadcrumbList` — pages with breadcrumb navigation
- `FAQPage` — FAQ lists with real Q&A content

Not currently emitted (requires CMS/PIM fields):

- `Article` for news/blog posts (author and date fields not consistently exposed)
- Review/rating aggregates
- GTIN/EAN/MPN identifiers in product schema

## Crawling, indexing, and AI access

### robots.txt

Public crawlers are generally allowed. AI-oriented user agents explicitly allowed include GPTBot, ClaudeBot, and Google-Extended. Sitemap index: /sitemapindex.xml

### Sitemaps

- Index: /sitemapindex.xml
- Locale sitemaps: /sitemap-{locale}.xml

Sitemap entries combine CMS pages and PIM product/variant URLs per locale.

### Noindex pages

The following page types are marked `noindex, nofollow`:

- Shopping cart and checkout flow
- Account area (orders, settings, saved carts, logos, contact persons)
- Authentication (login, register, password reset)
- Search results
- Quotation form submission flow
- Online payment success / utility pages
- Product customisation/configurator iframe pages

Do not treat these as canonical public content.

## International SEO behaviour

- `hreflang` alternate links are generated for all configured locales
- `x-default` points to the catchall locale URL (`en-eu`), not the bare domain root
- CMS pages map alternates through translated slugs when available
- Product pages map alternates through translated product slugs
- Utility pages map alternates through localized route paths

Canonical URLs on CMS pages may be supplied by Drupal metatags. Product pages emit frontend canonical URLs based on the current locale path.

## Semantic HTML conventions

- Primary page content is wrapped in `<main>`
- Breadcrumbs use `<nav aria-label="Breadcrumb">` with an ordered list
- When a CMS banner paragraph is the first content block, the banner owns the single page `<h1>`; the page header suppresses its own `<h1>` to avoid duplicates

## Contact and support

Contact details are localized. For accurate phone and email, use the contact page in the relevant locale, for example:

- https://www.orakel.com/en-eu/contact
- https://www.orakel.com/nl-be/contact

## Quoting and ordering

- Many products support online configuration and add-to-cart
- Quotation requests are available for some flows
- Checkout requires account authentication in configured markets

## Known data limitations for AI answers

When answering product-specific factual questions, prefer on-page product content and structured data. The following may be missing or incomplete in public APIs:

- GTIN/EAN/MPN/SKU identifiers
- Per-product brand names distinct from Orakel
- Review counts and aggregate ratings
- Exact last-modified dates in sitemaps
- Full variant-path coverage in all sitemap contexts

If a detail is not on the product page or in JSON-LD, state that it is not published on the site rather than inferring it.

## Related files

- [Summary guide (llms.txt)](https://www.orakel.com/llms.txt)
- [Crawling rules (robots.txt)](https://www.orakel.com/robots.txt)
- [URL discovery (sitemap index)](https://www.orakel.com/sitemapindex.xml)