Skip to documentation content

Article URL and BrowserTitle

On this page

    A page-capable Article needs URL and BrowserTitle together; Templates need Title; page-owning DatastoreItems, BlogPosts, and Calendar entries need the same page-identity fields when they have a page.

    When an Article is meant to be a page, the CMS expects page-identity fields — not only a Title. Missing them fails live import even when offline tooling used to look green.

    URL-bearing Articles need BrowserTitle
    Set `URL` for the page route (canonical form `//domain/path`, for example `"//help.marketpath.com/liquid/about"`). Once `URL` is set, `BrowserTitle` is required: the CMS rejects the import with "BrowserTitle: Value is required" if it is blank. `BrowserTitle` is the browser tab and search-result title; it is not the same as `Title` (display title) or `Name` (organizational identity). Offline validate errors when a URL-bearing Article lacks BrowserTitle — treat that as a real defect before import.

    Templates need Title
    Every Template record needs a non-empty `Title`. That is a separate CMS object rule from Article fields. A page Template without Title fails import the same way a URL-bearing Article without BrowserTitle does.

    Page-owning items use the same page fields
    A DatastoreItem, BlogPost, or Calendar entry that has its own page still needs its own `URL`, `TemplateGUID`, and `BrowserTitle` (plus the SEO fields the site conventionally sets). `CreatePageByDefault` on the parent does not fill those in a hand-authored package — see CreatePageByDefault.

    Not every Article is a page
    An Article with no `URL` is not necessarily page-capable; do not invent a URL only to satisfy BrowserTitle. When you do author a page, pair `URL` and `BrowserTitle` from the start, and usually set `TemplateGUID`, `MetaDescription`, `Keywords`, and `IncludeInSearch` with them — confirmed importable fixtures carry that full shape.

    Do not confuse these with menu or url-field shapes
    Article `URL` is the entity's page route. It is not MenuItem `Href` (a navigation string — MenuItem Identity and Order) and not a custom Type `url` field value (string or structured object — URL Field Values vs Menu Href).

    What this topic does not cover
    Validate CLI wording, stamp/combine workflows, and import-identity bookkeeping stay in the site-package toolkit.