I know Schema.org very well - First, to implement schema.org you should know… schema.org - google/YouTube it (This is not an issue of Webflow and not “small” topic for “one tutorial” + Its take some time to really understand the idea).
The official Google docs about this topic:
Under the link above - the reference tab is very usefull (List of all types google support for rich results + docs + examples):
BlogPosting & CMS Example
step 0: learn the schema vocabulary
Read the schema.org docs BlogPosting and google-data-type-article docs -and/or- google/youtube it.
Step 1/2: select Format (json-ld -or- microdata)
microdata added by HTML tag attributes. You could easily add webflow custom attributes - but in practice, its not so easy to manage & very easy to destroy the structure by design (To move elements in the tree and so on) + Endless copy-paste but this is option one.
II: json-ld - Better option (Also reccomend by google)
json-ld embedded in webflow by custom code:
The most important thing you should know about
json-ld is this:
Don’t mark up content that is not visible to readers of the page. For example, if the JSON-LD markup describes a performer, the HTML body should describe that same performer. Google Quality guidelines
Why it’s important? because its really easy to paste valid
json-ld to webflow and only change the content (By Dynamic -or- static data).
In other words:: if you added by
datePublished attribute the
datePublished should be visible also for the users (visible element on the page).
Real Example of https://schema.org/AggregateRating:
STEP 2/2: WEBFLOW : The easy part now
BlogPosting schema before
"headline": "14 Ways Json Can Improve Your SEO",
"alternativeHeadline": "and the women who love them",
"award": "Best article ever written",
"editor": "John Doe",
"genre": "search engine optimization",
"keywords": "seo sales b2b",
"publisher": "Book Publisher Inc",
"description": "We love to do stuff to help people and stuff",
"articleBody": "You can paste your entire post in here, and yes it can get really really long.",
** I only find problems with
articleBody (It should be
plain text) - one option, for now, is to create extra field and
copy-paste inside this field only the body text (Without images, bold text, italic and so on) - not perfect but work fine. Anyway google dont use this attribute (see her).
Last step - Structured Data Testing Tool - Google
Paste your url her:
Full Screenshot of
0 warning - 0 errors for blog post (post with reference feilds for
Extra Semantic - wrap your article with HTML
Extra Tip: Easier to work with relative domains
Use relative paths for
urls (Like this no need to update the code if you change the domain + will work fine also for
Relative URL (remember the