Tag Info

New answers tagged

1

The answer depends on the content of the three sites. If the content on all sites are very similar and are used primarily to "game the system" and take up as much real estate in the SERPs, you will lose. Google is smarter than that and uses signals such as same IPs, logins, user cookies, etc. to tell that one company is trying to manipulate the SERPs. An ...


1

This code is what you need in the first lines of an .htaccess file in the old website document root folder (provided the old server runs apache with mod_rewrite module installed): RewriteEngine On RewriteCond %{HTTP_HOST} ^www\.website1\.com$ [NC,OR] RewriteCond %{HTTP_HOST} ^website1\.com$ [NC] RewriteRule ^(.*)$ http://www.newwebsite.com/$1 [R=301,L] ...


0

You don't necessarily need to externally redirect. You could keep the (URL) filename the same and either internally rewrite to the actual .jpg file, or just make sure you send the correct Content-Type header. It is, after all, the mime-type that determines the file type, not the file extension (although this might be a bit confusing). Obviously if you ...


1

Doing a 301 redirect, you should be fine. I would not try and redirect each image by name, but rather make sure that each new image has the same name, just another file extension. This should make redirecting a simple regex operation. Having said that, I suggest using http://www.smalleranimals.com/thumb.htm especially since you have 10k images. Here are ...


1

I'm sure there must be a more elegant/efficient way of writing this, but this should work to do what you require: RewriteEngine On RewriteBase / # Restrict users from IP address 10.8.0.11 to user1 sub-folder RewriteCond %{REMOTE_ADDR} 10\.8\.0\.11 RewriteCond %{REQUEST_URI} !(user1) RewriteRule ^(.*)$ /user1/$1 [L,R=301] # Restrict users from IP address ...


1

You don't need to contact anybody. If you setup 301 redirects in your .htaccess file to the new pages correctly there will be no issues with duplicate content.


2

If you are moving your site from http to https, you would need to submite the https site as a new site. I was advised that I need not do it and over a period of time I saw that the stats were not reliable - the index status, crawl errors etc. Suddently, I saw a big drop in the indexed pages as well. But the actual site traffic was not affected in any way; ...


0

I'm gonna assume each domain you're inquiring about are assigned separate document root folders on the same server. I'll assume the document root for abc.com is in the /abc/public_html folder, and document root for xyz.com is in the /xyz/public_html folder. Because you don't want xyz.com to show up and you want data from it, you have a couple of options. ...


0

If you don't use www, then I think you'll have a problem with having clients sending extra unnecessary data when fetching resources that don't require cookies such as images unless you use a completely new domain name for your resources other than the HTML itself. See: http://www.phpied.com/www-vs-no-www-and-cookies/


0

As long as you have a 301 redirect from the www subdomain you're fine.


3

If you take all the right steps, there isn't a lot to worry about. 301 all existing pages (This is the major step!) Set all you canonical tags right (This is your 2nd most important step) You will lose a little PageRank for the redirect, but we're talking minimal amount here, nothing a little time won't fix. Just read up on how to migrate sites (which ...


1

If you break these 301's, you will lose all value for any link you break. You may not care of course. But then again, you might. Many bots work from databases that are shared, sold, passed around. As well, many are following existing links to your site. Also consider that there are a ton of scrapers from domain monetizers that will continue no matter what ...


0

I found the solution to my problem. I just changed "externalBaseUrl":"http:\/\/bhaveshladdagiri1.wix.com/tlbinnovation" to "externalBaseUrl":"http:\/\/tlb-innovation.tk" in the HTML code. Thanks to the Darcy website ripper support for this solution.


1

My co-worker that took this over was able to come up with a solution that worked for us on this one. Just figured I'd post to close the loop on this one so if anyone else runs into a similar issue, it might help them out as well. He wrote an ISAPI ReWrite/ReDirect rule using the ISAPI ReWrite Manager for ISS that looks like this: RewriteEngine on ...


1

I'm always setup 301 redirect from www.example.com domain to example.com. This code helps you: server { server_name www.example.com; return 301 $scheme://example.com$request_uri; }


2

I would think this would be the expected behaviour would be this instead: www.example.com -> example.com www.example.com/test.html -> example.com/test.html That's a good idea. Just map the last parts of the URL (particularly folder and file) from the old domain to the new domain. You can easily use mod-rewrite if you have apache. Just make an ...


3

The HTTP status code 301 is named "Moved Permanently": The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. So the resource (i.e., your document) would stay the same, it just gets a new URI. As your front page http://example.com/ is (usually) not the same resource ...


2

Google will be happy with either link, but it will likely show the resulting link in the search engine results so users don't have to be transferred to a redirect when clicking on a result. In your case, if you want mysite.com to appear in the results pages instead of mysite.com/blog to appear, then you need to have mysite.com point to content instead of a ...


1

I would guess you purchase a static single domain certificate which only covers the domain name and not subdomain. Sadly, www. is a sub by certificate standards. If that is the case I see 3 moves you could make. 1. Purchase another certificate for the www. that you never plan on using and make a redirect. (Waste of cash, forget I even mentioned it. ...


1

One way that comes to my mind would involve using PHP: $_SERVER['HTTP_REFERER'] You could check for the refering URL and implement a redirect accordingly: if($_SERVER['HTTP_REFERER']=="http://www.example.com/") { my_redirection_fuction(); } This is however a rather unreliable method since people can hide the refering url through browser privacy ...


0

This htaccess snippet should do it for you -- redirects non-WWW to WWW mode, redirects non-HTTPS to HTTPS mode: RewriteCond %{HTTP_HOST} ^example\.com$ RewriteRule ^(.*)$ "https://www\.example\.com/$1" [R=301,L] Sometimes for certain multi-app installs on a hosting account, you may work with "addon domains". These are basically masked subdomains of the ...


0

This requires you to carry out a 301 redirect, with which you can move to a new domain without affecting your SEO. Maybe you can refer to https://phpmatters.com/how-to-move-to-new-domain/ to get some inspirations.


3

The first parameter of RedirectPermanent should be a path, not a full URL (e.g. RedirectPermanent /foo http://example.com/bar), so you won't quite be able to get what you're trying to do to work. You should be able to do it if you split the www part into a separate vhost: <VirtualHost *:80> DocumentRoot /var/www/example ServerName example.com ...


0

I never try and do redirects on the configuration file. I would suggest removing your redirect and creating an .htaccess file within the root of the web space with the following code: RewriteEngine on RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC] RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]


0

I think if you redirect from competitor site to yours then google will show your biz when people are searching for competitor site.


1

Restaurants and takeaways use local rankings which is different to normal search listings, it uses NAP (Name Address Phone Number) and many other factors to determine where your business is located and the intended local audience. So, unless you sell the same food and serve the same area its generally a bad idea. Google has wised up to people purchasing ...


3

To redirect everyone else, apart from your IP address (eg. 123.123.123.123), to the /blog subdirectory then you can use something like the following in .htaccess: RewriteEngine On RewriteCond %{REQUEST_URI} !^/blog/ RewriteCond %{REMOTE_ADDR} !=123.123.123.123 RewriteRule (.*) /blog/$1 [R=301,L] If the requested URI does not start with /blog/ and the IP ...



Top 50 recent answers are included