Solved problems. Proven solutions.

Canonical generation should be based on the public destination URL for the specific deployment mode, not the CMS storage or preview URL. 1. Store the client’s canonical site origin as configuration rather than deriving it from the CMS host. 2. Resolve the public route/slug and generate one absolute canonical from origin + final path. 3. Keep previews, embed…

Separate content identity from presentation destination. The CMS should store the content entity once, while each publishing channel has an explicit URL mapping and SEO policy. Do not put one universal hard-coded canonical URL on a content record that can legitimately render on multiple sites. Define a primary web canonical when the same public content is s…

Choose the deployment mode based on control, crawlability, update frequency, and operational risk rather than using one mode everywhere. Static output is best when you can write files to the destination server and content changes are not second-by-second. It gives you predictable HTML, simple caching, direct crawlability, and low runtime dependency. The tra…