Tag Info

New answers tagged

0

ok I figured it out RewriteRule ^xy(.*)$ /xy/$1 [R=301,L]


1

Try this: RewriteCond %{REQUEST_URI} !^/xy/ [NC] RewriteCond %{REQUEST_URI} ^/xy(.*)$ [NC] RewriteRule .* http://www.example.org/xy/%1.html [R=301,L] I think should do it. Please let me know and I can update the answer.


0

Q1: The URLs of the 404 pages in the Webmaster Tools all bear the mistake and will never be available at the new site. I marked them as fixed in the tools. Do I need to do something about that, like 301 rewrite them with a condition to fix the error? You might want to redirect them to a page telling users these pages are not available anymore, rather than ...


0

The semantically correct HTTP response code for this situation would be 403 Forbidden: The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it ...


1

It is not a bad idea if you implement 301 redirects from .com to .ie properly. I am changing domain in an attempt to help SEO long term by having a CC TLD (.ie rather than .com) and having my main Keyword in the domain. There will be an impact, but it will be small regarding SEO. Delivering valuable content and attracting backlinks has more impact. ...


8

The correct code would be 401 Not Authorized As per the HTTP specifications 10.4.2 401 Unauthorized The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header ...


1

Since this is a page for administrators, with or without the "key" parameter, the pages can't and should not be indexed. Therefore the webpage for non-admin can send 404 status code, and you can leave the same URL intact. Do not redirect, since you tell Google that the page has moved, but then to a page that doesn't exist. This is how Google does it as ...


2

To answer your question, no, it is not too late to implement the 301 redirect from HTTP to HTTPS. Don't switch back your sitemap to HTTP, it is not necessary. Yes Google can still call your HTTP site for a while until its indexes only the HTTPS URLs.


1

Redirecting to the new site will not hurt SEO if your only issues are poor SEO and low PageRank. Poor SEO is just a design issue and doesn't have a negative connotation other than hurting your site's ability to have its pages rank well. Low PageRank is just due to having few links pointing to your pages. That's not a negative SEO signal. So you should ...


1

This can take a while. It will take Google and Bing to figure things out and make the necessary changes. I would expect 30-60 days though it could be much less. Unfortunately, making a domain name change is not transparent. It is a huge change as far as search engines are concerned. My best advice would be to link build and correct any links you can. You ...


0

I was able to get it to work using the following: <IfModule mod_rewrite.c> RewriteEngine on RewriteCond %{HTTP_HOST} ^(www\.)?olddomain\.com$ [NC] Rewriterule ^(.*) http://newdomain.com/ [L,R=301] </IfModule> Answer provided here: 301 redirect doersnt work in SERP


0

Google might need confirmation after you applied 301 redirect right after 302 redirect. Give some time to these pages of your website. Once the redirects will be confirmed in the eyes of Google, you might start seeing your pages back. If you have waited for so long, do these two tasks. Go to Google Webmaster Tools. Go to Fetch as Google and enter your ...


1

Give it a bit of time, your rankings of before should come back within days (or weeks at most). The drop is likely caused by the change from HTTP to HTTPS. However, according to the Moz plugin, your page authority is 32 with 280 links, and your domain authority is 19 with 25K links. Your PA and DA are very low for such a number of links. You probably want ...


3

Use HTTP_HOST not HTTP_REFERER <IfModule mod_rewrite.c> RewriteEngine on RewriteCond %{HTTP_HOST} ^(www\.)?olddomain\.com$ [NC] Rewriterule ^(.*) http://newdomain.com/ [L,R=301] </IfModule>


1

forward option 301 in GoDaddy I assume this is the Forwarding without masking option as detailed on the GoDaddy support page? In which case, they do state part way down that page: If you want your visitors to be able to go to your domain name with or without the www prefix, you need to forward your domain name to use www.


2

If you are redirecting old pages to the new pages that have the same content as the redirected pages (and ideally the same URL structure), then patience is needed. I suggest that you look at the analytics of the old domains and see which pages brought most of the traffic. Track those to see whether or not you regained the old traffic. But, if you are doing ...


0

There are several spiders that will create an XML sitemap that you can use to then audit your work. I used one once years ago, but I cannot find which one I used so I do not feel comfortable making a recommendation. However, you can search: https://www.google.com/?gws_rd=ssl#q=xml+sitemap+generator+software+free I would avoid the online options and go for a ...


0

You need to create a cname record for www pointing to your main A record. It looks like the website unavailable may be coming because you are missing a cname for WWW in your godaddy dns records.


2

When involved from the start When migrating I keep the existing URLs in mind right from the start of the project. Like that I already have most links covered when switching. Right after the switch I check site:example.com and see if most links there are still working. If a lot are failing I go through them manually if there are less than say 300. In the ...


0

Unless you've left out essential information: just add a 301 redirect for the homepage only and your sitemaps and webmaster authentication will keep on functioning.


2

Method One - Google search You can find out what Google has indexed by returning results the exact results by searching for site:http://www.example.com. You should be aware that this method may not track very new URLS or if you have a lot of pages then Google will just return a few hundred. Method Two - sitemap There might be a sitemap.xml already on the ...


0

I have am not too familiar with the GoDaddy option except that we get this question from time to time. It seems this option is somewhat limited. I cannot answer to GoDaddy, but I can offer this. You can create a blank site with your web host and use .htaccess (assuming Apache) to redirect both mydomain.com and www.mydomain.com to my-new-domain.com. ...


0

I would try to somehow still link from the old domain to the new one, possibly indirectly. You don't mention the specific situation, but if you have a third site, e.g. a blog related to the products but without any kind branding, you can boost that blog with links from the old site. And the blog could have regular posts with links to the new site.


0

Is there anything I can do? Pretty much, no. If you can't redirect the old domain to the new one then they are essentially starting from scratch in every way. But since that sounds like what they want maybe it isn't such a bad thing. One thing you can do is try to get the links on other sites to be updated to the new URL with the new company name as ...


1

I'd use the setting right away -- but make sure you have the 301 redirects in place ASAP too (especially for the most important pages). This setting helps us to confirm that you really want to transfer everything (all signals that we've collected over the years) over to the new domain. It just speeds things up a tiny bit, essentially. In addition to the ...


0

If the website is going to take 1 year to transfer to a new domain, then obviously that's potentially 1 year of not having the new site SEO'd. If the website transfer is very quick, then it's an easy choice! I think it's about finding the balance. You mention link structure changing so I guess you may feel you don't have any SEO to save because of the total ...


1

I need to double check the specifications, but I am pretty certain that cached objects depend on the request method. So an object using HTTP would be a different cache entity from HTTPS. So if you are redirecting to HTTPS, there should be no prior cache data. Also, you may want to consider using lower cache periods and requiring validation prior to ...


1

I don't know about GoDaddy's error, other than maybe it is expecting example.com rather than www.example.com (although I doubt it)?! You don't actually need to specify the host if redirecting on the same site? But anyway, this is easy to do in your root .htaccess file using mod_alias: Redirect 301 /oldpage.html /new-page.html (This assumes Apache 2.2.6+ ...



Top 50 recent answers are included