Core Features
The SEO Markup gcms Outputs by Default: Canonical, hreflang, Sitemap and JSON-LD
Server rendering, canonical, hreflang, sitemap, RSS and JSON-LD are generated by default. You write; gcms outputs the markup.
gcms outputs the core markup by default: you write the content, and the technical tags are already in place.

Every page is already-written HTML
The whole site is server-rendered, returning a complete page. Crawlers get the title, body and structured data without running any JavaScript, and above-the-fold content is already in the first HTML response — friendly to Core Web Vitals.
The SEO tags gcms outputs by default
- Self-referencing canonical, so search engines know each page's preferred URL;
- Multilingual hreflang (with
x-default); for language paths and translation groups, see how gcms handles multilingual sites; - Open Graph social cards;
- sitemap.xml and per-language RSS;
BlogPosting/BreadcrumbListJSON-LD that search engines can use for rich results.
Generated per page, and easy to check
Everything is generated per page to help search engines understand your content. Whether a page gets indexed or shows rich results is the search engine's call. To check a post's structured data yourself, run its URL through Google's Rich Results Test. If you serve the front end from Cloudflare, check after the first sync that canonical, sitemap and RSS URLs all use your production domain.
What to check before publishing
Automation does not replace editorial care. Each post still deserves a clear title, excerpt, meta description, keywords, slug and image alt text.