How to Boost Your SEO by Using Schema Markup: Best Tweets #SEMrushchat

Of course! We optimize key information on our website @schemaapptool. This includes Organization, BlogPosting, Product/SoftwareApplication, ContactPage/Contact Point, FAQ, Videos…

I have had lots of success with the Yoast plugin for FAQ using this technique: https://www.semrush.com/blog/weekly-wisdom-with-jason-barnard-how-to-create-google-friendly-faq/

All the Schema all the time. Of course. The question should be why are you not using it?!
JSON is my mark up weapon of choice.
and appropriate schema for the content. Events, company, breadcrumbs (they are underused!!)

Yes, most used:
Website
Organization
Breadcrumbs
Services

Yes, For Articles, Products & Reviews.

We are not – our site is hand-coded and adding it to our site would prove difficult. Ideas anyone?

@IntelliCentric Try using JSON-LD markup. It should be simple even if your site is hand-coded.

We do a lot of education on schema markup. We offer a free email course to learn the basics: https://t.co/PUeOI5TenT. I would also spend time really getting familiar with the Google documentation at https://developers.google.com/search/docs/data-types/article, and then going to read the examples at the bottom of the page on the class pages at https://schema.org/Article. Together they tell a story.

It depends on how you learn best. If you are like me and learn best by doing, I highly recommend:
1. Reading on the basics https://t.co/Jom4JEu04c
2. Browsing the gallery of what is possible https://bit.ly/2Se1IPi and
3. Trying this codelab from Google https://bit.ly/2vU5WEv
 

It is really not! I mean, I hate to do coding. But the logic in schema is so easy, I like checking what’s new and how I can use it.
I recommend looking for examples. look for basic schema added bij plugins and sites when http://schema.org lacks examples.
Use Google’s structured data testing tool, (or some other brand’s). But beware that a lot of warnings are false positives, like in any one-size SEO tool, and are not a true reflection of how the search engine machine itself handles the microdata.
Also, keep in the back of your mind that a CMS might throw up false positive errors and warnings too if specific microdata isn’t recognized as standard. Double-check how the output is handled with a good tool to make sure you’re not panicking over nothing.
And don’t worry: Google won’t punish bad form. If something’s wrong, you might not get a specific effect, but you won’t be punished. Unless you are obviously overdoing it with schema spam.

There is a learning curve but once you are in it really is simple. Google’s validator can throw the wrong errors sometimes but still a good starting point. @ScreamingFrog crawler now has a Schema check – very handy!
And of course @marthavanberkel’s fab site!

S-L-O-W and error-ridden writing by hand.

Some of the biggest challenges are around nesting elements correctly and figuring out the right values to use for certain attributes. Also dealing with attributes that are required but are not visible on the page.
There is some overlap between HTML5 semantic tags and schema tags. For example, <article>, <nav> vs https://schema.org/Article, https://schema.org/SiteNavigationElement.
Maybe, we could use semantic tags instead of schema when applicable.
See https://www.w3schools.com/html/html5_semantic_elements.asp

I would like to see more examples at Schema.org for implementing different types of Schema. There are some, but I think there would be more adoption of Schema if there were more fleshed out examples.

@bill_slawski Amen! Totally agree. I have challenged my team to start publishing our more complex examples, our own Schema.org example list 🙂

Getting developers to apply it automatically & explaining the schema concept to the client about how it is another facet in defining content for better relevancy for content spidering for SERP’s.

As with many SEO tactics/enhancements, the difficulty can often be explaining benefits to clients and implementation to dev resources. Some will get it, others will resist.

@schemaapptool Editor and Highlighter of course! Why? No code, automatic deployment, all schema types, great support and proper connected markup for simple and advanced content types. We also use Schema App WP Plugin for our blog = Free

We use Yoast, Schema & Structured Data for WP & AMP and I’ve heard great things about SchemaApp.
I like that they are effortless as they plug into the CMS to get what they need.

Use https://schema.org/Thing for reference, & I have used this plugin for WordPress sites https://wordpress.org/plugins/schema/. For other sites, it is getting developers to add Schema Markup into the code.

If your site uses Craft then @nystudio107 has built a brilliant schema plugin for it. Really takes the grunt out of the setup and running.

More types of Schema and more complex Schema could mean a steeper learning curve, but if it adds more value in terms of richer results & augmented search queries, it can be worth the effort.

I think these new challenges will breed new opportunities for SEOs and business owners. It wouldn’t be an exciting job without so many changes happening all the time!

I am excited for new types of content that can be optimized, especially in niches like health and finance. More features mean more opportunity, so overall = Good news. Depending on the team’s tools, knowledge and time to learn/test it can be good or bad!

Barrier to entry will seem higher.
Will probably demotivate some.
For those already on the bandwagon, this is a more (welcome) opportunity to express themselves.

We think it’ll be a combination of both. It would make their lives easier because having more types of schema could be beneficial for different types of websites. On the other hand, it would make it harder because it’s more to think about, implement, and test.

This is why it is critical to get out of plugins and explore the entire Schema library for properties in your respective type. The more familiar you are with the library, the easier your life will be marking up!