How would you treat a page with an offer that is no longer valid.
It is in Google's cache, you dont want to loose the searcher/visitor, but your cached offer is no longer valid.
A refresh to your home page?. ( will look like cloaking) A new mini content page with a link to your homepage?
What do you suggest ?
Subscribe to HRA Now!
Are you a Google Analytics enthusiast?
Share and download Custom Google Analytics Reports, dashboards and advanced segments--for FREE!
www.CustomReportSharing.com
From the folks who brought you High Rankings!
More SEO Content
International SEM | Social Media | Search Friendly Design | SEO | Paid Search / PPC | Seminars | Forum Threads | Q&A | Copywriting | Keyword Research | Web Analytics / Conversions | Blogging | Dynamic Sites | Linking | SEO Services | Site Architecture | Search Engine Spam | Wrap-ups | Business Issues | HRA Questions | Online Courses
Sponsored Content
A Cached Page With An Offer That Does Not Excist Aanymore
Started by
robmarketshare
, May 24 2007 06:41 PM
7 replies to this topic
#2
piskie
-
- Active Members
-
- 1,092 posts
HR 7
- Location:Cornwall
Posted 24 May 2007 - 06:51 PM
Possibly:
A page that describes some recent special offers and advises visitors to "Watch this Site" for more Simmilar Offers.
A page that describes some recent special offers and advises visitors to "Watch this Site" for more Simmilar Offers.
#3
Jill
-
- Admin
-
- 32,316 posts
High Rankings Advisor
Posted 24 May 2007 - 08:12 PM
piskie, how do you propose they do that on the CACHED page???
#4
robmarketshare
-
- Active Members
-
- 258 posts
HR 4
Posted 25 May 2007 - 02:26 AM
QUOTE(Jill @ May 25 2007, 03:12 AM) 
piskie, how do you propose they do that on the CACHED page???
I suppose he means a new page on our site with the exact same url as the cached page.
At the moment we use a refresh to our homepage when someone clicks on a page in the SERPS with an offer that doesn't excist anymore, but we feel this cloud be interpretated as cloaking ... anymore thoughts on this subject?
The problem only excist a few weeks (the 'old'pages will disapear) but it is an reincuring situation and we would like to use the best methode to "redirect" possible clients rather than give them a 404.
#5
Randy
-
- Moderator
-
- 17,540 posts
Convert Me!
Posted 25 May 2007 - 04:37 AM
So basically you're talking about a Featured Product page, correct?
I would use the same page name for each of those, changing out the content as necessary, rather than setting up a separate special page each time then having to worry about a redirect.
Keeping it as one file that doesn't change names every time can gain you a couple of advantage. First if you make it a prominent page --say by linking to it from your home page-- the engines will eventually pick up the fact that the page content changes more often than your other pages, so will be encouraged to spider it more often to look for these changes. How frequently they spider the page will depend upon how important you can make the page appear in their eyes, as well as to some degree how often the content changes. But having it on a dedicated page will certainly help them to realize what's what.
If you would like you can even make use of piskies suggestion above to link off to another page or even include on the same page Past specials. That way if real people do arrive at the page after the special they were looking for has run its course you may still have the opportunity to convert them into customers.
I would use the same page name for each of those, changing out the content as necessary, rather than setting up a separate special page each time then having to worry about a redirect.
Keeping it as one file that doesn't change names every time can gain you a couple of advantage. First if you make it a prominent page --say by linking to it from your home page-- the engines will eventually pick up the fact that the page content changes more often than your other pages, so will be encouraged to spider it more often to look for these changes. How frequently they spider the page will depend upon how important you can make the page appear in their eyes, as well as to some degree how often the content changes. But having it on a dedicated page will certainly help them to realize what's what.
If you would like you can even make use of piskies suggestion above to link off to another page or even include on the same page Past specials. That way if real people do arrive at the page after the special they were looking for has run its course you may still have the opportunity to convert them into customers.
#6
robmarketshare
-
- Active Members
-
- 258 posts
HR 4
Posted 25 May 2007 - 05:06 AM
Great idea to re-use these pages Randy.
Could the "refresh" hurt us. ( I need to convince, some people all the way up, to make the change in the set up) !
Could the "refresh" hurt us. ( I need to convince, some people all the way up, to make the change in the set up) !
#7
Randy
-
- Moderator
-
- 17,540 posts
Convert Me!
Posted 25 May 2007 - 05:39 AM
It depends upon how you're doing the refresh.
If you're doing a true redirect and delivering a 301 status code it won't hurt.
If you're doing a true redirect and delivering a 302 status code it shouldn't hurt, but the 302 is likely going to keep the old page filename in their index. Probably with not exactly correct information.
If you're using a Meta Refresh it depends upon the engine and how long the refresh rate is. They all treat them differently. Ian has documented this this and the differences. Most likely it's going to end up being treated as a 302 Redirect by the majority of the engines, which then leads to the above issues with 302s.
If you're using a JavaScript redirect you'll want to be careful with it. JS Redirects have been used in the past by some unscrupulous folks out there to fool the engines, so they may well take a second look to make sure you're not up to anything nefarious when they see one. This would be the one I'd personally stay away from on general principle.
FWIW, the above advice is really more for a single time event. I wouldn't want to put even a 301 in place 20 or 30 times per year. Not really because of the engines, but because it could quickly become unruly to manage a couple of years down the road. This is one of the main reasons for my suggestion above.
If you're doing a true redirect and delivering a 301 status code it won't hurt.
If you're doing a true redirect and delivering a 302 status code it shouldn't hurt, but the 302 is likely going to keep the old page filename in their index. Probably with not exactly correct information.
If you're using a Meta Refresh it depends upon the engine and how long the refresh rate is. They all treat them differently. Ian has documented this this and the differences. Most likely it's going to end up being treated as a 302 Redirect by the majority of the engines, which then leads to the above issues with 302s.
If you're using a JavaScript redirect you'll want to be careful with it. JS Redirects have been used in the past by some unscrupulous folks out there to fool the engines, so they may well take a second look to make sure you're not up to anything nefarious when they see one. This would be the one I'd personally stay away from on general principle.
FWIW, the above advice is really more for a single time event. I wouldn't want to put even a 301 in place 20 or 30 times per year. Not really because of the engines, but because it could quickly become unruly to manage a couple of years down the road. This is one of the main reasons for my suggestion above.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
