Is Schema markup inappropriate for ?
-
Is Schema(.org) markup meant specifically to be used on text? Or can you use it in a similar way that you can use Open Graph Protocol?
For example, for awhile I've been using something like this on my site:
Because it's in the head section, it appears on every page. In review, this seems to be an incorrect use? Should I only be using Schema to mark specific text? If not, what are the consequences of using Schema like this?
-
Ok, now I got the questions... sry. I didn't know the answers but I start to google and... I'll be back
-
I know what it is and how to use it, that's not the question.
When you use JSON-LD, specifically in something like the head section, you're using it without context. When this code appears on every page, it's labeling a person that may or may not be mentioned.
From the Google Developer Page on 'Specify your social profiles,'
"The social profiles in your markup must correspond to the ones that users can see on the same page."
It sounds like using this method within the head, especially with phone numbers, email, address, URL, etc., can be marked as either A) hidden text, or B) as something that would cause the rest of your markup to be ignored.
In this case... why would you ever use JSON-LD? It would never directly point to the object that's marked up like the HTML version does.
Maybe that helps clarify the question,
"In review, this seems to be an incorrect use? Should I only be using Schema to mark specific text? If not, what are the consequences of using Schema like this?"
When, exactly, is it appropriate and inappropriate to use Schema? I'm looking for an expansion in details that the Google Developer page doesn't mention. Maybe someone has been using and studying it for awhile?
-
Thats the Json-LD Mark-Up for a person, wich you can use with google like the microdate. It doesn’t matter if you place it in the or the section, Google will have no problem reading the code. It could look like that:
- <script< span="">type="application/ld+json"></script<>
- {
- "@context":"http://schema.org",
- "@type":"Person",
- "address":{
- "@type":"PostalAddress",
- "addressLocality":"Seattle",
- "addressRegion":"WA",
- "postalCode":"98052",
- "streetAddress":"20341 Whitworth Institute 405 N. Whitworth"
- },
- "colleague":[
- "http://www.xyz.edu/students/alicejones.html",
- "http://www.xyz.edu/students/bobsmith.html"
- ],
- "email":"mailto:jane-doe@xyz.edu",
- "image":"janedoe.jpg",
- "jobTitle":"Professor",
- "name":"Jane Doe",
- "telephone":"(425) 123-4567",
- "url":"http://www.janedoe.com"
- }
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Homepage name in Breadcrumb for schema.org
Hi all, We have recently implemented the schema.org structure for our breadcrumbs. In our breadcrumb we include a link to the homepage. Since implementation I'm receiving the following error in Google Search Console: Either "name" or "item.name" should be specified The error is being triggered because we don't have itemprop="name" defined for the homepage on each page. Our breadcrumbs look good in search but I'm wondering if anybody else has experienced this error and what can we do to fix it. Should itemprop="name" be our Brand name? Or should we define this as our root domain? Thanks in advance
Technical SEO | | Brando160 -
Schema Markup Errors - Priority or Not?
Greetings All... I've been digging through the search console on a few of my sites and I've been noticing quite a few structured data errors. Most of the errors are related to: hcard, hentry and hatom. Most of them are missing author & entry-title, while the other one is missing: fn. I recently saw an article on SEL about Google's focus on spammy mark-up. The sites I use are built and managed by vendors, so I would have to impress upon them the impact of these errors and have them prioritize, then fix them. My question is whether or not this should be prioritized? Should I have them correct these errors sooner than later or can I take a phased approach? I haven't noticed any loss in traffic or anything like that, I'm more focused on what negative impact a "phased approach" could have. Any thoughts?
Technical SEO | | AfroSEO0 -
Schema markup
Hi, I'd love to use schema markup, but I don't think there is one for the type of products we sell (mortgages). Does anyone know of a way of using schema markup for a page like this: https://www.turnkeymortgages.co.uk/mortgage/mortgage-rates/ The regulator for mortgages (FCA) in the UK has rules about how products are displayed, we have to show all the information in the table (see the link), and the compliance text (your home will be repossessed....) with every product. This is why I haven't tried to 'cobble' something together from the existing markup available - I can't fall foul of the regulator (or be misleading to customers). Anyone have any thoughts on this? Or, should I just wait until Schema come up with a markup suitable for such products.
Technical SEO | | CommT0 -
Schema.org implementation for physician's office vs physician herself?
Hi, Regarding schema.org microdata, which page(s) should have the microdata? 1) http://schema.org/Physician -- appears to be about the office. Since we have all of the contact/address info in the footer on each page, should we do the same with microdata? I can't seem to find a suggested implementation on schema.org Assuming an office has multiple MDs, how should the docs be listed since the physician schema appears to be for the office, not for the individual doctors? Thanks for any insight!
Technical SEO | | Titan5520 -
Author & Video Markup on the Same Page
I just have a quick question about using schema.org markup. Is there any situation where you'd want to include both author & video markup on the same page?
Technical SEO | | justinnerd0 -
Schema.org Review for Person
I'm trying to make some sense of Google's rich snippets and microdata/Schema.org. Wondering if it's allowed to have reviews or an aggregateReview for a Person, rather than a Thing, Product or Place. Of course, a Person is a Thing, but when I try to validate my markup with Google's Structured Data Testing Tool, it tells me: Warning: Page contains property "aggregaterating" which is not part of the schema. Anyone have any ideas here?
Technical SEO | | Mase0 -
Where to put Schema On Page
What part of my page should I put Schema data? Header? Footer? Also All pages? or just home page?
Technical SEO | | bozzie3114 -
How do i properly combine these two schema's from schema.org
So we're redoing our reviews/testimonials page on our website right now and moving over to the schema.org format as described here: http://schema.org/Review But we would like to combine each of our reviews with a location for which it was reviewed using this: http://schema.org/LocalBusiness What i can't wrap my head around would be the correct syntax? is it just the first block and then the next block? or is there a way of putting the actual physical address within the review page itself? So is this the correct way to do a page full of reviews that are reviewing various physical locations? * <div< span="">itemprop="reviews" itemscope itemtype="http://schema.org/Review"></div<>* <span< span="">itemprop="name">Value purchase</span<> -* by <span< span="">itemprop="author">Lucas</span<>,* <meta< span="">itemprop="datePublished" content="2011-03-25">March 25, 2011</meta<>* <div< span="">itemprop="reviewRating" itemscope itemtype="http://schema.org/Rating"></div<>* <meta< span="">itemprop="worstRating" content = "1"/></meta<>* <span< span="">itemprop="ratingValue">4</span<>/* <span< span="">itemprop="bestRating">5</span<>stars* <span< span="">itemprop="description">Great microwave for the price. It is small and</span<>* fits in my apartment. 1. <div< span="">itemscope itemtype="http://schema.org/LocalBusiness"></div<> 2. # <span< span="">itemprop="name">Beachwalk Beachwear & Giftware</span<> 3. <span< span="">itemprop="description"> A superb collection of fine gifts and clothing</span<> 4. to accent your stay in Mexico Beach. 5. <div< span="">itemprop="address" itemscope itemtype="http://schema.org/PostalAddress"></div<> 6. <span< span="">itemprop="streetAddress">3102 Highway 98</span<> 7. <span< span="">itemprop="addressLocality">Mexico Beach</span<>, 8. <span< span="">itemprop="addressRegion">FL</span<> 10. Phone: <span< span="">itemprop="telephone">850-648-4200</span<> <div< span="">itemprop="reviews" itemscope itemtype="http://schema.org/Review"></div<>* <span< span="">itemprop="name">Value purchase</span<> -* by <span< span="">itemprop="author">Lucas</span<>,* <meta< span="">itemprop="datePublished" content="2011-03-25">March 25, 2011</meta<>* <div< span="">itemprop="reviewRating" itemscope itemtype="http://schema.org/Rating"></div<>* <meta< span="">itemprop="worstRating" content = "1"/></meta<>* <span< span="">itemprop="ratingValue">4</span<>/* <span< span="">itemprop="bestRating">5</span<>stars* <span< span="">itemprop="description">Great microwave for the price. It is small and</span<>* fits in my apartment. <div< span="">itemscope itemtype="http://schema.org/LocalBusiness"></div<> <span< span="">itemprop="name">Beachwalk Beachwear & Giftware</span<> <span< span="">itemprop="description"> A superb collection of fine gifts and clothing</span<> to accent your stay in Mexico Beach. <div< span="">itemprop="address" itemscope itemtype="http://schema.org/PostalAddress"></div<> <span< span="">itemprop="streetAddress">3102 Highway 98</span<> <span< span="">itemprop="addressLocality">Mexico Beach</span<>, <span< span="">itemprop="addressRegion">FL</span<> Phone: <span< span="">itemprop="telephone">850-648-4200</span<>
Technical SEO | | adriandg0