Google and meta name="generator" content="ShopSite
Posted: Sun Oct 17, 2004 10:30 am
At the risk of making the people at ShopSite mad... here goes...
I believe the time has come where ShopSite should sit up and pay attention
to what they are doing wrong by not allowing more customization and or options
that can be set when building a site.
Especially when it comes to the <meta name="generator" content="ShopSite... tag
that they place in each and every page that comes from one of their templets.
I am sure that it is their advertising department that drives this decision
because if you view the source code of the shopsite back office...
it is not included there.
So why am I complaining? Simple... go to Google and search these terms:
meta name="generator" content="ShopSite
Your search - meta name="generator" content="ShopSite -
did not match any documents.
meta name="generator" content="text
about 118,000 matches
meta name="generator" content="Microsoft
about 62,600 matches
Why so little matches on the ones that do match? It is because the majority
of web sites on the internet do not place this tag in the head section at all.
The reasons are many but the fact is most do not use it and I believe that
search engines are using this information to penalize sites.
ShopSite had discovered, by chance or by design, the perfect combination
of page assembly, linking, <h*> tags etc. to help place our pages at the top
of most search engines results.
Believe me when I say that I am not just blowing off steam because of the
methodologies of the google search engine.
I believe Google also figured this out and is now penalizing any web site
which has a meta name="generator" content="ShopSite... in the head section.
I would love to hear from any other ShopSite user that took a heavy beating on
Google's search results to compare how many use ShopSite's built in templets
verses those that are still doing good with Google because they had the time
and budget to build custom templets so Google does not know that it is a
ShopSite store?
Yes I know I could spend a whole lot of time (time is money) building a
bunch of custom templets to override the ShopSite templets but the
ShopSite templets are part of what I paid for.
I know it would not have been that hard to simply drop the meta tag all
together because in older versions such as 4.x you could edit the templets
and easily rework them.
This is some of the code from one of the templets from shopsite 4.x that
I could change so that the "generator" meta tag did not even show up :
if ($PRODUCT_TYPE == $SSM_PRO) {
print
"\n<meta name=\"generator\" content=\"ShopSite Pro $VERSION\">";
} elsif ($PRODUCT_TYPE == $SSM_STD) {
print
"\n<meta name=\"generator\" content=\"ShopSite Manager $VERSION\">";
} elsif ($PRODUCT_TYPE == $SSM_LIT) {
print
"\n<meta name=\"generator\" content=\"ShopSite Lite $VERSION\">";
}
Since ShopSite decided to convert the templets to compiled code we can no
longer make any adjustments to their templets but are forced to build ones
of our own and that makes this product less valuable because we have to
write our own templets or pay someone to do it for us.
They want to keep their database proprietary and that is fine... but for the
love of pete... couldn't they at least give us the OPTION for this meta tag!
Ok... I've climbed off my soap box and am crawling back into my cave.
KP
I believe the time has come where ShopSite should sit up and pay attention
to what they are doing wrong by not allowing more customization and or options
that can be set when building a site.
Especially when it comes to the <meta name="generator" content="ShopSite... tag
that they place in each and every page that comes from one of their templets.
I am sure that it is their advertising department that drives this decision
because if you view the source code of the shopsite back office...
it is not included there.
So why am I complaining? Simple... go to Google and search these terms:
meta name="generator" content="ShopSite
Your search - meta name="generator" content="ShopSite -
did not match any documents.
meta name="generator" content="text
about 118,000 matches
meta name="generator" content="Microsoft
about 62,600 matches
Why so little matches on the ones that do match? It is because the majority
of web sites on the internet do not place this tag in the head section at all.
The reasons are many but the fact is most do not use it and I believe that
search engines are using this information to penalize sites.
ShopSite had discovered, by chance or by design, the perfect combination
of page assembly, linking, <h*> tags etc. to help place our pages at the top
of most search engines results.
Believe me when I say that I am not just blowing off steam because of the
methodologies of the google search engine.
I believe Google also figured this out and is now penalizing any web site
which has a meta name="generator" content="ShopSite... in the head section.
I would love to hear from any other ShopSite user that took a heavy beating on
Google's search results to compare how many use ShopSite's built in templets
verses those that are still doing good with Google because they had the time
and budget to build custom templets so Google does not know that it is a
ShopSite store?
Yes I know I could spend a whole lot of time (time is money) building a
bunch of custom templets to override the ShopSite templets but the
ShopSite templets are part of what I paid for.
I know it would not have been that hard to simply drop the meta tag all
together because in older versions such as 4.x you could edit the templets
and easily rework them.
This is some of the code from one of the templets from shopsite 4.x that
I could change so that the "generator" meta tag did not even show up :
if ($PRODUCT_TYPE == $SSM_PRO) {
"\n<meta name=\"generator\" content=\"ShopSite Pro $VERSION\">";
} elsif ($PRODUCT_TYPE == $SSM_STD) {
"\n<meta name=\"generator\" content=\"ShopSite Manager $VERSION\">";
} elsif ($PRODUCT_TYPE == $SSM_LIT) {
"\n<meta name=\"generator\" content=\"ShopSite Lite $VERSION\">";
}
Since ShopSite decided to convert the templets to compiled code we can no
longer make any adjustments to their templets but are forced to build ones
of our own and that makes this product less valuable because we have to
write our own templets or pay someone to do it for us.
They want to keep their database proprietary and that is fine... but for the
love of pete... couldn't they at least give us the OPTION for this meta tag!
Ok... I've climbed off my soap box and am crawling back into my cave.
KP