Signup to the waiting list!
In a previous lab post I talked about SEO for programming blogs and how organic traffic is a great way to get people to read what you have to say.
With all these visitors coming from search engines, what are you going to do?
First, forget advertising. It does not work, especially when you target developers. I am talking about PPC mainly. Unless you are CSS Tricks or some other huge site, you will make peanuts.
The thing that works with developers is
- pro content
in any case, they should be yours, not belonging to someone else / affiliates, because of margin reasons. If you sell an ebook for 10$, you get ~9$ after commissions. All it costs to you is a time investment up front.
I decided to start with an ebook. People liked it, validated my idea, and I wrote another one.
I then decided to create an online course. I already created 2 online courses in the past, but this is a story for another post.
Don’t make your email list call to action just be “get my next posts in your inbox”. That works, but I found that works best is to create something, and lead up some anticipation for it, and promise your people to deliver them greater stuff (and do it, of course!)
For example when I decided to create an online course about Vue.js, I drafted a timeline and I knew I had 70 days until my course was live.
I immediately put a CTA saying :
“I’m going to learn Vue full-time for 2 months, and I’ll create a resource for you to learn it quickly as well, with tutorials and projects, working examples and screencasts. I will send you the free content I create 👨🏼💻 and I will keep you up to date with the course and offer you a big discount when the course is released. Stay in the loop!”
That 10x-ed my mailing list sign-ups from 2-3 per day to 25 per day (I couldn’t believe it).
I think that if you center your blog around teaching something, creating an infoproduct like a book or a course is a perfect match, because people arrive to your site in learning mode, and they are sponges ready to absorb all you have to offer.
Another kind of product might not be aligned with what you write, and maybe in that case it’s best to create a blog that talks about your experience creating it, what you learn, document the journey and so on. But this is just a hint, not a rule of any kind.
More lab tutorials:
- The stack I use to run this blog
- 8 good reasons to become a software developer
- SEO for developers writing blogs
- Review of the book The 4-Hour Work Week
- Build a lifestyle business
- Build your own platform
- As an indie maker, what kind of product should you build?
- Create your own job security
- Developers, learn marketing
- The freedom of a product business
- Generating value
- Have a purpose for your business
- The idea is nothing
- The niche
- Remote working for software developers
- Product / market fit
- The best podcasts for frontend developers
- Why should I create an email list?
- Disconnect time from money
- The scarcity principle applied to software products
- The social proof principle
- How I added Dark Mode to my website
- My notes on the Deep Work book
- The pros of using a boring stack
- How to estimate programming time
- On going independent as a developer
- How to learn how to learn
- Why interview questions for programming jobs are so difficult?
- Do I need a degree to be a programmer?
- Everyone can learn programming
- How to be productive
- How to get the real number of pageviews of a static site
- Have you filled a developer bucket today?
- How I record my videos
- All the software projects I made in the past
- Tutorial purgatory from the perspective of a tutorial maker
- Every developer should have a blog. Here’s why, and how to stick with it
- Having a business mindset for developers
- How to write Unmaintainable Code
- What is Imposter Syndrome
- How to work from home without going crazy
- How I prototype a Web Page
- You should be the worst developer in your team
- How to start a blog using Hugo
- Write what you don't know
- How to block distractions using uBlock Origin
- Coding is an art
- I wrote 1 blog post every day for 2 years. Here's 5 things I learned about SEO
- Dealing with the fire
- On being a generalist
- The Developer’s Dilemma
- My plan for being hired as a Go developer. In 2017
- Productivity gains of using a Mac and an iOS device
- How to go from tutorials to your own project
- This is my little Digital Garden
- How to start freelancing as a developer
- Sharing the Journey Towards Building a Software Product Business
- Subfolder vs subdomain
- How I use text expanding to save time
- Software is a superpower
- I love books
- How I decided to create a new projects management app
- On using IndexedDB as the main database