ipopbb
Power Member
- Feb 24, 2008
- 626
- 855
Many people believe "on page" position matters. I'm not a believer , but I do like to randomize content order to make google think it is different or in many cases unique. I'm not going to go into detail on my "Spoofing Uniqueness" techniques in this post, but I will give you a small piece of the puzzle. Making content order in the source arbitrary.
The only requirement to my CSS only method is that you have to be ok with using a left-justified fixed-width layout.
So if you believe "on page" position matters then this is a CSS-only way to make your footer links top of page. Or if you want to read between the lines. This is a way to randomize the order of content blocks in your static source but yield the same natural order in the rendered view. (if you look at my source you'll see that I could put footer,content,header,leftnav,rightnav, or any number of other blocks in any order in the source and still render the same page view.)
Many believe that this gets your best tuned content to the top of page where it matters most. (I don't know about that but if you thinks so then...)
Many believe that this gets your footer links to the top of page where it matters most. (I don't know about that but if you thinks so then...)
I do believe this can help you reuse and freshen content blocks on pages to keep getting fresh content bonuses out of google without changing anything but some div orderings.
Cheers!
The only requirement to my CSS only method is that you have to be ok with using a left-justified fixed-width layout.
Code:
<html><head><style type="text/css">
html,body{ min-height: 600px;}
.header { position: absolute; top: 0px; left: 0px; width: 1000px; height: 200px;background-color: #ddd;}
.leftnav { position: absolute; top: 200px; left: 0px; width: 200px; height: 300px;background-color: #fdd;}
.content { position: absolute; top: 200px; left: 200px; width: 600px; min-height: 300px; background-color: #dfd;}
.rightnav{ position: absolute; top: 200px; left: 800px; width: 200px; height: 300px;background-color: #ffd;}
.footer { background-attachment: scroll;position: absolute; bottom: 0px; left: 0px; width: 1000px; height: 100px; background-color: #ddf; }
</style></head><body>
<div class="footer">footer</div>
<div class="content">content</div>
<div class="header">header</div>
<div class="rightnav">rightnav</div>
<div class="leftnav">leftnav</div>
</body></html>So if you believe "on page" position matters then this is a CSS-only way to make your footer links top of page. Or if you want to read between the lines. This is a way to randomize the order of content blocks in your static source but yield the same natural order in the rendered view. (if you look at my source you'll see that I could put footer,content,header,leftnav,rightnav, or any number of other blocks in any order in the source and still render the same page view.)
Many believe that this gets your best tuned content to the top of page where it matters most. (I don't know about that but if you thinks so then...)
Many believe that this gets your footer links to the top of page where it matters most. (I don't know about that but if you thinks so then...)
I do believe this can help you reuse and freshen content blocks on pages to keep getting fresh content bonuses out of google without changing anything but some div orderings.
Cheers!
