For my work on geo.codes
✅Done this week
- Autogenerated Python, JavaScript, Go, and PHP SDK libraries
- Linked to the SDK documentation hub in the onboarding email
- Added a content hub in the documentation for them
🎯 Actionable goals for next week
- Automatically add subscribers to my emailoctopus list
- Make an onboarding email sequence
- Make autogenerated documentation pages from the openapi spec
🙃 Struggles if any
- Not sure if my SEO approach is paying off - getting some organic traffic from Bing (?) and Yahoo (??) but not Google yet.
- The OpenAPI generators are pretty good, but not amazing. The READMEs they generate are very thorough, but kind of confusing. There are also lots of oddities in the autogenerated output. OTOH, I've been able to make working code with the generated libraries within 1 minute.
hey Jacob, what are you trying for SEO? would be good if there is any measurable metrics.
Ahoy - I started thinking about SEO like 3 weeks ago, starting from basically nothing. Since the most common thing I've heard is "it takes 3-6 months to really see the impact," it's not clear to me whether I'm on the right track.
What I've tried
Metrics:
What I'd like to try but haven't yet:
Interested to know how you did this?
I generate an OpenAPI spec using swaggo
It produces this spec: https://api.geo.codes/swagger/doc.json
This spec can be used to autogenerate a documentation page: https://api.geo.codes/swagger/index.html
Or you can plug it into something like OpenAPI Generator to produce client libraries. They have varying quality levels, so I don't feel like I've 100% solved this yet, but it's much handier than writing all the libraries yourself