|
[00:32] NickSunshine: cool
[00:32] NickSunshine: i think that covers my seo for the day
[00:32] NickSunshine: lol
[00:32] NickSunshine: thanks 
[00:32] Sands: No problem, may the Google gods shine upon you.
[00:33] NickSunshine: any other helpful tips or suggestions?
[00:33] NickSunshine: from your side of the fence?
[00:33] Sands: Link me to your site.
[00:33] NickSunshine: www.nicksunshine.com
[00:34] Sands: Switch the columns.
[00:35] NickSunshine: let the content get spidered before the sidebar?
[00:35] Sands: Your sidebar is getting indexed first.
[00:35] Sands: Yes.
[00:36] NickSunshine: theres a way to lay it out in css and style have the same result without changing the look tho eh?
[00:36] NickSunshine: *style = still
[00:37] NickSunshine: probably some heavier css than i wanna get into tho
[00:37] Sands: Umm, I think so.
[00:37] NickSunshine: but i think i hated the sidebar on the right
[00:37] NickSunshine: i think thats why it landed left
[00:37] Sands: Probably with position tags.
[00:37] Sands: Or actually, no.
[00:37] Sands: It doesn't matter what the CSS is.
[00:38] Sands: If it loads on that side, it gets indexed on that side.
[00:38] Sands: ....
[00:38] NickSunshine: i thought it was a matter of where the text is in the actual page data
[00:38] Sands: Yeah, in the source.
[00:39] NickSunshine: hrm
[00:39] Sands: Oh, ok, so yeah.
[00:39] Sands: You can.
[00:39] NickSunshine: you just lay it out like content shizzle = blah
[00:39] Sands: With CSS. Oy, it's almost 4 am here, lol.
[00:39] NickSunshine: sidebar = blah
[00:39] NickSunshine: sidebar goes here
[00:39] Sands: It might be something like...
[00:39] NickSunshine: content goes there
[00:39] NickSunshine: or i could just redirect it with some java to a more useful place eh?
[00:40] Sands: You make the sidebar and content into two divs.
[00:40] Sands: And then put them in a wrapper div.
[00:40] Sands: And use CSS to position them with margin, padding, position tags...
[00:40] Sands: So it'll look like:
[00:40] NickSunshine: and sexy times ensue
[00:41] Sands: <div id="wrapper><div id="content"><div id="sidebar></div></div></div>
[00:41] Sands: So with the code, the content will be first, but through CSS the content will appear on the right.
[00:41] * NickSunshine hugs sands
[00:41] NickSunshine: thanks bro 
[00:42] Sands: lol, No problem. In practice it'll be a bit harder.
[00:42] NickSunshine: yea i know
[00:42] NickSunshine: its always easier on paper
[00:42] NickSunshine: mind if i quote you?
[00:42] Sands: Haha, go for it. | |
SATURDAY NIGHT SEO SUICIDE!
(or, how to kill your website- almost overnight!)
Tired of that pesky Googlebot crawling around on your sites looking at shit and putting it into their index for all the world to see?
You might be alone. 
If you are using apache web server on a *nix box, and you want it all to stop. . .
Theres something you can about it!
HOW TO PWN GOOGLEBOT WITH .HTACCESS!
Create a file called .htaccess in your root web directory with the following commands inside:
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^Mozilla/5\.0\ \(compatible;\ googlebot/
RewriteRule ^.* - [F,L]
Done and done. 
Ok, a bit of insight into whats happening up there.
RewriteEngine On
This turns on the Apache mod_rewrite module.
RewriteCond %{HTTP_USER_AGENT} ^Mozilla/5\.0\ \(compatible;\ googlebot/
This sets a condition for mod_rewrite that evaluates true when the user agent (browser) of a computer visiting your site matches the evaluation criteria. . .
In this case we are looking to match:
Mozilla/5.0 (compatible; googlebot/2.1; +http://www.google.com/bot.html)
And with a little regular expression love we can trap that pig
RewriteRule ^.* - [F,L]
This tells mod_rewrite what to do when it is true.
In this case, we're taking any url that is requested and returning a [F] "Forbidden" response.
The [L] directive tells mod_rewrite to stop what it is doing after the command and to see it as the last rule.
Follow this guide, and Google will be off your nuts in no time.
Hope it helps | |
|
