Now in style.css in release 3.0.3:

h1 {
font-size: 4rem;
}

h2 {
font-size: 3.2rem;
}

h3 {
font-size: 3.2rem;
}

h4 {
font-size: 2rem;
}

h5 {
font-size: 1.8rem;
}

h6 {
font-size: 1.6rem;
}

It’s a strange problem, but when I try inserting an H3 subheading in the backend editor it disappears. On the front end of the site the H3 does not show.

I have deactivated Stackable and the problem goes away so there must be some kind of conflict. I have left the plugin deactivated now.

All other subheadings work fine.

Here’s a video showing what I’m talking about: https://drive.google.com/file/d/1fzmWv-fg8zJtio6Cnl2IormlgV1_bZpd/view?usp=drivesdk

Note that I am not using the H3 subheading using Stackable, just the standard H3 using Gutenberg.

I have been trying to add ads before my H3 headers. The general layout of my site and where I want to include my ads is:

Header 2

Header 3
Paragraph
Paragraph

Header 3
Paragraph
Paragraph

AD

And then repeat.

I have tried using %2@3 but it only works for the first ad space. The other ad spaces don’t show the ad image but show the code in the Console.

How can I fix this problem?

I enabled remote debugging and disabled caching.

This is the code that I am trying to plug in:

https://privatebin.support-tools.com/?68b2a7162784a92f#3RZZLE7Uy2UY5h+jfHao7mYy78xgFYhU70o+h5Zd1PE=

These are the settings I’m trying to use:

https://privatebin.support-tools.com/?8ad98752da86f237#mdC5r3kAKoRGwdgL0ZpjfcFZMqQ4x8DkvA6DeH8AH3k=

Thanks,

Tatiana

Keyphrase in subheading: More than 75% of your H2 and H3 subheadings reflect the topic of your copy. That’s too much. Don’t over-optimize!

so for checking i have removed 9 subheading & kept 1 to 9 digit for each subheading like . 1, 2, 3 , 4, 5 etc. but still showing More than 75% of your H2 and H3 subheadings reflect the topic of your copy. That’s too much.

I have latest updated yoast seo version

Using this as an example post, featuring Stackable’s ‘Table of Contents’ block: https://www.healabel.com/cabbage-benefits/

You can see it is not pulling the proper H3 title. Instead, it uses my previous H3 titles from several weeks ago that have been updated, saved, date updated, purged, etc.

I’ve tried just about everything I can think of and it’s a mystery why it won’t use my current H3 titles.

I reached out to Stackable support, they redirected me to WP, hence me posting this here…

This is exactly what they said after investigating:

“…After checking your Post, we saw that you are using the native Heading block and not the Stackable Heading block. This means that the HTML Anchor is linked to the native block, so we don’t have control over this. You may need to reach out to the WordPress team regarding this.

However, upon discussing this further with our dev team, we realized that this is actually the correct behavior and that the HTML Anchor should not change because if it does, it may break the link/s on your other existing pages. Perhaps you can clarify this further with the WordPress support team?”

Please help!

Thanks,

Adriane

I am working on the SEO of my website and WooCommerce related products shows themselves as H2. How I can change them into H3?

I saw this topic in the forum and I tried to apply the solution, copying the code with my Code Snippets plug-in, but the plug-in told me that it is disabled because there is an error in the second line of the code: “Cannot redeclarate function woocommerce_template_loop_product_title“.

This is the code I copy:
function woocommerce_template_loop_product_title() { echo ‘<h3 class=”woocommerce-loop-product__title”>’ . get_the_title() . ‘</h3>’; }

I am brand new in WordPress and I use Code Snippet to copy/paste the codes that I need.

Thank you so much for your attention and help

I really like your plugin and it works good with other plugins I use.

Now I encountered a problem to the current accessibility laws in my country.

I need the headline for every custom sidebar to be H1 instead of H3.

I couldn’t find anything that worked.

Screenshots to help visualize what I mean: https://ibb.co/brVnmLN , https://ibb.co/NTdPrGD

Thanks in advance.

Best regards,
Alexandra