Hi there,
I have the Yoast plugin installed and it should add automatically rel=”next” and rel=”prev” to the pagination links. It should also change the canonicals of pages. For example trendblog.net/page/2/ should have the canonical trendblog.net/page/2/. However, this is not working and Yoast suggests that it might be a conflict with the theme.
I wanted to check if you or anyone has encountered this issue and if there’s a fix.
Here’s some info from the Yoast Page:
https://kb.yoast.com/kb/is-the-plugin-compatible-with-paginated-content/
Thanks
Normally you should never have /page/2 from your home page as a home page is supposed to be a ‘single entity’ leading to other pages and categories, posts, pages, author bio, etc.
sitenameXXX/page/2 (no!)
Only page 2 from a post or index.
e.g.,
sitenameXXX/business-news/page/2/ (yes!)
Thanks for getting back to me.
Problem is then with the pagination offered by the Newsmag theme itself. On the front page there is a list of the latest posts including pagination.
See: http://trendblog.net
navigating to, for example, the next page leads to trendblog.net/page/2/
is there a way to customize that? One better option in my opinion would be a “see more” button which loads let’s say 10 more post excerpts at the bottom.
Thanks
Here’s a posting which exactly describes the same issue I am having:
https://github.com/Yoast/wordpress-seo/issues/437
Okay after researching some more I figured out what the issue is we’re having – and I’m sure that a lot of other people with the theme have as well.
We have a static front page with pagination (trendblog.net). WordPress and Yoast think it’s a static page and therefore we have a pagination problem with missing rel=”next” und rel=”prev” in the head.
We also have problems with canonicals. So on trendblog.net/page/2/ the canonical is shown as trendblog.net although it should show trendblog.net/page/2/. This is because WP and Yoast think it’s static and set the canonical to that static URL (trendblog.net).
I came across one potential reason, which might have to do with visual composer, which creates the pagination kind of “on the fly” AFTER the important section in the head which determines if the page is purely static or has pagination. Therefore Yoast thinks it’s just a static page.
Don’t know if this hypothesis is correct, but it clearly an issue nevertheless.
This pagination and canonical issue is bad SEO practice according to Google.
Can you please have a closer look at this since it probably impacts other users of Newsmag who have pagination on their front page.
Thanks
-
This reply was modified 8 years by
3pixelkindr.
Well again, pagination of home page is bad practice. You should link to categories at bottom to rwad more, or have ajax loading more posts, not paginated home page. My two cents anyway, but i dont work here. We never build a site with paginated home pages, nor do most.
Hey Chris,
thanks for your feedback and your advice. We are looking into other options like the one you suggested.
However, we still need a fix for our current issue.
By the way, we also had a look at other sites to check whether we’re the only ones using pagination on our homepage. Sites like searchenginejournal or the kissmetrics blog do it as well (with correct canonicals and rel next/prev). Doesn’t mean you’re wrong. Just wanted to point out some examples.
Hi,
you are correct if doing a ‘blog’ format, then it is one way to go. Very odd that Yoast isn’t working properly for you in that context.
For most magazines and newspapers, a front page is just that, it cannot have a ‘second front page’ or ’25th front page’ either, which was my basis for commenting.
Didn’t mean to imply you were doing it wrong in having a blog format for website, where front page is just essentially ‘page one of our index’ … and not a ‘true front page’ in the classic sense.
Since the issue is with Yoast SEO — theme doesn’t control that kind of canonical meta data, seems better to spend more time on the Yoast forum, and if you have Yoast PRO version put in direct support ticket.
But I don’t work here, so it was just some feedback as with classic blog indexing, you’re fighting your category indexes by doing that unless you also have all the home page 2+ as noindex, which I’m assuming you do. Yoast can manage that too obviously.
Sorry to butt in without helping with an actual solution! 🙂
Hey again,
could someone from the tagdiv team please have a look at our issue? We really need your support here.
Thanks
Hello 3pixelkindr,
I have inspected your website and I saw that your pagination works as expected. I saw that you are using the Pagebuilder+Latest Articles+Pagination as page template. So, if you want to have another pagination style, like Load More, you should simply switch to another page template, like, page template default and then, use a Block setup with Load More pagination, like this -> https://www.screencast.com/t/Dwx7b151X4 and then you will have Load More pagination, as you want.
If is not what you mean, please provide more details so I will be able to provide a more accurate response.
Hope this helps!
Thanks for the message!
Also the other news button and the related news pagination not working.
https://www.screencast.com/t/hVmoO8iNmmj
Hello sector,
I have inspected your source page and I saw that you are using a minified version of it and also, it seems that you are using some untested plugins which can interact with the theme core files and causes a lot of unknown issues.
Thanks for the message!
Hi Catalin,
i tested the plug in after u say. and now i figure out.
The problem is due to Autoptimize plugin (https://automattic.com/wordpress-plugins/).
i disabled to JavaScript option, everything is okey now i think.
But the other issue is when i click the next page, the screen throws me and the bottom of the page (not top of the page).
Hello sector,
Unfortunately, please notice that is not a natural theme’s behavior. Check again your plugin’s list and your customizations because all of these may be the main reasons for these errors, sorry! Also, if the problem is still there, try to make a new clean install from scratch via FTP way and check the results.
Thanks for the message!