Whats the best way to implement rel = “next/prev” if we have filters?
-
Hi everyone,
The filtered view results in paginated content and has different urls: example: https://modli.co/dresses.html?category=45&price=13%2C71&size=25
Look at what it says in search engine land: http://searchengineland.com/implementing-pagination-attributes-correctly-for-google-114970
Look at Advanced Techniques paragraph. do you agree? it seem like google will index the page multiple times for every filter variant.
Thanks,
Yehoshua
-
Just be sure that I understand what you're saying:
On pages like https://modli.co/dresses/elegant.html & https://modli.co/dresses.html you want to use rel next/rel previous.
On pages like https://modli.co/dresses.html?category=43&size=25 you plan to use a canonical to https://modli.co/dresses.html
Seem like a good strategy - the only minus is that you would not have a corresponding landing page for somebody looking for "red dress" (page exist on site but points to the generic dresses page). Not sure if these type of queries represent a search volume & if they would be important for your business.
rgds,
Dirk
PS You should check the H1 you use on your pages - on https://modli.co/dresses/elegant.html the H1 is "Elegant" - would be much better if it would be "Elegant dresses"
-
Hi Dirk,
I do not won't this pages to be accessible since then we will have lots of duplicate content.
Before i added canonical tags to all the category pages, lots of them where indexed by google (i have no clue way). Therefor we added the canonical.
What do you think of the following:
On all filtered pages have canonical tags to the main category page (the first one)
and category pages without filters have rel = “next/prev”.
what do you think?
Thanks,
Yehoshua
-
Hi,
You might want to check this article of Google on facetted navigation: http://googlewebmastercentral.blogspot.be/2014/02/faceted-navigation-best-and-5-of-worst.html
In your current set-up - Google isn't indexing pages of type https://modli.co/dresses.html?category=45&price=13%2C71&size=25 as these pages are only accessible using javascript (you can check this by crawling the site by using Screaming Frog or just using site:modli.co in Google) - so adding the rel next/previous will not change a lot for these pages.
If you want to make this pages accessible you will have to
- make this pages accessible using HTML links rather than js
- rewrite the parameters in your url's to make them more understandable for Search engines (https://modli.co/dresses.html?category=42 should become https://modli.co/dresses.html?category=elegant)
- use rel next/previous if pages are spread over multiple pages
- use canonical url's to eliminate parameters irrelevant for search (like size, price,...)
- eliminate potential duplicate content issues: both https://modli.co/dresses.html?category=42 & https://modli.co/dresses/elegant.html are showing elegant dresses
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
-
Is rel=prev/next necessary for ecommerce?
We are currently not using rel=prev/next for paginated categories. My predecessor instead canonicaled paginated pages back to the parent. This obviously needs to be fixed. The pages should self-canonical. Is using the parameter handling function of Google Search Console enough, or do we need to have our dev team implement rel=prev/next?
Intermediate & Advanced SEO | | Satans_Apprentice0 -
What’s the best way to handle multiple website languages in terms of metatags that should be used and pages sent on our sitemap?
Hey everyone, Has anyone here worked with SEO + website translations? When should we use canonical or alternate tag if we want the user to find our page on the language he used on Google? Should we send all pages on all the different locales on the sitemap? Looking forward to hearing from you! Thanks!
Intermediate & Advanced SEO | | allanformigoni0 -
Duplicate/ <title>element too long issues</title>
I have a "duplicate <title>"/"<title> element too long" issue with thousands of pages. In the future I would like to automate these in a way that keeps them from being duplicated AND too long. The solution I came up with was to standardize these monthly posts with a similar, shorter, <title>, but then differentiate by adding the month and the year of the post at the end of each <title>. Hundreds of these come out every week, so it is hard to sit there and come up with a unique <title> every time. With this solution the <title> tags would undoubtedly be short enough, however my primary concern is, would simply adding the month and year at the end of each <title> be enough for Google/Moz to decide it is not a duplicate? How much variation is enough for it not to be deemed a duplicate <title>? </p></title>
Intermediate & Advanced SEO | | Brian_Dowd0 -
I've got duplicate pages. For example, blog/page/2 is the same as author/admin/page/2\. Is this something I should just ignore, or should I create the author/admin/page2 and then 301 redirect?
I'm going through the crawl report and it says I've got duplicate pages. For example, blog/page/2 is the same as author/admin/page/2/ Now, the author/admin/page/2 I can't even find in WordPress, but it is the same thing as blog/page/2 nonetheless. Is this something I should just ignore, or should I create the author/admin/page2 and then 301 redirect it to blog/page/2?
Intermediate & Advanced SEO | | shift-inc0 -
Keyword Targeting / Cannibalisation
Hi Guys We're about to launch a very large website for a flooring company and would like to find out more about _key word _cannibalisation - to put my mind at rest. I know Rand posted a Whiteboard Friday early last year about this topic and mentioned using part of the same keyword was ok to use. All our keywords are specifically geared for "user intent" meaning each keyword has relevance and the content to back up the keyword. We've ensured the keywords are located within each url, placed at the start of the page title, h1 etc.
Intermediate & Advanced SEO | | GaryVictory1 -
Best practices with reoccurring event listings
On our client's events page there are a few reoccurring events that each have their own detail page. I'm trying to figure out what's the best practice for minimising duplicate content. For example, for the Bribie Island Markets that repeat weekly there are 2 (+more) detailed event pages: http://www.ourbribie.com/e/bribie-island-markets/1869/2013-12-07/2013-12-07
Intermediate & Advanced SEO | | michaelp85
http://www.ourbribie.com/e/bribie-island-markets/1869/2013-12-14/2013-12-14 While they both contain duplicated content, they're unique in that they display the specific events date/time. My thinking is that the future events (e.g. 2013-12-14) should have a canonical link to the upcoming/next event (i.e. 2013-12-07). However this would require constantly updating/changing the canonical links. What's the best way to deal with this from a duplicate content prospective? Any better recommendations?0 -
Regular Expressions for Filtering BOT Traffic?
I've set up a filter to remove bot traffic from Analytics. I relied on regular expressions posted in an article that eliminates what appears to be most of them. However, there are other bots I would like to filter but I'm having a hard time determining the regular expressions for them. How do I determine what the regular expression is for additional bots so I can apply them to the filter? I read an Analytics "how to" but its over my head and I'm hoping for some "dumbed down" guidance. 🙂
Intermediate & Advanced SEO | | AWCthreads1 -
Pagination Question: Google's 'rel=prev & rel=next' vs Javascript Re-fresh
We currently have all content on one URL and use # and Javascript refresh to paginate pages, and we are wondering if we transition to the Google's recommended pagination if we will see an improvement in traffic. Has anyone gone though a similar transition? What was the result? Did you see an improvement in traffic?
Intermediate & Advanced SEO | | nicole.healthline0