Aloha, its 2023 and we pay big money to keep our shops, all I ask is if there is any possibility to respond to a comment on blog posts?? This seems so trivial and don’t understand why Shopify doesn’t make this happen? Blogs that could create potential customers and drive traffic are so archaic it leaves me wondering what is the point..
Engagement is valuable! Please resolve asap, thank you
Hey there, @jjmagnificent . Thanks for taking the time to reach out to folks here in the Shopify Community with your feedback around our current blogging system. My name is Imogen. It’s good to meet you!
I appreciate you taking the time to reach out to us and provide feedback around our blogs. We’ve received a lot of feedback around this in the past, and our developers are absolutely aware of the value being able to reply to these comments directly via admin would bring.
Unfortunately, I have no information I can share at this time regarding when such a feature will be made available. However, I’ve gone ahead and made sure that your feedback was seen here by our developers. The more feedback requests we get, the better, so thank you for making sure we had something to pass along to folks internally.
MC here - I’m the founder of Turboblog, a blogging app that is an alternative to the built-in Shopify blog. Turboblog has a robust threaded commenting system with the ability for readers and authors/admins to reply directly to comments on blog posts. You can take a look at a sample post with a few comments at the end of the post here.
Turboblog has a 10 day free trial so I’d love for you to try out the commenting system and let me know what you think. Feel free to reach out to me directly with any questions!
Seconding this notion, I honestly can’t believe you can’t do something as basic as respond to blog comments. Shopify needs to do a better job supporting their blogging platform, alot of merchants use SEO to grow their store and need to engage with their audience.
Yes, I completely agree. This is a resource that we need on Shopify. Please resolve this issue!