Skip to content

How to Add Read More Button in Blog Posts in WordPress? (Load More Button)

Key Takeaways

  • Nexter Blocks 5.0.6 muestra que activar Show Button en Post Listing no añade ningĂşn botĂłn en la página publicada, aunque el ajuste se guarda en el editor.
  • Post Listing mantiene el tĂ­tulo como enlace al post, pero no genera ningĂşn botĂłn, texto de botĂłn ni marcado de enlace en el front end.
  • data-dypost concentra toda la configuraciĂłn de la consulta del bloque en la página publicada, asĂ­ que ahĂ­ es donde se revisa cuando un ajuste no hace lo esperado.
  • Custom loop skin es la forma actual de añadir un botĂłn real y funcional a cada tarjeta, porque el botĂłn del bloque gratuito no se renderiza en ninguna disposiciĂłn.
Table of Contents

A card whose title happens to be a link works, but only for people who think to click a heading. A read more button is meant to make the action explicit.

The setting exists in the block sidebar and can be switched on and configured, but measured on a real published page it produces no button. This doc shows the setting and the actual (button-less) result, so you don’t spend time chasing a missing button that isn’t a configuration mistake on your part.

Before You Start

  • Edition: Free — works in Nexter Blocks (free) and with Nexter Blocks Pro.
  • Block to enable: Post Listing, switched on under Nexter > Blocks in your WordPress dashboard.
  • Enough posts to see the effect. A listing with three posts cannot show pagination, filtering or a second row.

Steps

  1. Select your Post Listing block, open Content Listing → Select Style, and switch Show Button on.
Enabling the Show Button setting
  1. Set its text.
Setting the button text
  1. Publish and check the real page.
The published listing

How It Behaves

Measured on Nexter Blocks 5.0.6: switching this setting on does not add a button to the front end. ShowButton, the button text, and the icon setting are all present in the editor and saved as block attributes, but the block’s render code never uses them to output anything — no link, no button markup, no button text appears on a published page, with any combination of settings. This has been reported to the dev team as a defect; the text below describes what the setting currently does, not what the label implies it should do.

  • The toggle and text field both work in the editor and save correctly, so this is not a matter of the setting failing to save.
  • No output ever reaches the front end. The card looks identical whether the setting is on or off.
  • The title remains a link to the post regardless, so readers can still click through — there is just no second, explicit button.
  • Everything ends up in one attribute. The block writes its whole query configuration into a data-dypost attribute on the published page, so if a setting is not doing what you expect, that is where to look.
  • Measured with Nexter Blocks Pro deactivated: the listing still renders its posts. The block itself is free.

Limitations

  • The button does not currently render on the front end, on any layout, in this version of the free block. Do not rely on this setting for a launch.
  • If a future update fixes this, the same limitations that apply to a generic button label would still apply: one shared text across every card, and no per-post wording.
  • A custom loop skin is the current way to add a real, working button to each card — see create a custom loop skin.

Troubleshooting

The button does not appear even though the setting is on

This is expected right now, not a configuration error on your part. The setting is saved but the free Post Listing block does not currently render a button from it, measured on 5.0.6. Use a custom loop skin (create a custom loop skin) if you need a working button today.

I want different text per post

Not relevant until the setting itself renders anything, but for the record: this would not be possible from the block either way, since the label is a single setting. A custom loop skin is the route.

Will this be fixed?

Reported to the dev team with the exact attributes involved. Check the changelog for the block after an update if you need this feature.

Related Docs

Share your Thoughts

Still in Doubt? Let’s Assist You

Have Feedback or Questions?

Join our WordPress Community on Facebook!

Related Frequently Asked Questions

Why doesn’t the Read More button show up on my blog posts even when the setting is enabled?

That behavior is expected in this version of Nexter Blocks. The Post Listing block saves the Show Button, button text, and icon settings in the editor, but the front end does not render any button markup on a published page. In Nexter Blocks 5.0.6, the card looks the same whether the toggle is on or off, so this is a rendering issue rather than a save problem.

What do I need before trying to add a read more button in WordPress blog posts?

The setup depends on the free Post Listing block in Nexter Blocks, with the block enabled under Nexter > Blocks in your WordPress dashboard. You also need enough posts to see how the listing behaves, because a listing with three posts cannot show pagination, filtering, or a second row. That matters if you are testing layout changes and expecting more than one visible row.

Is there a working way to add a real button to each blog card?

A custom loop skin is the current way to get an actual working button on each card. The built-in Show Button setting saves correctly, but it does not output anything on the front end in this version. If you need a visible call to action today, create a custom loop skin instead of relying on the block’s button toggle.

Can I use different read more text for each post?

That is not possible with this block setting because the label is stored as one shared value for every card. Even if the feature starts rendering later, it would still apply one text string across all posts rather than per-post wording. For post-specific labels, a custom loop skin is the route because it gives you control at the card level.

Does turning on Show Button change how the post cards look on the front end?

In this version, no visual change appears on the published page. The title still links to the post, but there is no second explicit button, no link markup for a button, and no button text rendered anywhere on the card. That means readers can still click through from the title, but they do not get an extra call-to-action element.

Will Nexter Blocks fix the missing read more button later?

The issue has already been reported to the dev team with the exact attributes involved. The practical move is to watch the changelog after an update if you need this feature for production use. Until then, treat the current Show Button setting as non-functional on the front end and use a custom loop skin if you need a working button now.

Last reviewed: September 27, 2026

Related Docs