VBulletin Pagination
-
I've been looking for quite some time for a way of incorperating rel=next/rel=prev into my vBulletin forum however I've had no joy.
I want to try and consolidate my ranking as I have a very large amount of user generated content, but not enough links.
Any help would be most appreciated.
P.S - I have the vbSEO software and as far as I can see, there's no way of doing it through here.
-
Just wanted to bump this in case anyone had any ideas? Feel like we're missing a trick by not having good pagination on our forum. Have been unable to find any way of adding this.
-
If anyone has any ideas for this, would be most appreciated. Thanks.
-
Yep, have voted here but doesn't look like it's planned so hoping there was a way to add it manually.
Thanks.
-
It's beyond editing template files.. did you vote for it, here:
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
-
Why is pagination SEO such a mystery in 2021?
Hi folks. I would like to discuss pagination. I use WordPress (Genesis, specifically). I ran my site through a site scan and it flagged an error which told me that my blog was producing duplicate meta descriptions because the blog is paginated - the same meta description from the blog page is being used on Page 2, Page 3 etc. I looked into this and the Internet is awash with many other people scratching around for a solution. My understanding is that using a canonical link on the first page is not a good idea, because it says to Google that only Page 1 of the blog is important. I also read an article that states Google no longer reads the Rel=Prev/Next code that could be used to tell Google to ignore the issue. So, what's the solution? Do I even need one? As a side-thought, it seems to me that pagination is, well, pretty useless. I mean, if my blog has 20 pages and I've worked hard to create content, who is going to click through to anywhere near page 20? Nobody. There has to be a smarter way for people on-site to access content. I would love your thoughts on all of this. Cheers.
Intermediate & Advanced SEO | | Nobody16165422281340 -
Pagination & Canonicals
Hi I've been looking at how we paginate our product pages & have a quick question on canonicals. Is this the right way to display.. Or should the canonical point to the main page http://www.key.co.uk/en/key/euro-containers-stacking-containers, so Google doesn't pick up duplicate meta information? Thanks!
Intermediate & Advanced SEO | | BeckyKey0 -
E-Commerce Mobile Pagination Dillema
Hi Everybody, I'm managing the SEO for an E-commerce site with different desktop and mobile sites (meaning, not responsive). We're changing the way reviews on mobile product pages will be displayed from 'view all' to pagination (due to server load). Basically the above the fold part of the page will always display the product, and below the fold will have x numbers of reviews on each page. But here is where it gets tricky: 1 - A different number of review pages will exist on mobile vs desktop (due to different no. of reviews per page on each device) - so I'm wondering what's the solution regarding canonicals. Usually every mobile page points to its desktop parallel, but now we'll have non-matching pages. 2 - The users will be able to change the no. of reviews displayed on each page. So the number of paginated pages will change accordingly. I was thinking about a solution where all the reviews will be in the first page's html (and only X of them will be displayed on screen), and all the other paginated pages will be created dynamically (with # and won't be indexed, so basically no pagination in mobile). Does anyone think this can be seen as cloaking or has any other thoughts? Thanks, Sarah
Intermediate & Advanced SEO | | Don340 -
Rel=Alternate on Paginated Pages
I've a question about setting up the rel=alternate & rel=canonical tags between desktop and a dedicated mobile site in specific regards to paginated pages. On the desktop and mobile site, all paginated pages have the rel=canonical set towards a single URL as per usual. On the desktop site though, should the rel=alternate be to the relevant paginated page on the mobile site (ie a different rel=alternate on every paginated page) or to a single URL just as it is vice versa. Cheers chaps.
Intermediate & Advanced SEO | | eventurerob1 -
Hreflang and paginated page
Hi, I can not seem to find good documentation about the use of hreflang and paginated page when using rel=next , rel=prev
Intermediate & Advanced SEO | | TjeerdvZ
Does any know where to find decent documentatio?, I could only find documentation about pagination and hreflang when using canonicals on the paginated page. I have doubts on what is the best option: The way tripadvisor does it:
http://www.tripadvisor.nl/Hotels-g187139-oa390-Corsica-Hotels.html
Each paginated page is referring to it's hreflang paginated page, for example: So should the hreflang refer to the pagined specific page or should it refer to the "1st" page? in this case:
http://www.tripadvisor.nl/Hotels-g187139-Corsica-Hotels.html Looking foward to your suggestions.0 -
Dilemma: Should we use pagination or 'Load More' Function
In the interest of pleasing Google with their recent updates and clamping down on duplicate content and giving a higher preference to pages with rich data, we had a tiny dilemma that might help others too. We have a directory like site, very similar to Tripadvisor or Yelp, would it be best to: A) have paginated content with almost 40 pages deep of data < OR > B) display 20 results per page and at the bottom have "Load More" function which would feed more data only once its clicked. The problem we are having now is that deep pages are getting indexed and its doing us no good, most of the juice and page value is on the 1st one, not the inner pages. Wondering what are the schools of thought on this one. Thanks
Intermediate & Advanced SEO | | danialniazi0 -
Canonical VS Rel=Next & Rel=Prev for Paginated Pages
I run an ecommerce site that paginates product pages within Categories/Sub-Categories. Currently, products are not displayed in multiple categories but this will most likely happen as time goes on (in Clearance and Manufacturer Categories). I am unclear as to the proper implementation of Canonical tags and Rel=Next & Rel=Prev tags on paginated pages. I do not have a View All page to use as the Canonical URL so that is not an option. I want to avoid duplicate content issues down the road when products are displayed in multiple categories of the site and have Search Engines index paginated pages. My question is, should I use the Rel=Next & Rel=Prev tags on paginated pages as well as using Page One as the Canonical URL? Also, should I implement the Canonical tag on pages that are not yet paginated (only one page)?
Intermediate & Advanced SEO | | mj7750 -
Implementing Canonicals on Existing ASP Ecommerce Store with Pagination
So I have a store which has been around for a while and is custom built on ASP.net. Store has thousands of sku's and at least a few hundred subcategories. Have been tackling a bunch of the onsite issues and for categories which have more than 6 products in them, there are multiple pages and a view all present. Example.com/category example.com/category?PageIndex=2 example.com/category?PageIndex=3 example.com/category?PageIndex=4 example.com/category?viewall=True As well as the following for every page example.com/category?PageIndex=2&viewall=True So I know how I wish to handle the pagination/canoncial issue as per google's suggestions you do it to the view all or they have the rel=next/prev. But my question is google says if view all is present they should already do a good job at ranking the view all version. Well in the rankings, there are a lot of page1 variations showing. So once this is implementated, is it safe to assume that I will see a drop? Feel like if it was a brand new site it is easy but for something this old and established, it could cause some decent harm which at the current time we are already tackling a massive list of issues which in the long haul will improve it. Looking for some insight for someone who has dealt with ASP.net and this specific area. thanks
Intermediate & Advanced SEO | | Sean_Dawes
Sean0