PeakD & Rich Snippets - Some SEO Thoughts for our Articles and Blogposts on HIVE

[louis88]

Since the topic of search engine optimization is always on my mind and I have already seen that some articles written on PeakD are not displayed quite accurately in the search engines, I would like to publish a few articles in the near future that are dedicated to optimizing the articles that are published on PeakD. I will focus on the PeakD frontend, as this is my absolute favorite in terms of the developers behind it, its speed and reliability. So I won't be publishing any content for InLeo, Ecency or Hive.Blog for the time being.

_{Ideogram V2 • NONE • 16:9 • Feb 14, 2025 10:32 PM Prompt: "A User sitting in a space in front of his laptop, writing an article concentrated"}

In this article I would like to show 3 possibilities for schemas that could be integrated on PeakD in some way so that Google can better understand the articles we write here. In this article, I'm only taking a closer look at a blog post from back then that already has a pretty good ranking. This is my review of a pizzeria on the island of Koh Lanta from 2022. The article can be found here: https://peakd.com/hive-120586/@louis88/bows-pizza-on-koh-lanta-one-of-the-best-pizzeria-i-have-found-so-far-in-thailand

I'll show 3 code examples - 1. rich snippet review, 2. rich snippet article, 3. rich snippet blog post

Let's start with Rich Snippet Review, as my article was a review of my visit to the restaurant.

Rich Snippet Review

{
  "@context": "https://schema.org",
  "@type": "Review",
  "itemReviewed": {
    "@type": "Restaurant",
    "name": "Bow's Pizza",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "Koh Lanta",
      "addressCountry": "Thailand"
    },
    "servesCuisine": "Italian",
    "priceRange": "$$",
    "aggregateRating": {
      "@type": "AggregateRating",
      "ratingValue": "4.8",
      "reviewCount": "25"
    }
  },
  "author": {
    "@type": "Person",
    "name": "Louis88"
  },
  "publisher": {
    "@type": "Organization",
    "name": "PeakD",
    "url": "https://peakd.com"
  },
  "datePublished": "2022-12-29",
  "reviewBody": "Bow's Pizza on Koh Lanta is one of the best pizzerias I have found in Thailand so far. The crust is perfectly crispy, and the ingredients are fresh. Highly recommended for anyone visiting the island!",
  "reviewRating": {
    "@type": "Rating",
    "ratingValue": "5",
    "bestRating": "5",
    "worstRating": "1"
  }
}

Explanation:

• @type: Review → Indicates that this is a review.
• itemReviewed: Restaurant → Defines the reviewed entity (Bow's Pizza).
• address → Contains location details for Koh Lanta, Thailand.
• servesCuisine → Describes the type of cuisine (Italian/Pizza).
• priceRange → Indicates the approximate price level ($$ for mid-range pricing).
• aggregateRating → Represents an average rating based on multiple reviews.
• author → The author of the review (your Hive account louis88).
• publisher → The platform where the article was published (PeakD).
• datePublished → The publication date of the article.
• reviewBody → The actual review, including a short description.
• reviewRating → The rating of the restaurant (scale from 1 to 5).

We certainly cannot use some of the available rich snippets here, as we do not have or are not a rating system for locations. What I could imagine, however, is that @worldmappin from @detlev could also use some of them here. All in all, I think that rich snippets make a lot of sense so that Google and the other search engines can recognize better and faster what kind of content it is. However, I think the following two are better suited for longer articles that we publish on Hive.

Rich Snippet Article

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Bow's Pizza on Koh Lanta - One of the best pizzerias I have found so far in Thailand",
  "author": {
    "@type": "Person",
    "name": "Louis88",
    "url": "https://peakd.com/@louis88"
  },
  "publisher": {
    "@type": "Organization",
    "name": "PeakD",
    "logo": {
      "@type": "ImageObject",
      "url": "https://peakd.com/favicon.ico"
    }
  },
  "datePublished": "2022-12-29",
  "dateModified": "2022-12-29",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://peakd.com/hive-120586/@louis88/bows-pizza-on-koh-lanta-one-of-the-best-pizzeria-i-have-found-so-far-in-thailand"
  },
  "articleSection": "Travel, Food, Reviews",
  "keywords": "Pizza, Koh Lanta, Thailand, Best Pizzeria, Food Review",
  "description": "A detailed review of Bow's Pizza on Koh Lanta, Thailand – one of the best pizzerias I have found so far!",
  "image": "https://images.hive.blog/0x0/https://files.peakd.com/file/peakd-hive/louis88/EoK4qzGeutSgirjroXnGP8ZbbDLu5c4iZjMDUuQ9svYffWgnXHiwosBLBrzwm7G1nBV.jpg",
  "wordCount": "1200"
}

Rich Snippet BlogPosting

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Bow's Pizza on Koh Lanta - One of the best pizzerias I have found so far in Thailand",
  "author": {
    "@type": "Person",
    "name": "Louis88",
    "url": "https://peakd.com/@louis88"
  },
  "publisher": {
    "@type": "Organization",
    "name": "PeakD",
    "logo": {
      "@type": "ImageObject",
      "url": "https://peakd.com/favicon.ico"
    }
  },
  "datePublished": "2022-12-29",
  "dateModified": "2022-12-29",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://peakd.com/hive-120586/@louis88/bows-pizza-on-koh-lanta-one-of-the-best-pizzeria-i-have-found-so-far-in-thailand"
  },
  "articleBody": "Bow's Pizza on Koh Lanta is an amazing find for pizza lovers visiting Thailand. Their freshly baked pizzas, delicious crust, and authentic Italian flavors make it one of my favorite spots. Here’s why you should check it out!",
  "articleSection": "Travel, Food, Reviews",
  "keywords": "Pizza, Koh Lanta, Thailand, Best Pizzeria, Food Review",
  "description": "A travel blogger's review of Bow's Pizza on Koh Lanta, Thailand – one of the best pizzerias I have found so far!",
  "image": "https://images.hive.blog/0x0/https://files.peakd.com/file/peakd-hive/louis88/EoK4qzGeutSgirjroXnGP8ZbbDLu5c4iZjMDUuQ9svYffWgnXHiwosBLBrzwm7G1nBV.jpg",
  "wordCount": "1200"
}

Choosing the Right Schema Markup: Article vs. BlogPosting

When publishing content online, SEO optimization plays a key role in making sure my articles reach the right audience. One important factor in this is the Schema Markup I use. For written content like my review of Bow’s Pizza on Koh Lanta, the two most relevant options are Article and BlogPosting but they serve different purposes. The review too, actually, but I'm not sure about that as PeakD hasn't yet established itself as a review platform / service that does reviews.

🔍 Key Differences Between Article and BlogPosting

Feature	Article 📰	BlogPosting 📝
Purpose	General articles, news, or structured research pieces	Blog posts, personal experiences, and storytelling
SEO Optimization	Better for editorial content & news	Better for personal blogs & search rankings in blog-related queries
Structure & Style	More structured, meant for formal reporting	More casual, often includes personal opinions and emotions
Best For	News websites, corporate articles, research	Travel blogs, experience-based reviews, storytelling

---

📰 Why Article Doesn't Fit My Review

If I were writing a formal travel article for a professional publication, Article could be a reasonable choice. It's designed for news, research, and structured reports things like “The 10 Best Pizzerias in Thailand” or a fact-based analysis of Koh Lanta’s food scene.

But that's not what my content is about. I’m not trying to provide a corporate or journalistic perspective. I want to share my personal experience and honest thoughts about one of the best pizzerias I’ve found so far in Thailand.

---

📝 Why BlogPosting is the Right Choice

Since this review is based on my personal experience, BlogPosting is the perfect schema markup because:

• It signals to Google that this is a blog post, making it more likely to appear in blog-related search results.
• It allows me to structure the content in a more informal, storytelling-driven way, rather than following strict journalistic guidelines.
• The articleBody property enables a detailed, in-depth description of my experience, which fits my long-form travel content.

If someone searches for “Best Pizza in Koh Lanta”, I want them to find my personal review, not just another travel guide listing. This is why BlogPosting makes the most sense.

---

Final Thoughts

At the end of the day, Schema Markup isn’t just about SEO! It’s about context. Choosing BlogPosting over Article helps me categorize this review in a way that matches my intent and helps readers find authentic experiences rather than generic travel summaries.

So, if you’re writing a personal food review, travel story, or experience-based blog, BlogPosting is the way to go. If it’s more of a formal, research-driven piece, then Article is a better fit.

For my Bow’s Pizza review, I’m sticking with BlogPosting, because this is my story, my experience, and my recommendation. And now I need an integration in PeakD's source code for my blog post that integrates the Markup BlogPosting schema - yes, I know it won't work overnight, but would be a good first step in good search engine optimization for our blogs and articles here on Hive :) Looking forward to feedback from @asgarth @peakd @jarvie

Comments

[coldbeetrootsoup]

What about FAQ? Questions and answers can also be a huge SEO help.

[bozz]

So you do that in markdown or you actually do something in the code? I think there was a different front end that does reviews. Tasteem went away, but there was another one waivio. It doesn't really matter since you are just talking about peakd. Thats mainly what I use anyway.

[nicklewis]

This is interesting as our content must be indexed quite a lot due to the different front-ends. Therefore different indexes will exist for each of our posts in guessing?

Is that even a good thing?

[detlev]

All what drives more visibility for all our Hive Posts is for my understanding

HIGHLY WELCOME

So, automatically extracting this information from the metadata, including all tags and data, doesn’t seem overly complex.