Tag Info

Hot answers tagged

3

In SEO perspective wrapping contents with <div> tags is not an issue but large amount unwanted coding will increase the bytes of data which may increase the PageSpeed. Here an extract from this source: Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up downloading, parsing, ...


2

Microdata (Note) can only be used on HTML elements as defined by HTML5. According to HTML5 (CR), the svg element is not in the HTML namespace. WHATWG’s HTML spec explicitly mentions that Microdata doesn’t work for svg (quoted on 2014-01-02): Currently, the itemscope, itemprop, and other microdata attributes are only defined for HTML elements. This means ...


2

As bybe mentioned, it can take a few weeks before your structured data begins to appear, and there have been some bugs in the reporting system lately. But one thing that you can do if you haven't already is use the Fetch tool in your Webmaster account to prod Google to go crawl your site again and notice the changes.


2

Sadly with anything Google there is nothing that is given in approx. time frames. This is because Google allocates resources to your site based on its authority and how busy their bot is. But in experience structured data normally appears between 1-6 weeks after the first index - it can take a few crawls before Google decides to display it within Google ...


1

This link describes what Google is expecting in terms of a product listing, items in bold are required. So from looking at your mark-up you have the name property of product in the wrong place as it comes after the image property, I would move this above the image and I think it should validate OK. <span itemprop="name">Blackforest Cake BFC1 ...


1

Max, Google does support structured data for Organization markups, but they don't support rich snippets for the type. If you change schema.org/Organization to schema.org/LocalBusiness in your markup, you'll see the testing tool results change and the rich snippets displaying. So the error message you're seeing is in regards to rich snippets, not the ...


1

Although their documentation doesn't say so, using the rel attribute is supported by Google, so both should work. The 'in-URL' ?rel= syntax exists for blog users, who may not have access to edit the page's HTML tags, but the HTML5 separate attribute version is more 'correct' so I'd recommend: <a href="[profile_url]" rel="author">Author</a>


1

Your questions seem to be: Can I specify itemprop="url" on li? Can I specify itemprop="name" on a? The answer to both of these questions is: No, you should not do that. Microdata defines special parsing rules for elements like a. Schema.org’s url property expects a URL as value. Microdata defines that you have to use a, area or link for specifying ...


1

SiteNavigationElement has a problem for me, and for some other people as well, like we can see in the question posted by @bybe in a comment. we can say that the problem is lack of scope. Is SiteNavigationElement referred to a single item of the navigation system, and so it is read as: an Element of the Navigation of the Site. Or it is referred to the whole ...


1

Another problem with a code-heavy site is it takes the search engine spiders longer to crawl your pages. Even if bloated code does not affect page load time (from the visitor's perspective) the longer crawl time can negatively affect how the search engines rate your site. (It's not a major signal but every little bit helps.) From SearchEngineGuide.com: ...


1

I don’t think that http://schema.org/Article is limited to "articles of a publication". "Newspapers and magazines" (from the description) are just an example, not the only possible publication mediums. It is defined as: An article You even might consider the more specific http://schema.org/NewsArticle: A news article


1

This is a bit subjective, but I don't believe Schema.org dicatates in anyway what tags the itemprop attributes can be added to, so I don't see any problem with your <h1><span itemprop="name">Cut and Blow</span> Devon</h1> approach. You could quite conceivably have something like this: <h1>New for 2013: <span ...


1

Images are not headers and generally using <h1><img src="" alt=""/></h1> is bad practice, you could opt to use a text-indent: -9999em but this is becoming unfavourable and the best practice is just to use a H1 as intended. The text indent method is pretty easy to do you just do something like this in the HTML/CSS: HTML <h1><a ...


1

I know this is three years old, but I came across it looking for the same answer today, for Office 2010 anyway there is an option to save as "filtered HTML" without the extra Microsoft code : About using filtered HTML When you save Web pages or send e-mail messages in HTML format with Microsoft Word, additional tags are added so that you can continue ...


1

There's no specific recommendations for WCAG 2.0 or even in HTML5 (yet). You can probably wrap it with a <code> tag (like Joel Etherton suggested). ASCII art is different though. WCAG recommends that you provide the user a text description and a way to skip it. See H86.



Only top voted, non community-wiki answers of a minimum length are eligible