Metas.liquid

Purpose

Metas.liquid is responsible for rendering the HTML <head> metadata used across the Noir theme.

It centralizes common head tags such as:

charset / viewport

page title

SEO-related meta tags (description, robots, canonical)

social sharing tags (Open Graph, Twitter cards) when available

any other required headers provided by the platform/page model

Keeping these tags in a single file ensures consistency and minimizes duplication across layouts.

Where it's used

Metas.liquid is rendered by the main layout template:

Structure/LayoutA.liquid

Example (from the layout):

{% render 'Structure\\Metas' %}

This means every page that uses LayoutA.liquid will also include Metas.liquid.

Inputs / data sources

Metas.liquid reads metadata from global Liquid objects provided by the platform.

Common data sources you'll typically see used in metas templates:

Root.Page.Metas.*

language / iso language

title

description

canonical url (if provided)

additional meta flags

GlobalData.*

root paths (used for absolute URLs in OG images, icons, etc.)

settings that affect indexing, analytics, environment, etc.

Note
The exact metadata keys depend on what the platform provides in Root.Page.Metas.
The goal of this doc page is to explain what Metas.liquid is responsible for, not to enforce a fixed set of keys.

Output

The template outputs tags inside <head> such as:

<meta ...>

<title>...</title>

<link rel="canonical" ...>

<link rel="icon" ...> (if included)

<meta property="og:*" ...> (if included)

Common changes

Typical reasons to modify Metas.liquid:

add or adjust canonical logic

add missing SEO tags (robots, theme-color, hreflang)

adjust Open Graph / Twitter meta tags for social sharing

add favicon links / manifest links

include platform-required headers once, centrally

Recommendations

Avoid duplicates: don't output the same meta tag from multiple places (layout + component). Keep head elements here.

Prefer absolute URLs for OG images/canonical when possible, especially for social platforms.

Be careful with robots/noindex rules: ensure staging/dev environments don't leak as indexable pages if that's a concern.

Encoding: keep <meta charset="utf-8"> early in the head.

Metas.liquid

Purpose#

Where it's used#

Inputs / data sources#

Output#