Fix: Empty state of custom field can cause SEO problem#68699
Fix: Empty state of custom field can cause SEO problem#68699dhananjaykuber wants to merge 1 commit intoWordPress:trunkfrom
Conversation
|
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Hi |
Fixes #66887
What?
Prevents empty heading tags from being rendered in the frontend when using block bindings or when heading content is empty.
Why?
Empty heading tags
(<h1>, <h2>, etc.)can cause SEO issues as they create unnecessary markup in the page structure. This is particularly problematic when using block bindings where the heading content might be dynamically empty. The fix ensures better SEO practices by preventing empty heading tags from being output.How?
Added empty content checks in both:
Testing Instructions