GSA: microdata gets truncated - schema.org

I'm feeding the data of into Google Search Appliance. My feed contains HTML documents enchanced with Microdata from schema.org (specifically this).
To my surprise:
the search results aren't any different to the ones I receive without microdata enhancement in place,
while using test tool, I'm seeing that GSA cuts the Microdata from the markup.
Questions:
How to improve GSA search results?
Why would GSA cut the Microdata from the markup? Should I be concerned about it?

The GSA does not support those microdata.
It typically only supports meta tags under the format <meta name="category" content="computer"/>

Related

can I write semantic web markup for an external web resource?

I am interested adding semantic markup details to some web content. Some of the content is public and I can reproduce, but a lot of the content is content I don't own and I don't want to avoid or get around copy right issues, by not hosting the content my self, and all I really want to do is markup the content, not reproduce it.
So is there some way for me to annotate or write semantic markup like RDFa and then point that scemantic markup information at an external resource?
Maybe by combining different technologies.
For example:
I could try and write an XSLT document and add RDFA markup and point that at a XHTML document. But if I did do that would any or the search engines or SPARQL query engines still understand that.
Or maybe there would be some other way to reference the external content with HTML5 imports or javascript and xpath.

Google requiring certain properties for certain types when adding Schema.org markup?

I tried to add Schema.org markup on my site, with the type Article, then adding some properties on it, when checked on Google Structured Data Testing Tool, it said required certain properties, like dataPublished, author etc.
I can add some properties to meet the requirement, but not all of them. Is this requirement real? I mean really required by the rule? Or just Google rule? I came across this page https://developers.google.com/search/docs/data-types/articles It said for non-AMP, those requirements are only optional (ignored or recommended, non of them said required for non-AMP).
This get me confused, anyone knows about this, what's your opinion? Do Google Structured Data Testing Tool already include AMP requirement?
These are required/recommended for getting one of Google’s search features.
If you don’t want that Google search feature, or if you can’t provide all necessary properties, you can keep everything like it is and ignore the errors and warnings.
Related answers
Should Schema.org dateModified have some default value if not available?
Schema.org/Microdata markup for list of recent posts without providing “author” / “publisher”?
Do I have to create new visible elements to abide by Google's Microdata Schema.org requirements?
Omitting price property for sold products?
Use Schema.org for Article without image property?
Image missing and required - Wordpress AMP Structure doesn't add Image attribute
On Webmasters SE:
Schema.org BlogPosting and image required
Is it mandatory to have rich snippets for AMP pages?

What is the current state of Google support for JSON-LD schema formatting?

On Google's page About Schema.org it is stated:
JSON-LD is the newest and simplest markup format... Google is in the
process of adding JSON-LD support to more markup-powered features. So
far, JSON-LD is supported for all Knowledge Graph features, sitelink
search boxes, Event Rich Snippets, and Recipe Rich Snippets; Google
recommends the use of JSON-LD for those features. For the remaining
Rich Snippets types and breadcrumbs, Google recommends the use of
microdata or RDFa.
Yet on the page Enabling Rich Snippets for Articles JSON-LD is shown in the examples as the first way to format article schema markup. Additionally, in the Markup Helper Tool article schema markup can be output as JSON-LD.
Seeing as one page does not list Rich Snippets for articles as a supported use of JSON-LD, and any uses not listed there are not recommended, one would think that it is not available for use. Then why is JSON-LD listed as an example, the first example no less, on the page about rich snippets for articles? A bit confusing.
I would like to begin using JSON-LD as the schema format for our site's articles, but only if it is certain that Google does in fact support its use. Could I get an official answer on the state of JSON-LD formatted schema markup support regarding article rich snippets from Google Support?
https://developers.google.com/structured-data/rich-snippets/articles
https://www.google.com/webmasters/markup-helper/

google text search vs. metadata search

I'm very interested in search engines.
Today in a talk I heard that google performs a text search, while more complex engines could rely on the use of metadata, which is apparently not so used by google.
Which is the difference between text search and metadata search?
Could you provide some links where I can go deeper on this subject?
Metadata is 100% text.
The reason why Google doesn't use it is because people tend to lie about their content (not automatically on purpose.)
Now, what Google doesn't use is the Keywords meta data tag (although they may be checking it out to see whether you're a liar...) They do use the other meta tags.
I just wrote a long list of meta tags supported by many systems. I still need to add many more, but out of those that are there the og:image and description and some others are very useful.
http://snapwebsites.org/implementation/feature-requirements/layout-feature-core/meta-tags-and-links-supported-core

Can Ektron Do This in SEO?

Can tell me if Ektron can do these things in SEO?
XHTML Compliant - Renders in XHTML compliant mark-up out of the box
Canonical URLs - Able to specific a canonical URL for a single page SEO
Friendly URLs - Able to create and configure SEO friendly URLs and formats
XML Site Map - Able to dynamically and automatically generate an XML Site Map Granular
Site Map Priorities - Able to set XML sitemap priorities in the page admin
Semantic Menu - A menu system that uses semantic mark-up
Google Analytics Integration - Full integration of the Google Analytics script
Search Engine Submission - Allows you to submit the website to a variety of search engines from an admin interface
XHTML Compatible Controls - All controls used (menus, grids, etc.) render XHTML compliant mark-up
XHTML Compliant - Renders in XHTML compliant mark-up out of the box
Not sure. You'll want to download the Developer starter site to check the control you are interested in. If you're concerned about accessibilty, I several controls have a 508 Compliance switch.
Canonical URLs - Able to specific a canonical URL for a single page SEO
In theory yes, in practise no.
Friendly URLs - Able to create and configure SEO friendly URLs and
formats
Yes. Option for manual, regex and automatic aliasing.
XML Site Map - Able to dynamically and automatically generate an XML Site
Map Granular
Site Map Priorities - Able to set XML sitemap priorities in the page
admin
Don't think this is out of the box. You would need to look at a custom solution.
Semantic Menu - A menu system that uses semantic mark-up
Not out of the box. You would need to customise the mark-up via XSLT.
Google Analytics Integration - Full integration of the Google Analytics
script
Yes, out of the box. See here for some help implimenting this.
Search Engine Submission - Allows you to submit the website to a variety
of search engines from an admin
interface
Not that I am aware of.
XHTML Compatible Controls - All controls used (menus, grids, etc.)
render XHTML compliant mark-up
See my answer to question 1. Out of the box - no, but depends on which controls you are using.
As Justin Niessner mentions, there is the option to overcome any of this via custom work. To help with your evaluatation, I recommend downloading the Developer starter site and having a look at the default markup of the control.
Also, there is an Ektron forum which is quite vibrant.
Edit - To clarify, I am not employed nor speak for Ektron. Just a developer who is working on the platform.
Yes. Ektron's CMS400 can do everything that you have listed there. It's all up to the developer to implement everything though (and it's a hell of a lot of work to get it all working correctly).