Parameter Handling for SMF in Google Webmaster Tools

Started by Paracelsus, April 29, 2010, 07:25:21 AM

Previous topic - Next topic

Paracelsus

Ok, this more of a general question for those who work with Google Webmaster Tools.

If you go to the Settings part on the Site Configuration menu you find this "Parameter handling" thing where you have something like this (take into account that there's also a wiki on my domain):
Parameter    Action    
topic    Suggested: Don't ignore    Edit
title    Suggested: Don't ignore    Edit
target    Suggested: Don't ignore    Edit
hideminor    Suggested: Don't ignore    Edit
from    Suggested: Don't ignore    Edit
limit    Suggested: Don't ignore    Edit
days    Suggested: Don't ignore    Edit
board    Suggested: Don't ignore    Edit
hidebots    Suggested: Don't ignore    Edit
hidemyself    Suggested: Don't ignore    Edit
hideanons    Suggested: Don't ignore    Edit
hideliu    Suggested: Don't ignore    Edit
diff    Suggested: Don't ignore    Edit

After this Google adds:
+ Add parameter    Found parameters: action printable returnto oldid until redlink namespace id utm_source utm_medium jumpto redirect page feed PHPSESSID type wpDestFile top search q mode externaledit 0

Does anybody know how to tune these settings and if it's worth the time? (for instance PHPSESSID would probably be something to put on ignore... or am I wrong?)

Arantor

It would be really helpful to know what version of SMF you're referring to.

Re PHPSESSID, this is added to the URL to keep track of the user (so you know you have x number of guests rather than just some anonymous browsing). In 2.0 it's a non issue since all public facing pages get canonical content references - indicating they're all the same basic page. For 1.1 it's a little more of an issue.

But all of those things seem to be unrelated to viable content (since in SMF, all actual content is either index.php, index.php?board=something, index.php?topic=something or index.php?msg=something) so they're probably OK to ignore.
Holder of controversial views, all of which my own.


Paracelsus

Quote from: Arantor on April 29, 2010, 07:40:56 AM
It would be really helpful to know what version of SMF you're referring to.

Re PHPSESSID, this is added to the URL to keep track of the user (so you know you have x number of guests rather than just some anonymous browsing). In 2.0 it's a non issue since all public facing pages get canonical content references - indicating they're all the same basic page. For 1.1 it's a little more of an issue.

But all of those things seem to be unrelated to viable content (since in SMF, all actual content is either index.php, index.php?board=something, index.php?topic=something or index.php?msg=something) so they're probably OK to ignore.

I was talking about v1.1.x, already noticed that v2 has this "canonical" path thing... in fact, is it possible to have the same canonical path feature for 1.1.x in the form of a quick hard-coded edit or is it too complicated to do?

Arantor

It's not a particularly quick edit since it's something that has to be applied in multiple places but of course it is possible to do with work.
Holder of controversial views, all of which my own.


Paracelsus

Quote from: Arantor on April 29, 2010, 08:11:38 AM
It's not a particularly quick edit since it's something that has to be applied in multiple places but of course it is possible to do with work.

Stupid me... I just noticed there's a MOD that does something similar: SMF Canonical Tag

Arantor

Holder of controversial views, all of which my own.


Advertisement: