I get an "Exploit Link to Exploit Site (type 1317)" warning from AVG on this site.
hm...there are no ads on the site, disqus?
HTML5: SEO Incompatibility
11–16 of 16 posts
Re: HTML5: SEO Incompatibility
#12- http://www.seomoz.org/blog/seo-best-practices-seomozs-new-po...
If their research is correct, this is likely to have little to no effect on your search rankings anyway.
Re: HTML5: SEO Incompatibility
#13Re: HTML5: SEO Incompatibility
#14Earlier quoted context omitted.
hm...there are no ads on the site, disqus?
I'm not disqus or talking about ads. I'm talking about the warning pop-up I get when I try to go to that site.
The website at www.mikesingleton.net contains elements from the site 85.234.191.190, which appears to host malwareRe: HTML5: SEO Incompatibility
#15>>
>> Truthfully I don’t know (if you do, post in the comments!).
Yeah, definitely going to listen to this guy.
Seriously, though. We're way past tweaking html tags for improving rankings these days. Rather than wasting time debating whether you should use an h1 or h2, it's much smarter to focus your time on having good content and getting inbound links from other sites.
Re: HTML5: SEO Incompatibility
#16Online Marketing Manager here. (I work for a small integrated marketing and online development agency in Kansas City.) This is a non-issue. The only way this argument holds any weight is if the search engines ignore the new HTML5 tags, which is preposterous. Does anyone actually think that Google's search algorithm which looks at over 200 factors including such on-page nuances like keyword proximity, phrase groupings…
This is exactly the point -- these HTML5 tags are being used in production today without people realizing that search engines may not being using the new document outline model since it's a moving spec.
The conclusion is to avoid using these new semantics until they are further developed to avoid an unexpected document outline.