Wasn't that hard actually. xD
My blog "11 Best Practices for Writing API Documentation" made it to the 1st page of google for search queries:
This was exactly what I was aiming for and I did it. Feels great to see a result happen out of this. πͺ
π Just some #SEO statistics:
The volume of searches globally for these longtails:
β 1. You'll need a tool like Semrush, ahrefs, ubbersuggest... something that can give you insight into what longtail keywords you can aim and try to get positioned for.
β 2. Research. These tools will give you a general score of how hard it is to get positioned for these keywords (on a scale of 1 - 100). Since we are new, I aimed at high 30s and low 40s. Turned out "API documentation best practices" had a score of 43.
So I decided to go for it.
β 3. Content. Content MUST be relevant, and accurate and it needs to give value. You can't just put in random keywords in a text that doesn't make any real sense. I was helped by our developers and by a tool called Jenni.ai. Really cool tool, if you write content, check it out.
β 4. Sharing. It really helped that I shared this blog all over the place. The most helpful was a LinkedIn group called API documentation. Got a lot of engagement and the admins pinned my blog to the top. Still don't know who these incredible people are, but THANK YOU!
β 5. Sit back, relax, and occasionally repost it on Twitter, Indie Hackers and anywhere else your audience might be.
β οΈ It can take a couple of months, but definitely worth the wait, because right now, our website traffic is 80% organic, and it was 70% paid just a few months ago.