OT: Google link?
Ok now I'm gonna have to have a drink.....
Just took out the robots.txt edit till I get this figured out.
Where should we 301 redirect all the old pages???
Simply to the SFNT ?
Or maybe to a special static page that explains that was an old page
and suggest the hit the Search page or the Storefront and provide them
the links ??
What would we all do without this group...
Thanks,
-Barrett
http://handmade-paper.us
Hosted by Hostasaurus.com (MM v4.20 OUI)
ShipWorks by Interapptive.com
On Tuesday, May 17, 2005, at 06:15 PM, Kelly XR wrote:
> Why don't you also do a rewrite rule to directly anything from /home/
> to your new storefront?
> That would update any bots (ones that respect 301s anyway) like
> googlebot. And means that links listed that way won't just be thrown
> away by the search engine... they'll be updated to the new location.
>
> RewriteRule ^/home/$ http://yourdomain/ [NC,R=301,L]
>
> Maybe even send them to your sitemap! If it's a spider... that would
> help it index your new pages.
> RewriteRule ^/home/$ http://yourdomain/sitemap.html [NC,R=301,L]
>
> FYI
> NC means no case (upper lower case of the url doesn't matter)
> R=301 means permanently redirect this link to the new one I'm giving
> you.
> L means stop right here... quit htaccess... don't do anything else.
> If you need more stuff done to the url you just rewrote.. then leave
> off the L
>
> I think it's a good idea to head off trouble. But can I suggest you
> rewrite those urls instead of banning them via the robots file.
> You've got the urls in the serch engine... just to notify the bot to
> dump them ... not allow them... seems like wasting gold being handed
> to you.
> Instead 'correct' those sek results and permanently redirect them to
> the ones you want listed in teh search engine.
> That way also anyone who has those old links to you (that get followed
> by the spiders) will still be of value for inbound links (and will
> help the spiders update their search engines at the same time).
>
> I feel that just blocking those older urls... is like cutting off your
> nose in spite of your face... we fight for rankings and work so hard
> to get them..
> any inbound link to our sites is a treasure... a potentential revenue
> source... use them to improve your rankings instead. Tell the bots
> what they should have instead.
>
> rewrite rules can be really confusing and a pain in the butt to figure
> out... but they really are our friends in situations like this.
>
> Kelly
>
>
> Barrett wrote:
>
>> Ok folks after digesting this thread best I can and applying to our
>> situation
>> the first step I've taken to head off trouble (omg I hope I'm not
>> breaking the if it works don't fix it rule !!!)
>>
>> Added to the robots.txt
>>
>> User-agent: googlebot
>> Disallow: /home/
>>
>> this directory was to our old sek based site
>>
>> I did a queery at google and that showed 6,000 plus from that old
>> site and I was thinking oh gosh this is scary, but then
>> queried for url string to indicate the real site now with SFL
>> directory styles
>> that returned 24,600 results
>>
>> For probably a couple years now we had not linked from the dynamic
>> site to /home/ in any manner
>> The old /home/ was only there to not give a 404 to people hitting
>> links still indexed with the engines and most of those pages were
>> hacked up and had a great big proceed to the new site link on them.
>>
>> Our site map only includes SFL links.
>> Afaik all cats and prods for the site are all SFL directory style.
>> .htaccess at the root has the SFL rewrite strings
>> domain root pulls index.mvc and loads the SFNT with all prods and
>> cats as SFL
>>
>> How does this sound so far ?
>>
>> Thanks,
>> -Barrett
>> http://handmade-paper.us
>> Hosted by Hostasaurus.com (MM v4.20 OUI)
>> ShipWorks by Interapptive.com
>>
>>
>> On Tuesday, May 17, 2005, at 10:10 AM, Julie Thompson wrote:
>>
>>> Jason, I know you mentioned you were unsure if blocking the
>>> /Merchant2/ folder (or in my case, the /miva/ folder) would or
>>> wouldn't effect SFL's, but do you know where I (and I am sure many
>>> others reading this thread) can find out for sure? I don't want to
>>> open a $99.00 support ticket for this with MIVA ;-) And nor do I
>>> willy-nilly want to block the /miva/ folder only to find that all my
>>> SFL were blocked too.
>>>
>>> What I am wondering is if all the links in my store are just like
>>> this one:
>>>
>>> <A HREF ="http://www.ultimate-weight-products.com/page/UN/PROD/AN/AB-001">http://www.ultimate-weight-products.com/page/UN/PROD/AN/AB-001</A>
>>>
>>> Would blocking the /miva/ folder block the dynamic ones, like this
>>> one below, but not the SFL above (even though technically the SFL
>>> above is located in the /miva/ folder)?
>>>
>>> <A HREF ="http://www.ultimate-weight-products.com/miva/ ">http://www.ultimate-weight-products.com/miva/ </A>
>>> merchant.mvc?Screen=PROD&Product_Code=AB-001
>>>
>>> Julie <---- who is waiting for plane ticket prices to come down to
>>> confirm attending the Dallas Conference.... PHX to D/FW is $400!
>>>
>>> Jason Henderson wrote:
>>>
>>>> Same thing. There will be what "appears" to be two different pages
>>>> with the
>>>> exact same content. Banning /Merchant2/ directory "should" not
>>>> affect
>>>> rewritten urls via .htaccess such as SFL but don't quote me on that.
>>>> Jason
>>>>
>>>>> I tried to follow the entire thread and didn't see this asked. If
>>>>> so, I
>>>>> apologize. What happens if your site has both SFL and normal
>>>>> links to the
>>>>> same page? Will this cause issues?
>>>>>
>>>>>
>>>>> Paul
>>>>
>>>
>>
>>
>
>
Ok now I'm gonna have to have a drink.....
Just took out the robots.txt edit till I get this figured out.
Where should we 301 redirect all the old pages???
Simply to the SFNT ?
Or maybe to a special static page that explains that was an old page
and suggest the hit the Search page or the Storefront and provide them
the links ??
What would we all do without this group...
Thanks,
-Barrett
http://handmade-paper.us
Hosted by Hostasaurus.com (MM v4.20 OUI)
ShipWorks by Interapptive.com
On Tuesday, May 17, 2005, at 06:15 PM, Kelly XR wrote:
> Why don't you also do a rewrite rule to directly anything from /home/
> to your new storefront?
> That would update any bots (ones that respect 301s anyway) like
> googlebot. And means that links listed that way won't just be thrown
> away by the search engine... they'll be updated to the new location.
>
> RewriteRule ^/home/$ http://yourdomain/ [NC,R=301,L]
>
> Maybe even send them to your sitemap! If it's a spider... that would
> help it index your new pages.
> RewriteRule ^/home/$ http://yourdomain/sitemap.html [NC,R=301,L]
>
> FYI
> NC means no case (upper lower case of the url doesn't matter)
> R=301 means permanently redirect this link to the new one I'm giving
> you.
> L means stop right here... quit htaccess... don't do anything else.
> If you need more stuff done to the url you just rewrote.. then leave
> off the L
>
> I think it's a good idea to head off trouble. But can I suggest you
> rewrite those urls instead of banning them via the robots file.
> You've got the urls in the serch engine... just to notify the bot to
> dump them ... not allow them... seems like wasting gold being handed
> to you.
> Instead 'correct' those sek results and permanently redirect them to
> the ones you want listed in teh search engine.
> That way also anyone who has those old links to you (that get followed
> by the spiders) will still be of value for inbound links (and will
> help the spiders update their search engines at the same time).
>
> I feel that just blocking those older urls... is like cutting off your
> nose in spite of your face... we fight for rankings and work so hard
> to get them..
> any inbound link to our sites is a treasure... a potentential revenue
> source... use them to improve your rankings instead. Tell the bots
> what they should have instead.
>
> rewrite rules can be really confusing and a pain in the butt to figure
> out... but they really are our friends in situations like this.
>
> Kelly
>
>
> Barrett wrote:
>
>> Ok folks after digesting this thread best I can and applying to our
>> situation
>> the first step I've taken to head off trouble (omg I hope I'm not
>> breaking the if it works don't fix it rule !!!)
>>
>> Added to the robots.txt
>>
>> User-agent: googlebot
>> Disallow: /home/
>>
>> this directory was to our old sek based site
>>
>> I did a queery at google and that showed 6,000 plus from that old
>> site and I was thinking oh gosh this is scary, but then
>> queried for url string to indicate the real site now with SFL
>> directory styles
>> that returned 24,600 results
>>
>> For probably a couple years now we had not linked from the dynamic
>> site to /home/ in any manner
>> The old /home/ was only there to not give a 404 to people hitting
>> links still indexed with the engines and most of those pages were
>> hacked up and had a great big proceed to the new site link on them.
>>
>> Our site map only includes SFL links.
>> Afaik all cats and prods for the site are all SFL directory style.
>> .htaccess at the root has the SFL rewrite strings
>> domain root pulls index.mvc and loads the SFNT with all prods and
>> cats as SFL
>>
>> How does this sound so far ?
>>
>> Thanks,
>> -Barrett
>> http://handmade-paper.us
>> Hosted by Hostasaurus.com (MM v4.20 OUI)
>> ShipWorks by Interapptive.com
>>
>>
>> On Tuesday, May 17, 2005, at 10:10 AM, Julie Thompson wrote:
>>
>>> Jason, I know you mentioned you were unsure if blocking the
>>> /Merchant2/ folder (or in my case, the /miva/ folder) would or
>>> wouldn't effect SFL's, but do you know where I (and I am sure many
>>> others reading this thread) can find out for sure? I don't want to
>>> open a $99.00 support ticket for this with MIVA ;-) And nor do I
>>> willy-nilly want to block the /miva/ folder only to find that all my
>>> SFL were blocked too.
>>>
>>> What I am wondering is if all the links in my store are just like
>>> this one:
>>>
>>> <A HREF ="http://www.ultimate-weight-products.com/page/UN/PROD/AN/AB-001">http://www.ultimate-weight-products.com/page/UN/PROD/AN/AB-001</A>
>>>
>>> Would blocking the /miva/ folder block the dynamic ones, like this
>>> one below, but not the SFL above (even though technically the SFL
>>> above is located in the /miva/ folder)?
>>>
>>> <A HREF ="http://www.ultimate-weight-products.com/miva/ ">http://www.ultimate-weight-products.com/miva/ </A>
>>> merchant.mvc?Screen=PROD&Product_Code=AB-001
>>>
>>> Julie <---- who is waiting for plane ticket prices to come down to
>>> confirm attending the Dallas Conference.... PHX to D/FW is $400!
>>>
>>> Jason Henderson wrote:
>>>
>>>> Same thing. There will be what "appears" to be two different pages
>>>> with the
>>>> exact same content. Banning /Merchant2/ directory "should" not
>>>> affect
>>>> rewritten urls via .htaccess such as SFL but don't quote me on that.
>>>> Jason
>>>>
>>>>> I tried to follow the entire thread and didn't see this asked. If
>>>>> so, I
>>>>> apologize. What happens if your site has both SFL and normal
>>>>> links to the
>>>>> same page? Will this cause issues?
>>>>>
>>>>>
>>>>> Paul
>>>>
>>>
>>
>>
>
>
Comment