Tag Info

New answers tagged

2

We've recently had advice on best practice for a very similar structure. Canonical: Canonical shouldn't be shared across languages, but used within a language. For instance, your Masai homepage would have a canonical tag of: https://www.domain.com/mas But the canonical for your German homepage would be: https://www.domain.com/de x-default: ...


0

If your canonical tag points to the URL with the extension then is what search engines will cache and index. So the URL with the extension will be in the search results. But you have to ask yourself this, If search engines cannot see any internal links with the exception of the canonical URL on your site, what value would they place on a page if the site ...


10

Spaces in URLs should be encoded. That would eliminate foo abc.jpg as the canonical. Here is a question that addresses how the space should be encoded: In a URL, should spaces be encoded using %20 or +? Spaces may only be encoded as a + in the query string portion of the URL, so that eliminates the foo+abc.jpg as the canonical. Your canonical URL ...


2

There's nothing to worry about here, since http://example.com and http://example.com/ are the same URL. The useragent has to include a path in the HTTP request (as per RFC 2616), so what it sends to the server will be GET / in either case. If you add the verbose flag to CURL this is quite easy to verify: $ curl -v http://example.com * Rebuilt URL to: ...


1

There are several questions to answer here: What's the best way for me to take care of this situation and avoid wasting Google's crawl budget and also let my pages get the most of the weight from authority pages? As you say the parameters do not create millions of new URLs. So it would be okay to let Google crawl them. Your Canonicals do the rest of ...



Top 50 recent answers are included