HeadRandom
Back to Main Site

PolyCMS Permalink & URL Settings

Last updated on May 16, 2026 3:05 AM

Permalink Settings

Navigate to Blog > Settings > Permalinks to configure your blog URL structure. PolyCMS supports fully customizable URL patterns for SEO-friendly content organization.

Blog Prefix

The blog prefix defines the root URL path for all CMS frontend pages:

PrefixResult URL
/blog (default)yourdomain.com/blog/post-title
/newsyourdomain.com/news/post-title
/articlesyourdomain.com/articles/post-title

Changing the prefix takes effect immediately. PolyCMS automatically regenerates the routing cache.

Category Base

Configure the URL segment for category archive pages:

  • Default: category → yourdomain.com/blog/category/web-development
  • Custom: topics → yourdomain.com/blog/topics/web-development

Tag Base

Configure the URL segment for tag archive pages:

  • Default: tag → yourdomain.com/blog/tag/php
  • Custom: label → yourdomain.com/blog/label/php

URL Caching

PolyCMS uses a prefix cache file (.blog_prefix_cache.php) to optimize dynamic routing performance. This cache is automatically regenerated when you save permalink settings.

If you experience 404 errors on frontend pages, navigate to Blog > Settings > Permalinks and click Save Settings to regenerate the cache manually.

Dynamic Routing System

The routing engine handles:

  • Post URLs: /{prefix}/{post-slug}
  • Category archives: /{prefix}/{category-base}/{category-slug}
  • Tag archives: /{prefix}/{tag-base}/{tag-slug}
  • Page URLs: /{prefix}/{page-slug}
  • Search: /{prefix}/search?q={query}

All routes are registered dynamically at runtime, requiring no manual .htaccess or web server configuration changes.

301 Redirects

When you change a post slug, PolyCMS maintains SEO integrity by supporting 301 redirect configuration. This ensures search engines update their index to the new URL without losing accumulated page authority.

Best Practices

  • Choose a blog prefix once and avoid changing it after content is indexed by search engines.
  • Use short, descriptive category and tag base slugs.
  • If migrating from another CMS, set up 301 redirects for old URLs.
  • After any permalink change, verify frontend pages load correctly.

Related Documentation