Tag Info

Hot answers tagged

8

Web browsers do not care about canonical URLs. It is for search engine use only (specifically Google). Additionally, canonical URLs do not affect the loading or rendering of a web page. So no assets will be loaded over HTTP which is what would cause an insecure error message. So, no, they will not display any error message.


5

Putting the ID near the beginning of a URL is better than putting it near the end. URLs often get truncated in emails or by CMS systems that show them to users. When the ID is at the end the truncation will often lop it off and cause 404 errors on your site. When it is near the beginning, your site can still redirect to the full URL. When Googlebot ...


4

Use a 301 redirect to /folder1/page1. This tells the search engines and users the pages have moved so they can update accordingly. In the case of search engines this means making sure all links to the old URLs are credited to the new URL. In the case of users, their bookmarks (if they use them that is). It's also a usability issue (albeit a minor one). ...


4

The redirect is the better solution, as it stops the erroneous URLs ever being linked to or shared, and so should help crawl efficiency (i.e., search engines shouldn't have to crawl multiple non-canonical versions of pages, thereby wasting time that could be spent elsewhere on your site). I'd do your redirects on the server though, if possible. A fairly ...


4

Two of the most widely used web servers have very different settings for case sensitivity of URLs by default. Whether or not your URLs are case sensitive is likely a function of which you are using: Microsoft IIS - case insensitive URLs - shows the same content regardless of capitalization. Apache HTTPD Server - case sensitive URLs - gives a 404 not ...


4

Here is Google's position from an archived live chat session (the link is now dead): *Does inconsistent capitalization of URLs cause duplicate content issues and dilution of page rank? For example www.site.com/abc vs www.site.com/Abc. On Windows hosts, these are the same page, but are different pages on Unix hosts. JohnMu: Hi John, based on the ...


4

From the SEO prospective, i bet there might be a difference: In you first example, the ID is separated from the title, making it clear to the crawler it is a different resource (as the / character does it naturally). In your second example, the ID is mixed with the title. It requires more brains from the crawler to determine the meaning of it. Imagine ...


4

Google allows you to specify the canonical as an HTTP header. They give an example for canonicalizing one PDF file to another: Link: <http://www.example.com/downloads/white-paper.pdf>; rel="canonical" This page shows how to use .htaccess to put these headers in. It would be: RewriteRule ([^/]+)\.(pdf|doc|txt)$ - [E=FILENAME:$1] <FilesMatch ...


3

It shouldn't. The unsecure warning comes about when a secured page incorporates non-secured elements. A canonical tag is a link, not an object to be incorporated into the page, so there's no reason why the padlock should care whether the URL it points to is http or https.


3

No, not if their content is identical (or very nearly so), and they all have a canonical link element referencing www.mysite.net. However, that sort of issue happening site wide can be considered a crawl efficiency issue and the canonical link element doesn't really solve that. In your example, a search bot would crawl three pages when it really only needed ...


3

You should not use both noindex and rel=canonical, because noindex won't let pages pass any PageRank to its canonical version. rel="canonical" is a hint, not a directive, so Google will decide which page to take and show in search results. Here are posts at seroundtable, there they cite John Mueller's comments, from Google: No, you should not ...


3

The reason to use the rel=canonical shouldn't be the term users use to get to the site, but the content. If each page has different content and/or different reason to exist, like index and content, then there is no need for canonical, even more, it's use would be incorrect, semantically speaking. What you should do, for instance, is improve the product ...


3

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 ...


3

You may run into issues with duplicate content. You probably do not want to create canonical tags when they are not necessary. Too much work. You can try a redirect: RewriteCond %{REMOTE_ADDR} ^123\.321\.123\.32$ [NC] RewriteRule ^(.*)$ http://site.com/$1 [R=301,L] Of course you can adjust this to suit your needs. Insert this into your .htaccess file. ...


3

You could simple make a button/link with a text like "This site is in https, click here to view via https", maybe add a little warning "might not function 100%". Https Everywhere works with a whitelist. Can't find how-to real quick, but this rulsets page might help. I'm not aware of any preference or setting in the browser. You can't send a header "https, ...


2

The fact that these pages may be competing against each other is worrying. rel="canonical" will help you towards that. If you have 3 pages alike for example, and use this in 2 of them, only one will rank. There's many different ways to go about product variations. In my opinion, it would be better to list these 3 products all within one page, for example: ...


2

Use rel=canonical when you have pages with small variations. I have an eshop for rubber stamps and each stamp can have a different color. Selecting a different color changes the anchor link, which means that it is a slightly different url. I would use rel=canonical in this instance - I really have a single page that has major value to the visitor, the ...


2

...the product pages doesn't seem to rank in search engines. Setting a rel="canonical" is unlikely to help your ranking if you aren't currently being ranked already. Setting a rel="canonical" tag informs search engines which of the two (essentially duplicate) pages should appear in search engine results (SERPs). If you don't specify this then the ...


2

It's actually very simple. If you have two URLs which display the same content, you need to use canonical URLs. Which URLs is the canonical URL? The one you want Google to list in its search results. In your example, you would have the main search result without the filters being your canonical URL. So /jobs/new-york or /jobs?jobs_position_id=3 would be the ...


2

If you have a one page site you should host the content on the root of the site and not try to stuff more keywords in the URL by using a second page. Use a Title for the Home Page that uses the keywords you are targeting and proper on page SEO such as H1 tags and keyword rich content that is not spammy or written to try to only target the Google Bot. If ...


2

I had the exact same situation ( a webshop), just wait. I also 301 all the uppercased paged to the lowercase version, that might speed things up. Make sure you canonical all pages Header 301 all pages to the lowercase Make sure your sitemap is up to date Make sure all inpage anchors are correct


2

If you have NOINDEX meta tag on your page it is not good idea to put inner page links to it, because this link juice will be lost. Search engines are disabled to index the pages, so neither canonical, nor robots.txt disallow removing will help there, if you have NOINDEX meta tag. The best way I see here it is to ask people to link to your main pages, ...


2

You misunderstand some SEO principles: keywords in URLs are not so powerful for SEO than you think URLs must be chosen for users (to remember easily) before SEO Moreover, you can rank on Google for rj onetitle and janeiro onetitle with only one of these URLs. You just need to work SEO of this page. Otherwise, if you have just one of these URLs, it's ...


2

Too add a bit more info to Binarysurfs answer, if the content on the paginated pages isn't the same as on the first page you are setting the canonical tag too, it often doesn't work as the content on canonicalised pages should be the same as the canonical page. What you might want to do instead of noindexing the paginated pages is using the rel=”next” and ...


2

Replace spaces with hyphens in URL's without a doubt. They are more readable otherwise URL's will be encoded in the browser like:- example.com/category%20name/article%20name.html It's more friendly for search engines and humans like:- example.com/category-name/article-name.html You can accomplish replacing spaces with hyphens by using the php function ...


2

Google takes several things in account to determine how relevant a page is. The most important factors are: Page content Domain name URL name Let's assume that your content and your domain name didn't change. Even your HTML markup is still the same. OLD example.com/category/subcategory.html NEW example.com/category/filter/cat/subcategory.html By ...


2

I would carry on using pagination mark up on both sets of paginated pages. Google introduced the mark up for this specific purpose, it provides a hint to Google that you would like to treat the paginated pages as a logical sequence, thus consolidating their linking properties and usually sending searchers to the first page. If you noindex the paginated ...


2

This is one way people canonicalise duplicate product pages on ecommerce and is a valid way to use it. As long as the content on the product page is identical, or a large part of the content is exact and appears on both pages. If the pages are not extremely close in exact words, the canonical designation might be disregarded by search engines. For the most ...


2

Each URL on your site has its own PageRank. So http://example.com/?id=344 will have separate PageRank from http://example.com/ and both will have separate PageRank from http://example.com/page.html. In many cases a URL parameter will not cause the page shown to change, or will cause a 404 not found error. Either of those may cause the link juice ...


2

For SEO, I would say an id doesn't permit to easy remember the URL for users. Therefore, no matter on which URL you choose; an id in the middle or at the end of an URL doesn't change anything regarding SEO. However, an id in an URL can be very useful in case of you would have two pages with the same URL. This is the case for StackOverflow because the URL is ...



Only top voted, non community-wiki answers of a minimum length are eligible