GatsbyJS: How to Implement Schema Markup on Your Gatsby Site

Поделиться
HTML-код
  • Опубликовано: 12 дек 2024

Комментарии • 29

  • @jayeshsolanki1032
    @jayeshsolanki1032 4 года назад +1

    Amazing Content Phil. Will definitely share with my friends

  • @Sonotto
    @Sonotto 3 года назад +1

    Thanks for support@

  • @savitakumari729
    @savitakumari729 2 года назад

    Google rich results test not showing any items. I can see script tag with application/ld+json under elements tab in developers tools but not on google rich results test.
    Any idea ?
    Struggling with same thing for gatsby-plugin-next-seo

  • @lumina.studio8870
    @lumina.studio8870 3 года назад +1

    Thanks man, best regards!

  • @brunocesarlima1
    @brunocesarlima1 4 года назад

    Thank you! I had to adapt because I have another query, but it worked!

  • @wymarzonezycie194
    @wymarzonezycie194 3 года назад

    Thanks. To the point and well done. Nice voice btw.

  • @julieta1790
    @julieta1790 2 года назад

    Thank you! This helped a lot!

  • @JerenVids
    @JerenVids 4 года назад

    Thank you, worked!

  • @edrisaleigh6584
    @edrisaleigh6584 4 года назад

    Awesome video, but do i have to add the schema on all my pages

    • @GuidingDigital
      @GuidingDigital  3 года назад +2

      Not necessarily. In general, only add schema markup to the page that it applies. For example, the FAQ schema type should only be included on the FAQ page. For the organization schema type, only include it on one page (usually either the home page or contact us page). For other pages, only if you have content on the page that corresponds to a schema markup type. If your focus is to enable Google search results features, then just focus on the items that apply to those. I read an article recently that said that Google only cares about the schema items that enabled search features. This would be things on this page....
      developers.google.com/search/docs/guides/search-gallery

  • @sandeeshkumar4203
    @sandeeshkumar4203 3 года назад

    Automatically create schema markup for blog posts is that possible??

    • @GuidingDigital
      @GuidingDigital  3 года назад

      Yes. For my site, I've created a template for blog pages and then create the blog detail pages dynamically using logic in the gatsby node file. In your blog template you can add your schema markup with parameters for the parts such as title and description that will vary per blog post.

  • @fb7541
    @fb7541 3 года назад

    What would be the proper schema type to use for a service business? (LocalBusiness, Organisation, WebPage) I notice a lot of businesses in a similar industry are using the WebPage type... Does this matter?

    • @fb7541
      @fb7541 3 года назад

      And is it possible to use multiple schemas per page? And if so, how would I implement that for gatsby?

    • @GuidingDigital
      @GuidingDigital  3 года назад +1

      If your service business is physical in nature vs online I would use LocalBusiness. LocalBusiness is a subtype of organization. You also might even be able to get more specific than LocalBusiness. Go to schema.org/LocalBusiness and scroll down to the "More specific Types" section. If you see one that applies to your business, then use that instead. Regarding the use of webpage, you could also use that as well since it is a distinct type vs a sub-type. WebPage is less critical than LocalBusiness in my opinion since Google does not apply any search features based off of it that I know of.

    • @GuidingDigital
      @GuidingDigital  3 года назад +1

      Yes. You can have multiple schemas per page if they are distinct. Using the ones from your previous example, it would be valid to have both webpage and localbusiness since they are different types but you would not want to have both localbusiness and organization since localbusiness is a sub-type of organization.
      To include two you could add them to an array like this...
      [
      {
      "@context": "schema.org/",
      "@type": "WebSite",
      "name": "test",
      "url": "",
      "potentialAction": {
      "@type": "SearchAction",
      "target": "{search_term_string}",
      "query-input": "required name=search_term_string"
      }
      },
      {
      "@context": "schema.org",
      "@type": "Article",
      "author": "John Doe",
      "interactionCount": [
      "UserTweets:1203",
      "UserComments:78"
      ],
      "name": "How to Tie a Reef Knot"
      }
      ]
      or separate them into two script tags like this...
      {
      "@context": "schema.org/",
      "@type": "WebSite",
      "name": "test",
      "url": "",
      "potentialAction": {
      "@type": "SearchAction",
      "target": "{search_term_string}",
      "query-input": "required name=search_term_string"
      }
      }
      {
      "@context": "schema.org",
      "@type": "Article",
      "author": "John Doe",
      "interactionCount": [
      "UserTweets:1203",
      "UserComments:78"
      ],
      "name": "How to Tie a Reef Knot"
      }
      I'm showing that both of these methods validate (except for the missing values of course)

    • @frederickbogdanoff3796
      @frederickbogdanoff3796 3 года назад

      @@GuidingDigital fantastic! thanks for the response!

  • @kedronrhodes
    @kedronrhodes 4 года назад

    Thank you! This was so helpful!

  • @Wakpinside
    @Wakpinside 2 года назад

    Thanks :)

  • @vadymmotornyi555
    @vadymmotornyi555 2 года назад

    nice, ty

  • @anam7735
    @anam7735 4 года назад +1

    Hvala

  • @zulzdn9348
    @zulzdn9348 4 года назад +1

    nice