Blog post roast - Input from (native) English speakers needed
Hi there,
I just uploaded the initial post to our startup’s blog. As I am usually not a content creator, I need your input on the style and readability. I will definitely still make changes to the post, but I need more input on where to improve.
I am using Yoast SEO as support and so far which covers two areas: readability and SEO. I already optimized the SEO part, but I am a bit stuck on the readability part. My main problem is that as a German, I like long sentences which has a negative impact on the readability score. It feels unnatural to me to shorten most of the sentences and since our product is a specific B2B and not B2C product, I am not even sure if it is really necessary.
I can imagine that I am not the only one having this problem and many of you have already overcome it. Feel free to comment on anything you’re stumbling upon, your help is greatly appreciated!
Here's the link: https://blog.campr.biz/camper-to-campr-to-beta/
Cheers,
Hannes
I took a look. There were a couple minor grammar issues. I think it's ok as a blog post, but not great.
It's very dense and wordy, and takes a long time to explain some of the core features. I think someone would have to be very interested in solving the problem and would have to be in "research mode" for this to be useful.
Have you read some basics on writing copy? English aside, I think it would help you a lot to focus on Problem -> Solution. Have some bullet points ready to make it clear what you're offering. If your intro isn't very good, people drop off very quickly in most cases.
I'm not great at copy, but my first thought is: If you want to go into detail, I would start light, back story and/or hammer some core points (maybe intrigue with the acronyms and standards), then mention the sign up in a sentence or something, then dive in more.
Hi Andrew,
thanks for your time and feedback! I will have it proofread next time. This was basically only a trial run.
I will try to rewrite the text tomorrow and make it a bit lighter. I created this post as a sort of teaser, explaining our roots and scratching the surface on what we have to offer. My plan was to create an outlook and more in depth content on single modules in the following weeks.
I will keep your suggestions in mind and read a bit more about copy.
Yep, and there's always a place for what you're writing. Getting structure down and making it engaging is a journey :)