Putting rel=canonical tags on blogpost pointing to product pages
-
I came across an article mentioning this as a strategy for getting product pages (which are tough to get links for) some link equity.
See #21: content flipping:
https://www.matthewbarby.com/customer-acquisition-strategies
Has anyone done this? Seems like this isn't what the tag is meant for, and Google may see this as deceptive? Any thoughts?
Jim
-
It might work, but eventually Google will catch on. If the site gets penalized for it, trying to get the ranking back up is a pain.
-
Jim,
I'd steer WAY clear of this tactic. That's a very deceptive trick (and definitely not the tag's intended use) that is almost guaranteed to get you dinged by the big G. Additionally, canonicalizing one URL to a completely different URL can get the original URL de-indexed, which wouldn't give you much value once removed.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Whats the negative effect of incorrect canonical to first page in paginated set?
Hi, I have a new client that has pagination handled incorrectly on their website.... They have it setup as follows: example.com/article?story=cupcake-news&page=1 example.com/article?story=cupcake-news&page=2 example.com/article?story=cupcake-news&page=3
Intermediate & Advanced SEO | | QubaSEO
etc etc rel=canonical from page 2 to page 1
rel=canonical from page 3 to page 1
etc etc i.e. they aren't using rel=prev, rel=next To get them to invest in the development time need to change this I need to explain to the client how what they have is negatively affecting things? Anyone? Thanks in advance!0 -
Canonical tags for duplicate listings
Hi there, We are restructuring a website. The website originally lists jobs that will have duplicate content. We have tried to ask the client not to use duplicates but apparently their industry is not something they can control. The recommendations I had is to have categories (which will have the idea description for a group of jobs), and the job listing pages. The job listing pages will then have canonical tags pointing to the category page as the primary URL to be indexed. Another opinion came from a third party that this can be seen as if we are tricking Google and would get penalised, **Is that even true? **Why would Google penalise for this if thats their recommendations in the first place? This third party suggested using nofollow on the links to these listings, or even not not index them all together. What are your thoughts? Thanks Issa
Intermediate & Advanced SEO | | iQi0 -
Why does Google rank a product page rather than a category page?
Hi, everybody In the Moz ranking tool for one of our client's (the client sells sport equipment) account, there is a trend where more and more of their landing pages are product pages instead of category pages. The optimal landing page for the term "sleeping bag" is of course the sleeping bag category page, but Google is sending them to a product page for a specific sleeping bag.. What could be the critical factors that makes the product page more relevant than the category page as the landing page?
Intermediate & Advanced SEO | | Inevo0 -
Switching from HTTP to HTTPS: 301 redirect or keep both & rel canonical?
Hey Mozzers, I'll be moving several sites from HTTP to HTTPS in the coming weeks (same brand, multiple ccTLDs). We'll start on a low traffic site and test it for 2-4 weeks to see the impact before rolling out across all 8 sites. Ideally, I'd like to simply 301 redirect the HTTP version page to the HTTPS version of the page (to get that potential SEO rankings boost). However, I'm concerned about the potential drop in rankings, links and traffic. I'm thinking of alternative ways and so instead of the 301 redirect approach, I would keep both sites live and accessible, and then add rel canonical on the HTTPS pages to point towards HTTP so that Google keeps the current pages/ links/ indexed as they are today (in this case, HTTPS is more UX than for SEO). Has anyone tried the rel canonical approach, and if so, what were the results? Do you recommend it? Also, for those who have implemented HTTPS, how long did it take for Google to index those pages over the older HTTP pages?
Intermediate & Advanced SEO | | Steven_Macdonald0 -
Why is rel="canonical" pointing at a URL with parameters bad?
Context Our website has a large number of crawl issues stemming from duplicate page content (source: Moz). According to an SEO firm which recently audited our website, some amount of these crawl issues are due to URL parameter usage. They have recommended that we "make sure every page has a Rel Canonical tag that points to the non-parameter version of that URL…parameters should never appear in Canonical tags." Here's an example URL where we have parameters in our canonical tag... http://www.chasing-fireflies.com/costumes-dress-up/womens-costumes/ rel="canonical" href="http://www.chasing-fireflies.com/costumes-dress-up/womens-costumes/?pageSize=0&pageSizeBottom=0" /> Our website runs on IBM WebSphere v 7. Questions Why it is important that the rel canonical tag points to a non-parameter URL? What is the extent of the negative impact from having rel canonicals pointing to URLs including parameters? Any advice for correcting this? Thanks for any help!
Intermediate & Advanced SEO | | Solid_Gold1 -
Canonical tag
Hi all, I have an ecommerce client and on the pages they have a drop down so customers can view via price, list etc. Natrurally I want a canonical tag on these pages, here's the question. as they have different pages of products, the canonical tag on http://www.thegreatgiftcompany.com/occassion/christmas#items-/occassion/christmas/page=7/?sort=price_asc,searchterm=,layout=grid,page=1 is to http://www.thegreatgiftcompany.com/occassion/christmas#items-/occassion/christmas/page=7. now, because the page=7 is a duplicate of the main page, shouldn't the canonical just be to the main page rather than page=7? Even when there is a canonical tag on the /Christmas/page=7 to the /Christmas page? hope that makes sense to everyone!
Intermediate & Advanced SEO | | KarlBantleman0 -
Should we Use rel=canonical in ccTLDs websites
We have multilingual eCommerce websites with some content variations but majority of the content remains the same We have used rel=alternate hreflang on corresponding ccTLDs respective countries. for example on example.com -which is the oldest of these sites- we have used Now should we also use link rel="canonical" href="example.com" on all ccTLDs? What are the advantages and disadvantages of using it?
Intermediate & Advanced SEO | | CyrilWilson0 -
Rel Alternate tag and canonical tag implementation question
Hello, I have a question about the correct way to implement the canoncial and alternate tags for a site supporting multiple languages and markets. Here's our setup. We have 3 sites, each serving a specific region, and each available in 3 languages. www.example.com : serves the US, default language is English www.example.ca : serves Canada, default language is English www.example.com.mx : serves Mexico, default language is Spanish In addition, each sites can be viewed in English, French or Spanish, by adding a language specific sub-directory prefix ( /fr , /en, /es). The implementation of the alternate tag is fairly straightforward. For the homepage, on www.example.com, it would be: -MX” href=“http://www.example.com.mx/index.html” /> -MX” href=”http://www.example.com.mx/fr/index.html“ />
Intermediate & Advanced SEO | | Amiee
-MX” href=”http://www.example.com.mx/en/index.html“ />
-US” href=”http://www.example.com/fr/index.html” />
-US” href=”http://www.example.com/es/index.html“ />
-CA” href=”http://www.example.ca/fr/index.html” />
-CA” href=”http://www.example.ca/index.html” />
-CA” href=”http://www.example.ca/es/index.html” /> My question is about the implementation of the canonical tag. Currently, each domain has its own canonical tag, as follows: rel="canonical" href="http://www.example.com/index.html"> <link rel="canonical" href="http: www.example.ca="" index.html"=""></link rel="canonical" href="http:>
<link rel="canonical" href="http: www.example.com.mx="" index.html"=""></link rel="canonical" href="http:> I am now wondering is I should set the canonical tag for all my domains to: <link rel="canonical" href="http: www.example.com="" index.html"=""></link rel="canonical" href="http:> This is what seems to be suggested on this example from the Google help center. http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077 What do you think?0