Hot answers tagged markup
15
Give HTML5 some time to mature and gain wide acceptance and you might have some specific guidelines for SEO, but I don't think it will differ much from what's currently considered good practice. Either way, I think it's a little too early.
In general, if it's good for your users, it will be good for SEO. Make your site accessible and usable. Use a good ...
9
To speculate (because I think that's all you can do on this question without rigorous testing in an essentially uncontrollable environment) I personally doubt that there are yet ANY ranking factors associated with HTML5, for the same reason that Google doesn't assign quality points for valid HTML. There aren't enough sites using these structured elements ...
5
Assuming those search results are available to be crawled by search engines as their support for form submissions is very limited at best, repeating that text isn't going to hurt your SEO efforts at all. Text repeated in that manner is perfectly normal and common. I wouldn't change how you are doing or or worry about this at all.
4
You should use
<meta itemprop="image" content="/uploads/images/medium/product_img.jpg">
Since src="" is associated with embedding content on the page and content="" is associated with embedding items off the page so to speak. This is the same method as used with the Facebook Open Graph meta as well, take a look:
<meta property='og:image' ...
3
I think you'll find Dive Into HTML5, a book in progress, a great resource. Here's a relevant section on when and how to use new semantic elements. For your example, I think that you may be able to omit the <section> tag.
3
The main thing I would keep in mind at the moment is that if your pages rely on meta-tags, you will want to test and monitor their acceptance regularly. For instance, for Google Webmaster Tools, if you want to verify ownership via meta-tag, you will have to place it in a "head" element (there are other ways to verify ownership, so generally that's not a ...
3
I can't find any recent numbers on HTML usage, but this site has some figures from 2 years ago.
Here's a small-scale poll of web developers (figures will be skewed since it's from a development site) from 2008 as well.
But it's probably best to just choose your HTML version or doctype by looking at browser support. On new projects, you should just use the ...
2
Possible answer, I will only select my answer as the correct one if up voted 3 times:
http://w3techs.com/technologies/overview/markup_language/all
Also, found these of interest too:
Javascript Libraries
http://w3techs.com/technologies/overview/javascript_library/all
client-side programming
...
2
You can always use another application as an intermediary, like LibreOffice, and use it to save it as an HTML document.
LibreOffice (formerly OpenOffice, which is still available if you prefer it) generates much cleaner code comparatively.
2
While your checkbox idea is much more efficient, I think you would have to avoid stating it as a question for it to make sense. For instance:
<label for="the_question">I would answer yes to this long winded question.</label>
<input type="checkbox" name="the_question" id="the_question" value="1">
However, if your designers are dead set on ...
2
<meta http-equiv="content-language" content="ll-cc"> what is this
John Conde is correct that it should be included as part of the tag, but there's also the important consideration of ensuring that it's included as part of the HTTP Headers.
Most Meta elements are redundant replacements or over-rides for information that should be sent as part of the ...
2
The full answer to the question is answered by the W3C here: http://www.w3.org/International/questions/qa-http-and-lang.en
@John Conde is correct that it should be included as part of the <html> tag, but there's also the important consideration of ensuring that it's included as part of the HTTP Headers.
Most Meta elements are redundant replacements ...
2
You may wish to consider a code snippet collection sharing service such as Smipple, Code Barrel, or CodePad Projects. They're designed for teams to share code/markup; some (e.g. Code Barrel) allow you to tag snippets, which may help your team organise them by UI element.
2
I don't think I get what you are trying to do. If you want to reference objects inside a page, you can give each object an ID, and form the links so they will point to the ID you you've tagged.
Template page:
<div id="{{{ID|1}}}">{{{object|2}}}</div>
On relevant pages:
{{obj|cool_table|image}}
...some text...[[#cool_table|in figure 4]] ...
2
schema.org: Article, BlogPosting
If something is a schema:BlogPosting, it is an schema:Article, too, isn't it? As schema:BlogPosting is a more specific schema:Article:
More specific types
BlogPosting
NewsArticle
ScholarlyArticle
So you have an schema:Article, and now you may decide if one of these more specific types applies to your ...
2
Yes to both. Or mostly, depending upon a potential inaccuracy in your question.
Textile is just a simplified markup convention. Browsers won't do anything with it; as far as they're concerned it's just text. You'll need a pre-processor of some sort to generate HTML from it. Some text editors support this directly, there are command-line scripts and ...
1
Micro data has strict rules regarding the tags that you can use, you can open an itemprop with using the p tag and specify the data-vocabulary but nested elements must not be in a p tag.
For example you can use:
<p itemprop="address" itemscope
itemtype="http://data-vocabulary.org/Address">
<span itemprop="street-address">123 Road ...
1
I don't know of a microformat specifically for interviews, but you could combine definition lists (with the question as the term, the answer as the description) with Google's author markup.
1
This used to be much more important than it is now. As long as your individual files aren't huge, everything's going to get indexed.
Make sure you look at how your pages look to Google. Search for cache:yourdomain.com and then click to see a text-only version in the upper right.
If it looks ridiculous or very wrong, fix it until it looks right.
1
Text at top of code supposedly has more weight. (but google changes algorythms often)
( Can't you float left both (you can get the help of margin-left and right) ? or if you can go position absolute(I think you can do also with relative) and fixed widths using "left", etc, to position. )
1
I disagree with both of the approaches.
Mostly, if the "long winded question" really does have two answers then "Yes" and "No" are poor choices to offer. The options should be short phrases that state the decision being made.
An example. Instead of this:
Do you want to book conference accomodation now as a part of your ticket?
( ) Yes
( ) No
do ...
1
If you don't need sections (have small articles) you can just use a bare <article> entity around your content. And when you don't, the section can wrap sub-titles and paragraphs in those sections.
Check out the html5 section specs.
Example:
<header>
<h1>Blog Posts</h1>
</header>
<article>
<header>
...
Only top voted, non community-wiki answers of a minimum length are eligible
