Tag Info

New answers tagged

0

The only thing that matter is what clients (including Googlebot) see. When you implement 301 redirects, it doesn't matter if you do it using Apache's mod_alias, rewrite rules, or through a custom 404 handler. The only thing that matters is the status code that browsers and bots see when they visit the URL. You should test this yourself using the ...


0

It won't harm your website. Make proper 301 redirection of your old domain. e.g. www.badges-and-buttons.com 301 redirect to www.badges-buttons.com Also, read this http://stackoverflow.com/questions/8450573/how-to-301-redirect-an-entire-domain-while-preserving-the-path


1

Google punishments If both sites are the same and both sites are in the index then yes, one will be marked as duplicate. Do a site: www.example.com` as a search on Google. Generally what normally happens is when a site is marked duplicate it will noted by Google and if enough pages and content gets marked as duplicate the site will receive a punishment ...


0

It could just be a misconfigured .htaccess file. If you don't have an .htaccess file that could be it, too. Check it to see if there is any forwarding rules in there, and change it from http to https if there are.


2

# curl -IL http://www.ligatures.net/a.html -v * Connection #0 to host www.ligatures.net left intact * Issue another request to this URL: 'https://www.ligatures.net/a.html' * Found bundle for host www.ligatures.net: 0x14103c0 * Adding handle: conn: 0x1410930 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 ...


0

yes you need to redirect all your links to the new domain then only you will be able to get the same ranking as of old one.Once you upload the content on the new website you will need to place redirects from the old domain to the new one. Note that this should be done on the page level, meaning that each page of the old site should be redirected to the new ...


1

Google SEO logic is always a tightly held secret, but moving your domain can/will always result in a lower site ranking. By having the auto forward setup the way you did you might be effectively giving Google two sites (so far as it knows) to keep page rankings for, and as a result your ranking will always be lower if it is being divided among two or more ...


1

Google has announced a big update secretly that going from HTTP to HTTPS will give you a minor rank boost. Google says that your site will get a small ranking benefit within whole ranking algorithm. Based on number of researches and tests, Google says that this minor change has an impact on “less than 1% of all the global queries” but it is not clear that ...


3

Let the user choose. Few things are more frustrating than being forced to use a lacking mobile site. Consider allowing desktop users to choose mobile as well -- perhaps they're tethering their laptop to their unrooted iPhone and would appreciate the low-bandwidth alternative for their limited data quota. I think you will find the first problem case ...


5

You do not want to do a 301 redirect to a 404 page. The 404 HTTP response tells the user-agent (browser, search engine, etc) that the requested document cannot be found. If you send a 301 HTTP response then they will think the document has moved to the new location which is your 404 page. That is not accurate. When you encounter a page not found send the ...


14

Mobile to desktop version should be a choice the user initiates. Sometimes the user may want the mobile version due to: 1) A focused and less cluttered experience 2) Faster browsing for low-bandwidth users (e.g. laptop with a 3G connection) 3) Ability to fit on a small screen Whatever the reason, I don't think deciding for your users is right. Let the ...


3

I don't see why not. The question here is whether you think it will benefit your users or not. Personally speaking, I find it a tad bit annoying whenever I'm brought to the mobile version of a website, even though I'm using a desktop computer. Do note that you should create some sort of URL fragment that can be used whenever you do not want to be redirected ...


1

Your question is a very good one, very far from being silly. What you probably need to do is to point your domain registered through http://www.dot.tk to the server where your website is hosted. By website I mean your files not the doamin name. That will be achieved by updating the DNS settings at http://www.dot.tk with nameservers associated with your ...


0

Go to your domain manager (wherever you bought the domain name from), and set the CNAME alias of example.tk to example.com. It make may take some fiddling but i'm pretty sure this is what you're looking for.


0

When a user goes to example.tk the content of example.com is shown but the url in the address bar should not change. Though not recommended, you can use frames. With a frame the URL will not change. Example: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd"> <html ...


2

This looks pretty spot on to me, apart from on the Spanish desktop site set, where there are quite a few errors. You are referencing the mobile version with the three rel="alternate" hreflang= tags, you should be referencing the desktop version. The canonical tag on the Spanish desktop is pointing to the English language page. If you need to set a ...


0

CDN servers are configured to serve the resource if they already have a copy. If they don't have a copy, they need to fetch it from your website. To do so, they need to know what the address of your server is. You would have told them this information during the setup process for the CDN. It seems likely to me that the CDN is set up to fetch content from ...


1

So you want to serve the content that's on a.com/xyz on b.com? Definitely possible but that's duplicate content and it's not something you want if you care about SEO. Better go with one of these options: simply 301 redirect from b.com to a.com/xyz. serve the content only on b.com. keep duplicate content and make sure the content on either a.com or ...


0

NON-WWW URLS TO WWW WITH HTTPS USING HTACCESS: You can add the following code to your .htaccess file, you can find it in your website root directory, if you don't find it you can copy this in a text editor and save it as .htaccess, then upload it. p.s.: Make sure that you backup the .HTACCESS file before you proceed. Incorrect codes can lead to 500 ...


2

HTTPS/HTTP is a protocol and technically are not classed as a new site You do not need to inform Google Webmaster Tools that your site has moved, this is because HTTPS and HTTP are protocols and not are not treated the same as say changing domain or sub domain. You can even see when adding a site to webmaster tools it doesn't even ask for a protocol: ...



Top 50 recent answers are included