View Full Version : Is This Code a Redirect??
Waterpup
07-13-2004, 04:47 PM
I have a SEO/Marketing company doing some things to my site
http://www.MoonlightMile.net so far I am not real happy with them.
Anyhow, I have now been rejected a link exchange twice due to
having a redirect. Before all this I did not have any redirects so
I turned around and reamed them. Probably should not have now.
I can no loger manually enter my url and stay at just the .net
My site now always lands at /home.php
Here's the code I suspect and will hurt hurt me in the SERPs?
<SCRIPT language="JavaScript">
<!--
top.location.replace('<?php
if ( $goto == '' )
echo "home.php";
else
echo decode($goto);
?>');
//-->
</SCRIPT>
Waterpup
07-13-2004, 05:00 PM
Upon further investigation I see that is not the redirect I was thinking it was.
Maybe another question to ask is; where would the redirect be? htaccess?
Waterpup
07-14-2004, 10:07 AM
Anybody????
starbug
07-14-2004, 10:43 AM
Its a JS redirect which isn't as frowned upon as a meta...
at least thats my own newbie opinion :)
seo guy
07-15-2004, 12:49 AM
A better question would be why the hell did they do it? That I would take up with them, who'd you hire btw?
Waterpup
07-15-2004, 08:13 AM
They claim they didn't do it. I'll send you a PM with the company name as I am not quite ready to publicly trash them. It's not traffic power if that's what you are thinking.
owlcroft
07-15-2004, 05:55 PM
[QUOTE=Waterpup]I can no loger manually enter my url and stay at just the .net
My site now always lands at /home.php[/QUOTE] And your problem with that is . . . ?
A URL consists of three distinct parts: the protocol specifier (such as http://), the domain name (such as www.mywonderfulsite.com), and the requested resource URI (such as /book-store.html). All three need to be present for a call to be able to be interpreted by the server receiving it.
When you enter a URL of the general form--
http://www.mywonderfulsite.com/
--it might seem that you are not supplying an actual resource URI, since the bare / slash specifies only a directory (the site's root). But it works by courtesy--literally--of a server convention, that a call to any directory (not necessarily just the root) that does not specify a particular "resource" (file) will be interpreted by the server s seeking an "index" file; the server will seek such a file in that directory following, in order, a set list of possible names (almost invariably starting with index.html) and going on till it finds one or the list is exhausted. What it does then depends on the server's settings: it will either display a directory listing of the contents of that directory (as much as to say "Hey, I looked, now you find whatever it was you think you wanted") or will display a curt message to the effect that the directory contents cannot be displayed.
Now if you want (or, more commonly, need) the default "front page" of your site to be one that is not a name on the server's to-try list (or which you cannot be sure is a name on the server's to-try list), then you need to overtly redirect any such no-file-named calls direct to the file you need to have found as your "front page". Typically, one does that with an entry in one's .htaccess file if one's server offers such files (as Apache-powered servers all do).
I cannot imagine how a redirect from--http://www.MoonlightMile.net
--to--
http://www.MoonlightMile.net/home.php
--could possibly be getting up anyone's nose. Considerably more extensive redirecting than that is perfectly sound, and irrelevant.
Anyway, if you want to know exactly what is going on with respect to redirection, post a copy of your .htaccess file (modified, if need be, to preserve privacy or security).
Waterpup
07-16-2004, 02:23 PM
Other than them doing that without my knowledge or consent is one thing. The fact that I've had two different people believe I have a redirect installed and deny me a link exchange is a problem. Even if it is just a natter of perception. Plus I liked it landing on .net rather than /home.php
Anyway they claim it wasn;t them but I know better. It couldn't have been anyone else. That with a few other things ticks me off.
I've verified there's nothing in the htaccess file causing this though.
vBulletin v3.0.3, Copyright ©2000-2013, Jelsoft Enterprises Ltd.