Schema Markup x Entity Home (Finally) Explained 🧐

แชร์
ฝัง
  • เผยแพร่เมื่อ 4 ก.พ. 2025

ความคิดเห็น • 34

  • @BrendaMalone
    @BrendaMalone 11 หลายเดือนก่อน +3

    @SchemingSchemas,
    Can you further explain about only including information in schema that appears on the page? Does that ONLY apply to the main entity of the page?
    I ask because in your entity Home Page Schema for Emerald Bridal, you do include information that is not on the page, like their Tax ID.
    So, when I am marking up an author, is it okay for my to include information about the university that they attended, even though it is not on the page? Thank you, Daniel.

  • @MertMango
    @MertMango ปีที่แล้ว +2

    Awesome, long time follower on LI. Happy to see long form content from you

  • @Wise.Webmaster
    @Wise.Webmaster 11 หลายเดือนก่อน +1

    Thanks a lot for the detailed explanation on Entities and schema.

  • @shafikhan6935
    @shafikhan6935 ปีที่แล้ว +1

    Saving it for later 😊

  • @yofredgs
    @yofredgs 11 หลายเดือนก่อน +1

    Nice video bro!

  • @devbash
    @devbash 11 หลายเดือนก่อน +2

    Good video! Would have just added that entity references (e.g. Wikidata pointing to /entity/ over /wiki/) should be in machine readable formats. You do use them in bridal example. I've been meaning to do a video/write up on this as well :)

  • @TheThinFrame
    @TheThinFrame 9 หลายเดือนก่อน

    If you have a pillar post in a blog doing a cluster witg 3 or 4 more blog posts how do u interconnect them with schema? U have a video? Thanks!

  • @BrendaMalone
    @BrendaMalone 11 หลายเดือนก่อน

    @SchemingSchemas, another esoteric question: with Google's Large Language Models now understanding most entities, is it possible that schema for larger sites is not as imperative as it used to be? Just a question we are pondering. I mean, I know schema publication is still important, just not AS important as it was when our schema markup was training the LLMs, so in the prioritization scope, I would not sacrifice more important SEO implementations over Schema publication. I would LOVE to know your thoughts. Thank you.

  • @GiorgioRumore
    @GiorgioRumore 11 หลายเดือนก่อน

    hi Daniel, thank you very much for this video. I have one question, is it wrong to use the "mainEntityofPage" instead of using "@id" to link the about page? In this way I link the webpage in which the Entity (organization) is the primary entity. Thank you in advance

  • @grasshopperweb
    @grasshopperweb 9 หลายเดือนก่อน

    I was under the impression you shouldn't use aggregateRating on your own business but I see you did that for your friends wedding dress shop. Is that common practice?

  • @danielivanov8617
    @danielivanov8617 ปีที่แล้ว +1

    Great video Daniel. If someone wanted to offer schema markup as a service to businesses, how would you charge that?

    • @SchemingSchemas
      @SchemingSchemas  ปีที่แล้ว +1

      I’ve offered day rates attached to tangible deliverables so that it’s easier for decision makers to measure value. Others I know charge per page or by template type. Then there are services that also create entity entries in various knowledge graph databases.

    • @danielivanov8617
      @danielivanov8617 11 หลายเดือนก่อน

      Great thank you Daniel. You feel there is enough business to create a full-time agency just out of Schema Markup? Or would it just have to be a service add as an SEO agency?

    • @SchemingSchemas
      @SchemingSchemas  11 หลายเดือนก่อน

      @@danielivanov8617 Agency model? Perhaps not.

  • @nebojsadurmanovic2268
    @nebojsadurmanovic2268 3 หลายเดือนก่อน

    Watching the video on October 18th and neither rich results test nor the schema validator show the category "mainEntity" anymore on the Emerald bridal website. Why is that?

    • @SchemingSchemas
      @SchemingSchemas  19 วันที่ผ่านมา

      I've removed schema markup across the entire site. I don't really see value in having an entity home anymore.

    • @nebojsadurmanovic2268
      @nebojsadurmanovic2268 19 วันที่ผ่านมา

      @SchemingSchemas damn. So what are the preferred schemas you're targeting now?

    • @SchemingSchemas
      @SchemingSchemas  15 วันที่ผ่านมา +1

      @ to be honest, none. Now if this were a real e-commerce site where product rich results would matter then it would be an entirely different story. However, outside of e-commerce related rich results I just don’t see any value in marking up entities any more.

  • @marcoilardi
    @marcoilardi 11 หลายเดือนก่อน

    Hi Daniel you have well structured data on your website but i can't see your knowledge panel searching on Google. Why?

    • @SchemingSchemas
      @SchemingSchemas  11 หลายเดือนก่อน +1

      Easy. I don’t have enough relevant backlinks 😅👀

    • @marcoilardi
      @marcoilardi 11 หลายเดือนก่อน

      @@SchemingSchemas start optimizing your Crunchbase profile

    • @marcoilardi
      @marcoilardi 11 หลายเดือนก่อน

      i work on knowledge panels and i found your video very very interesting

    • @x7mdNet
      @x7mdNet 11 หลายเดือนก่อน

      @@SchemingSchemas
      I think your gkg id is: /g/11mn0sqdg3 right?
      I don't think google count backlink itself to create a kg entity panel... there's others factors that google take like the context of a person like how much people search about him or about his work...

    • @SchemingSchemas
      @SchemingSchemas  11 หลายเดือนก่อน +1

      Correct. According to the API, you’ve found the URL of my knowledge panel.
      Links from relevant industry websites help. So my job this year is to land a few contributor bylines from SEJ, SEL, Backlinko, Semrush etc as these serve as strong trust signals for who I say I am based on my profession and content topics.
      I’d love to learn what you’ve observed!

  • @VojtěchFiala-r5e
    @VojtěchFiala-r5e 11 หลายเดือนก่อน

    Hi Daniel! Thank you for your work. You pretty much taught me to write structured data properly. However I'm now a little bit confused...
    In your post named "How to write JSON-LD code (from start to finish) for maximum semantic SEO gains" you wrote specifically that "Google does not crawl node identifiers from other URLs, therefore, even though you can reference a node identify from another page (.e.g., Person schema), Google won’t recognize it. As such, you will need to repeat the JSON-LD code on the page that you’re marking up."
    So... which one is correct? Does Google recognize identifyers across pages or not?
    Keep up the googd work and thanks in advance for any reply!

    • @SchemingSchemas
      @SchemingSchemas  11 หลายเดือนก่อน

      Good question.
      Any schema markup should reflect what is on the page itself. So instead of using only the unique identifier, add the name of the entity and type of entity.