Preview
What it is.
It builds a keyword plan out of the queries developers type: pasted error messages, how to do something in a named language, tool comparisons and library function examples.
You use it to reach traffic a general SEO plan misses, starting with the errors your own support queue already sees. It also tells you to cut the introduction, because this audience bounces from preamble.
What you get.
- Query patterns specific to technical searchers, including error messages
- Error-message SEO, which is a page type most content plans miss
- Long-tail technical keyword strategy
- Guidance on competing with official documentation for the same query
- A read on what thin content costs you with this audience
How to set it up.
Install with npx add-skill jonathimer/devmarketing-skills.
Pull the error messages your own support and issue tracker see most. Those are search queries with commercial intent behind them.
Write one page per error, with the resolution first. A developer who pasted an error wants the answer above the fold.
Add how-to-in-language pages for each framework you support, because the language name is part of the query.
Build comparison pages for the tools you genuinely get compared against, since that pattern is in the query set.
Cut the introduction. This audience bounces from preamble, and the skill treats that as a ranking factor by proxy.
Pricing Plans
Free. MIT license.
Checked against the repo in July 2026.
Use cases
Turning errors into pages
The support queue sees the same errors on repeat. Pull the ones your issue tracker logs and hand them over; back comes a page-per-error plan with the resolution above the fold.
How-to pages per language
Developers search with the language name inside the query. Give it the frameworks you support; you get a how-to page set keyed to each one, since a general SEO plan never targets those shapes.
Competing with official docs
The top result for your target query is the framework's own documentation. The plan comes back with specific guidance for that fight, which changes how the page gets structured and paired with docs-as-marketing.
Best for
A developer tool with a blog nobody finds
Error-message and how-to-in-language pages reach an audience that a general SEO plan misses entirely.
Support tickets that repeat
Every repeated error is a page, and the traffic arrives with a problem you already know how to solve.
Competing with official docs
There is specific guidance for this, which matters when the top result is the framework's own documentation.