Tag Info

New answers tagged

2

Note that syntaxes like Microdata and RDFa don’t annotate the HTML, they use the HTML just as a carrier. After parsing the Microdata/RDFa, it doesn’t matter anymore which markup was used. If your two properties with the same content belong to the same item, it’s not useful to have the additional one, as it doesn’t add anything new (but it’s not forbidden ...


-2

As noted in this article, having duplicate content will result in bad SEO performance and possibly getting a page ranked so low it cannot be found by users. A critical aspect of SEO is quality content and you cannot maintain a good organic SEO position with duplicate content. Changing both content and HTML structure will be important to having both sites ...


-1

Search engines always hate duplicates if You have duplicate itemprop the bot must be confused to take which one for your markup result so avoid that markup once on the page


1

From what I found, Google Structured Data Validation tool doesn't allow you to use PostalAddress for 'location' despite it being allowed by the schema. In here https://schema.org/location it's specifically said that 'location' can be either Place or PostalAddress. Given that the Place have attributes 'address' and 'name' and GSDVT is asking for them ...


0

Here's the final mark-up I have on my page: <div itemscope itemtype="http://schema.org/Article"> <meta itemprop="datePublished" content="2014-05-09T05:40:51+01:00"> ... Page goes here... <time itemprop="dateModified" datetime="2015-02-22T14:55:06+00:00">Last Updated: 22 Feb 15</time> </div> Which gives me a ...


1

If your web page is a search results page, simply use SearchResultsPage instead of WebPage. It’s a hierarchy. Each child inherits from all its ancestors. So a SearchResultsPage is a more specific WebPage, which is a more specific CreativeWork, which is a more specific Thing. Always go with the most specific type that applies to your case. On a type’s ...


2

You are missing some closing </div> tags. If I correctly interpret your intentions, it should look like this: <div itemscope itemtype="http://schema.org/SocialEvent"> <a itemprop="url" href="www.convention-name.org"><div itemprop="name"><strong>Bob's Convention</strong></div></a> <div ...


1

I had the same problem in a different context. My solution was to set the price of the offer to the lowest price and then specify an instance of PriceSpecification where I state the minimum price that is of EQUAL value to the value in the price tag and then a maximum price. This effectively means that there is a product with price X AND that X price ...


1

Historically, Google said they ignored structured data which was not used to markup visible content. Because your snippet shows both date published and date updated as visible on-page content but the Moz example shows date published as non-visible meta data, I'd try tweaking that and seeing if it works to get Google to show the last update date instead.


4

I guess there is no reason to assume that Google wouldn’t handle SVGs as value of the image property: Schema.org’s image property expects an image URL (or an ImageObject). SVG is an image format (image/svg+xml). Google does index SVG images. (Of course, we can never be sure; and things might change always.) Generally, the syntax shouldn’t matter, as ...



Top 50 recent answers are included