Understanding SEO Strict URLs in Evolution CMS 1.0.12

SEO Strict URL handling is useful only when the project clearly understands which requests should redirect, which should 404, and which aliases should resolve cleanly.

SEO Strict URLs can be powerful, but they also expose routing assumptions very quickly. The old 1.0.12 discussion behind this post centered on how requests such as index.html or made-up aliases should behave.

The Important Distinction

Strict URL logic should not be a vague “make URLs pretty” feature. It should define:

which alias is canonical
which requests deserve a 301 redirect
which requests should become a real 404

Why Confusion Happens

As soon as a site mixes IDs, aliases, rewritten paths, and home-page edge cases, teams can lose track of what the router is actually promising. Then a request like index.html becomes an argument instead of a rule.

The safe approach is to document the canonical URL policy and make sure the rewrite layer enforces it consistently. That is why this old topic still fits squarely into Best Practices.

Newer post

Diagnosing Random 500 and 424 Errors on a VDS Stack

A troubleshooting checklist for unstable server-side errors on Apache, PHP, and MySQL stacks where static files still load normally.

Older post

Protecting a Subscriber Database in MODX Revo

A practical security note on subscriber data, mailing lists, and why backups and access rules matter as much as the newsletter tool itself.