Hi,
Same concern here if saved text with html characters will not be fetched by the SEO activities, and if there is any other place where the stylized text (html characters) displayed than through the Rick text plugins on the Bubble?
Thanks!
1 Like
Greetings,
I am unsure if I have correctly grasped the essence of your inquiry.
Generally speaking, the output of this plugin is presented on the page using HTML tags that correspond to the text formatting. The data storage method employed by this plugin (Delta) should not adversely affect SEO, as it is simply the coding utilized by Quill to save content.
Should you have any further inquiries or concerns, please do not hesitate to reach out to us. We are here to assist you.
1 Like
Okay @NoCodeDataArtisan, I see half way through what you mean in regards to my thought question.
Here is one practical example:
When a text is saved to a data base with html stylizing characters, it looks something like this:
<h1>This is the biggest one</h1>
<h2>This one is a little smaller</h2>
<h3>This one is even smaller</h3>
<h4>They keep getting smaller</h4>
<h5>This one isn't even that big</h5>
<h6>Pretty small now, actually</h6>
And than if we want to read from the data by using the plugin, it would be something like this:
This is the biggest one
This one is a little smaller
This one is even smaller
They keep getting smaller
This one isn't even that big
Pretty small now, actually
Question is now, if those html characters will go to the SEO or other places as well, rather than just being in the database and being read by the plugin, or they will be fetched by a Google crawler and create a bad UX outside it’s purpose linked with the plugin.
Hope this helps to see my concern here in the first place.
Thanks! Looking forward!
1 Like
Thank you for the more detailed explanation of your concern. I understand your question better now. 
Regarding SEO, how your data is read and indexed by search engines like Google depends largely on how it is rendered on the front-end. When search engine crawlers scan your website, they will read the HTML that is generated by your site’s front-end code.
If the HTML tags are rendered correctly on the page (meaning, the actual headers appear as headers, and not just plain text), then they will be indexed as such by the search engines, contributing to your site’s SEO.
If, however, the plugin is stripping away the HTML tags and only presenting the plain text, then that’s what search engines will index. They wouldn’t know that
This is the biggest one
was intended to be a header, because all they see is “This is the biggest one” as plain text.Now, when it comes to the user experience, HTML tags shouldn’t inherently create a bad UX unless they are being displayed to users where they shouldn’t be. If they are being rendered correctly on the page, the users will only see the formatted text, not the HTML tags. If users are seeing raw HTML, then that’s a UX problem that needs to be addressed.
Please let me know if you have further questions or if anything is unclear.
I’m here to help!
1 Like
Oh, thank you! This answers my question. I was assuming for SEO and crawler to actually work with the backend data, as I was seeing also some SEO keywords and concepts I guess that refer to the backend as well, but now it makes sense. Thanks again! 
1 Like
You’re welcome! I’m happy to hear that your questions were answered. 
If you need any more assistance in the future, feel free to reach out.
Best,
@NoCodeDataArtisan
1 Like
Hey @rod.danan ,
In response to your request, we understand that you intend to utilize a shared editor for several sections, with changes occurring based on user tab changes.
We have begun to implement this feature. However, we found that it’s best if you handle this task yourself. If we enable this feature for you, there’s a risk of losing your current content. But if you take care of it, you can save your current content before setting up the “new content” in the editor.
Keep in mind that this feature might cause some issues for you and other users of the plugin, which could lead to disruptions. We recommend triggering a workflow with each tab change. Start by saving the content of the editor in the previous tab, and then use ‘set content’ to apply the content you want in the editor.
We also made some tweaks to the placeholder settings. Now you can personalize it to a normal style and change the text conditionally, based on your needs.
If I’ve misunderstood what you’re looking for, just let me know and give me some more details. This will help me better understand what you need and make sure we’re on the same page. Your feedback is super important to us, and it helps us improve our services.
Sorry we couldn’t directly provide the solution you had in mind. We want to make sure that other users of the plugin don’t run into any problems. Thanks for understanding!
Looking forward to hearing from you.
So I am trying to use the “Set content” but it throws an error. I see in the action, it says to pass in “Delta” but I save contents from my editor as HTML. What do you recommend?
EDIT: Also, looks like the content comes out as italics for some reason by default. When highlighting any text and clicking the italic button, nothing happens so it can’t be turned off.
EDIT 2: Changing the placeholder style from italic to regular fixed the issue. Looks like a bug here.
1 Like
We sincerely apologize for the oversight regarding the absence of HTML in the action. It will be promptly added.
We appreciate you bringing this to our attention and acknowledge that the styles have merged. We are grateful for your feedback.
Rest assured, we will rectify both issues at the earliest opportunity.
Once again, please accept our apologies for any inconvenience caused.
Hello! Thank you for this amazing plug-in, it’s so much better than the other RTEs, I’m very grateful to you for creating it.
I just have one minor bug, which is that if I set the height to be variable, scaling to the content, then when there is no or just a small amount of text, the bottom of the element seems to continuously alternate by 1-2 pixels of height, which causes the rest of the page below it to shake slightly.
I’m using a custom toolbar. In the screenshot there is an initial content set but the same bug happens without any initial content.
Thank you in advance!
2 Likes
Hello! @lucarade
I’m glad to hear that you’re enjoying Quill and find it better than other Rich Text Editors. Thank you for your kind words.
Regarding the minor bug you mentioned, I apologize for the inconvenience it’s causing. To better understand the issue, could you kindly provide more information? It would be helpful if you could make a GIF or video demonstrating the problem. That way, I can visualize the behavior you’re experiencing and provide you with a more accurate solution.
Additionally, have you tried setting a minimum height for the element? Sometimes, setting a minimum height can help stabilize the layout and prevent the shaking effect you mentioned when there is minimal or no text.
I’ll be happy to assist you further once I have more details or visual representation of the bug. Thank you for reaching out, and I’ll do my best to help you resolve this issue with Quill!
Same thing happened to me. I had a minimum and maximum height and checked the “Fit height to content”. It was shaking like you mentioned adding pixels at the bottom. Once I turned off fit to height, that stopped.
1 Like
Hello @NoCodeDataArtisan, thank you for the quick response. Yes, I have a minimum height set, the issue still occurs.
Here is a video of the shaking:
1 Like
Hi, would it be possible for you to send us the link to this page so we can check it out?
I apologize for this problem, we will fix it as soon as possible.
I can’t show the original pages because I can’t have the bug there with users, but I made a clone page with the bug:
1 Like
Hi @lucarade
Thanks for reaching out and providing us with a clone page to investigate the issue you’re experiencing. We’ve been actively checking and testing the provided page but were unable to replicate the bug you’ve mentioned.
Could you provide some more details to help us isolate the issue? Specifically, is this a bug that only occurs under certain conditions or specific situations? Knowing this would help our investigation and ensure a faster resolution to your problem.
Thank you in advance for your cooperation. We’re looking forward to hearing from you soon to further assist you!
It seems to depend on screen resolution.
The bug occurs in both Chrome and Edge on my laptop at 1920x1080 resolution. It occurs regardless of the window size.
When I switch to 1600x900, it no longer occurs.
It does not occur on my iPhone using Safari.
1 Like
Thank you so much for informing us about this. @lucarade
Your input is highly valuable to us and greatly appreciated.
To ensure we identify the underlying cause, we will conduct a series of thorough tests. Our aim is to pinpoint the root of the problem and implement the necessary solutions to fix it.
Once again, we sincerely appreciate your feedback and assure you that we are dedicated to providing you with the best possible experience.
Has this issue been resolved?
We can’t find it in our tests and the content is correct and accessible via the element’s state.