on 10 June 2026, by Bogdan, in Blog, Cloud, Updates, Guides

by Bogdan

A clean URL is worth more than you think. Before a visitor even clicks on your link, your URL is already doing SEO work - signaling to search engines what your page is about, building trust with readers, and reflecting the professionalism of your brand.
In Brizy Cloud, you now have full control over how your URLs are structured: from setting global permalink patterns for blog posts and custom content types, to assigning custom slugs to individual pages. This guide walks you through everything you need to know to get your permalink structure right from day one.
Your URL is one of the most overlooked on-page SEO factors. Yet it influences:
The bottom line: good URLs don't just look professional - they actively contribute to your rankings, your CTR, and your site's overall SEO health.
Before diving into the Brizy Cloud settings, here's a quick reference for writing SEO-friendly URLs:
✅ Do:
❌ Avoid:
A great URL answers the question: "Could someone guess what this page is about just from reading the URL?" If yes, you're on the right track.
Rather than setting a URL manually for every blog post you publish, Brizy Cloud lets you define a permalink pattern - a template that automatically generates the right URL structure for every new post.

/{collectionType.slug}/{slug} |
Here, {collectionType.slug} pulls in your Asset Slug (blog), and {slug} is automatically generated from your post title. So a post titled "Introducing Brizy AI for WordPress" would get the URL:
file:///blog/introducing-brizy-ai-for-wordpress |
For full setup instructions with screenshots, see the Brizy Cloud permalink documentation.
Pattern | Example URL |
|---|---|
/{collectionType.slug}/{slug} | /blog/introducing-brizy-ai-for-wordpress |
/{id} | /9101925 |
/{year}/{month}/{day}/{slug} | /2026/05/20/introducing-brizy-ai-for-wordpress |
SEO recommendation: Use /{collectionType.slug}/{slug} for blog posts. It's clean, descriptive, and future-proof. Avoid the date-based pattern for evergreen content - dates can make posts look outdated even when the content is still highly relevant.
Brizy Cloud's CMS supports custom content types beyond blog posts: things like Recipes, Case Studies, Team Members, Properties, or whatever fits your business. You can set permalink patterns for these custom assets exactly the same way.
Example: A Recipes collection
/{collectionType.slug}/{slug} |
A recipe called "Baked Sausage Breakfast Hash" would automatically receive the URL:
/recipes/baked-sausage-breakfast-hash |
This approach works beautifully for any custom collection. The key is choosing an Asset Slug that clearly represents the content type and matches how users would naturally search for it.
Why consistent patterns matter
When all your content of a given type lives under the same URL prefix (/recipes/, /case-studies/, /properties/), you're sending clear topical signals to search engines. It groups related content together, reinforces your site's subject matter, and makes internal linking much more intuitive.
Permalink patterns handle the vast majority of your content automatically. But sometimes you need more control: to organize content into subcategories, or to craft a URL that's particularly keyword-rich.
Brizy Cloud lets you override the auto-generated permalink on any individual post or custom asset.
Say the auto-generated permalink for a recipe is:
/recipes/baked-sausage-breakfast-hash |
You can change this to:
/recipes/breakfast-brunch/baked-sausage-breakfast-hash |
Simply type the new permalink in the Permalink field for that asset and click Update.
Auto-generated:
/blog/introducing-brizy-ai-for-wordpress |
Custom:
/blog/updates/introducing-brizy-ai-for-wordpress |
When should you use custom permalinks?
Important: If you change the permalink of a published page after it's already indexed, make sure to set up a 301 redirect from the old URL to the new one. Broken links and lost backlink equity are a common SEO pitfall when URLs are changed carelessly.
Unlike posts and custom assets, standard pages in Brizy Cloud don't use permalink patterns, each one gets its URL set individually. This is actually a feature, not a limitation. It gives you complete flexibility to structure your pages however you like.
One of the most useful applications is grouping related pages under a shared URL prefix, even if those pages don't share a CMS collection.
For example, if you offer multiple services, you can organize all your service pages like this:
/services/web-design /services/seo-consulting /services/branding /services/copywriting |
To set this up, simply click the page name in your Brizy Cloud dashboard and type the desired permalink in the Permalink field.
Why this matters for SEO: Consistent URL prefixes signal to search engines that these pages belong to the same topical cluster. It reinforces site structure, supports your internal linking strategy, and makes breadcrumb navigation more meaningful.
This is where custom page permalinks unlock some genuinely powerful SEO capability.
If you offer services in multiple cities or regions, but don't have a physical address in each location, you can create location-specific landing pages with URLs that target each area. This is one of the most effective tactics for local SEO, and Brizy Cloud makes it easy to implement.
/[service]/[country-or-state]/[city]/[neighborhood] |
/web-design/us/washington-dc /web-design/us/washington-dc/capitol-hill /web-design/us/washington-dc/georgetown /web-design/us/arlington-va /web-design/us/bethesda-md |
Each of these pages can be individually tailored with location-specific content, local keywords, testimonials from clients in that area, and references to local landmarks - all signals that boost local search relevance.
Why this works:
To implement this, create a dedicated page for each location in Brizy Cloud and assign the appropriate custom permalink via the Permalink field.
Blog Posts | ✅ Yes | ✅ Yes (overrides pattern) |
Custom Assets (e.g., Recipes) | ✅ Yes | ✅ Yes (overrides pattern) |
Pages | ❌ No | ✅ Yes |
{collectionType.slug} | The Asset Slug set for the collection (e.g., blog, recipes) |
{slug} | The individual post or asset slug (auto-generated from title) |
{id} | The numeric page ID |
{year} | Publication year (4 digits) |
{month} | Publication month (2 digits) |
{day} | Publication day (2 digits) |
1. Not setting a permalink pattern before publishing content. If you add posts before configuring your permalink pattern, those posts may get suboptimal URLs. Set your patterns before you start publishing.
2. Changing live URLs without redirects. Every time a published URL changes, any existing backlinks, bookmarks, and indexed pages point to a dead address. Always set up 301 redirects when changing URLs.
3. Using date-based patterns for evergreen content. /2022/04/15/how-to-bake-sourdough looks stale in 2026. Use the /{collectionType.slug}/{slug} pattern for timeless content.
4. Ignoring the asset slug. The Asset Slug is the prefix for your entire collection. Choose it carefully - it should be the word your audience would naturally use to navigate to that content type (e.g., blog, recipes, resources, case-studies).
5. Creating overly deep URL structures. While hierarchical URLs are great for SEO, going more than 3–4 levels deep (/a/b/c/d/e/f) dilutes the signals and makes URLs harder to share. Keep it meaningful but lean.
Getting your permalink structure right in Brizy Cloud is one of the highest-leverage SEO tasks you can do early in your site's life. Here's the short version:
Have questions about setting up your permalink structure? Just reach out to our support team at [email protected]
Contact Support
Email: [email protected]