This article shows step-by-step how to configure friendly URLs for a datastore or a specific record, including slug generation rules and resolving collisions.
Datastore-Level Configuration
- Open Architect Panel → Datastores → (your datastore) → URLs.
- Define URL pattern — e.g.
/products/{slug}. - Choose which field is the slug source — typically the record's name.
- Set slug generation options:
- Lowercase.
- Replace spaces with hyphens.
- Strip non-ASCII (transliterate).
- Max length.
- Collision suffix (e.g. add -2, -3 on duplicates).
- Save.
Per-Record Override
For specific records you want a different slug than the auto-generated one:
- Open the record.
- Click Edit slug.
- Enter the desired slug (must be unique within the datastore).
- Save. The platform creates a redirect from the old slug to the new for 90 days.
Worked Examples
- Products: Pattern
/products/{slug}, slug from name, max 80 chars. “Widget Pro 2026 Edition” → widget-pro-2026-edition. - Customers (private): Pattern
/customers/{id}— internal-only; no SEO concern; keep IDs for stability. - Knowledge articles: Pattern
/help/{category}/{slug}— nested hierarchy. - Special-case override: A product named “Widget Pro™” auto-slugs to “widget-pro”; if there's already a “Widget Pro Lite” using that slug, the second uses “widget-pro-2”.