![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
I heard somebody say most of the 'SEO theories' are a 'big hoax'. Comments? |
#2
| |||||||
| |||||||
|
|
Here's my take on SEO: 1. Realise that search engine bots are machines. They do not have eyes, so they can't see a great Flash presentation. |
|
They don't have ears, so great music is not going to sway them. They cannot submit forms, so form based drop down navigation is lost on them. |
|
They do not have javascript or any other kind of client side plug in available. |
|
All they see is the plain text. |
|
3. Try not to use tables for layout. That's more markup for the bot to parse, and more chance of an error. Tables should be used for tabular data. |
|
4. Validate to W3 standards, and fix the errors the validator comes up with. Use a Strict doctype, which will force you to not use presenational markup. |
|
6. For dynamic pages, don't use ?id= because the bot will think it's going to get into an endless loop (it might), and it will go away. |
#3
| |||
| |||
|
|
Gazing into my crystal ball I observed John Dunlop <usenet+2004 @john.dunlop.name> writing in news:MPG.1d34d5ca42feed829896b4 @news.ntlworld.com: I heard somebody say most of the 'SEO theories' are a 'big hoax'. Comments? Here's my take on SEO: 1. Realise that search engine bots are machines. They do not have eyes, so they can't see a great Flash presentation. They don't have ears, so great music is not going to sway them. They cannot submit forms, so form based drop down navigation is lost on them. They do not have javascript or any other kind of client side plug in available. All they see is the plain text. 2. Write semantically correct markup without any presentational markup. Save the presentation for CSS. Use external javascripts to enhance the site, not for anything crutial like navigation. 3. Try not to use tables for layout. That's more markup for the bot to parse, and more chance of an error. Tables should be used for tabular data. 4. Validate to W3 standards, and fix the errors the validator comes up with. Use a Strict doctype, which will force you to not use presenational markup. 5. Try do have a domain name that has something do to with what you are trying to promote. If not for the bots, at least for people who might remember it. 6. For dynamic pages, don't use ?id= because the bot will think it's going to get into an endless loop (it might), and it will go away. |
#4
| ||||||
| ||||||
|
|
Gazing into my crystal ball I observed John Dunlop <usenet+2004 @john.dunlop.name> writing in news:MPG.1d34d5ca42feed829896b4 @news.ntlworld.com: I heard somebody say most of the 'SEO theories' are a 'big hoax'. Comments? Here's my take on SEO: 1. Realise that search engine bots are machines. They do not have eyes, so they can't see a great Flash presentation. They don't have ears, so great music is not going to sway them. They cannot submit forms, so form based drop down navigation is lost on them. They do not have javascript or any other kind of client side plug in available. All they see is the plain text. |
|
2. Write semantically correct markup without any presentational markup. Save the presentation for CSS. Use external javascripts to enhance the site, not for anything crutial like navigation. |
|
3. Try not to use tables for layout. That's more markup for the bot to parse, and more chance of an error. Tables should be used for tabular data. |
|
4. Validate to W3 standards, and fix the errors the validator comes up with. Use a Strict doctype, which will force you to not use presenational markup. |
|
5. Try do have a domain name that has something do to with what you are trying to promote. If not for the bots, at least for people who might remember it. |
|
6. For dynamic pages, don't use ?id= because the bot will think it's going to get into an endless loop (it might), and it will go away. |
#5
| |||||
| |||||
|
|
On Tue, 05 Jul 2005 21:37:16 GMT, Adrienne <arbpen2003 (AT) sbcglobal (DOT) net wrote: 2. Write semantically correct markup without any presentational markup. Save the presentation for CSS. Use external javascripts to enhance the site, not for anything crutial like navigation. I've seen no evidence or anything suggestive that presentational markup has a negative effect on a pages SERPs. Been meaning to do some tests, but not got around to it. |
|
3. Try not to use tables for layout. That's more markup for the bot to parse, and more chance of an error. Tables should be used for tabular data. For non SEO reasons I agree, but again tables are used extensively for layout, I see no reason why this could be treated negatively by the search engines. Why would they? |
|
4. Validate to W3 standards, and fix the errors the validator comes up with. Use a Strict doctype, which will force you to not use presenational markup. There's no evidence this helps again. |
|
Interesting how this is becoming standard SEO advice on this NG though. |
|
It's like blind sheep following other blind sheep down the wrong path, fortunately there's no big bad wolf on this path, |
#6
| |||
| |||
|
|
Interesting how this is becoming standard SEO advice on this NG though. |
|
It's like blind sheep following other blind sheep down the wrong path, |
#7
| |||
| |||
|
|
On Tue, 05 Jul 2005 21:37:16 GMT, Adrienne <arbpen2003 (AT) sbcglobal (DOT) net wrote: Gazing into my crystal ball I observed John Dunlop <usenet+2004 @john.dunlop.name> writing in news:MPG.1d34d5ca42feed829896b4 @news.ntlworld.com: I heard somebody say most of the 'SEO theories' are a 'big hoax'. Comments? Here's my take on SEO: 1. Realise that search engine bots are machines. They do not have eyes, so they can't see a great Flash presentation. They don't have ears, so great music is not going to sway them. They cannot submit forms, so form based drop down navigation is lost on them. They do not have javascript or any other kind of client side plug in available. All they see is the plain text. Generally true, there are exceptions like alt attributes, but for the most part it's just the text that counts. 2. Write semantically correct markup without any presentational markup. Save the presentation for CSS. Use external javascripts to enhance the site, not for anything crutial like navigation. I've seen no evidence or anything suggestive that presentational markup has a negative effect on a pages SERPs. Been meaning to do some tests, but not got around to it. 3. Try not to use tables for layout. That's more markup for the bot to parse, and more chance of an error. Tables should be used for tabular data. For non SEO reasons I agree, but again tables are used extensively for layout, I see no reason why this could be treated negatively by the search engines. Why would they? BTW I don't use tables for layout, everything I create is tables free (unless tables are appropriate, or I'm feeling lazy :-)). It's good advice to move away from tables for layout. 4. Validate to W3 standards, and fix the errors the validator comes up with. Use a Strict doctype, which will force you to not use presenational markup. There's no evidence this helps again. Interesting how this is becoming standard SEO advice on this NG though. |
#8
| |||
| |||
|
|
Would you agree those six pieces of advice (with the possible exception of the last) are a subset of the superset of authoring guidelines? |
#9
| |||
| |||
|
|
John Dunlop wrote: Would you agree those six pieces of advice (with the possible exception of the last) are a subset of the superset of authoring guidelines? There is no either / or Jock. Think about it, what does a Search Engine Robot have to go on? The content of the page, the structure of the site, the links coming to a page, their anchor text and certain bits of meta data such as the age of the domain, link creation rates etc. |
#10
| |||
| |||
|
|
Adrienne <arbpen2003 (AT) sbcglobal (DOT) net> wrote: snip |
|
6. For dynamic pages, don't use ?id= because the bot will think it's going to get into an endless loop (it might), and it will go away. Google has no problem with ?id=. Moreover, if you cause endless loops by parameters, you are not restricted to id. And hence Google is probably able to detect such loops. |
![]() |
| Thread Tools | |
| Display Modes | |
| |