Schema for Framer CMS: A Practical JSON-LD Guide

1. Match the schema to the page

   Schema is useful when it describes a real page clearly. It should not introduce claims, images, dates, or entities that appear nowhere in the article itself. A CMS template makes this easier because the same fields can power both the visible layout and the JSON-LD.

   For Giao.News, the relevant CMS fields already exist: Title, Meta Desc, Image, Date, Updated Date and Author. The template can describe a BlogPosting without inventing ratings, testimonials, prices or publication details that are absent from the article.

   
   

2. Map fields before choosing markup

   Begin with the CMS fields you already maintain. The article title maps to headline. The preview image maps to image. The author, date, updated date, and description should come from their own fields rather than copied text.

   This prevents one of the most common template problems: a page changes in the CMS while its structured data keeps an old headline or an unrelated description. The CMS should stay the source of truth.

   • Article or BlogPosting for a news entry

   • WebPage or ItemPage for the page that contains it

   • BreadcrumbList for the real navigation path

   • Organization and WebSite at the site level, not repeated as filler

   In Framer, open Project Settings, then Custom Code. Add a script scoped to the Giao.News CMS detail template, place it in the document head, and enter the following markup. The expressions must match the CMS field names in the live project.

   <script type="application/ld+json">
   {
     "@context": "https://schema.org",
     "@type": "BlogPosting",
     "headline": {{Title | json}},
     "description": {{Meta Desc | json}},
     "image": {{Image | json}},
     "datePublished": {{Date | json}},
     "dateModified": {{Updated Date | json}},
     "author": {
       "@type": "Person",
       "name": {{Author | json}}
     },
     "publisher": {
       "@type": "Organization",
       "name": "QART",
       "url": "https://qart.gallery"
     }
   }
   </script>

   The | json filter produces JSON-safe field values, so do not wrap the expressions in additional quotation marks. This code belongs in Framer Custom Code, not in an article’s rich-text body. A displayed code sample is documentation, not installed schema. Framer explains the process in its structured data guide.

   
   

3. Keep the article graph small and accurate

   Start with one BlogPosting object for the article. If the site already defines an organization, website, or breadcrumbs elsewhere, avoid adding conflicting copies. More types will not fix incorrect field mapping.

   Choose a type because the page earns it. A Giao.News essay is an Article. An artwork page may also need VisualArtwork. A product page may need Product. The category should follow the object the user is actually viewing.

   Do not add ratings, reviews, prices, availability, or author credentials that visitors cannot verify on the page. Structured data should not create a second, more promotional version of the content.

   
   

4. Maintain the template as content changes

   After publishing, inspect at least two live article URLs, including one with an apostrophe or quotation mark in the title. Confirm that the source contains one valid application/ld+json script for the article, that the CMS expressions have resolved, and that headline, image, publication date, modified date and author match the visible article. Run the Rich Results Test for Google-supported features and Schema Markup Validator for general syntax.

   Schema is maintenance work. When a collection changes, revisit the template before it creates hundreds of mismatched entries. The goal is not a perfect score from a tool. The goal is a site whose machine-readable structure stays honest as the site grows.

Related articles

• QART.Studio

• Website Content Audits: What to Fix Before a Redesign