Core Blog and posts
Links to the next and previous post
wp="next-post-link" At the bottom of a post, a way on to its neighbours: readers keep reading without going back to the list. Neighbours are found by publication date.
Where it goes
On <a> links: wp="prev-post-link" for the previous (older) post, wp="next-post-link" for the next one.
On single.html, next to wp="post-title".
Example: navigation under a post
Markup single.html
<main class="post" wp="post">
<h1 wp="post-title">New autumn menu</h1>
<nav class="pager">
<a class="pager__prev" href="#" wp="prev-post-link">Summer cold brew</a>
<a class="pager__next" href="#" wp="next-post-link">Open late on Fridays</a>
</nav>
</main>In the admin Posts
Posts
- Open late on Fridays
- New autumn menu
- Summer cold brew
On the site post page
New autumn menu
← Summer cold brew Open late on Fridays →
The arrows are drawn with styles; the link texts are the neighbours’ titles.
What matters
- The link text is replaced with the neighbouring post’s title.
- The first post has no previous one and the last has no next one: that link is simply not on the page.
- Neighbours are posts of the same type: a blog post’s neighbours are blog posts.
Common mistakes
The build log is the “Logs” tab of your project on themeforge.pro; the free markup check shows the same notes.
Not like this
<a class="pager__next" href="#" wp="next-post-link">Next post →</a>A “Next post →” caption inside the link: on the site the neighbour’s title replaces it. The log stays silent.
Like this
<a class="pager__next" href="#" wp="next-post-link">Open late on Fridays</a>The link holds the title from the design; the arrow or caption comes from styles (::after).
Alternative spelling
wp="next_post_link" works the same: the build gives an identical theme.