Page Groups - URL Patterns
# Page Groups - URL Patterns
URL patterns define the structure of your generated page URLs. Each page group has a single URL pattern that determines how data entries map to specific URLs.
## Pattern Syntax
A URL pattern consists of a static path with a `{slug}` placeholder:
- `/services/{slug}/` — resolves to `/services/new-york/`, `/services/london/`, etc.
- `/products/detail/{slug}/` — resolves to `/products/detail/widget-pro/`, etc.
The `{slug}` portion is replaced with the value of the slug field from each data entry.
## Base Page Relationship
The base page acts as the template for all generated pages under a URL pattern. When a matching URL is requested:
1. SleekRank matches the URL against all active page group patterns
2. It extracts the slug from the URL
3. It looks up the corresponding data entry by slug
4. It loads the base page content
5. It applies all configured replacements
6. It serves the modified content as the response
## URL Resolution
SleekRank intercepts WordPress's URL resolution early in the request lifecycle. If a requested URL matches a page group pattern and a valid data entry exists for the extracted slug, the page is served. Otherwise, WordPress continues its normal routing (resulting in a 404 if no other page matches).
## Best Practices
- **Use descriptive paths**: `/services/{slug}/` is better than `/{slug}/` for SEO
- **Keep slugs clean**: Ensure your data slugs are lowercase, hyphenated, and URL-safe
- **Avoid conflicts**: Don't create URL patterns that overlap with existing WordPress pages
- **Trailing slashes**: Include trailing slashes to match WordPress permalink conventions
URL patterns define the structure of your generated page URLs. Each page group has a single URL pattern that determines how data entries map to specific URLs.
Pattern Syntax
A URL pattern consists of a static path with a {slug} placeholder:
/services/{slug}/— resolves to/services/new-york/,/services/london/, etc./products/detail/{slug}/— resolves to/products/detail/widget-pro/, etc.
The {slug} portion is replaced with the value of the slug field from each data
entry.
Base Page Relationship
The base page acts as the template for all generated pages under a URL pattern. When a matching URL is requested:
- SleekRank matches the URL against all active page group patterns
- It extracts the slug from the URL
- It looks up the corresponding data entry by slug
- It loads the base page content
- It applies all configured replacements
- It serves the modified content as the response
URL Resolution
SleekRank intercepts WordPress's URL resolution early in the request lifecycle. If a requested URL matches a page group pattern and a valid data entry exists for the extracted slug, the page is served. Otherwise, WordPress continues its normal routing (resulting in a 404 if no other page matches).
Best Practices
- Use descriptive paths:
/services/{slug}/is better than/{slug}/for SEO - Keep slugs clean: Ensure your data slugs are lowercase, hyphenated, and URL-safe
- Avoid conflicts: Don't create URL patterns that overlap with existing WordPress pages
- Trailing slashes: Include trailing slashes to match WordPress permalink conventions