Forums Forums White Hat SEO Does the old structured data testing tool still work properly? Started getting unusual errors on there

  • Does the old structured data testing tool still work properly? Started getting unusual errors on there

    Posted by seohelper on April 14, 2021 at 10:32 pm

    The old structured data testing tool which is apparently being replaced by Rich Results Test seems to have issues lately. I get errors on sites where there are no issues, and sometimes it isn’t even displaying structured data results. Is this because they’re shutting it down?

    A real shame because it’s always been the best tool for checking valid schema.

    The Rich Results Test is garbage and doesn’t provide any detailed info on valid/invalid schema.

    theonetechnologies1 replied 3 years ago 1 Member · 4 Replies
  • 4 Replies
  • q_ali_seattle

    Guest
    April 15, 2021 at 5:01 am

    Are you talking about google rich data tool?

    I had bookmarklet which is still working and one click.

    Plus my understanding is you can have multiple json ld schema on a page. Vs back in the early days only one type.

  • bsasson

    Guest
    April 15, 2021 at 7:16 am

    Yea, it’s not as reliable anymore. I use the rich results tester more now, especially for site’s using lots of JS.

  • sebranly

    Guest
    April 15, 2021 at 10:13 am

    It’s deprecated and they mention it. Please use Rich Results Test instead. If you don’t have enough information, you can verify on production via Google Search Console.

  • theonetechnologies1

    Guest
    April 15, 2021 at 1:32 pm

    Yes, you are right. I have just checked schema for my website because semrush is showing some error in a schema and when I checked in the rich results, it shows the schema is perfect. However, I find the mistake and Semrush has given me a green single for that.

    The error is I have created a schema for blog posting in microdata there is one itemprop which should be headline instead of that we are using name headline. I just changed the same and the schema issue has been resolved.

Log in to reply.