So I'm got a bunch of domains redirecting type in traffic to a main site.
I want to be able to track each one of these domains to see how each is performing.
What I currently do is use a URL Forward (through the registrar) like this: www.mysite.com/home.html?typeintrafficdomain.com
The problem is that the above url got indexed in Google.
So the SERP looks like this:
MySite.com - Check us Out!
Info on blah blah blah
www.typeintrafficdomain.com
So when you click on the result above it redirects you to www.mysite.com/home.html?typeintrafficdomain.com
Is this hurting my main sites ranking?
Is there a cleaner way (like through a DNS) to redirect domains without having the risk of the search engines indexing your tracking pages, BUT still be able to track type in traffic from each domain?
Because I noticed that the webserver logs DON'T produce a referrer by doing a URL Foward, that is why I need to append the?typeintraffic.com to the end of the url.
[edited by: Webwork at 12:09 pm (utc) on Aug. 30, 2006]
[edit reason]
[1][edit reason] Tidying up for clarity [/edit] [/edit][/1]
You really need a 301 redirect; if that gives you useful stats, great - if it doesn't, well that's a shame, but not as much of a shame as a forwarding method that causes problems for your site or your visitors.
I have a .com as my main URL but I have a few typo domains and the .net .org variants etc etc that I want to 301 to the main .com site.
My question is; Is it OK to have those variant domains on the same WHOIS and on the same hosting package/server?
... I just set up the 301 htaccess in a separate root level server folder for each domain, yes? Is that completely SEO safe?
No problems or risks at all.
[edited by: Asia_Expat at 5:28 pm (utc) on Aug. 31, 2006]
I've got the type in domains doing a URL forward on a registrar and have tried doing:
1. mainsitedomain.com/?typeintrafficdomain.com
1. mainsitedomain.com/#typeintrafficdomain.com
...and NEITHER is tracked via Google Analytics or AwStats.
Should I look into a DNS solution? I don't have hosting on these domains so a 301 redirect in PHP or using meta tags is out of the question. To maintain this system is would be best to do it at the registrar level (URL fowarding or DNS).
<html>
<head>
<title>examplesubject</title>
<meta name="keywords" content="examplekeywords here,">
<meta name="description" content="exampledescription here">
</head>
<frameset rows='*' frameborder='NO' border='0' framespacing='0' cols='*'>
<frame name='content' src='http://forwardedtodomain dot com goes here'></frameset>
<noframes>
<a href='http://forwardedfromdomain dot com goes here'><font size='+2'>
More information on examplesubject is next.....
</font></a></noframes>
</html>
Surely someone out of the many experts here must have some knowledge on this?
Should I look into a DNS solution? I don't have hosting on these domains so a 301 redirect in PHP or using meta tags is out of the question. To maintain this system is would be best to do it at the registrar level (URL fowarding or DNS).
You might want to look into this recent thread, 302 versus 301 domain redirection [webmasterworld.com], as it deals with the same territory.
The short story is that you must use a 301 redirect, otherwise you risk a lot of muddled and duplicate entries, as noted in the example in your first post. That's going to hurt you, so you have to fix it fast.
As noted in the cited thread, most redirects at the registrar level use 302s, Moniker uses 301s.
Is the index page code method I posted even better than a Code 301 or any negatives to it since it involves framing?
Anyhing else is frought with problems and danger.
Avoid 302 redirects, meta refresh, and all Javascript stuff.
How do you big domainers track all the type in traffic to your main site?
There must be a very simple way to set this up in godaddy or moniker to do this that I'm missing.
301 or 302, it shouldn't matter for tracking purposes.
For say ASP, detect the URL, detect the referrer, use server transfer or include whatever is feasible and in the back ground can store the details in some database too.
Or can use services like google analytics , sedo etc.
I hope i making music and not sound!
:)
Regds
Dipendra
...I'm really interested in tracking the traffic from typeindomain.com to mymainsite.com...
The method I posted above which involves framed forwarding may be circa 1997 (as jimbeetle said) but it does seem to work OK. After doing a lot of research on this issue it may be the only method to track the stats and typeins since it results in a normal header Code 200.
The AWstats are available at the site forwarded FROM, but not the to site. We use it occasionally when we want to know stats and typeins on domains on forwarding which do not have their own website. Another advantage to this method is both domains can be listed in the SE Serps so you may get a bit of extra SE traffic as a nice bonus.
The disadvantage is you need to spend time setting up 2 sites on the server. The forwarded from domain needs an index page with the framed code, plus I heard the SE may not like the framing too much due to a lack of content (however I feel you can still add a little content but with dubious value - see line 11 in my code). Have not been able to get opinions on this approach from the experts though I have asked several times.
exampple.com/ is pr3
example.com/index.php is PR5
how can I forward the PR to home without index.php?
