Every article has a permalink — a short URL-friendly string that identifies it inside its channel. Readers see it in the address bar; search engines treat it as part of the page's identity. Get it right the first time and you won't have to think about it again.
How article URLs are built
For a channel served on the platform host:
/{culture}/c/{channel-permalink}/d/{article-permalink}For a channel served on a custom domain:
https://yourdomain.com/d/{article-permalink}For News and Help content, the URL shortens to:
/{culture}/news/{article-permalink}
/{culture}/help/{article-permalink}Rules for a good permalink
- Lowercase. Mixed case causes trouble with case-sensitive routing.
- Hyphens, not spaces or underscores.
my-first-post, notmy_first_post. - Short and meaningful. 2–5 words max.
pricing-update-2026beatsa-detailed-look-at-our-pricing-changes-for-the-new-year. - Unique within the channel. Two articles in the same channel can't share a permalink.
- Stable. Once you publish, don't change it without setting up a redirect.
If you leave it blank
OmniCon auto-derives a permalink from the title. It lowercases, strips punctuation, and joins words with hyphens. Usually fine, but review it before you publish — auto-derived slugs can be long or awkward.
Changing a permalink after publishing
Editing a permalink breaks every existing link to that article, both external (social posts, search results, bookmarks) and internal (other articles that link to it). Avoid it if you can.
If you must rename:
- Change the permalink.
- Update any internal links that pointed at the old slug.
- If the old URL has traffic worth keeping, add a redirect rule at the hosting layer.
Canonical URL
The optional Canonical URL field sets <link rel="canonical"> on the article page. Use it when the same content is published somewhere else and you want search engines to credit the other copy as the source of truth — for example, if you're re-publishing an article that originally ran on a partner site.