Many writers use Grammarly daily, and it’s super sad that after being Ghost’s customer for the second year, Grammarly still doesn’t work properly in the editor.
When you try accept suggestions, it just doesn’t edit the text - or even worse - sometimes pastes the suggestions in a completely random place on the blog and you don’t even know.
I hope this finally gets fixed as a Christmas / New Year’s gift for us!
That’s a shame!
Given the support they provided a few years ago was reasonably good.
Not Grammarly, so may not be relevant. I use LanguageTool integration, which does appear to work with the Ghost editor. There’s an extension for Chrome and probably other browsers (I use Vivaldi), and it works well with Obsidian which I use for most of my writing. You can self-host if you want, though the features are limited.
LT worked in Safari for a while until it didn’t. I’ve tried QuillBot as well. I had to open a ticket with Ghost support. It’s frustrating that these grammar-checking tools don’t work while writing native posts.
Updated | August 6, 2026
I think that I figured out the issue. I accidentally had set up a second profile in another browser window. This error caused several extensions to work intermittently or not at all, especially on the grammar side. D’oh!
Is the paid-for LT product different in implementation of its function to the self-hosted one? I’d be surprised. The self-hosted LT works just fine with the Ghost editor. There are fewer
features, but the way they are implemented is likely similar. I use it all the time, as ~2 years ago on Vivaldi (a Chrome variant).
Thanks, @fatshark.
Yes, the paid version of LT in Safari. I’m using Ghost Pro. I don’t know if that’s driving the problem.
I’m on MagicPages. @jannis might know if there are any differences in the editor, but I doubt there are.
No differences at all with the open source version (which is also what Ghost(Pro) runs).
I am building a bespoke Safari extension based on my custom Claude skill. I’ll see if I keep it after MacOS lets users build their own extensions via natural language next month. I’m leaning towards open-sourcing it.
A few other extensions aren’t working properly, such as the Notion Web Clipper. Damned if I can’t figure out the cause.
Ironically, your example shows probably my biggest grammatical pet peeve.
