http://www.youtube.com/user/m0serious
A few good points that he makes that I don’t harp on:
- Title your links, this can be handy giving users more information on where the link might take them and adding keywords to your page for search engines
- Tables hurt search engine ranking. I havent heard this, and actually heard a lot of the opposite, but one site says
- If you MUST use tables, put a summary attribute in the main table tag – it will help the search engines figure out what the table is about. Summary attributes work like this:
<table summary=”keyword for the page goes here”>
- If you MUST use tables, put a summary attribute in the main table tag – it will help the search engines figure out what the table is about. Summary attributes work like this:
- Heres another tidbit:
- The problem with tables is that all the slicing and dicing can create Web pages containing tables embedded four or more deep to accommodate the design—and all the good content ends up inside the inner-most embedded tables.
From a technical perspective, search engine spiders can read tables, and even embedded tables, but once a design gets to be more than about three tables deep, most spiders run into problems. Either it’s simply too much code for them to keep track of, or the search engine thinks you placed that content deep in the page because it’s not important, and so the engine gives it little or no value.
Tip 9
Avoid unnecessary tables where possible. Limit your table embedding to a depth of three.
Where possible avoid the whole table thing and start using XHTML with
divtags and CSS to define position. This makes for a much cleaner design and has the bonus of being easier to manage.
- The problem with tables is that all the slicing and dicing can create Web pages containing tables embedded four or more deep to accommodate the design—and all the good content ends up inside the inner-most embedded tables.
