System label reference

Output types and sources

title, description, keywords, and H1 return text from the page editor's language tab. home_link returns the current language's home URL according to language and SEO settings. lang_menu, breadcrumbs, page_header_media, and site_search return complete HTML. Configure the language menu under Settings → Languages; breadcrumbs depend on the site tree and system module; the header background on page settings; and search on its results page and module.

Do not build a link to another page as [#home_link#]policy.html: nested URLs or an .html suffix may produce an invalid address. Use a field of type Internal Link instead. keywords remains for compatibility; modern search engines rarely use meta keywords for ranking. Do not place HTML-returning labels inside attributes.

System labels are available only in a page file template; the core fills them automatically, so the page editor does not offer a module binding for them. Variables %items%, %form%, %control%, and %message% belong to module templates and are filled by their modules. Sections <!-- @wrapper --> and <!-- @item --> also belong to module templates, not page labels.

If a label remains in the HTML

Check its capitalization, especially the uppercase H in [#H1#]. Confirm you are editing the file assigned to the current page. Save the template and reopen the page editor so the scanner detects its labels, then fill the corresponding field. For an ordinary, non-system label, assign an editor or active module instance. The same reference is available in the panel through the ? System Labels button.

The core resolves system labels in a page template. You do not have to create them as ordinary content blocks.

Set page-specific SEO fields and headings in the page editor for each language. Global elements such as the language switcher depend on site settings, active languages, and the current page.

Use the exact label capitalization: [#H1#] is not [#h1#]. If a label appears literally on the public page, check its spelling, module availability, and instance binding. Tokens such as %items% and %title% belong to module file templates and are not substitutes for page-level system labels.