The Block Editor/Gutenberg: Why you should be using it

At Yoast, we truly believe you should be using the Block Editor (formerly known as Gutenberg) in WordPress, simply because it’s a much better experience than the ‘classic editor’. Unfortunately, when we look at our statistics, we see that a large segment of our users still uses the classic editor. This makes us sad, but also makes us want to explain why you really should start switching over.

When we talk about Gutenberg/the Block Editor within the WordPress community, there are always a lot of emotions involved. A large percentage of these emotions were down to the release process of Gutenberg. I have certainly also been critical of that process. But, while that launch could undoubtedly have been handled better, it shouldn’t cloud our judgment of the product. Unfortunately, some of that negativity has spilled into the wider world without the context, and that really is a shame.

In our eyes, it’s simple: the Block Editor is now much better than when it launched. Smashing Magazine did a good post mortem. In their post, they also differentiate between the problematic launching process and its current state. And, they assess it to be very good at the moment. It’s important to note that the Block Editor is still under heavy development within the Gutenberg project. The current version of the Block Editor is much, much better than what it was like a year ago. In fact, I can say it’s very good.

Why you should switch to the Block Editor

The Gutenberg project and with it, the Block Editor is literally where all the innovation in the WordPress space is happening. Think of it this way: the only car race you’re going to win by using old technology, is a classic car race. If you want to win in SEO in the next few years, I guarantee you’ll need to be on the Block Editor. If you’re not, and if some of your competitors are, they’re going to beat you.

While the Block Editor may be very good, you may think: why would I switch? If the classic editor is working for me, so why bother? Well: the Block Editor is only step one in a longer process. More and more parts of the WordPress admin will start using blocks, and because of that, getting familiar with the Block Editor is essential.

Future versions will iterate on what the Block Editor already does, moving to site-wide editing, instead of just the content area. The first required step for that is defining content edit areas, something Matias discussed in this post on Make Core, one of the blogs of the core WordPress development team. That post by Matias prompted this post by Justin Tadlock on how the Gutenberg project is shaping the future of WordPress themes. This is getting me, and our entire team at Yoast, very excited.

The Gutenberg project aims at making WordPress easier to use. That’s a long term goal, but it’s already doing that now too. When we have site-wide editing, we won’t need to teach people how to use widgets anymore: they’ll be the same as the blocks they see in the editor. In fact, the entire distinction will be gone.

Reasons to use the Block Editor now

Besides all of these great developments, you really should use the Block Editor now and stop using the classic editor. Let me give you an overview of simple and clear reasons. With the Block Editor:

  • You will be able to build layouts that you can’t make in TinyMCE. Most of the stuff we did for our recent digital story required no coding. Plugins like Grids make it even easier to make very smooth designs.
  • You can make FAQs and HowTo’s that’ll look awesome in search results. Our Yoast SEO Schema blocks are already providing an SEO advantage that is unmatched. For instance, check out our FAQ blocks.
  • Simple things like images next to paragraphs and other things that could be painful in TinyMCE have become so much better in Gutenberg. Want multiple columns? You can have them, like that, without extra coding.
  • Speaking of things you couldn’t do without plugins before: you can now embed tables in your content, just by adding a table block. No plugins required.
  • Creating custom blocks is relatively simple, and allows people to do 90% of the custom things they would do with plugins in the past, but easier. It becomes even easier when you use a plugin like ACF Pro or Block Lab to build those custom blocks.
  • Custom blocks, or blocks you’ve added with plugins, can be easily found by users just by clicking the + sign in the editor. Shortcodes, in the classic editor, didn’t have such a discovery method.
  • Re-usable blocks allow you to easily create content you can re-use across posts or pages, see this nice tutorial on WP Beginner.

There are many more nice features; please share yours in the comments!

Finally, it’s good to know that WordPress 5.3, slated for November 12th, will have the best version of the Block Editor yet. If you want that experience now, you can! Just install Gutenberg: the plugin.

If you haven’t used the Block Editor recently: go, try it! I’m sure you’ll be happy with it.

Read more: Pressing questions about Gutenberg: the new editor in WordPress 5.0 »

Free: WordPress for beginners training

  • Find out how to set up your own WordPress site
  • Learn everything about creating and maintaining a WordPress site
  • Plus: learn all about WordPress, like its history and its open-source community
  • Free online & on-demand training by Yoast
More info

171 Responses to The Block Editor/Gutenberg: Why you should be using it

  1. Michael
    Michael  • 2 weeks ago

    I moved to Gutenberg soon after it was released and really enjoyed using it, it appeared to be a major step forward.

    But after a while, I started to get complaints that photos weren’t fully loading and/or were loading over each other. This appeared to only occur on (some) mobile devices.

    This was obviously a major issue and after some investigation and some assistance, I found that it was a clash between Gutenberg and my site’s theme colorlib’s Sparkling. Colorlib’s response (Dec 2018) was that it would likely be fixed in a week, since then they haven’t even had the courtesy to answer follow up questions about timing or how to move the site to a Gutenberg-ready theme.

    So while I’d love to make the move (again), I keep using the old editor because while it’s limiting, it works.

  2. Michelle Spaul
    Michelle Spaul  • 3 weeks ago

    I use the Block editor on my WordPress.com site and love it, but for my .org sites I use a theme that has WP Bakery built in. Neither the plugin nor the theme author have any reason to become compatible with the Block Editor. And I don’t want to learn a new theme. So stalemate.

  3. Michael Hörnlimann
    Michael Hörnlimann  • 3 weeks ago

    Thank you very much Joost for sharing this information.
    I would like to mention that I was not an early adopter of Gutenberg. However, I changed my view on things drastically during the past weeks. If I see how it improved and also how the Yoast SEO plugin has been integrated into Gutenberg… just great!

    Like Matt mentioned at WCUS yesterday, there is currently no easy way to migrate content from the Classic Editor to Gutenberg. However, I think this can always be a good chance to do a redesign on the website, check older blog articles, etc. Then why not use Gutenberg for that?

    Gutenberg is the future, like you wrote.

    By the way: https://wordpress.org/plugins/wordpress-beta-tester/ is a great way to see the latest changes of Gutenberg in core by having WP 5.3 RC2 installed locally or on a test server.

    Cheers
    Michael

  4. Joost de Valk

    Hey everyone,

    thanks for the enormous amount of comments. I’ve read almost all of them now, but unfortunately lack the time to reply to each and every one of them individually. I do appreciate all of you taking the time to comment and will share these experiences both within Yoast and with developers on the Gutenberg team!

  5. Kij
    Kij  • 3 weeks ago

    This is what technical people fail to grasp. Innovation, invention, bells, and whistles, only matter to their circle. Real people like “not being frustrated.” Real people like simple. Doesn’t matter how innovative the block editor is if it’s not intuitive and it’s highly frustrating to use.

    • Joost de Valk

      Well, I disagree that this is innovation for innovation’s sake. There are real problems with how the classic editor worked that the new editor is allowing us to solve. That that is a painful process: yes, I agree with that entirely.

  6. Amanda
    Amanda  • 3 weeks ago

    I came here, wondering if you would offer me a good reason to switch after all this time. It turns out that the most compelling reason you offered, Joost, is irrelevant to me (the FAQ/how-to schema blocks, which do not apply to the content on my site). So, I remain on the classic editor side.

    I’m not anti-block, though. Some kinds of content are easier to publish with the classic editor, while others would be great to build with a block editor. So I vote for keeping both and having them coexist, so to speak. Of course, I know that WP isn’t a democracy, so I have no grand expectations of this ever happening. But I think that a block editor is a great idea for certain kinds of content. I have a dream of starting a second blog for a different purpose, one which would be very suitable for the block editor, and I very much look forward to using it for that (if/when I find the time).

    I have a question, though. Will Team Yoast continue to actively develop the classic editor version of your plugin for those of us that choose not to make the switch? Even if you say that blocks are the way of the future, there may be many of us that continue to cling to the classic editor plugin as long as the option exists. It may be that we just find that the old system suits our content better, or that the block editor breaks our sites and we have no choice. Will you continue to support and develop the Yoast plugin for those users’ sakes?

    Thank you for your time. :)

    • Joost de Valk

      So I vote for keeping both and having them coexist, so to speak

      Unfortunately, while I think the idea isn’t weird at all, this is undoable for companies like ourselves. Maintaining two implementations of our software indefinitely would mean smaller progress on all ends…

  7. David Wilkinson
    David Wilkinson  • 3 weeks ago

    I have stayed away from blocks… but your post prompted me to switch over. Found this video https://www.youtube.com/watch?v=rld_XRvAOfs and three mins later I did my first Gutenberg post – https://www.oxford-review.com/experts-think-less/.
    Way quicker than the old editor and looks better – took about half the time of a old blog and there are loads of great blocks – found a great table of contents plugin – contents done automatically – no more anchor links.
    Thanks for the nudge. :-)

    • Joost de Valk

      Great to hear David!

  8. Eileen
    Eileen  • 3 weeks ago

    To be frank, I’m afraid (terrifed) to make the switch. What if my site goes down? How to I learn all I need to start producing posts at the same rate I do now? How many readers will I lose during the transition?

    I need a video course. Call it “Gutenberg for Dummies.”

    • Joost de Valk

      Those are valid questions Eileen. Actually, we have a (section of a) free course for that, in our WordPress for Beginners course. Not sure if that answers all your questions but it might help!

  9. Brenna
    Brenna  • 3 weeks ago

    I really want to use the block editor but it breaks my sites. I have two sites with mostly different plugins. Yesterday when I got your email about switching I decided to give it a try.

    It worked great for a few hours and suddenly I couldn’t edit posts on either site. I got white screens. My sites wouldn’t load on the front end at that point either.

    I decided to give it a last try and disabled and removed all plugins. The issue didn’t go away until I reinstalled classic editor.

    What could be the issue? Two different themes so I don’t think that is the issue.

    • Joost de Valk

      Hi Brenna,

      that’s so unfortunate. Unfortunately for me it’s also impossible to say what could be the issue here as it could be many, many different things. Maybe your host can help you figure it out? But I also completely understand if you’re not willing to invest more time right now :)

  10. Sam Hal
    Sam Hal  • 3 weeks ago

    unfortunately yoast plugin is not compatible with Gutenberg in RTL websites and when using it, the seo url become corrupted with lots of letters. That’s the reason I don’t use it.

    • Joost de Valk

      Hey Sam,

      first time I heard of that bug, to be absolutely honest. Our QA team says we have had a bug for that in the past but that was fixed, when did you last try this? If it’s still an issue, please file a bug report!

  11. Emma
    Emma  • 4 weeks ago

    Can you give some reasons why a non-technical person would want to use block editor? Ie Someone that is not so concerned about fancy formatting and just wants to write a good story? The classic editor, while not pretty, at least is simple and easy.

    • Joost de Valk

      I think that in the end the block editor should be easier to work with than the classic editor. But I do also realize that if the classic editor is what you’re used to, any change is more work than no change…

  12. Ed Tobias
    Ed Tobias  • 4 weeks ago

    I hate Block Editor. You say it’s easy to insert an image and wrap text around it. I find it difficult. I do a lot more clicking to get things done for my simple, little blog than I used to do.

    • Joost de Valk

      Hey Ed,

      sorry to hear that, what would make it easier?

  13. R.W. "Doc" Boyle
    R.W. "Doc" Boyle  • 4 weeks ago

    My website has somewhere around the equivalent of 3,000 pages typewritten, with a thousand+ photos and huge number of internal links. I don’t quite see how to start using the Block Editor. I certainly can’t re-write the website. The site is paywalled (subscription). with somewhat more than 100 subscribers. I’d be glad to give you a subscription if it would help, if you could peruse the site. I first put up the site somewhere back about 2011. I’m 78 years old, live on Social security and have never had the money to advertise the site. There are NO ads on it and I’d like to keep it that way. SEO issues seem somewhat irrelevant due to the paywall. Comments or advice appreciated.
    Doc

    • Joost de Valk

      Hey Doc,

      no need to do anything to the existing content: it should just keep on working. The only time you’ll have to do something with the block editor on old content is if you want to, then you can convert a post to blocks, but I’d not advise that if it’s not needed.

      You could just start using the block editor for your new content?

  14. Eric
    Eric  • 4 weeks ago

    Block is the evolution of web design. Criticize it all you want but it is not going away (but traditional methods are).

    • Joost de Valk

      I think you’re right. But at the same time, all this feedback on this post is very helpful to understand where the problems are.

  15. Greg Rankin
    Greg Rankin  • 4 weeks ago

    We’re currently using WP Bakery. Are there any SEO advantages in switching to Gutenberg?

    • Danny
      Danny  • 3 weeks ago

      I would like more info on this too! Add FAQ schema through Gutenberg is easier along with other SEO improvements without complicated code, however. switching all out pages to Gutenberg would break the pages, am I right?

      Cheers,
      Danny

      • Joost de Valk

        I’m honestly not sure how easy it is to switch from WP Bakery to Gutenberg and can totally imagine that not being easy. In the long run, Gutenberg should create a base API that all page builders can build on top of so they become a bit more interoperable, as it stands right now, WordPress + WP Bakery is basically almost a different CMS…

  16. Mike Bianchi
    Mike Bianchi  • 4 weeks ago

    I see how the Block(head) editor appeals to the non-coders, as it could make it easier for them to create pages. Still, it shouldn’t be part of WordPress core. It should be a standard plugin that is installed with WordPress (like Akismet). This way the editor can be improved/extended without having to update WP core.

    The Block(head) editor needs more development for it to become a very good tool. The sites I have built using the Block(head) editor have required many of the blocks to be re-coded in HTML in order to get the desired format. The Classic editor did not limit me as I coded most static pages in HTML.

    This editor seems to be an attempt by WordPress.com to compete with Wix and Squarespace (good luck with that), and yet it is imposed on all WordPress developers.

    I hope that the Block(head) editor evolves to be a great tool. Meanwhile, I’ll still be coding a lot of HTML blocks.

    • Joost de Valk

      Still, it shouldn’t be part of WordPress core.

      That ship has sailed :)

  17. Susan Wesley-Vega
    Susan Wesley-Vega  • 4 weeks ago

    Hi! I abandoned both the classic and G-Block editó early on for all the reasons you met. Also, I don’t know coding. So, I switched to Elementor and there is so much I can do—fast, easy, creative, elegant!! I haven’t even needed to up grade from the free version yet!

    So, my sincere question is to ask you to explain if there is a reason to use the Block Editor over Elementor? I don’t think there’s a way to use both, but if there is, PLEASE advise about that too.

    I love your blogs. Many thanks!
    Susan

    • Joost de Valk

      Elementor is absolutely lovely, so I can understand that. I think they’re on track to allow interoperability between Gutenberg / the block editor and Elementor, so you should be ok in the long run.

  18. Jasper
    Jasper  • 4 weeks ago

    Reasons to not ever use the block editor and directly install Classic Editor upon installing a new WordPress website:

    1) Gutenberg is not done. not even close. it’s buggy AF,
    2) With Gutenberg enabled, our clients send in a TON more support tickets
    3) the reviews about Gutenberg on WP.org aren’t lying. This thing is not done yet, and therefore it shouldn’t be used on production websites. Or ever.

    • Joost de Valk

      Jasper,

      “Gutenberg is not done. not even close. it’s buggy AF,”

      That’s too easy. What is broken? What can’t your clients figure out? Did you submit that feedback?

  19. Ron
    Ron  • 4 weeks ago

    Completely agree. It takes getting used to but the block editor works really well. Many possibilities and easy to work with.

  20. JC
    JC  • 4 weeks ago

    I tried the block editor on two of my sites; I’ve switched both sites back to the classic editor for a couple of reasons.
    1- Block is not for long-form content. For my reference site, I start by pasting in long articles, then adapt them for online by adding paragraphs, subheads, and images. In block editor, every heading/image/paragraph had a separate block, which had to be dragged and dropped, making editing a pain. Instead of simply cutting and pasting multiple paragraphs with headers and images, every single fragment had to be dealt with individually. This meant that it was alarmingly easy to accidentally get paragraphs or headings out of order. It was slow and caused endless scrolling.
    2- Images/embedded videos were a pain. The items I most often place are small-size book images linked to Amazon (affiliate links, obviously) and YouTube videos. I like book covers to be flush left within text. I like videos to be fully embedded. This is simple in classic code view; just paste a snippet of code and everything worked. I could not find a simple way to make block editor do this.
    Finally, it disturbs me that every single item has to have a separate block. It seems that a malicious person with a bit of coding knowledge could destroy millions of sites with a few lines of code designed to scramble all the blocks in a site. Unlikely? Maybe, but it just seems too big a risk to take.

    • Joost de Valk

      Hey JC, thanks for these points, I think they show mostly an education problem within the tool: stuff that should be easy to find obviously isn’t. Embedding videos is really easy, once you know how to, but I can totally understand if you couldn’t find that.

  21. Ralph
    Ralph  • 4 weeks ago

    Well that was a weak post Yoast! You seem to saying that we should use block editor now – because it might help us win “in SEO in the next few years.” Hardly a convincing reason to change right now.
    In our opinion, for newly created websites using the block editor does makes sense.

    But for legacy sites the block editor can and DOES inflict pain. It can mean creating the need to go through all the content and re-optimize it. That can be a big job Yoast. And then there’s legacy WP themes which often have a preferred editor which is very different from the block editor – potentially impacting styles and layout. That’s more work Yoast. And the block editor is perfectly capable of messing up numerous plug-ins. That’s more work Yoast.

    Perhaps the message you should be circulating is that the block editor is a work in progress and versus quality page builders which overlay the classic editor – it’s not quite there yet. It’s not as capable. The block editor needs more development. :-)

    • Joost de Valk

      Well that was a weak post Yoast!

      Thanks for your candid feedback, I respectfully disagree, with 150 comments, I think a lot of people were at least thinking about the topic :)

  22. Ron
    Ron  • 4 weeks ago

    Gutenberg, the interface is horrible, and un-intuitive, especially for those who are used to tiny editor. A decent tutorial on how to use the block editor is no where to found. It was released way to close to the holiday season. These and the fact people hate change are just a few of the reasons Gutenberg is so rarely used.

    • Joost de Valk

      A decent tutorial on how to use the block editor is no where to found

      That is… Unfortunate. You could check out our WordPress for Beginners course, it’s free and has a block editor chapter that might be helpful!

  23. Mark
    Mark  • 4 weeks ago

    We have tried gutenberg and found it clunky and very poorly executed. The roll out leaves something to be desired too. Lots of horrible reviews seems to confirm our experience. It reminds us updating something for updating sake, like the way cell phones are done. They update until the phone no longer works or the UI is something completely different that what attracted you to it in the first place. Are we missing something guys?

  24. Donna Frano
    Donna Frano  • 4 weeks ago

    Good grief, I can’t believe ANYONE is sticking with the Classic Editor! The Block Editor is SO much easier and faster. I can create posts for my client much faster AND they look cleaner and more professional. Why wouldn’t someone switch?

  25. ruth.billheimer
    ruth.billheimer  • 4 weeks ago

    I’m a bit confused about this. I can see the point of starting to use the block editor now for new posts and pages, but do you have to go back over all your previous posts/pages and re-do them with the block editor?

  26. Jane Littlewood
    Jane Littlewood  • 4 weeks ago

    I’ve just switched an Open Cart shop to Woo Commerce. I need to go through all the content and optimise it (big job). There are some bits of content common to all the items in a category. Would not be a good time to switch to Guttenberg so I can build a range of blocks to insert rather than copy/pasting each time?

    • Joost de Valk

      Yes absolutely!

  27. micibama
    micibama  • 4 weeks ago

    I am new to WordPress and trying this now may be confusing. However, I gat to try it out in the near future when I probably become a WordPress pro. Thanks for sharing.

  28. Harrison
    Harrison  • 4 weeks ago

    You never did say why we should switch over.

    • Joost de Valk

      I think I did say, if you read the “reasons” section. Those might not be reasons for you, which I totally respect if that’s the case.

  29. kevin
    kevin  • 4 weeks ago

    Block editor is a solution in search of a problem.

    • Matt Orley
      Matt Orley  • 4 weeks ago

      I agree with kevin, block editor is a solution in search of a problem.

    • Joost de Valk

      I disagree, but you’re entitled to that opinion.

  30. GregW
    GregW  • 4 weeks ago

    If Gutenberg continues to be pushed … maybe its time for a different website builder, e.g. ClassicPress.

    Gutenberg should be and continue to be a ‘plugin’ like any other. If you want it then install it, otherwise leave it out. It should have NEVER been a default embedded editor.

    I’ve tried quite a few times to get use to the Gutenberg block editor, but it keeps being unable to do some very basic tasks and slows editing too much if there is no out of the box suitable block.

    I use another and IMHO a better page builder for some sites, and still use the Classic Editor on others. What I am concerned about with WP is that the focus on Gutenberg (Bock Editor) may result in issues/conflicts with other page editors.

    I just feels like WP are taking away choice of what to and what not to use by ‘almost forcing’, or at least appear to be heavily recommending you use the (built in) Block Editor., even if you do not want to.

    The WP developers made a wrong turn on this one, but with this post I am now concerned that maybe Yoast is too, if you are Block Editor centric then Yoast may no longer be suited to non Gutenberg/block editor WP websites. I’ve been reviewing other SEO tools and that may become a reality

    • Joost de Valk

      Hey Greg,

      there’s a group of people who think like you and I can’t blame you for it. But the ship has sailed: the block editor is WordPress’ future. I personally think no other CMS can compete with WordPress’ size and forward motion, so fighting this change is not useful. However, I do think that giving concrete constructive feedback on stuff that you think should be improved is helpful for everyone involved in the project.

  31. Arnold Wender
    Arnold Wender  • 4 weeks ago

    Maybe is good for new websites but for existing sites I will still use my Page Builder, if you want extra functionality you still need third party blocks and the performance goes down, so why use Gutenberg?

    • Michele
      Michele  • 4 weeks ago

      My thoughts exactly. My 3 year old website is done with Page Builder, and 90% of what I do is simply updating existing pages, not adding new ones. Why would I rebuild all my pages if I don’t have to?

      • Joost de Valk

        Nobody is forcing you to. If you don’t think you need to make the change, don’t do it :)

  32. Paul
    Paul  • 4 weeks ago

    …or you just use a theme which has a great block editor itself: Enfold

  33. Ricky.Heidi
    Ricky.Heidi  • 4 weeks ago

    Thanks for sharing details and motivation points for using the Block Editor. But isn’t that basically we are already doing by using the block editors provided with the Template companies? Like with Template Monster – Power Builder? Or Customizer offers one now and Elementor? Wix has a built-in Block Editor that works great. Isn’t, in fact, all of these a part of the Block editor family? Please advise. Thanks — Ricky

    • Joost de Valk

      Honestly there are so many different editors on top of WordPress, that’s the problem that Gutenberg is trying to solve. Integrating with all those different editors is a no-go for plugins like ours, whereas it’d be a lot easier if they all integrated with Gutenberg :)

  34. Maria
    Maria  • 4 weeks ago

    It’s clunky and I simply will not use it.

    • Joost de Valk

      I do want to challenge you to be more constructive in your feedback: what is “clunky”? What should be improved? If you do that, you might find that things can actually progress.

  35. Ben Brok
    Ben Brok  • 4 weeks ago

    I find the block editor very annoying to work with. I really miss the old WordPress set up

    • Joost de Valk

      I do want to challenge you to be more constructive in your feedback: what is “annoying to work with”? What should be improved? If you do that, you might find that things can actually progress.

  36. Diana
    Diana  • 4 weeks ago

    Maybe they should have made the Block Editor more intuitive and easy to use. I tried it and was lost. I went back to the classic editor within a week. Thanks, but no thanks.

    • Joost de Valk

      Hey Diana,

      I understand that, and want to challenge you to try again. It’s a lot better than it was.

  37. Johan Terve
    Johan Terve  • 4 weeks ago

    I think that the main reason for not moving over is that people already have themes that supports the elements needed and that these themes haven’t yet found out how to co-exist with the WP native block editing. I think that this is the case of my theme Enfold for instance. I am very focused on SEO and it scares the sh*t of me hearing you say that not moving over will have a negative impact. Is this really the case? I mean what matters must be the content not the tool? Please clarify.

    • Joost de Valk

      The content matters more than anything else. But if the content is more easily enriched with Schema because the block editor makes that so easy, your competitors will start using it and create more “meaningful experiences”, rank more easily, etc. So yeah… At some point, you should move over :)

  38. DylanG
    DylanG  • 4 weeks ago

    Sorry, but I will “NEVER” use it, completely un-intuitive, and servers no purpose as far as I can see. I sincerely urge you to keep supporting the classic editor. 100%. Otherwise, I will guarantee you people will use something else.

    • Joost de Valk

      I do want to challenge you to be more constructive in your feedback: what is “completely un-intuitive”? What should be improved? If you do that, you might find that things can actually progress.

  39. Joost
    Joost  • 4 weeks ago

    I took some time to get used to it, plus some time to convert my existing posts, but now I am perfectly happy with the new editor.

    • Joost de Valk

      That is great to hear Joost!

  40. Marcel BOTEZAT
    Marcel BOTEZAT  • 4 weeks ago

    By reusing the same block content on multiple pages/ posts, does that mean we will have duplicate content?

    • Joost de Valk

      A bit, yes, so don’t over-do it :)

  41. Yakub
    Yakub  • 4 weeks ago

    Joost de Valk,
    I almost understand the benefits of Block Editor. But if you make a video about this matter, it will be very helpful for me.
    Thanks.

  42. Hod
    Hod  • 4 weeks ago

    One week ago I uninstalled elementor and am using only WP block editor since then.
    Love the new block editor.

    • Joost de Valk

      That’s great to hear!

  43. Gal Baras
    Gal Baras  • 4 weeks ago

    On your side, of course, it sucks having to maintain 2 sets of code and I totally get it. However…

    Copying text in the block editor and pasting it again adds spaces at both ends of the pasted text. This bug, which hasn’t been fixed in a few months.

    I think the block editor was released prematurely and is being vetted by the user population. Not how software should be released.

    The block editor is a great proposition for bloggers. Business sites are likely using professionals to create/update their content and their theme and plugins (a page builder and/or Advanced Custom Fields) take care of everything they need right now.

    Having a separate block for every paragraph, list, image, etc, seems to me like overkill and makes some things more difficult to understand, e.g. image embedding at a specific point.

    New sites should probably be built with the block editor, because that’s the future and it saves money. Those users are giving up nothing, so block editor usage will gradually increase.

    As long as WordPress and the Yoast team support the pre-block-editor setup, SEO will actually be fine. Anyone not needing FAQ Block, and anyone using an FAQ plugin, will miss nothing.

    Keep up the good work. Nothing wrong with a bit of controversy ;P

  44. Willy Pujo Hidayat
    Willy Pujo Hidayat  • 4 weeks ago

    Gutenberg helps me to add a button on my blog post by only drag-and-drop the buttons block (and customize it as well), it’s easier than install additional plugin, or doing some codes.

    • Joost de Valk

      That’s good to hear :)

  45. Dwain Wilder
    Dwain Wilder  • 4 weeks ago

    The reason I use the Classic Editor is that I publish an email edition based on the html it creates. I have not heard a word about publishing an email edition of a wordpress site that is created with Gutenberg and displays well in email.

    If there is a way, please let me know!

    • Joost de Valk

      In the end the HTML output from either editor is not all that different to be honest…

  46. Sol
    Sol  • 4 weeks ago

    I was going to ask about Elementor, but I see Luke’s beaten me to it.
    What does the Block Editor do that Elementor can’t, or what does it do better? Intuitively, it seems that throwing the Block Editor into existing Elementor workflows is just going to complicate things, and I don’t see a compelling reason … ?

  47. Larry Smart
    Larry Smart  • 4 weeks ago

    One major problem for me using the block editor is that each paragraph starts a new block. This makes narrative ugly with wide spacing. At a minimum, the block editor should allow a shift enter to put different paragraphs within the same block.

    • Joost de Valk

      Well… No, the whole point is that a paragraph is a block. The spacing should also only be an issue in the backend, if at all, on the frontend it should look the same.

  48. John
    John  • 4 weeks ago

    My website heavily depends on Custom Fields. Will I be able to move to Block Editor and still being able to use the data from the Custom Fields?

    • Joost de Valk

      Yes absolutely.

  49. gary63
    gary63  • 4 weeks ago

    I like Gutenberg, but I don’t like that I can’t highlight and copy and paste it all, like the old editor.

    I think this is something that might discourage others, too.

  50. Greg Rankin
    Greg Rankin  • 4 weeks ago

    We’re currently using WP Bakery. Are there any advantages to moving to the WP block editor from an SEO standpoint?

  51. MD
    MD  • 4 weeks ago

    The main reason why I haven’t switched over is because, I write all my articles in Microsoft Word and the block editor produces too many mistakes with it. I have to manually go in and correct too many things.

    • Joost de Valk

      When you copy and paste from MS Word it creates “mistakes”? What goes wrong?

  52. Backpackerbill
    Backpackerbill  • 4 weeks ago

    Thanks, for the update. I wanted to wait until the bugs were worked out.
    When I tried it and found it far too complicated and would take too long to learn. So I’ve stuck with Classic. Until the other day I began to switch over. Still find nagging little issues like being unable to click and drag text from one place to another in writing text. It works in classic and not in block.
    I’ll probably stick with block now that I’m working in it.

  53. Keith Rowley
    Keith Rowley  • 4 weeks ago

    I use Elementor, Thrive Architect and WP Bakery. Why on Earth would I need Block Editor? With the above tools I still use some custom html and css.

  54. Sarah Bradberry
    Sarah Bradberry  • 4 weeks ago

    I was using the block editor but then a bug was introduced that meant sites with a lot of pages no longer allowed you to choose a parent page for new pages so I was forced to switch back to the classic editor. After a few moths of checking if it had been fixed whenever I added a new page, I gave up and stuck with the classic editor.

  55. Jennifer Nelson
    Jennifer Nelson  • 4 weeks ago

    Newb here, but here’s my two cents: my problem with the block editor is in adding links, it won’t give me the option of replacing the link with text. Maybe that is changing, hope so. I haven’t had my site long enough to be terribly attached to the classic editor, so I’m still on the fence about it.

  56. Scott
    Scott  • 4 weeks ago

    What is the he Gutenberg project?

  57. Mary
    Mary  • 4 weeks ago

    Do I need to install the Gutenberg Plugin to use Gutenberg? Or do I simply deactivate my classic editor? My WordPress is version 5.2.4.

    • Amanda
      Amanda  • 3 weeks ago

      Since it seems no one has answered you, I’ll just let you know that you only need to deactivate your Classic Editor plugin. The block editor is the default now.

  58. booker talk
    booker talk  • 4 weeks ago

    My first experience with Block Editor wasn’t great. I thought it was clumsy. But now I love it – one good reason to use this is that you can easily move text and other elements around to give the page a better visual structure.
    Just wish that there was a quicker way to assign a custom colour to text.

  59. Rodney Thomas
    Rodney Thomas  • 4 weeks ago

    Greetings Yoast. Appreciated your article on using the “block editor.” You make a compelling point, but I think given the passion that seems to be overwhelmingly expressed against transitioning to the block editor, it’s going to take quite a while for most to make the transition. I myself have been using a premium block theme editor called “Divi” for 2-years now and have no intentions of abandoning it for Gutenberg. I did play around with Gutenberg when it formally launched a few months ago. I found it to be inferior to my Divi block editor theme and have not had any inclination whatsoever to return to Gutenberg. I’m going to continue to monitor the discussion on this very important topic to see where it will ultimately go. Apart from this, thank you for putting out a fantastic, top-notch SEO plug-in.

  60. David Gorski
    David Gorski  • 4 weeks ago

    I’ve switched over, but the Block Editor still screws a lot of things up. For instance, I’ve yet to be able to get it to embed an Instagram post. Whenever I try, I get an error message. The centering function doesn’t work for images, and whenever I try to do a blockquote with a list in it, I have to use custom HTML. I find myself having to activate the Classic Editor plugin and do a post the old way, just to be able to embed content that I want to.

    • Joost de Valk

      Hey David,

      that sounds pretty bad, how are you trying to embed instagram posts? (I never do that myself so not even sure how that works)

  61. caban
    caban  • 4 weeks ago

    You should read the statistics, people does not like Gutenberg. Simple.

    Classic Editor: 5+ million active installations
    Classic Editor Addon: 30,000+ active installations
    Disable Gutenberg: 400,000+ active installations
    No Gutenberg: 10,000+ active installations

    I am NOT afraid of HTML or CSS…
    Classic Editor is not great but Gutenberg is worst.

    • Joy
      Joy  • 3 weeks ago

      Just so it’s clear, WP stats are capped at 5 million. It could be way higher, but only 5 million are reported. You can see this in the code.

    • Joost de Valk

      Those numbers are indeed high, but it’s all relative: lots and lots and lots of people are using sites with the block editor too. For our users, it’s about 50/50.

  62. Keith Blakemore-Noble
    Keith Blakemore-Noble  • 4 weeks ago

    Sorry, I’m going to have to completely disagree here.

    Gutenburg is not something the user community called for, it was foisted upon us.
    It was very badly implemented, and frankly it was a complete mess.
    Like most web developers, I’ve got better things to do that to keep trying out something I never even wanted on the off-chance the developers actually made it semi-useable.

    So even now, I won’t be switching to Gutenburg. My existing theme, running in Classic mode, is far better for my purposes, it does what I want, it doesn’t get in the way (none of which apply to Gutenburg).

    It is disappointing that Yoast seem to be suggesting they are ditching Classic support, but I guess that’s up to Yoast, and if the company wants to abandon its paying Classic users over time, then there’s not much we can do, alas.
    I sincerely hope you will reconsider.

    • Joost de Valk

      It is disappointing that Yoast seem to be suggesting they are ditching Classic support

      Nowhere did we say that. Nor do we plan to.

  63. Bill
    Bill  • 4 weeks ago

    Are there any plans to add accordion functionality to your FAQ block capability?

  64. Henry Scullion
    Henry Scullion  • 4 weeks ago

    One of the many advantages of Gutenberg is that I don’t have to register widgets for my home pages any more. It’s much easier to achieve the same result by creating a regular page using blocks (from the Atomic Blocks plugin for example) and set that as my home page. Philip Gledhill’s Genesis site has a great tutorial on this:

    https://philipgledhill.co.uk/build-a-simple-homepage-with-atomic-blocks-and-gutenberg/

  65. Roberta Perry
    Roberta Perry  • 4 weeks ago

    My problem is not so much learning how to use the blocks as my frustration in that it it not recognizing my words for SEO purposes. For example. I wrote a piece on fragrance and I have 11 included blocks of H4 headers and copy. I have a photo at the top.

    The Yoast section says this:
    “The text contains 0 words. This is far below the recommended minimum of 300 words. Add more content that is relevant for the topic.” ( I have 533 words according to MSWord)
    Bad SEO score:
    The focus keyword doesn’t appear in the first paragraph of the copy. Make sure the topic is clear immediately.” ( It does in both header and first paragraph)

    My sidebar has a comment like this: “Once you add a bit more copy, we’ll give you a list of related content here to which you could link in your post.”

    I never used to have issues like this before blocks. What should I do and is anyone else having this same issue?

  66. John Givens
    John Givens  • 4 weeks ago

    Still confused. Still see no reason to switch.
    I’m using a page builder – WP Bakery over top of the classic editor. I don’t code in HTML. The page builder does a very good job of giving me just the look and ease of use I want. I see no reason to change.

    I searched the web a month ago looking for a comparison of:
    Block Editor vs Page Builders…? Which is easier/has more function?

    By a huge margin, the comments from (what I would trust as )experts came back: “Block Editior is nowhere as capable in creating attractive and sound content as the Page Builders. It’s just not there yet.”

    If I could flick a toggle switch and convert what I have to the Block Editor – and then switch back if I didn’t like it…I might do that. But no where do I see a way to compare creating a page in one vs the other – especially the kinds of pages I have in my website – and want to have in the future. I’ve found nothing I can’t do in WP Bakery page builder that I would need to move for.

    Can someone show me?

    • Amie
      Amie  • 4 weeks ago

      I’m with you. I run WP Bakery on top of classic editor. This has allowed me to do some great design work on our site. It’s easy to use and creates great sites.

      I actually run a 501c3 site also and tried Gutenberg on that site just to test it out. I really tried to like it but couldn’t do some of the simplest tasks. I couldn’t stand it. After about 9 months I finally just loaded Classic Editor plugin and run the site on that.

      Gutenberg, in my opinion, has/had no where near the ease or capability of a builder like WP Bakery.

    • Jonathan
      Jonathan  • 4 weeks ago

      Nope, I don’t think that’s possible. I use Elementor, and if you mess with the code, you bork the whole page. Elementor also uses the block concept but is far, far, far more powerful than Gutenberg.

  67. Michael Kohlfürst
    Michael Kohlfürst  • 4 weeks ago

    Do you advice to update all old contentnow to Block Editor or should I wait until I update the Blog / Page Content somewhen in the next 12 month? THX, Michael

  68. Scott Robinson
    Scott Robinson  • 4 weeks ago

    Hi,

    I’m having problems synching Jetpack with WordPress because ACF is installed by my developers. Yoast also does not work properly with ACF. Will Gutenberg and a block based editor help?

    Thanks,

    Scott

  69. Alun Davies
    Alun Davies  • 4 weeks ago

    “When we talk about Gutenberg/the Block Editor within the WordPress community”

    And (quite probably without realising it) Joost walks straight into the problem. WordPress only really consults with it’s so-called community, a community made up almost exclusively of narrowly focused IT professionals who have the time and emotional inclination to invest in the block editor. For the most part they don’t need to balance the competing demands such as accounting, product development, invoicing, procurement, legal compliance, customer service, marketing, sales presentation and proposals, general administration etc Consequently they tend to view the universe through the single prism of IT, which is fine if you possess the knowledge to assimilate it. A lot of us haven’t got the time or money to lose on the block editor though, and this is why we’re rejecting it. This shouldn’t be difficult for the self-regarding WordPress community to understand.

    Personally I hate the block editor. I regard it as a known threat to the business, the same way I do the exchange rate. Quite apart from anything, we run a theme that has white font on a black background. The block editor couldn’t handle this. It displayed white on white in the editor. Absolutely useless.

    • Joost de Valk

      It displayed white on white in the editor.

      That is both a bit funny (sorry :) ) and utterly stupid of course.

      We do try to perceive things like you do. We’re part of the WordPress community and to us too, Gutenberg / the block editor came as a surprise in the beginning. We worked hard to get it to a state where Yoast SEO could work with it, and over the last year I’ve really seen it progress to something better than we had before. I don’t think it should be a threat to your business, but if it is, the classic editor will be around for quite a while longer :)

  70. Per Karlsson
    Per Karlsson  • 4 weeks ago

    I am still not convinced.

    Partially because most things published don’t need fancy layouts. In most cases, the simpler the better.

    More importantly:

    No sensible writer would author directly in WordPress. You first write your text in Word, or whichever word processor you prefer. The you copy and paste all the text over to WordPress.

    With the Classic Editor that is simple. Well, in a way, it is just as simple with the Block Editor I guess.

    But where the Block Editor fails is when I want to add images. Images are, everyone agrees, very important.

    It is easy, very easy, to insert images in the Classic Editor. Insert an image from the library where you want it in the text and, boom, it is there.

    In the Block Editor not so. You have to fiddle with creating new text blocks, copying and pasting bits of text, inserting new image blocks…. And repeat for every image. Much more complicated and more time consuming.

    Possibly, this workflow scenario has been solved or improved in a recent version of the block editor, but when I tried it it was just to cumbersome.

  71. Wilfried Mestdagh
    Wilfried Mestdagh  • 4 weeks ago

    I use block editor from beginning, but the moment you want something else than pure text you have to switch over to classic editor.
    I have many user new to WP, almost all of them only want to use only the classic editor.
    Until now I did not see any advantage in block editor…

  72. Eldon Beard
    Eldon Beard  • 4 weeks ago

    Aren’t editors like Thrive Architect doing essentially the same thing, building content with blocks and elements? If a WordPress site’s content is built using a utility like this, is there any reason to change anything? Asking from the standpoint of maximizing SEO, etc.

  73. Sam D'Amico
    Sam D'Amico  • 4 weeks ago

    Thanks for the push.
    I’ve been avoiding “Gutenberg”.
    But your article convinced me to make the switch.

  74. Nick Mee
    Nick Mee  • 4 weeks ago

    I really understand some of the benefits when it comes to structured data and i realise that it takes time to make the block editor work as well (or even better) as others such as WP bakery or Elementor.
    But besides the issues/conflicts with other plugins and blocks/elements not working properly (gallery block for example still causes layout issues on iPads) it is still not a very user friendly editor in my opinion.
    For example the adding button (+ symbol) is only visible on hover and sometimes (in the middle/centre of 2 columns for example) on such a small amount of space that you need to act with surgical precision in order to be able to click on it… time consuming and it really annoys me.
    Another example is that the standard layout of the “image with text block” is inline on mobile devices…. one of the benefits of responsiveness is that the image can be below/above the text so it looks clean and readable instead of it all being shrinked to screen size without “stacking them on top of eachother” …. why go back to the ugly old way in block editor? of course you can change this by clicking on options but these are all extra adjustments, which are time consuming and not logical if you ask me..
    To sum up i totally get the benefits for using the Yoast schema blocks and the possibility to get featured results and other SEO advantages but the block editor itself is a long way from being user friendly and complete.

  75. Gerard Sosz
    Gerard Sosz  • 4 weeks ago

    Unfortunately when it comes to re-edit a whole site that has been out for many years is a very complicated task. I have a 15 year old site with more than 1800 entries and I do not think I will be editing it just for changing to the block editor.

    What I do is to try to start new posts from the block editor, but I still like more the old classic editor… this new Gutemberg requires a lot of “clics” and dragging to achieve the same in the classic editor.

  76. Bruce Maples
    Bruce Maples  • 4 weeks ago

    I have tried the block editor on multiple occasions, but my content workflow is SO dependent on custom features that aren’t available in the block editor. When you are running a media site, posting multiple articles every day as well as doing research and running a business, you just don’t have time to try to figure out how to replicate something you currently can do in your sleep. (And, if anyone wants a list of the things I can do in my current setup that are not possible in the block editor, I’d be glad to provide it.)

    Do I like having to use plugins to get all this functionality? No, I don’t — but until I can edit and post as fast in the block editor as I currently can do in the classic editor, I cannot afford to switch.

  77. Jack
    Jack  • 4 weeks ago

    I tried to convert to the new block editor but I have a number of website that use an older theme with a lot of content. Updating existing pages with Gutenberg is an exercise in frustration.

    You really need to provide a transition path for existing websites.

  78. Cali Bird
    Cali Bird  • 4 weeks ago

    I switched to the Block Editor straightaway for my posts and they took longer to set up than before. A year ago there were quite a few glitches. I’ve got used to it now but I still haven’t found a way to indent text. For that you have to use a Classic block. Unless someone can tell me how to do that??

  79. Tony Payne
    Tony Payne  • 4 weeks ago

    I tried the block editor when it came out and with a site that is 10 years old and a lot of editing to do, I found trying to learn it was too complicated.
    I know the theme I am using (Customizr) is supposed to handle the block editor well, so maybe this is a good time to try and get to grips with it again. I am definitely struggling to get the SEO results I desire, anything that helps is a step in the right direction.

  80. Jasper
    Jasper  • 4 weeks ago

    What about editors like Elementor? Is this the same? Or must I alway use Gutenberg?
    Good article btw…

  81. Lynn Spencer
    Lynn Spencer  • 4 weeks ago

    The biggest thing holding me back from Gutenberg is the inability to easily tag affiliate links as no-follow. Once they roll that out, I’m sure I will jump on the bandwagon.

  82. Timothy BOLTON-MILHAS
    Timothy BOLTON-MILHAS  • 4 weeks ago

    All fine and well, but the block editor does not offer a satisfactory working experience. It was rushed into production and was very buggy…probably less buggy now, but the overall experience remains u changed. If using blocks (and there is absolutely no reason why the block editor should be any better in SEO than the classic editor – it’s all about readability in the end) I still prefer well-proved third block editors like Elementor and SiteOrigin.

  83. Philip Miller
    Philip Miller  • 4 weeks ago

    The original version of block editor was a disaster. So we all abandoned it. It didn’t work. Now you are trying to convince us it’s better. An uphill battle.

    Can you assure that an import from word doc to WordPress block editor is now more seamless and successful ?

  84. Roberta Perry
    Roberta Perry  • 4 weeks ago

    My problem is more with SEO word recognition in my blogs. When I type blocks of text, including headers and then I look at the blog post in general, it tells me that it can’t help me with my SEO because I have “0 words and that’s less than the 300 necessary to help“(paraphrased)
    Does anyone else have that problem?

  85. wayne
    wayne  • 4 weeks ago

    Unfortunately the themes we use are not compatible… Enfold

  86. Paul Roberts
    Paul Roberts  • 4 weeks ago

    All wordpress websites should have two ways of building pages. The Tiny MCE editor and a page builder. Page builders do quickly layouts and designs that the MCE editor cannot do well. So many people, like Yoast in this article, compare the MCE editor to the Gutenberg block editor, but I think that’s a mistake. The question isn’t whether you should be using a block editor on some of your posts and pages (you should.) It’s whether you should be the Gutenberg block or some other page builder. For me, I think Elementor Pro is still miles ahead of the wordpress page builder.

    I’ve tried all the page builders and there many good ones. Each has its own pros and cons for sure. So I’m going laydown the gauntlet to Yoast here. Tell why I should the Gutenberg block editor is better than Elementor Pro. Because when I tested it myself, I found the block editor confusing and slow to use. Whereas Elementor Pro is feature rich, with great documentation, and easy to learn.

  87. Jon Peltier
    Jon Peltier  • 4 weeks ago

    The block editor is great, and it was easy to learn, but it has some shortcomings. It does not permit custom of formatting of some text within a block, for example; span tags are ignored. It also does not provide an easy way to enter title text for a link, only the url.

  88. prajwal
    prajwal  • 4 weeks ago

    I had a query. It’s been a week I started a blog and I’ve written three posts so far. I rank in between 77-123 for the keywords I targeted in posts. I’ve tried to write and reconfirmed this fact from a friend that my article is way more better and detailed than the site which ranks first.
    Shall I be worried about my writing? I’ve heard that it takes time to get on the first page. Is it so?????

  89. Scott Robinson
    Scott Robinson  • 4 weeks ago

    Hi,

    thanks for this. I must admit, whilst my knowledge of WordPress has improved, I’m still learning. My new developers included the ACF plug-in on Wp-Admin, which isn’t compatible with Yoast, nor with Jetpack. Jetpack tells me I should be moving towards a block-based editor. I thought ACF was a block based editor? Can you pls tell me the difference? Sorry for the basic question!

    Thanks,

    Scott

  90. stefan
    stefan  • 4 weeks ago

    “Change is the law of life. And those who look only to the past or present are certain to miss the future.”
    ―John F. Kennedy

    The only thing i see when looking at this block editor is tons of opportunities.

  91. Apu
    Apu  • 4 weeks ago

    I have recently started to use the block edit. it’s easy to use & customize. Besides it has many extra features that once cold be done by plugins…

  92. Keith Greywood
    Keith Greywood  • 4 weeks ago

    You’ve convinced me to take another look – loving the content example you have used to show what can be done.

  93. Kelleen Guyer
    Kelleen Guyer  • 4 weeks ago

    Hello,
    I am one of those folks who just went for it and updated to Gutenberg-Block Editor. I am slowly updating all my pages, but have two concerns.
    Would it be better to rebuild from scratch than to update slowly? I am worried my original template is over 6 years old.
    Also, I am having trouble adding GA event tracking code to the blocks, I keep getting errors that need to be resolved. Do you know a way to fix this? Thanks.

  94. Christian Olesen
    Christian Olesen  • 4 weeks ago

    I honestly have started to love the blog editor. Themes like Flatsome have made it really easy to use blocks, and most premium plugins now supports blocks and shortcodes.

    I would love to make schema easier, but seeing the progress lately we are getting closer and closer to it.

  95. Paul Sherland
    Paul Sherland  • 4 weeks ago

    Howdy Joost,
    I understand the need to move away from the Classic Editor with my websites, but I dread the time lost in learning the Block Editor. Can you recommend video and/or text resources to help me get started in updating existing pages and posts from the Classic to the Block Editor?
    Thanks very much!

    • Barry
      Barry  • 4 weeks ago

      I’m waiting for a response to your questions along with you.

    • Paddy Landau
      Paddy Landau  • 4 weeks ago

      @Paul Sherland — I’m neither an expert in WordPress nor a prolific writer, yet it took me just minutes (without a tutorial) to understand the basics of the block editor, and only a couple of hours (incrementally, over time) to get the full hang of it.

      It’s easy. Just create a new post or page and get going.

      A quick google of “how to use block editor in wordpress” will give you plenty of tutorials, if you really feel that you need one.

      • Paul Sherland
        Paul Sherland  • 3 weeks ago

        Thanks Paddy, I’m sure you’re right. I’m changing themes for several clients (and myself) over the next couple of months and that can be the learning experience.

  96. VV
    VV  • 4 weeks ago

    The way Gutenberg was rolled out and the way the team handled product criticism has led us to experimenting with new platforms. We will stick with the Classic Editor for as long as possible.

    • akash
      akash  • 4 weeks ago

      I love Google Docs! It’s by far the best place to collaborate on writing posts. It’s real-time editing by multiple people makes it a breeze to collaborate on posts with people who might be on the other side of the world from you.

    • Sally Smith
      Sally Smith  • 4 weeks ago

      This ^.
      The block editor is a massive time drain when typing up longer blog posts, editing, and then revising.
      It slows me down to the point that I cannot afford to use the block editor. It is bloated and has essentially dumbed down wordpress to reflect the wix experience.

  97. Patrick B
    Patrick B  • 4 weeks ago

    I think on of the big issues has been the lack of themes that are fully built for the block editing experience. It is something quite different to try the editor on a theme not built to support it ( or just the minimum ) and a theme with well integrated styles and layout. When you have that it can be a really nice experience, even with its existing issues and quirks.

    • Stephen Bielawski
      Stephen Bielawski  • 4 weeks ago

      What advantages does it provide with running a small e-commerce site with 300+ products?

  98. Jerry Stevens
    Jerry Stevens  • 4 weeks ago

    This is timely for me because I just started getting familiar with the block editor. In fact, according to your post, my timing is perfect. I skipped the launch, waited for the dust to settle and just started using it a few days ago. I never want to hang on to old ways too long for fear I’ll be left behind.

    • Julian Park
      Julian Park  • 4 weeks ago

      I’m surprised by the number of negative comments on the block editor. I have been using it for 6 months now and have found it easy to use. I have also coverted older classic editor content as I update and refresh older blogs.

  99. Adjie Purbojati
    Adjie Purbojati  • 4 weeks ago

    Please provide FAQ and Howto schema to classic editor. Gutenberg is suck. I already learn it many times. But still it’s confusing and so much time consuming.

  100. Ian Harris
    Ian Harris  • 4 weeks ago

    Face it, you’ve made a boo-boo with Block Editor. Change for changes sake and perhaps above all not very well explained

  101. Linda Hobbis
    Linda Hobbis  • 4 weeks ago

    I tried Block Editor and hated it. I’d love to know how many of WordPress’ paying customers actually asked for it. I found it clunky, difficult to understand and time consuming. If you are running a business and using WordPress you simply don’t have the time to learn it. To me it smacks of tinkering for the sake of it. I’ll be sticking with the Classic Editor for as long as possible. I can certainly see no particularly convincing reason to change.

    • Gerry McLaughlin
      Gerry McLaughlin  • 4 weeks ago

      I find the block editor hard to understand and difficult to use. I have to use workarounds in order to be able to use it. And it is not doing anything for me.

    • Joost de Valk

      Hi Linda, when did you last try it? It really is tons better than 10 months ago now.

      • Lll
        Lll  • 3 weeks ago

        For older sites with a large number of articles – editing 900 articles anew using the block editor is not possible!

  102. Naomi Hanna
    Naomi Hanna  • 4 weeks ago

    still using classic editor, simple & habbitualy…

  103. Matt
    Matt  • 4 weeks ago

    “Unfortunately, when we look at our statistics, we see that a large segment of our users still uses the classic editor. This makes us sad, but also makes us want to explain why you really should start switching over.”

    You realize that you’re suggesting that the over 5 million people still using the classic editor are only doing so out of ignorance, right? Did it ever occur to you that many of us prefer to write html and therefore don’t want to mess with a visual editor? Or that the block editor messes up some existing plugins? So rather than spending hours, if not weeks, fixing bugs in someone else’s plugin, we just disable the block editor.

    “If you want to win in SEO in the next few years, I guarantee you’ll need to be on the Block Editor.”

    Why? You make a bold claim, but don’t back it up with any evidence.

    “Future versions will iterate on what the Block Editor already does, moving to site-wide editing, instead of just the content area.”

    If this happens (and I’m forced to use the block editor), I can almost guarantee that all of my future web projects will be done in something other than WordPress. And I’m pretty sure I’m not the only developer that feels that way.

    • Joy
      Joy  • 3 weeks ago

      “moving to site-wide editing, instead of just the content area.”

      If this happens (and I’m forced to use the block editor), I can almost guarantee that all of my future web projects will be done in something other than WordPress.

      This is why I won’t be using WordPress much longer, or keeping the existing version. I might try ClassicPress, but I might have to use something totally different.

    • Ryan Smith
      Ryan Smith  • 4 weeks ago

      This doesn’t make sense. You never could write correct html in the classic editor anyway. I actually hated it because it would always mess up the code. Now there is an actual html block that works correctly. If you want you could create the whole page in an html block. There just isn’t any reason to use the old classic editor that I can see. And of course for people who don’t know html it makes wordpress much more usable.

    • Joost de Valk

      Our schema blocks are almost impossible to build in the classic editor. You’d end up with clunky shortcodes or other ways of implementing that that simply aren’t as user friendly…

      Those schema blocks will help people get nice snippets in search results. If you don’t use them, one of your competitors will, soon enough. That’s my claim…

      • Olaf Mueller
        Olaf Mueller  • 3 weeks ago

        «Our schema blocks are almost impossible to build in the classic editor»: That sounds like a very convincing reason, indeed. How about when you use a Theme or a builder like Elementor? Will those play together nicely? Can I just rev up my SEO-content in Gutenberg, and then, for layout purposes, go back into Elementor?

      • Jim
        Jim  • 4 weeks ago

        I have a recipe website. More than 1000 recipes. All data stored in the Custom Field. Could you give a suggestion how to move to the Block Editor and use the data in the Custom Field since I can’t retype them all.

      • Luke
        Luke  • 4 weeks ago

        What about Elementor? With over 3 million active Elementor users, I hope there is something similar for Elementor pages?

        • Jeff Safire
          Jeff Safire  • 4 weeks ago

          I used Elementor for last two projects. Although several bugs were a nuisance, I found it mostly fantastic. Then, two weeks ago, I ran across Brizy. Soooo much better than Elementor! Much cleaner, easier, and more intuitive interface. My favorite feature is having all options for a given element pop-up right next to the element, rather than having to move to the left sidebar for setting options as in Elementor. Makes adjustments much quicker.

          Anyway, after playing with Brizy (with Astra theme) for several hours, it will be a long time before Block Editor can match it.

        • Tom wirt
          Tom wirt  • 4 weeks ago

          My site is designed in Theforest Theme by Wope Studio. It seems to be based on a block editor other than Gutenberg. Is this true?

        • Asif Mughal
          Asif Mughal  • 4 weeks ago

          Well… I am with you.
          Simply…
          Block Editor is not good for Coding websites.

          • Egbuachor Anthony
            Egbuachor Anthony  • 4 weeks ago

            I totally agree with you. Block Editor is something everyone should start using now. It is easy, and more User friendly than the classic editor.