Choosing Between `[(site_url)]` and a Dynamic siteUrl Snippet in Evolution CMS

On a clean install, https://evo.im/ often looks good enough. But once a project has multiple host variants, staging copies, AJAX-heavy pages, or inconsistent www handling, the wrong base URL choice starts causing subtle breakage.

The key distinction is whether you want the configured canonical site URL or the current runtime host context. Those are not always the same thing. A static configuration value is safer for canonical consistency, while a dynamic snippet can better reflect the current host during certain frontend interactions.

This becomes especially sensitive around the <base href> tag. A wrong base value can quietly distort relative links, AJAX requests, and asset loading across alternate hosts or staging domains.

The practical takeaway is to decide which behavior you want on purpose instead of treating both options as interchangeable.