Using cononical and rel=next / prev for single page app
-
Hi,
We are currently working on a single page ember.js website which compares LED light bulbs (seriously...)
the site is www.whichledlight.com
the problem in question is www.whichledlight.com/bulbs
we are using both rel=next/prev as well as cononical and wondering what affect this would have?
all the canonical reference themselves I think, and are also present on the product pages.
Our google impressions have dropped recently as well, so we are wondering wether or not this is having a negative affect in regards to how well google wants to play with us.
Any ideas?
-
Thanks Dirk!
Will look into it now.. I wasn't checking the source but rather looking in Chrome Dev Tools
-
-
Hi Dirk,
in regards to https://www.whichledlight.com/bulbs?page=2
the link syntax is as follows though...
Are you saying that when you're on that page that the href is missing..??
Thanks
-
Hi
The syntax you use is wrong:
Example page: https://www.whichledlight.com/bulbs?page=2
The canonical should be
(currently )
Check this reference: https://support.google.com/webmasters/answer/139066?hl=en
The rel next /previous should be:
(currently:
Check this reference: https://support.google.com/webmasters/answer/1663744?hl=en
Hope this helps;
Dirk
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
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
-
Will google be able to crawl all of the pages given that the pages displayed or the info on a page varies according to the city of a user?
So the website I am working for asks for a location before displaying the product pages. There are two cities with multiple warehouses. Based on the users' location, the product pages available in the warehouse serving only in that area are shown. If the user skips location, default warehouse-related product pages are shown. The APIs are all location-based.
Intermediate & Advanced SEO | | Airlift0 -
Validated pages on GSC displays 5x more pages than when performing site:domain.com?
Hi mozzers, When checking the coverage report on GSC I am seeing over 649,000 valid pages https://cl.ly/ae46ec25f494 but when performing site:domain.com I am only seeing 130,000 pages. Which one is more the source of truth especially I have checked some of these "valid" pages and noticed they're not even indexed?
Intermediate & Advanced SEO | | Ty19860 -
Using the same picture, but 2 differents pages and Alt descriptions
Hi Moz experts, I have a quick technical question for you. If we would like to use the same picture on the website, but using differ Alt description and also, be sure to customize it to make sure, it will not look like the other. This strategy is for saving cost on new picture. Do you think google will see this as iidentical content ? Thank you for your hands up on this question.
Intermediate & Advanced SEO | | johncurlee0 -
Canonical use when dynamically placing items on "all products" page
Hi all, We're trying to get our canonical situation straightened out. We have a section of our site with 100 product pages in it (in our case a city with hotels that we've reviewed), and we have a single page where we list them all out--an "all products" page called "all.html." However, because we have 100 and that's a lot for a user to see at once, we plan to first show only 50 on "all.html." When the user scrolls down to the bottom, we use AJAX to place another 50 on the page (these come from another page called "more.html" and are placed onto "all.html"). So, as you scroll down from the front end, you see "all.html" with 100 listings. We have other listings pages that are sorted and filtered subsets of this list with little or no unique content. Thus, we want to place a canonical on those pages. Question: Should the canonical point to "all.html"? Would spiders get confused, because they see that all.html is only half the listings? Is it dangerous to dynamically place content on a page that's used as a canonical? Is this a non-issue? Thanks, Tom
Intermediate & Advanced SEO | | TomNYC0 -
Pagination, Canonical, Prev & Next
Hello All
Intermediate & Advanced SEO | | Vitalized
I have a question about my Magento setup. I have lots of categories which have many products so the categories paginate. I've seen info about making sure the Canonical tag doesn't simply send Search Engines back to the first page meaning the paginated pages won't get indexed. I've also seen info about using the rel=next & rel=prev to help Search Engines understand the category pages are paginated... Is it okay to use both? I've made sure that: category/?p=1 has a canonical of category/ to make sure there isn't duplicate content. Here's an example of category/?p=2 meta data:
http://website.com/category/?p=2" />
http://website.com/category/" />
http://website.com/category/?p=3" />0 -
Adding rel=next / prev to pagination that uses Ajax?
Hi I have just been informed that I should be using the rel=next / rel=prev markup on my category pages and search results pages that use pagination. How do i add these in? Is it just the simple case of adding rel=next in the<a href="" for="" item="" in="" the="" pagination?<="" p=""></a> <a href="" for="" item="" in="" the="" pagination?<="" p="">Also does this work if your are using AJAX - on page load it displays the search / category pages then uses AJAX for additional pages so there is no page refresh</a> <a href="" for="" item="" in="" the="" pagination?<="" p="">Many Thanks</a>
Intermediate & Advanced SEO | | ocelot0 -
301 - should I redirect entire domain or page for page?
Hi, We recently enabled a 301 on our domain from our old website to our new website. On the advice of fellow mozzer's we copied the old site exactly to the new domain, then did the 301 so that the sites are identical. Question is, should we be doing the 301 as a whole domain redirect, i.e. www.oldsite.com is now > www.newsite.com, or individually setting each page, i.e. www.oldsite.com/page1 is now www.newsite.com/page1 etc for each page in our site? Remembering that both old and new sites (for now) are identical copies. Also we set the 301 about 5 days ago and have verified its working but haven't seen a single change in rank either from the old site or new - is this because Google hasn't likely re-indexed yet? Thanks, Anthony
Intermediate & Advanced SEO | | Grenadi0 -
Pagination with rel=“next” and rel=“prev”
Hey mozzers Would be interested to know if anyone has used the rel=“next” and rel=“prev” attributes more info here http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html If you have used it, has it worked and what are your thoughts etc:? And for those that have used it, is it a better way of handling pagination other than the obvious of Google saying so. Thanks
Intermediate & Advanced SEO | | CraigAddyman0