Bill - did you solve the RSD schema...
The software I've been using for years has an "edit html" where you access the div etc.
I can't seem to find anything but the HTML element which kind of defeats the built in CSS.
Did you find a jason generator or something or go that google route where you add them through there servers.. not too familiar with that one. Anyway I was wondering if you figured a hack other than the HTML element or re-coding after generation?
I can't seem to find anything but the HTML element which kind of defeats the built in CSS.
Did you find a jason generator or something or go that google route where you add them through there servers.. not too familiar with that one. Anyway I was wondering if you figured a hack other than the HTML element or re-coding after generation?
RSD provides no support for schema markup. I am puzzled that it does not, despite CC saying in their own pages that schema markup should be a top priority for - 2015. You will have to take each page from the final output of RSD and recode it using Coffeecup's HTML editor (I think the pro version). Or manually do it, or add html elements with handcoded schema. If the page is not complicated, the html element might be the way to go, and instead of wraping content with a schema div and spans, put the div and spans in a html element, and use content=" ... " for the date like this: (instead of the span for the name being wrapped around the name in the page, I gave it a name in the span using 'content="" ')
<div itemscope itemtype="http://schema.org/Book">
<span itemprop="name" content="Book name"></span>
</div>
So far, what I have tested seems to be checking out with Google's tester. They have a site and code snippet tester. https://search.google.com/structured-data/testing-tool
They also have a page markup tool, but it send out new code for you to replace the old webpage.
https://www.google.com/webmasters/markup-helper/u/0/
The problem if if Google will detent a lot of content="" tags and think you are spamming irrelevant data, even those the code data detects no code errors.
<div itemscope itemtype="http://schema.org/Book">
<span itemprop="name" content="Book name"></span>
</div>
So far, what I have tested seems to be checking out with Google's tester. They have a site and code snippet tester. https://search.google.com/structured-data/testing-tool
They also have a page markup tool, but it send out new code for you to replace the old webpage.
https://www.google.com/webmasters/markup-helper/u/0/
The problem if if Google will detent a lot of content="" tags and think you are spamming irrelevant data, even those the code data detects no code errors.
I haven't used JASON, but it looks like its just a script, not sure where it would have to go. Fromt he code I have seen, it does not appear that its ideally used to wrap around page content, so maybe it can just be used within a RSD HTML Element.
I did find a JASON-LD generator - is the 2nd link I gave in the earlier post, after clicking "create html" just go to microdata - its a drop down and select JASON, then it just outputs a script and it instructs where to put the script in the head or body. Buts its not a full generator, it just a "helper" thing to get basics or get people started. So - there apparently isn't a need for content to be wrapped, but I dill don't know how prolific one cab use content="..." in microdata until/if Google hits you for it. But - if I was google, I would be looking for things like "ratings" to also be on the page, not just in microdata content or jason-ld. Something to ask in the Google webmaster forums.
Yeah, jason might be the way to go I'll have to look into that too, it didn't seem to me like it's hit the points either like microdata does. Turning into a love/hate relationship with RSD
Just found out about the case URL naming bug too.
I'll let you know what I come up with, might have to end up doing a boat load of hand coding again.

I'll let you know what I come up with, might have to end up doing a boat load of hand coding again.
I did some research on it because I am at a point where I need to markup schema, and JASON-LD is WAY better than microdata. Just forget using microdata, learn JASON-LD! It is the way to go, and is not a hot mess of coding in a html document. JASON-LD is a little more complicated to wrap wround, but the code output is so much better, and easier to read (seemingly harder to hand code because of the characters, arrays and things, but reading the lines for the content, one can easily see what the data is saying). And because it offers arrays and nesting, it is superior to microdata.
From what I understand, you are looking to schema a small business, and so am I. And this is what I learned. So far, following these websites, I check out on Google's validation - after pasting the code into a RSD html element, and supplying the html from the entire page to the validation tool
So check out these websites.....
Using Jason-LD for a local business. Basically, read it then fill in the descriptions for your business! Its basic, but covers far more than other "generators." If you business is any more complicated or have multiple locations or services, then one needs to hand code an array or maybe nest some properties.
https://whitespark.ca/blog/the-json-ld-markup-guide-to-local-business-schema/
The above webpage links to the next two, but I include them because they are helpful and the links might not be easily found
Spreadsheet summary of business and what type of businesses they fall under for schema.
https://docs.google.com/spreadsheets/d/ … edit#gid=0
This is to narrow down your exact field of business that is not already a default, of what sub-type of business you are, you use a custom type that schema.org now accepts, but you have say that you are using a particular way to describe your business type, and the way to do this is to use a method that relies on Wikipedia definitions.
http://www.localvisibilitysystem.com/20 … -business/
Additionally, I know it can be done, but I am not 100% sure how, but one should be able to define a geographical area for a business, because many businesses just do not have an address, but serve an area. So, there should be a way in JASON-LD to pick that up. And, JASON-LD can use arrays, so one should be able to set into the JASON-LD script, a array of multiple areas, mailing addresses, telephone numbers in a compact list. And since JASON-LD allows sub-nesting, one can subnest for any of their properties when needed.
From what I understand, you are looking to schema a small business, and so am I. And this is what I learned. So far, following these websites, I check out on Google's validation - after pasting the code into a RSD html element, and supplying the html from the entire page to the validation tool
So check out these websites.....
Using Jason-LD for a local business. Basically, read it then fill in the descriptions for your business! Its basic, but covers far more than other "generators." If you business is any more complicated or have multiple locations or services, then one needs to hand code an array or maybe nest some properties.
https://whitespark.ca/blog/the-json-ld-markup-guide-to-local-business-schema/
The above webpage links to the next two, but I include them because they are helpful and the links might not be easily found
Spreadsheet summary of business and what type of businesses they fall under for schema.
https://docs.google.com/spreadsheets/d/ … edit#gid=0
This is to narrow down your exact field of business that is not already a default, of what sub-type of business you are, you use a custom type that schema.org now accepts, but you have say that you are using a particular way to describe your business type, and the way to do this is to use a method that relies on Wikipedia definitions.
http://www.localvisibilitysystem.com/20 … -business/
Additionally, I know it can be done, but I am not 100% sure how, but one should be able to define a geographical area for a business, because many businesses just do not have an address, but serve an area. So, there should be a way in JASON-LD to pick that up. And, JASON-LD can use arrays, so one should be able to set into the JASON-LD script, a array of multiple areas, mailing addresses, telephone numbers in a compact list. And since JASON-LD allows sub-nesting, one can subnest for any of their properties when needed.
Yeah Bill, that is cool... not to the setting the schema like you are with your site still sortin' through the hack list for RSD.
But that will help a lot, some great info links... and yes I scope to "HomeAndConstructionBusiness" schema probably like you do. I did read a bit on the map schema and location thing a while ago now but I do believe you can set in lat/long coords for a service area too? Not that you'd want to commit too far on that one, don't want to be cut out of searches either too much right.
So looks like at least that tiny hurdle can be bridged in RSD, thanks for the update.
But that will help a lot, some great info links... and yes I scope to "HomeAndConstructionBusiness" schema probably like you do. I did read a bit on the map schema and location thing a while ago now but I do believe you can set in lat/long coords for a service area too? Not that you'd want to commit too far on that one, don't want to be cut out of searches either too much right.
So looks like at least that tiny hurdle can be bridged in RSD, thanks for the update.
Just to be clear, you can further define what you do within the "Home and Construction" Follow that last link. There was a way, way back in Schema.org for someone to make a custom name, but now if one follows the "Productontology" method described in the last link, the specific type of business you do, if defined in wikipedia, will be defined in the schema. Its like an extension, but you have to tell schema you are going to do that in the script, then use the method outlined to specifically describe your type of business.
For instance, if someone can someone be described as a professional service in schema.org, they can use the productontology method to extend that to being a Tailor, along with all the descriptions of service that might help in a google search.
In your case, I did a quick search for finishing carpentry. Only Carpentry came up in wikipedia. But - that is still a drilled down definition of a service you offer, so - your JASON-LD will look like this in part;
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "Product",
"additionalType": "http://www.productontology.org/id/Carpentry",
While you will want to keep the home and construction, you may want to create an array of services - however that syntax is done in JASON-LD. This this example, the additional type Carpentry is classed under Product (which is a product or service). So - I would learn how the arrays are done, then spec up all your services, because I know you at least would want to add this as a product: http://www.productontology.org/id/Cabinetry
For instance, if someone can someone be described as a professional service in schema.org, they can use the productontology method to extend that to being a Tailor, along with all the descriptions of service that might help in a google search.
In your case, I did a quick search for finishing carpentry. Only Carpentry came up in wikipedia. But - that is still a drilled down definition of a service you offer, so - your JASON-LD will look like this in part;
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "Product",
"additionalType": "http://www.productontology.org/id/Carpentry",
While you will want to keep the home and construction, you may want to create an array of services - however that syntax is done in JASON-LD. This this example, the additional type Carpentry is classed under Product (which is a product or service). So - I would learn how the arrays are done, then spec up all your services, because I know you at least would want to add this as a product: http://www.productontology.org/id/Cabinetry
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.