Riksdagsmonitor Intelligence Platform โ€” API Documentation - v1.0.30
    Preparing search index...

    Result of computeArticleHeadMetadata.

    Carries both the raw front-matter inputs that fed the SEO composer and the computed <head> strings that ship in the rendered HTML, so consumers (renderer, QA reports) get a complete picture in one call.

    interface ArticleHeadMetadata {
    ย ย ย ย rawTitle: string;
    ย ย ย ย rawDescription: string;
    ย ย ย ย rawKeywords: string;
    ย ย ย ย date: string;
    ย ย ย ย articleTypeId: string;
    ย ย ย ย articleTypeLabel: string;
    ย ย ย ย articleSection: string;
    ย ย ย ย seo: ArticleSeoMetadata;
    ย ย ย ย brandedTitle: string;
    }
    Index
    rawTitle: string

    Raw title: from the article.md front-matter (post-cascade).

    rawDescription: string

    Raw description: from the article.md front-matter (post-cascade).

    rawKeywords: string

    Raw keywords: from the article.md front-matter (post-cascade), or undefined.

    date: string

    Normalised publication date (YYYY-MM-DD).

    articleTypeId: string

    Article-type ID slug (propositions, committee-reports, โ€ฆ).

    articleTypeLabel: string

    Localized article-type label (Propositions, Komitรฉindstillinger, โ€ฆ).

    articleSection: string

    The article:section / articleSection value passed to chrome and JSON-LD by the renderer. Exposed here so the audit CLI reports exactly what ships in the rendered HTML without re-implementing the same derivation.

    Computed SEO <title> / <meta description> / <meta keywords> triple from buildArticleSeoMetadata โ€” i.e. exactly what the renderer hands to chrome.

    brandedTitle: string

    Branded <title> as emitted by chrome/head.ts: seo.title unchanged when it already mentions "Riksdagsmonitor", otherwise ${seo.title} โ€” Riksdagsmonitor.