<p>Thanks again <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/RiccardoMasutti/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/RiccardoMasutti">@RiccardoMasutti</a>, another solid idea. However I think this one can be implemented better.</p>
<p>It would be <em>way</em> better if the blog post writer didn't have to manually adjust the JSON-LD markup.</p>
<p>Putting the following markup in <code>_layouts/post.html</code> solves this:</p>
<pre><code>    {
        "@context": "https://schema.org",
        "@type": "BlogPosting",
        "headline": "{{ page.title }}",
        "description": "{{ page.excerpt }}",
        "image": "https://bisq.network/images/bisq-fav.png",  
        "author": {
            "@type": "Person",
            "name": "{{ page.author }}"
        },  
        "publisher": {
            "@type": "Organization",
            "name": "Bisq",
            "logo": {
                "@type": "ImageObject",
                "url": "https://bisq.network/images/bisq-fav.png"
            }
        },
        "datePublished": "{{ page.date }}",
        "dateModified": "{{ page.date }}",
        "mainEntityOfPage": "{{ site.url }}{{ page.url }}"
    }
</code></pre>
<p>The markup above also makes the following changes:</p>
<ul>
<li>change <code>@type</code> to <code>BlogPosting</code> (is there a reason you picked <code>NewsArticle</code> instead?)</li>
<li>change publisher <code>name</code> to "Bisq" (see <a href="https://github.com/bisq-network/bisq-website/pull/290#discussion_r353023279" data-hovercard-type="pull_request" data-hovercard-url="/bisq-network/bisq-website/pull/290/hovercard">this comment</a>)</li>
<li>add <code>dateModified</code> and <code>mainEntityOfPage</code> properties, as the testing tool highly recommended them (see <code>mainEntityOfPage</code> documentation at the bottom of <a href="https://developers.google.com/search/docs/data-types/article" rel="nofollow">this page</a>)</li>
</ul>
<p>As for images, perhaps we could start adding some. In any case, some posts will have images and some will not, so it would be nice to assign <code>image</code> a value based on whether or not <code>page.image</code> exists...but that's more of a "nice-to-have" feature than a "must-have" feature for now, in my opinion.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq-website/pull/300?email_source=notifications&email_token=AJFFTNQ3M2AH2NKIYJACEEDQWYOIHA5CNFSM4JSNHRTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFYTTEA#issuecomment-561068432">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNX6TSPVNCZWOIQ3UWDQWYOIHANCNFSM4JSNHRTA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNQ2ADNCK7TBJSFJXVLQWYOIHA5CNFSM4JSNHRTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFYTTEA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq-website/pull/300?email_source=notifications\u0026email_token=AJFFTNQ3M2AH2NKIYJACEEDQWYOIHA5CNFSM4JSNHRTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFYTTEA#issuecomment-561068432",
"url": "https://github.com/bisq-network/bisq-website/pull/300?email_source=notifications\u0026email_token=AJFFTNQ3M2AH2NKIYJACEEDQWYOIHA5CNFSM4JSNHRTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFYTTEA#issuecomment-561068432",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>