A confused noob with some questions.

Hello everyone. I'm new here and have been reading through some of the
older topics to try and familiarize myself with the "front lines" of
SEO as opposed to what the engine sites are saying. I'm trying to get a
site up and found on the 'net. As I read through some of the comments
here I'm seeing that what the search engines tell you to do (to
optimise your site) isn't always what is best to do. Am I right in
that?

I also am seeing some things about Google. Is it not an important
engine any longer? Or is it just changing so often that it's more
frustrating than anything? What are the major engines and directories I
should be submitting to?

G sitemaps are interesting. Is it just a way for them to try and
correct all that has gone wrong with their secretive-algorithm? lol

With regards to having multiple domains and one site. I saw a few posts
about having one domain pointing at the site and then redirecting all
the other domains to that main domain. Is that right? What about the
http://url vs http://www.url? Should that be redirected to the main
version too?

From reading what Google says about designing your site for the user
and not the engine is that really the case? I find this all very

interesting. Before I just thought that getting listed was about meta
tags and keywords! Boy was I wrong.

I would love to have any links/resources you might be willing to share
with me too.

Many thanks!
J

"JDL" <whatchoogot (AT) hotmail (DOT) com> wrote:

With regards to having multiple domains and one site. I saw a few posts
about having one domain pointing at the site and then redirecting all
the other domains to that main domain. Is that right?

I see no point into that, other then when you want to secure alternative
spellings.

What about the
http://url vs http://www.url? Should that be redirected to the main
version too?

you mean: http://example.com/ and http://www.example.com/

Technically www is a subdomain. It was one day used because the www server
was a different machine compared to the ftp server, the mail server, etc.
And hence the subdomain had it's own IP address, and it was easier to see
which machine was having troubles.

Nowadays, with virtual hosting, one machine can host many, many domains,
and I see no need for the www prefix. It's hard to pronounce in several
languages, and it has 0 use, so I redirect the www subdomain to the main
domain, also to combine the page rank of the subdomain and the domain.

--
John

Googlebot Stats: http://johnbokma.com/perl/googlebot-statistics.html

John Bokma wrote:

"JDL" <whatchoogot (AT) hotmail (DOT) com> wrote:


With regards to having multiple domains and one site. I saw a few posts
about having one domain pointing at the site and then redirecting all
the other domains to that main domain. Is that right?

I see no point into that, other then when you want to secure alternative
spellings.

The organization has secured some other domains that are related to
specific off-line marketing initiatives is why. They also have secured
the French spellings for thos domains and intend to have the main page
be a Splash screen with an language option (this is mandatory for where
we live...it's part of the Languages Act).

What about the
http://url vs http://www.url? Should that be redirected to the main
version too?

you mean: http://example.com/ and http://www.example.com/

Yup, that's what I meant.

Technically www is a subdomain. It was one day used because the www server
was a different machine compared to the ftp server, the mail server, etc.
And hence the subdomain had it's own IP address, and it was easier to see
which machine was having troubles.

Nowadays, with virtual hosting, one machine can host many, many domains,
and I see no need for the www prefix. It's hard to pronounce in several
languages, and it has 0 use, so I redirect the www subdomain to the main
domain, also to combine the page rank of the subdomain and the domain.

Thanks John. That makes sense. What do you think would be the best
strategy if a website has multiple domain names.

--
John

Googlebot Stats: http://johnbokma.com/perl/googlebot-statistics.html

To further elaborate on this there is also an issue with old pages that
are no longer on the website. Is it best to just allow the 404 to come
up, or should we detect where they are coming from and redirect them on
to the new page?

What's best practice for something like that?

Thanks,
J

PS - I thought it would be OK to top post in this case. Is that ok?


JDL wrote:

John Bokma wrote:
"JDL" <whatchoogot (AT) hotmail (DOT) com> wrote:


With regards to having multiple domains and one site. I saw a few posts
about having one domain pointing at the site and then redirecting all
the other domains to that main domain. Is that right?

I see no point into that, other then when you want to secure alternative
spellings.

The organization has secured some other domains that are related to
specific off-line marketing initiatives is why. They also have secured
the French spellings for thos domains and intend to have the main page
be a Splash screen with an language option (this is mandatory for where
we live...it's part of the Languages Act).


What about the
http://url vs http://www.url? Should that be redirected to the main
version too?

you mean: http://example.com/ and http://www.example.com/

Yup, that's what I meant.


Technically www is a subdomain. It was one day used because the www server
was a different machine compared to the ftp server, the mail server, etc.
And hence the subdomain had it's own IP address, and it was easier to see
which machine was having troubles.

Nowadays, with virtual hosting, one machine can host many, many domains,
and I see no need for the www prefix. It's hard to pronounce in several
languages, and it has 0 use, so I redirect the www subdomain to the main
domain, also to combine the page rank of the subdomain and the domain.


Thanks John. That makes sense. What do you think would be the best
strategy if a website has multiple domain names.
--
John

Googlebot Stats: http://johnbokma.com/perl/googlebot-statistics.html

"JDL" <whatchoogot (AT) hotmail (DOT) com> wrote:

To further elaborate on this there is also an issue with old pages
that are no longer on the website. Is it best to just allow the 404
to come up, or should we detect where they are coming from and
redirect them on to the new page?

What's best practice for something like that?

Thanks,
J

PS - I thought it would be OK to top post in this case. Is that ok?

IMO NO: if you start an entire new topic, post a new post. If you reply,
always quote some context. Sometimes you can get away with

[redirection]

Thanks for the explanation.

<http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html>
"10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication
is given of whether the condition is temporary or permanent. The 410
(Gone) status code SHOULD be used if the server knows, through some
internally configurable mechanism, that an old resource is permanently
unavailable and has no forwarding address. This status code is commonly
used when the server does not wish to reveal exactly why the request has
been refused, or when no other response is applicable. "

So basically: if it's really gone, you should give a 410. If you have a
page that contains similar or closely related information, you should 301
to it.

404 is a kind of: the visitor entered an URL which doesn't exists.

410 is more: this page was here, it's gone, and there is no alternative,
and it's not coming back, ever.

--
John Freelance Perl programmer: http://castleamber.com/

A better start menu with Quick Launch:
http://johnbokma.com/windows/quick-launch.html

On 6 Jun 2006 11:47:58 -0700, "JDL" <whatchoogot (AT) hotmail (DOT) com> wrote:

No.

BB

To further elaborate on this there is also an issue with old pages that
are no longer on the website. Is it best to just allow the 404 to come
up, or should we detect where they are coming from and redirect them on
to the new page?

What's best practice for something like that?

Thanks,
J

PS - I thought it would be OK to top post in this case. Is that ok?


JDL wrote:
John Bokma wrote:
"JDL" <whatchoogot (AT) hotmail (DOT) com> wrote:


With regards to having multiple domains and one site. I saw a few posts
about having one domain pointing at the site and then redirecting all
the other domains to that main domain. Is that right?

I see no point into that, other then when you want to secure alternative
spellings.

The organization has secured some other domains that are related to
specific off-line marketing initiatives is why. They also have secured
the French spellings for thos domains and intend to have the main page
be a Splash screen with an language option (this is mandatory for where
we live...it's part of the Languages Act).


What about the
http://url vs http://www.url? Should that be redirected to the main
version too?

you mean: http://example.com/ and http://www.example.com/

Yup, that's what I meant.


Technically www is a subdomain. It was one day used because the www server
was a different machine compared to the ftp server, the mail server, etc.
And hence the subdomain had it's own IP address, and it was easier to see
which machine was having troubles.

Nowadays, with virtual hosting, one machine can host many, many domains,
and I see no need for the www prefix. It's hard to pronounce in several
languages, and it has 0 use, so I redirect the www subdomain to the main
domain, also to combine the page rank of the subdomain and the domain.


Thanks John. That makes sense. What do you think would be the best
strategy if a website has multiple domain names.
--
John

Googlebot Stats: http://johnbokma.com/perl/googlebot-statistics.html

--

http://www.kruse.co.uk/seo-services.htm
http://www.here-be-posters.co.uk/lempicka-prints.htm
http://www.crystal-liaison.com/armani/index.html

On Tue, 06 Jun 2006 21:16:30 GMT, Big Bill <kruse (AT) cityscape (DOT) co.uk>
wrote:

You see my point? It's difficult to follow the existing thread.

BB

On 6 Jun 2006 11:47:58 -0700, "JDL" <whatchoogot (AT) hotmail (DOT) com> wrote:

No.

BB


To further elaborate on this there is also an issue with old pages that
are no longer on the website. Is it best to just allow the 404 to come
up, or should we detect where they are coming from and redirect them on
to the new page?

What's best practice for something like that?

Thanks,
J

PS - I thought it would be OK to top post in this case. Is that ok?


JDL wrote:
John Bokma wrote:
"JDL" <whatchoogot (AT) hotmail (DOT) com> wrote:


With regards to having multiple domains and one site. I saw a few posts
about having one domain pointing at the site and then redirecting all
the other domains to that main domain. Is that right?

I see no point into that, other then when you want to secure alternative
spellings.

The organization has secured some other domains that are related to
specific off-line marketing initiatives is why. They also have secured
the French spellings for thos domains and intend to have the main page
be a Splash screen with an language option (this is mandatory for where
we live...it's part of the Languages Act).


What about the
http://url vs http://www.url? Should that be redirected to the main
version too?

you mean: http://example.com/ and http://www.example.com/

Yup, that's what I meant.


Technically www is a subdomain. It was one day used because the www server
was a different machine compared to the ftp server, the mail server, etc.
And hence the subdomain had it's own IP address, and it was easier to see
which machine was having troubles.

Nowadays, with virtual hosting, one machine can host many, many domains,
and I see no need for the www prefix. It's hard to pronounce in several
languages, and it has 0 use, so I redirect the www subdomain to the main
domain, also to combine the page rank of the subdomain and the domain.


Thanks John. That makes sense. What do you think would be the best
strategy if a website has multiple domain names.
--
John

Googlebot Stats: http://johnbokma.com/perl/googlebot-statistics.html

--

http://www.kruse.co.uk/seo-services.htm
http://www.here-be-posters.co.uk/lempicka-prints.htm
http://www.crystal-liaison.com/armani/index.html

Big Bill <kruse (AT) cityscape (DOT) co.uk> wrote:

On Tue, 06 Jun 2006 21:16:30 GMT, Big Bill <kruse (AT) cityscape (DOT) co.uk
wrote:

You see my point? It's difficult to follow the existing thread.

BB


On 6 Jun 2006 11:47:58 -0700, "JDL" <whatchoogot (AT) hotmail (DOT) com> wrote:

No.

BB


To further elaborate on this there is also an issue with old pages
that are no longer on the website. Is it best to just allow the 404
to come up, or should we detect where they are coming from and
redirect them on to the new page?

What's best practice for something like that? H
A
Thanks, H
J !

PS - I thought it would be OK to top post in this case. Is that ok?

YOU THOUGHT THAT WAS DIFFICULT?
JDL wrote:
John Bokma wrote:
"JDL" <whatchoogot (AT) hotmail (DOT) com> wrote:


With regards to having multiple domains and one site. I saw a
few posts about having one domain pointing at the site and then
redirecting all the other domains to that main domain. Is that
right?

I see no point into that, other then when you want to secure
alternative spellings.

The organization has secured some other domains that are related to
specific off-line marketing initiatives is why. They also have
secured the French spellings for thos domains and intend to have
the main page be a Splash screen with an language option (this is
mandatory for where we live...it's part of the Languages Act).

HOW ABOUT THIS?
What about the
http://url vs http://www.url? Should that be redirected to the
main version too?

you mean: http://example.com/ and http://www.example.com/

Yup, that's what I meant.


Technically www is a subdomain. It was one day used because the
www server was a different machine compared to the ftp server,
the mail server, etc. And hence the subdomain had it's own IP
address, and it was easier to see which machine was having
troubles.

Nowadays, with virtual hosting, one machine can host many, many
domains, and I see no need for the www prefix. It's hard to
pronounce in several languages, and it has 0 use, so I redirect
the www subdomain to the main domain, also to combine the page
rank of the subdomain and the domain.


Thanks John. That makes sense. What do you think would be the best
strategy if a website has multiple domain names.
--
John

Googlebot Stats:
http://johnbokma.com/perl/googlebot-statistics.html

--
John Freelance Perl programmer: http://castleamber.com/

A better start menu with Quick Launch:
http://johnbokma.com/windows/quick-launch.html

"Big Bill" <kruse (AT) cityscape (DOT) co.uk> wrote

On Tue, 06 Jun 2006 21:16:30 GMT, Big Bill <kruse (AT) cityscape (DOT) co.uk
wrote:

You see my point? It's difficult to follow the existing thread.

BB

It appears I am not the only one to bitch.:-)

Stacey wrote:

It appears I am not the only one to bitch.:-)

LOL. Got it folks.