Author
Quan
Date
12/9/25
Updated
6/24/26
Read Time
2 min
Web Design
Category
technical seo
ai overviews
More in
Web Design
Start with the page a visitor can see
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 a Giao.News article, the central information is simple: a headline, a summary, an author, an image, published and updated dates, a canonical URL, and a place in the site hierarchy. Those are the facts search systems need help reading.
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
Keep the article graph small and accurate
A complicated schema graph does not make an article more useful. One well-described article connected to its page and breadcrumb is usually more durable than a pile of loosely related types.
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.
Test the rendered template, then keep auditing
Publishing is the point where markup becomes real. Check the live URL after an import, especially when images, CMS references, or custom code are involved. Confirm that the canonical, headline, dates, and image in the markup match the rendered page.
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.
Answer first
Schema gives search engines a reliable description of a page, but it only works when it matches what visitors can actually see. In Framer, the scalable approach is to map CMS fields once and generate JSON-LD from the template.
Key Takeaways
Treat schema as a reflection of the CMS, not a second editorial system.
Use one clear primary type for each template, then add only relationships the page truly supports.
Keep the headline, visible page copy, image, author, dates, and structured data aligned.
Validate the rendered page after publishing, not only the code before launch.
FAQ
Does schema improve rankings by itself?
No. Schema helps search systems interpret a page. It does not replace strong content, clear information architecture, or technical performance.
Which fields should every article template expose?
At minimum, use the visible headline, description, image, author, published date, updated date, canonical URL, and breadcrumb path.
Why use CMS fields instead of writing markup manually?
Template-level mapping keeps every article consistent and reduces the chance that a title, image, or date becomes stale in the structured data.