-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
next and prev rel links in head #685
Comments
Had a couple of requests for this + links to "prev" and "next" posts within the #post context (rather than archive context) recently. A couple from people who we would really like to deliver this to sooner rather than later to get/keep them on Ghost. What's the current status of this @cobbspur // overall progress for prev/next links @ErisDS ? |
There is an open pull request #1545 but we decided it was important to performance test this before merging it. I can try to get someone to do this sooner rather than later & also investigate to see if there are possible improvements to the approach given that bookshelf/knex are always evolving. |
This is especially important in the current search landscape for engines to be able to understand series of pages. +1 |
+1 |
closes TryGhost#685 - Now that we have a ‘pagination’ meta object, we can implement SEO-friendly `next` and `prev` ref links in `<head>`. - This implementation works uniformly for anything that supports pagination in the current schema (posts, tags, authors) - Regex should make the implementation future-proof for additional pagination
As per the links at the bottom of this post, we need to add next and prev
<link>
tags to the head section of Ghost to indicate the next and previous page in the paged archives.Need to figure out the best way to wire up the contenxt and output with
{{ghost_head}}
.. prob using filters. Probably need to move the concept of what the prev/next URL is back from the pageUrl helper back to the controller, so that we can do this.The text was updated successfully, but these errors were encountered: