I am interested in tagging the page that features all the services.
My particular industry Schema doesn't offer the span itemprop="itemOffered". Thus, should I make each the services page reflect the Product Schema rather than the industry specific itemtype, Or is it best to specify on the services page the product Schema and then on the individual product pages use the industry-specific itemtype and list the product using makesoffer?
Technically, Poe, a product can also be a service. So in your case (without knowing more info about what you offer), you can use the Product Schema for your service.
However, there is another way to mark up your service, which is by using a GoodRelations markup to augment the Schema.org/Offer markup. Here's a link to another stackoverflow post that perhaps can give a better example that I can: Using Schema.org and GoodRelations markups for services
Hope that helps.
Related
I have two websites: www.mycompany.com and shopmycompany.com (not a subdomain) and would like to publish the relationship between them using schema.org. At present the www.mycompany.com identifies itself as an Organization and shopmycompany.com as a WebSite but there is no linkage between them. What would be best practices to present that connection?
Just from a quick skimming of https://schema.org/WebSite, there are multiple properties that would be fine as linking the website with the company:
author/creator
maintainer
provider
publisher
However, I wonder whether the Shop really should classified as a WebSite (which is a CreativeWork) and not rather as a Store which may simply have a parentOrganisation.
Yet another alternative would be to classify it as a Service, which is provided by the Organisation and can offer things.
And yet another alternative could be to classify the shop website as the OfferCatalog of offers made by the company.
I'm working on a site optimizing their structured data and noticed they use YotPo to pull in ratings and reviews. YotPo is defining the Product and only has a couple of values for AggregateRating that are being injected via JavaScript.
I have all of the other product data coming from the CMS, so I defined all the other information there, but when I run Google's testing tool on the page, it sees it as 2 products and says it's missing fields for the YotPo markup that are already defined in my markup.
Is there some way to let Google know that they're both chunks of data for the same product so it only sees it as a single product with the combined data?
You need to make sure both Yotpo and your CMS use the same format. e.g. json-ld or microdata.
You can then indicate that they relate to the same product by setting both up to use the same id.
I'm trying to understand this from a REST theoretical perspective.
You have a book collection, it's an entity you can get, delete, etc.
You have an individual book, you get it with an id, delete it with an id, etc
You have an Angular app where you can add new books. So you get the book collection, add a book locally, haven't sent it to the server yet
You need additional info on the book before you add it, for example you need to know if there are any other books with the same title
Can you have multiple GET calls in a RESTful architecture for the same entity? i.e. one with id and another with a name? So you could try to GET the book with the name to see if it already exists
Where does 'get additional info for an as of yet uncreated entity' fit into this? Lets say you need an image for the book and you have stock images, I'm assuming that the images are entities in and of themselves so they have their own REST APIs
If I understand your question correctly, you basically want to do a search on some criteria (name, etc) to check that the book does not already exist. You can use GET for book which would not include id as a path variable but would include the criteria filter params as request parameters(query string). Something like this:
/book?name=bookname -- List book with name as bookname
/book/{id} -- List book with given id
Multiple GET calls for the same entity is not encouraged in a RESTful architecture.
Can you have multiple GET calls in a RESTful architecture for the same entity?
Jim Webber: You should expect to have many many more resources in your integration domain than you do business objects in your business domain.
So sure, why not? How could the client possibly know?
Where does 'get additional info for an as of yet uncreated entity' fit into this?
When in doubt, try to envision what you are doing as a web page. Would be be reasonable to send to ask the web server for a form to add a new book with a particular title, and have it return the form, a list of known books with similar titles, a set of stock images, etc? Of course. So it's going to be fine for your API to do the same thing.
Or perhaps the form should be a separate idea, and the search results should look like a link to the form, and a bunch of links to representations of existing books. That's also fine.
Using links from unstable things to stable things is often a good idea, because it affords caching.
I am creating a website form my enterprise and I wonder how/how many snippets I should use on my homepage.
I know they are separate into multiple categories such as
local business or more generic organization, events, product etc.
I have read this post:
Homepage Rich Snippets
And this one:
Multiple Schema.org Product items & how will it look like in search engine result?
In my case on my homepage (let's say index.html) I want to present my activity, put some links to the services/products I propose, and show incoming events.
Which snippet(s) should I use?
1) Only one such as organization? (my services are not available directly so I suppose it is not a local business category)
2) Or should I put several snippets: organization + event + products
because all three categories are described/present on my homepage?
According to a Google employee, Google Search won’t show Rich Snippets for homepages. But this is not documented, and it might change anytime.
From the perspective of Schema.org, it’s fine to provide as much data as possible. If you have multiple entities on your homepage, you can use multiple Schema.org types to describe them.
If one of these entities can be considered the primary entity (for example, on an organization’s website it would typically be the entity for the organization itself), you can use the mainEntity property for it.
I have been looking around on Schema.org but I don't understand one thing.
Can a single HTML page be made up of multiple schemas? If so do they need to be nested?
We have a one page landing / selling page we are working on.
I would like to have the following Schemas in place on it:
Organization
Product
Product Reviews
I am guessing the product reviews need to be nested within a product? Or can they be in a totally different part of the page?
Looked over what little docs there are.
You can have multiple schemas as well as mix on other markup types.
Some schema types naturally nest other types, like a product may contain product reviews. It is possible to markup the reviews outside the product but you may find less systems pick up the association correctly.