+1 looking for an update on this. Any news?
@emmanuel @josh can you guys answer here please?
This is a major issue, brought up multiple times around the forums with no answers from the Bubble team. It’s a huge blocker for anyone who wants to build SEO-friendly sites.
I’m sharing this with the team to see what we can do and when
Awesome, thanks.
If you go to your app settings > SEO / metatags, then you can enable this setting. Once you’ve done that, you can select text elements and specify if they’re h1, h2, h3, etc.
Done long ago @johnny. The issue is that the tags aren’t picked up by indexing bots, even though they appear there.
That, amongst other SEO issues which seemingly haven’t got a response.
The team is investigating how big of a change that is to our page generation engine.
What makes you say that?.. how do you know that’s the case?
Test on any of the SEO tools available - you get a bunch of errors saying your pages have no heading tags.
Additionally, if you look at the HTML of the page, if you apply any bbCode style markup to text, it gets wrapped in a div (not a span), which is another potential SEO issue.
Test on any of the SEO tools available - you get a bunch of errors saying your pages have no heading tags.
We regularly check our websites with various SEO tools, and our H tags always show up (and are ranked by Google just fine)…
Which SEO tools are you using? - it’s well known (and discussed on this forum, including in this thread) that some of the Free SEO tools don’t pick up H tags correctly, they just read the page source code… you can assume that Google is a lot more sophisticated than those cheap/free SEO checkers…
Additionally, if you look at the HTML of the page, if you apply any bbCode style markup to text, it gets wrapped in a div (not a span), which is another potential SEO issue.
In what sense is it an issue - what makes you say that? (Pretty much every website I’ve ever seen has their H1 tags inside a div?)
Ahrefs. Which I would say is a pretty reputable SEO tool, no?
And the div wrapping is the way around. If you look at the source code (as mentioned), the structure is
h1 → div → text… → /div → /h1
which is definitely not standard.
Ahrefs. Which I would say is a pretty reputable SEO tool, no?
Ahrefs is a great tool, but (evidently) it only checks the initial page html for H tags (not the processed DOM)…
the structure is
h1 → div → text… → /div → /h1
which is definitely not standard.
Ah yes, I see what you’re saying… (I forgot you were adding BBCode)…
I don’t know why it does that… so aside from avoiding using BBcode in your H tags (is there a reason you are?), I guess only Bubble can answer that question…
Ahrefs. Which I would say is a pretty reputable SEO tool, no?
Ahrefs is a great tool, but (evidently) it only checks the initial page html for H tags (not the processed DOM)…
UPDATE On The Above: actually the default setting in Ahrefs is not to execute JavaScript when when doing crawl analysis… so it will only check the initial HTML (hence why your H1 tags are not picked up)…
If you want it to execute JavaScript when crawling (which you do) there is a setting to do just that… so just turn it on then do another crawl analysis and your H 1 tags should show up (mine certainly do).
Looks like no SEO improvements were implemented by Bubble on the rendering of the page it seems.
2 years on, this is still a problem.