Read More and/or Button blocks inside Terms Query template can’t link to term permalink

[g-dom3]

Description

When using the Terms Query block, there doesn’t seem to be a way to use a Read More block or a Button block inside the term template that links to the current term’s permalink.

In a regular Query Loop for posts, the Read More block automatically links to the post permalink (or can be set to “Post link”). Inside a Terms Query → Term Template, the same pattern doesn’t seem possible: the Read More block doesn’t expose a way to use the term permalink, and the Button block also doesn’t have a dynamic “term link” option.

So at the moment I can show Term Name and Term Description, but I can’t add a CTA inside the loop that links to the term archive page.

Step-by-step reproduction instructions

• Start a new site (tested with WordPress Playground).
• Make sure you have some taxonomy terms, e.g. Categories with descriptions.
• Create a new page.
• Add a Terms Query block and configure it to show taxonomy terms (e.g. Categories).
• Inside Term Template, add:
  • Term Name
  • Term Description
  • A Read More block or a Button block for a “Read More” CTA.
• View the page on the front end.

Screenshots, screen recording, code snippet

No response

Environment info

• WordPress 6.9
• Google Chrome

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

• Yes

Please confirm which theme type you used for testing.

• Block
• Classic
• Hybrid (e.g. classic with theme.json)
• Not sure

[GovardhaneNitin]

Hi, I'd like to work on this enhancement.

My current understanding is:

• Inside a Terms Query → Term Template, blocks like Read More and Button don't have access to the current term's permalink, so they can't be used as a CTA that links to the term archive.
• In a regular Query Loop for posts, the Read More block can automatically link to the post permalink (via the "Post link" option).

My proposal is to:

1. Expose the current term context (e.g. term ID / term link) from the Terms Query block to its children.
2. Update the Read More and/or Button block so that, when used inside a Term Template, they offer a dynamic "Term link" option similar to "Post link" in the Query Loop.

Please let me know if this direction aligns with how you'd like this enhancement to work, or if you'd prefer a different UX (for example, a dedicated 'Term Read More' block or another pattern). If it looks good, I'd be happy to start working on a PR.

[g-dom3]

Thanks for the follow-up, @GovardhaneNitin — looping in @youknowriad as well.

I’m not in favour of the proposed approach. I would prefer to keep the contexts clearly separated and/or consistently associated with the two main blocks involved: the Query Loop and the Terms Query.
We already have everything we need, in terms of available APIs and context methods, to properly manage these two different entities.

It’s also possible that we may not even need a dedicated block for this use case, considering that the Term Name block already allows linking the title to the term permalink, which in many design scenarios might be sufficient.

However, my context is slightly different: I need to display the terms of a specific taxonomy, and I require a different front-end structure.

The Read More block appears among the suggested blocks inside the Term Template, but since it is bound to postId rather than termId or taxonomy contexts, it simply outputs an empty string.

if ( ! isset( $block->context['postId'] ) ) { return ''; }

So i'm wondering, is the existing 'Read More' block being surfaced in the wrong context (the Terms Query block), given that it cannot return anything? What would be the best approach here?

I am exploring my proposal in this PR: #73800

Feedback welcome.

[t-hamano]

In my opinion, the easiest way to do would be to extend the Read More block and modify it to link to the term archive when it's in a term query context. With a little tweaking to the server-side rendering code, this should work. Or maybe we could create a variation of the READ MORE block.

cc @ntsekouras @mikachan @cr0ybot

[ntsekouras]

It’s also possible that we may not even need a dedicated block for this use case, considering that the Term Name block already allows linking the title to the term permalink, which in many design scenarios might be sufficient.

I kind of agree here that we might not need a new block for this.

Could adding a button block with block bindings be enough for now and close this issue?

Below is markup for a button inside a Terms Query block that links to each item.

<!-- wp:buttons -->
<div class="wp-block-buttons"><!-- wp:button {"metadata":{"bindings":{"url":{"source":"core/term-data","args":{"field":"link"}}}}} -->
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button">read more</a></div>
<!-- /wp:button --></div>
<!-- /wp:buttons -->

Screen.Recording.2025-12-08.at.1.08.31.PM.mov

[g-dom3]

@ntsekouras Great catch, thanks!

Binding attributes are still a bit of a hidden field to me.

Your solution works on my end; however, I’ll leave it to your consideration whether the “Read More” block should be disabled within the “Term Query” block, given that it currently does not produce any output.

Thanks @t-hamano for joining the discussion.

[ntsekouras]

“Read More” block should be disabled within the “Term Query” block, given that it currently does not produce any output.

This block and many other post blocks wouldn't output anything in a context outside of a post, and I'm not sure we should introduce an API to fine tune this behavior right now.

The Read More description is: Displays the link of a post, page, or any other content-type., which I believe is explanatory enough. That's subjective though, and if you think it needs some kind of copy update, please open an issue about that.

I'm going to close this one for now. Thanks for the issue and the discussions all!