Great example of programmatic SEO from Snyk.
They created a page calledย snyk advisor.
It is a repository of pages about open-source packages.
Each page is created automatically out of publicly available information.
Enhances it with Snyk-generated security scans and reports.
It builds awareness for other Snyk products in the security space.
A lot of those pages rank high in google for the {package} keyword which is incredible.
And when people land on the package report page the CTAs to Snyk products push conversions.
Marketing through free tools is powerful. And Auth0 implemented it beautifully.
In an old article from Gonto I read about some free tools that Auth0 created years ago.
And those tools are still generating traffic and leads today.
And they are helpful to developers and make the Auht0 brand even more appreciated by the community.
One of those tools is JSON Web Token Debugger.
So how this works for them is this:
Now, Gonto suggested that is important to do it on a separate domain to make it less promotional.
I am not sold on that especially when I know there are companies like @VEED.IO that build "SEO tool clusters" in the /tools/ subfolder of their page and crush it in search.
But either way, if you can solve a real problem your target devs have, no matter how small, you should be able to get some developer love (and $) from the value you created.
Great SEO tactic.
What folks from Cronitor did is:
This can be used for many dev-focused tools as by definition they use commands which can be templated.
I've heard about it originally from Harry Dry over at https://marketingexamples.com/seo/cronitor
โ
How to write a "What is {MY CORE KEYWORD}" article that gets to the top of HackerNews? ๐
First of all, almost no one succeeds at that as you write those articles for SEO distribution, not HN distribution.
To get an SEO-first article on HN your content quality bar needs to be super high.
But you can do it.
PlanetScale managed to get their "What is database sharding and how does it work?" on the orange page (kudos to Justin Gage!).
Here is what was interesting about that article:
๐ฆ๐๐ฝ๐ฒ๐ฟ ๐๐ผ ๐๐ต๐ฒ ๐ฝ๐ผ๐ถ๐ป๐ ๐ถ๐ป๐๐ฟ๐ผ.
โข โ No "In today's fast-paced data-driven world enterprises work with data" stuff.
โข โ
Justย ย "Learn what database sharding is, how sharding works, and some common sharding frameworks and tools."
๐๐ถ๐๐๐ถ๐ป๐ด ๐ธ๐ฒ๐๐๐ผ๐ฟ๐ฑ๐ ๐๐ต๐ถ๐น๐ฒ ๐ฏ๐๐ถ๐น๐ฑ๐ถ๐ป๐ด ๐ฟ๐ฎ๐ฝ๐ฝ๐ผ๐ฟ๐ ๐๐ถ๐๐ต ๐๐ต๐ฒ ๐ฑ๐ฒ๐ ๐ฟ๐ฒ๐ฎ๐ฑ๐ฒ๐ฟ.
๐ Speaking peer to peer, not authority-student:
โข "Youโve probably seen this table before, about how scaling out helps you take this users table, all stored on a single server:"
โข "And turn it into this users table, stored across 2 (or 1,000) servers:"
โข "But thatโs only one type of sharding (row level, or horizontal). "
๐จ๐๐ถ๐ป๐ด ๐ท๐ฎ๐ฟ๐ด๐ผ๐ป ๐ฎ๐ป๐ฑ ๐๐ป๐ฑ๐ฒ๐ฟ๐๐๐ฎ๐ป๐ฑ๐ถ๐ป๐ด ๐๐ผ๐๐ฟ ๐ฎ๐๐ฑ๐ถ๐ฒ๐ป๐ฐ๐ฒ
Things like:
โข "Partitioning has existed โ especially in OLAP setups"
โข "Sifting through HDFS partitions to find the missing snapshot "
๐๐ฐ๐๐๐ฎ๐น๐น๐ ๐ฒ๐ ๐ฝ๐น๐ฎ๐ถ๐ป๐ถ๐ป๐ด ๐๐ฒ๐ฐ๐ต๐ป๐ถ๐ฐ๐ฎ๐น๐น๐ ๐ต๐ผ๐ ๐๐ต๐ถ๐ป๐ด๐ ๐๐ผ๐ฟ๐ธ
๐ฅ Look at the section "How database sharding works under the hood" with subsections:
โข Sharding schemes and algorithms
โข Deciding on what servers to use
โข Routing your sharded queries to the right databases
โข Planning and executing your migration to a sharded solution
๐ ๐๐ผ๐ป๐๐: ๐ฝ๐น๐๐ด ๐ถ๐ป ๐๐ผ๐๐ฟ ๐ฝ๐ฟ๐ผ๐ฑ๐๐ฐ๐ ๐ด๐ฒ๐ป๐๐น๐
Section "Sharding frameworks and tools" shares open-source tools (every dev, but HN devs in particular like OS projects).
And there as an info box, you have the info that Planetscale comes with one of those OS projects deployed.
Just a beautifully executed piece of content marketing.
This is how you write dev tool JTBD blog posts.
Masterclass of writing this type of content from @WorkOS imho.
Deep 2000 word guide that explains how to add webhooks the your application.
Goes into examples, best practices, everything.
One thing it doesn't do?
It doesn't push the product left right and center.
In fact, the only CTA is hidden in the very last sentence of the very last section.
Why?
Because most likely, the reader's intent is around understanding the problem at this point.
They want to understand what adding webhooks to their app really means from the practitioner's standpoint.
And they did that beautifully.
Could you have pushed the product a bit more? Sure.
But by answering the actual questions devs came here for they managed to build trust.
And I am sure got their fair share of click-throughs and signups anyway.