301 redirect from root to /index.aspx
-
I have taken over the SEO for www.domain.net.
The way i've inherited the setup is that www.domain.net is 301 redirected to www.domain.net/index.aspx Looking at top pages and linking root domains in Opensiteexplorer I can see that
www.domain.net/index.aspx has 1,006 linking root domains www.domain.net has 806 linking root domains.
I assume that www.domain.net is passing the value of it's 806 domain links to www.domain.net/index.aspx via the 301 redirect and because of this would expect www.domain.net/index.aspx to be the strongest page on the site and be the url that ranks in the listings for many relevant searches.
It appears however that www.domain.net is what is shown in listings and not www.domain.net/index.aspx ??
Can anyone explain why this might be??
If I do a site: search in Google then www.domain.net is indexed and not www.domain.net/index.aspx ??
-
These could be mostly internal links - are you linking to "/index.aspx" from your navigation, logo, etc.? In OSE, select "from [only external]", and you won't see your internal links. That can really skew the count.
-
Thanks once again Brian.
I have double checked the header response and the redirect from "index.aspx" to the international pages is definitely a 302.
I'm hoping that Google is not assuming that the 302 is intended to be a 301 as I want the link juice to stay at the root domain and I assume this is why 302s were used by whoever setup the IP redirects to international pages.
-
Thanks Dr. Pete,
I am comforted slightly by what you say about Google having a strong preference for the root and that you've seen it before. With the volume of links coming in to "index.aspx" you can see why seeing the root in Google listings made me nervous that all of those links were being ignored.
This comment also comforts me..
301/302 chain could exacerbate the problem, although it would typically leave link-juice after the 301
as that is what I would expect too.
I am hesitant to make changes because of the risks it involves and might just have to accept that I'll never know for sure whether those links to "index.aspx" are definitely being counted.
-
Well, here are some more possible issues....
1. Are you sure the redirect to the English page is a 302 and not a 301? As Dr Peter suggested - check the headers.
2. Google has said that in cases where it believes the 302 is a mistake it will treat the 302 as a 301....if this is the case, there's really nothing you can do, besides getting rid of the 302 and using a meta refresh instead. The meta refresh is commonly used in situations like yours, and while not a perfect solution, it would seem to be better than using a 302, which is typically not a good solution at all anymore. I'd bet this is your issue.
-
Google seems to have a strong preference for the root domain, and I've seen this before. Unfortunately, ASP/.NET can be really stubborn about going for the "index.aspx" or "default.aspx" page. You're probably still getting credit for the back-links, but it can be tough to tell. A couple of things:
(1) Make sure you're linking internally to the canonical version (in this case "index.aspx"). Otherwise, you're sending a mixed signal and that can disrupt the 301.
(2) Add a canonical tag to the "index.aspx" page. It can't hurt to double up, in this case.
Oh, sorry - just saw your follow-up. That 301/302 chain could exacerbate the problem, although it would typically leave link-juice after the 301. It's a bit complex, though. You could consider moving your English home-page up a level and only redirecting other audiences. That is a tricky proposition, though, and carries risk.
I'd also grab a header checker and just make sure Google is seeing what you're seeing. It's always best to verify that your redirects are working as expected.
-
Thanks again for giving this some thought and trying to help!
OK, I left out some info that I thought would complicate my description of setup but I wonder whether it is pertinent to the problem....
The site has international content areas and is geo-targeted using the directory method i.e /en-gb, /en-au,, /en-us etc
I have mentioned that www.domain.net does a 301 redirect to www.domain.net/index.aspx but I did not mention that www.domain.net/index.aspx then 302 redirects to the relevant international landing page based on IP address.
I'm pretty sure that the Google spider crawls from a US IP address so I believe that what it will see is:
www.domain.net 301 redirects to www.domain.net/index.aspx
www.domain.net/index.aspx 302 redirects to www.domain.net/en-us/index.aspx
Could the 302 redirect from www.domain.net/index.aspx be responsible for Google keeping www.domain.net in their index despite the 301??
Also, and concerning me more, do you think the considerable link juice to www.domain.net/index.aspx is being lost in all of this??
-
Quba I've thought about this more, and...I have to say that I'm at a loss. All of the links to the domain.net should be lost to domain.net and gained by domain.net/index.aspx
Is it possible that the index.aspx url has a noindex instruction from the robots.txt?. Is index.aspx showing up at all?
-
Thanks for your response Brian,
it could be that most of the links are initially directed at www.domain.net.
According to Opensiteexplorer www.domain.net/index.aspx has more links than www.domain.net though?
Where is your non-www domain directed? Is it directed to www.domain.net or or www.domain.net/index.aspx ? If it's directed to the former then that could explain some or all of your issue.
domain.net redirects to www.domain.net/index.aspx
-
Quba it's hard to say, but....
1. We know that (according to Google) some PR is lost in redirection, and it could be that most of the links are initially directed at www.domain.net.
2. Where is your non-www domain directed? Is it directed to www.domain.net or or www.domain.net/index.aspx ? If it's directed to the former then that could explain some or all of your issue.
-
Why has the main domain been redirected to index.aspx? it makes no sense
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Redirects, 301's & 404's
I have tons of links that I have had added a redirect to after creating my companies new website. Is it bad to have all these 301s? How do I permanently redirect those links? Also, on Google Search Console it's telling me I have 1,000+ excluded links. Is this bad? Will it negatively affect me? Is this something to do with my sitemap? Any help would be greatly appreciated 🙂
Technical SEO | | sammecooper0 -
301 Domain Redirect from old domain with HTTPS
My domain was indexed with HTTPS://WWW. now that we redirected it the certificate has been removed and if you try to visit the old site with https it throws an obvious error that this sites not secure and the 301 does not happen. My question is will googles bot have this issue. Right now the domain has been in redirection status to the new domain for a couple months and the old site is still indexed, while the new one is not ranking well for half its terms. If that is not causing the problem can anyone tell me why would the 301 take such a long time. Ive double and quadruple checked the 301's and all settings to ensure its being redirected properly. Yet it still hasn't fully redirected. Something is wrong and my clients ready to ditch the old domain we worked on for a good amount of time. backgorund:About 30 days ago we found some redirect loops .. well not loop but it was redirecting from old domain to the new domain several times without error. I removed the plugins causing the multi redirects and now we have just one redirect from any page on the old domain to the new https version. Any suggestions? This is really frustrating me and I just can't figure it out. My only answer at this point is wait it out because others have had this issue where it takes up to 2 months to redirect the domain. My only issue is that this is the first domain redirect out of many that have ever taken more than a week or three.
Technical SEO | | waqid0 -
Switched from and HTTPS to HTTP. My home page is facing a redirect issue from the http to https. Should I no index the HTTP or find the redirect and delete it? Thank you
Switched from and HTTPS to HTTP. My home page is facing a redirect issue from the http to https. Should I no index the HTTP or find the redirect and delete it? Thank you
Technical SEO | | LandmarkRecovery20170 -
How long does Google/Bing take to index
Hello we have 2-3 new pages being submitted every night to google/bing via our sitemap. Two issues I am noticing. Wondering if anyone else has same issues. a) 22 URL submitted via sitemap but only 1 indexed in two weeks. there are no errors showing b) If i submit manually using "Fetch As Google" and request indexing - the page gets indexed right way but after a day it seems to be unindexed - it will show up when i search (site:domain.com) but then disappear from the results doing the same search a few days later. Is this normal or do i have a problem that needs addressing? thank you
Technical SEO | | sancarlos0 -
Site Penalized - 301 Redirect Question
Hello, We have a website that was penalized roughly two years by Google for "Unnatural Links"... We are experiencing a lot of problems with this site, completely unrelated to the penalty or SERPS, and we're debating doing a 301 Re-direct to another site we own that is totally clean and has no "Unnatural Links". If we do a 301 from the penalized site to our alternative website, will there be any cross-contamination? Will the penalty carry over to our other site? Please let me know what you guys think. Thanks
Technical SEO | | Prime850 -
When to use mod rewrite / canonical / 301 redirect
Hello, I have taken over the management of a site which has a big problem with duplicate content. The duplicate content is caused by two things: Upper and lower case urls e.g: www.mysite.com/blog and www.mysite.com/Blog The other reason is the use of product filters / pagination which mean you can get to the same 'page' via different filters. The filters generate separate URLs. http://www.mysite.com/casestudy
Technical SEO | | Barques-Design
http://www.mysite.com/casestudy/filter?page=1
http://www.mysite.com/casestudy/filter?solution=0&page=1
http://www.mysite.com/casestudy?page=1
http://www.cpio.co.uk/casestudy/filter?solution=0" Am I right to assume that for the case sensitive URLs I should use a 301 redirect because I only want the lower page to be shown? For the issue with dynamic URLs should we implement a mod-rewrite and 301 to one page? Any advice would be greatly appreciated.
Mat0 -
Questions about the Sandbox and 301 Redirects
Does the sandbox still exist? What if you have a brand new URL and do a 301 redirect from another website because the name of the service business changed? Thanks for any insight and help.
Technical SEO | | SDSLaw0 -
301 Redirect vs Domain Alias
We have hundreds of domains which are either alternate spelling of our primary domain or close keyword names we didn't want our competitor to get before us. The primary domain is running on a dedicated Windows server running IIS6 and set to a static IP. Since it is a static IP and not using host headers any domain pointed to the static IP will immediately show the contents of the site, however the domain will be whatever was typed. Which could be the primary domain or an alias. Two concerns. First, is it possible that Google would penalize us for the alias domains or dilute our primary domain "juice"? Second, we need to properly track traffic from the alias domains. We could make unique content for those performing well and sell or let expire those that are sending no traffic. It's not my goal to use the alias domains to artificially pump up our primary domain. We have them for spelling errors and direct traffic. What is the best practice for handling one or both of these issues?
Technical SEO | | briankb0