all my forum's page is php?id=xxx
I found which seo article said google,yahoo etc like html page,
is that ?

Neither,

The article is wrong.

Originally Posted by meme258

all my forum's page is php?id=xxx
I found which seo article said google,yahoo etc like html page,
is that ?

Originally Posted by chrishirst

Neither,

The article is wrong.

thank you!

PHP is fine, it is better for SEO if you name the URL's for the pages like this:

forum.com/a-post.php

as apposed to:

forum.com/phpid=122645

Originally Posted by David Eaves

PHP is fine, it is better for SEO if you name the URL's for the pages like this:

forum.com/a-post.php

as apposed to:

forum.com/phpid=122645

it doesent make much of a difference besides perhaps adding keywords into the url

the page will get spidered whether its php or html, its how the web works, why would a search engine be designed to not slurp up pages?

The theory was, way back in the day, that search engines didn't like pages containing any variant of an id= parameter since they were primarily used for affiliate marketing (id=whatever implied an affiliate) and because a number of people tried to game the engine by "creating" the same page millions of times over and merely altering the id= querystring. This is going back a LONG time, however.

As of fairly recently (8 months ago), Matt Cutts from Google mentioned that id= as a parameter isn't a very good idea since big G treats it as a session hash.

http://www.mattcutts.com/blog/guest-...eview-session/

Scroll down to the bottom to see the comment.

This is probably the basis of the article comment and something that has been bent way out of proportion. There probably is a small kernel of truth to it, but not enough for users not to create querystrings if necessary, and if things such as custom 404s and URL rewriting (I think that's what it's called in PHP...don't hold me to it, though, since I don't work in PHP) aren't readily available.

Personally, I don't use any common variant of id= or s= or sid= or any other querystring that could be interpreted as a session hash and I don't have problems that way. So if you need to use querystrings, then try to come up with some other unique identifier.

Originally Posted by ADAM Web Design

The theory was, way back in the day, that search engines didn't like pages containing any variant of an id= parameter since they were primarily used for affiliate marketing (id=whatever implied an affiliate) and because a number of people tried to game the engine by "creating" the same page millions of times over and merely altering the id= querystring. This is going back a LONG time, however.

As of fairly recently (8 months ago), Matt Cutts from Google mentioned that id= as a parameter isn't a very good idea since big G treats it as a session hash.

http://www.mattcutts.com/blog/guest-...eview-session/

Scroll down to the bottom to see the comment.

This is probably the basis of the article comment and something that has been bent way out of proportion. There probably is a small kernel of truth to it, but not enough for users not to create querystrings if necessary, and if things such as custom 404s and URL rewriting (I think that's what it's called in PHP...don't hold me to it, though, since I don't work in PHP) aren't readily available.

Personally, I don't use any common variant of id= or s= or sid= or any other querystring that could be interpreted as a session hash and I don't have problems that way. So if you need to use querystrings, then try to come up with some other unique identifier.

try it

All the search engines can read php links, so don't need to worry about the index. But if you use like xxx.php or xxx.htm after the domain, google can also search in these for keywords. For example, if searching "website promotion", I found some listings like www.domain.com/websitepromotion.htm, which means google search in the url, however if it's id?=1234, I don't think google will look in that for keywords.