If I can't redirect to new url, how bad is forwarding it?
Steve Harris
which is un-hosted, is indexed and points to the new domain. A
permanet re-direct, from the old domain to the new, would be the best
way to go, but frankly, it's too much of a hassle to use a permanent
redirect with FrontPage. (I'm told it can be done, but it's not easy.)
I was thinking about removing the "pointing to" scenario, so Google
can see my new url, and index it, but then I'm afraid of not being in
Google for awhile. I wonder if I stop the old domain from pointing to
the new domain, and then set up an url forwarding service, if that
will free up Google to index my new domain, while showing a listing of
the old indexed domain? Thanks!
http://www.guymacon.com/ "03@spamcop.net Guy Macon
Steve Harris wrote:
>
>Google apparently can't index my new domain, because my old domain,
>which is un-hosted, is indexed and points to the new domain. A
>permanet re-direct, from the old domain to the new, would be the best
>way to go, but frankly, it's too much of a hassle to use a permanent
>redirect with FrontPage. (I'm told it can be done, but it's not easy.)
You were told wrong. The permanet redirect is programmed at the server
level. If it's an apache server, it's set in the .htaccess file.
The server has to return a 301 Moved Permanently, and any frontpage
page will return a 200 OK no matter what the content is.
You can do a different sort of (not as good) redirect in your html
that Google will follow, and you can do it with notepad. Here it is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII" />
<meta name="robots" content="noindex, follow" />
<title>http://www.example.com</title>
<meta http-equiv="refresh" content="http://www.example.com" />
</head>
<body>
<h1>
<a href="http://www.example.com">
http://www.example.com
</a>
</h1>
</body>
</html>
Replace http://www.example.com with your new URL, and place this at
your old URL.
BTW, I did some usability testing, and found that having the URL as
a h1 by itself is more effective than a "this page has moved" message.
If a user only sees one big link, he clicks on the link.
--
My email address is valid and RFC 2822 compliant - no changes needed.
<html><head><title>Guy Macon Electrical Engineer</title></head><body>
<a href="http://www.guymacon.com/" >Electrical Engineer</a> for hire:
Buena Park, CA USA Phone: 714-670-1687 Web: http://www.guymacon.com
Email: guymacon+" YOUR NAME GOES HERE "0...@spamcop.net</body></html>
rfgdxm/Robert F. Golaszewski
> Steve Harris wrote:
>>
>> Google apparently can't index my new domain, because my old domain,
>> which is un-hosted, is indexed and points to the new domain. A
>> permanet re-direct, from the old domain to the new, would be the best
>> way to go, but frankly, it's too much of a hassle to use a permanent
>> redirect with FrontPage. (I'm told it can be done, but it's not
>> easy.)
>
> You were told wrong. The permanet redirect is programmed at the server
> level. If it's an apache server, it's set in the .htaccess file.
> The server has to return a 301 Moved Permanently, and any frontpage
> page will return a 200 OK no matter what the content is.
Right. FrontPage creates website pages. Some of the pages on my site
are done with FrontPage. A 301 redirect is done by the server itself. With
my host this can be done from the control panel. Altering .htaccess is the
other way on Apache. You need to contact your host about this.
--
http://www.dextromethorphan.ws/
"The victors invariably write the history to their own advantage."
Jean-Luc Picard, Star Trek, The Next Generation, Contagion
patrick deese
> Google apparently can't index my new domain, because my old domain,
> which is un-hosted, is indexed and points to the new domain. A
> permanet re-direct, from the old domain to the new, would be the best
> way to go, but frankly, it's too much of a hassle to use a permanent
> redirect with FrontPage. (I'm told it can be done, but it's not easy.)
A permanent redirect, ie a 301 from a server has nothing to do with
front page (unless maybe you have a win2K server?). anyhow - ask your
hosting co. to 301 your old domain to your new one. its about 30
seconds for any relative skilled unix hacker.
kind regards -
patrick deese
www.electrondesign.com
Frank
everyone else.
Steve Harris
allow one, but perhaps I'll call them on the phone and read your
responses to them. It would be great if I could find an expert over
there...thanks again!
rfgdxm/Robert F. Golaszewski
>
>> Thanks! My host says I need an .htaccess file and FrontPage doesn't
>> allow one,
>
> Notepad to make your .htaccess file?
I'm not familiar with all the details of FrontPage, but I seem to
recall that at least with some servers it can be used also to FTP things
to the server on its own without a stand alone FTP client. I do have and
sometimes use FrontPage, but only know about creating web pages with it.
However, since every host I know of lets you use an FTP client, an
.htaccess file can be uploaded with that.
--
http://www.dextromethorphan.ws/
"The victors invariably write the history to their own advantage."
Jean-Luc Picard, "Star Trek, The Next Generation", Contagion episode