SEO markup for News article

I implemented the following SEO markup on news article pages (around article text): <div class="articleBody" itemscope="" itemtype="https://schema.org/NewsArticle">

is it enough to implement / is this good for SEO?

on other sites I see <html lang="it" itemscope itemtype="http://schema.org/NewsArticle"> or <script type="application/ld+json"> with "@context": "https://schema.org", "@type": "NewsArticle"

so I am not sure if my implementation is correct or needs to be changed.

Thanks

Schema markup for product categories and subcategories – how to?

I’ve been wondering about which Schema should I use for an e-commerce site of one of my clients’ website. Can’t show proper code and sensitive information, but I’ll try to explain what I’ve been thinking about.

Right here: https://inchoo.net/online-marketing/schema-markup-for-ecommerce-websites/

The author says that for category pages I should use ItemList Schema

<script type="application/ld+json">  {  "@context":"http://schema.org",  "@type":"ItemList",  "ItemListElement":  [    {   "@type":"ListItem",    "position":0,    "url":"https://www.example.com/ankle-boots-ana.html"   },    {    "@type":"ListItem",    "position":1,    "url":"https://www.example.com/ankle-boots-clara.html"    },    {    "@type":"ListItem",    "position":2,    "url":"https://www.example.com/ankle-boots-maria.html"    }   ]  } </script> 

Does anyone have an example of how it would look? For example, if I have a category with electric guitars with 5 subcategories that contain certain electric guitar models which would be listed in the schema ListItem. Is that the best schema type for this instance?

Second question – when it comes to subcategories, should I use ItemList Schema?

<script type="application/ld+json"> {     "@context": "http://schema.org",     "@type": "ItemList",     "url": "https://www.myexamplestore.com/products/",     "numberOfItems": "2",     "itemListElement": [           {             "@type": "ListItem",             "position": 1,             "item": {               "@type": "Product",                   "image": "https://www.myexamplestore.com/product-one/image.jpg",                   "url": "https://www.myexamplestore.com/products/#productone",                   "name": "Product One",                   "offers": {                       "@type": "Offer",                       "price": "13.00",                       "priceCurrency": "USD",                       "url": "https://www.myexamplestore.com/products/"                   }             }           },           {             "@type": "ListItem",             "position": 2,             "item": {               "@type": "Product",                   "image": "https://www.myexamplestore.com/product-two/image.jpg",                   "url": "https://www.myexamplestore.com/products/#producttwo",                   "name": "Product Two",                   "offers": {                       "@type": "Offer",                       "price": "12.00",                       "priceCurrency": "USD",                       "url": "https://www.myexamplestore.com/products/"                   }               }           }     ] } </script> 

I know that it’s a bit of a gray area for Google when it comes to adding product information on category pages – does that apply also for the subcategory pages?

I would be so thankful for Your help and guidance <3 Cheers

Schema.org – How to present Statistical data in markup

I have a website where I visualize statistical data with geoJSON. The description of a statistic e.g. is Graduation ratio of primary education and the data looks smth. like:

features: [ {     geometry: {type: "Polygon", coordinates: Array(1)}     properties: {name: "Afghanistan", id: "AF", value: 64, latitude: 33, longitude: 65, …}     type: "Feature" }, {     geometry: {type: "Polygon", coordinates: Array(1)}     properties: {name: "Albania", id: "AL", value: 98, latitude: 41, longitude: 20, …}     type: "Feature" } ] 

My question is now on how could I represent this data best with schema.org. There are 2 types which I feel like could come close to it:

  • https://schema.org/Observation
  • https://schema.org/Dataset

I went with the dataSet approach and the markup looks to smth like this:

@context: "http://schema.org" @type: "Dataset" creator: {@type: "Organization", url: "...", name: "Eduinsights", contactPoint: {…}} description: "Global visualization for educational statistics/observations provided by UNESCO: Graduation ratio of primary education,Net enrolment rate for primary education,Percentage of female repeaters primary education,Percentage of qualified teachers secondary education,Proportion of primary schools with access to internet for pedagogical purposes" keywords: ["Statistics > education > Graduation ratio of primary education", "Statistics > education > Net enrolment rate for primary education", "Statistics > education > Percentage of female repeaters primary education", "Statistics > education > Percentage of qualified teachers secondary education", "Statistics > education > Proportion of primary sch… with access to internet for pedagogical purposes"] name: "Educational statistics" spatialCoverage: {@type: "Place", geo: {…}} temporalCoverage: "Thu Jan 01 1970 01:00:02 GMT+0100 (Mitteleuropäische Normalzeit)/Thu Jan 01 1970 01:00:02 GMT+0100 (Mitteleuropäische Normalzeit)" url: "..." 

Is this really the right way to go? There are not much sources online about schema.org representation of statistical data.

JSON-LD for schema.org markup – what to include and where

I’m trying to take advantage of using JSON-LD for Schema.org markup over Microdata because it seems way easier to implement and to maintain. Also, I’ve heard that consumers like Google and Bing now prefer it’s use. However, since JSON-LD markup is not directly part of the source code it presents a possible issue. That being, it’s now way easier to add anything you want into your markup, which makes me wonder if this could be viewed as spammy or duplicate content.

For instance, take my example code:

JSON-LD Markup:

{ "@context": "http://schema.org", "@type": "LocalBusiness", "additionalType": "http://www.productontology.org/id/Company_Catagory", "address": {     "@type": "PostalAddress",     "addressLocality": "some city",     "addressRegion": "XX",     "postalCode":"12345",     "streetAddress": "123 any st."     }, "description": "Detailed description of the Company", "name": "Company Name", "openingHours": "Mo-Fri 08:30-17:00", "geo": {     "@type": "GeoCoordinates",     "latitude": "42.000",     "longitude": "-81.000"     }, "logo": "https://www.campany-name.com/logo.png", "image": "https://www.company-name.com/logo.png", "url": "https://www.company-name.com", "telephone": "(xxx) xxx-xxxx", "faxNumber": "(xxx) xxx-xxxx", "foundingDate": "1900", "priceRange": "$  $  ", "email": "info@company-name.com", "currenciesAccepted": "USD", "hasMap": "https://www.google.com/maps/place/direct-link-to-google-map", "paymentAccepted":"Cash, Credit Card, ACH, Debit", "sameAs" : [ "https://www.facebook.com/company-name/",     "https://twitter.com/company-name"] } 

The above markup example seems to satisfy the Google markup validator for a LocalBusiness, but the actual page it’s referencing might only contain a few pieces of that information.

So my question is a few parts:

  1. Would it be best to only include markup that actually appears in the source code or should I provide all the bits of markup information the consumers like Google and Bing want?

  2. If the answer to question 1 is to only include markup that appears in the source code. Then, what if it’s not feasible to include some items in the source code such as the geo item. Would it be best to not include it in the markup at all?

  3. Is it necessary to include the same markup on every page, or are the consumers smart enough to understand that if the LocalBusiness type has been populated on a different page inside a domain that it applies to the entire domain?

  4. If the answer to question 3 is to only include LocalBusiness markup data on one page throughout an entire site, is there a best practice regarding which page to place it on? ie. home page, contact us page…. any SEO benefit?

l’ll do Shopify Store SEO optimization, Product Tags, Meta Description, Alt Tags and Schema Markup for $20

Shopify Store SEO optimization is the process of optimizing each and every product and page of your store in order to rank higher in the Search Engine Results Pages (SERPS). If you want to enhance Shopify Store ranking, organic web traffic and sales, you simply can’t ignore search engine optimization(SEO). This White Hat on page SEO services can boost google ranking of your Shopify Store or Store traffic by 90% or more. Our on page SEO optimization services include: Free: Shopify Store SEO analysis and Store SEO audit report.LSI, Focused & Long tail keywords Optimization.Install & configure necessary store apps.Compelling Meta descriptions, SEO Meta Titles and Product tags.Heading tags (H₁, H₂, H₃), Image alt tags and Shopify store Speed Optimization.Fix duplicate content & Redirect Broken Links to the Homepage or Parent Page.Social media Meta tags, Hyperlink and anchor text optimization.Search Engines friendly URLs and SEO Titles.Schema Markup, XML Sitemaps, Internal / External Linking and Robots.txt.Webmaster Tools(Google, Bing, Yahoo) & Google analytics. Why us? 100% Client Satisfaction and Money back Guarantee.Increased store authority.Top-ranked website based SEO keywords research.100% White Hat manual work.WordPress SEO, Wix SEO and Shopify Store SEO Specialists.If you have any questions, please don’t hesitate to get in touch. Tags: Shopify SEO, Shopify store SEO, e-commerce store SEO, store optimization, SEO services, Store SEO analysis, Shopify store SEO optimization, Shopify store SEO ranking, Shopify store on page SEO optimization, Shopify store SEO services, Shopify store SEO specialist, Shopify store SEO agency, Shopify store SEO consultant, Product Tags, SEO keyword research, LSI keywords research, Keywords analysis, Shopify store SEO Audit Report, Shopify store SEO audit, 301 redirect, Competitor analysis, Meta descriptions, image alt tags, Shopify store speed optimization, XML sitemap, robots file, hyper link optimization, anchor text optimization, SEO friendly titles, long tail keywords research and Targeted Organic Traffic.

by: ONELIFESEO
Created: —
Category: Local SEO
Viewed: 197


Need Help With JSON-LD Markup for Educational Software

My small company develops educational software that teaches algebra, geometry, and other math subjects. The software is designed for desktop Windows PCs. We have a website through which we sell the software, and each software package has its own page.

I would like to add JSON-LD markup to these product pages so that our search results listings would be richer and more descriptive. But I am struggling to understand the different types and categories of products that schema.org defines. My goal is to specify as closely as possible the details of each software product.

For example, I sell a program that teaches high school algebra. If I were to invent my own categories and sub-categories to specify the product I would do it like this:

Product -> Software -> Educational -> Math -> Algebra

But I don’t see a hierarchy like that in the schema.org documentation.

Instead I see the following:

Thing -> CreativeWork -> SoftwareApplication

Within SoftwareApplication I see “applicationCategory” with “Game” as an example. But I don’t see a list of other possible categories, like “Educational”. Do you make up your own categories, or do you select from pre-defined choices?

And there is “applicationSubCategory” with “arcade game” as an example. I don’t know how to view the other possible sub-categories. I would choose “Math” if it is allowed. Additionally, I would like to have a sub-SubCategory, where I would specify “algebra”.

Can anyone offer some guidance on how to categorize my products in JSON-LD?
Or perhaps you could point me to documentation that would clear things up for me.

Thank you very much.