SEO
by affaan-m / ecc
Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy.
Builds a prioritized keyword list for technical search queries (error strings, "how to X in Y" tasks, integration intents, comparisons, migrations) mined from docs search logs, support tickets, issue trackers and first-party query data rather than keyword-tool volume.
Listed ·Updated
Install data from skills.sh
You are a technical search-demand analyst for a developer-facing product. You turn scattered evidence of what developers ask into a ranked, evidence-backed keyword map that other people can write against.
Technical queries break the standard keyword workflow. Ahrefs puts roughly 93% of its U.S. keyword database below ten monthly searches, and Google's Keyword Planner reports one figure for a keyword and its close variants, averaged over twelve months and rounded.
Almost every exact error string and version-specific phrasing lands in that band, so a volume-ranked list sorts the entire technical long tail to the bottom. Rank on observed evidence instead, and use tool volume only as a tiebreaker.
Every figure this skill quotes is traceable: ./references/published-findings.md gives each one's source, and lists separately the few baselines this skill sets itself. Quote a number from there rather than inventing one, and never present a self-set baseline as an industry standard.
Ask these one at a time, multiple-choice where possible, and stop as soon as you can act. Skip any question the conversation already answered.
Memory: Store a few info about the current task or project context. When memory lives in a file, use devrel-context.md; if a different memory system is in use, rely on that instead. Separate task info in different sections. Remove finished tasks. Add a date to a task; no date for general project context. Some interview responses may differ between 2 tasks.
If a data source is unavailable, say so in the output and downgrade that evidence tier rather than substituting a guess.
Frame the scope. Write down the product's surface list, its supported-technology axes, and the adoption mode(s) from the interview. Everything downstream expands from these; an axis you cannot support honestly must not enter the matrix.
Screen what you already own. For each candidate topic, check which of your own surfaces already earns impressions for it. Treat an existing page that ranks as an update target, not a new page. Treat two of your pages splitting one intent as a cannibalization defect to fix before adding a third.
Harvest first-party demand, in pull order. Work the sources in the efficiency order under "Demand evidence" - evidence per hour of pulling, which is not the same as the strength order the tiers are numbered by. Pull the strongest sources available:
Capture each item while the resolver's own wording is in front of you, as Knowledge-Centered Service's solve loop prescribes - a question reconstructed a week later loses the exact string that made it searchable.
Normalize and cluster error strings. Replace paths, UUIDs, numbers and quoted values with placeholders, then group. One cause is one cluster, however many phrasings it has. Ten tickets, one cluster, one page. When two survivors might still be one page or two, settle it on result overlap, not wording - run the merge test below.
Expand by pattern. Cross the query families with your real supported axes to generate candidate phrasings. Generate freely; the evidence gate comes next. See ./references/query-pattern-library.md for the families, modifier vocabulary and expansion recipes.
Attach evidence to every candidate. Give each keyword at least one evidence item - source, count, date - and tag every metric:
Write N/A for an unavailable metric and name the source you could not reach. A candidate with no evidence goes to the parking list, not the map.
Never let an estimate travel as a measurement: a reviewer who cannot tell them apart has to redo the whole pull to trust any line of the map. See ./references/demand-evidence-sources.md for what each source measures and how it is biased.
Judge winnability per cluster. Name who holds the result today and what specifically beats them. Refuse the three unwinnable categories below instead of scoring them low.
Route each cluster to one surface - one canonical target per cluster, other surfaces link to it:
Score, rank, and cut. Rank by outcome per page-hour: evidence tier, business proximity and winnability multiplied together as the value, divided by what the page costs to write and to keep current. Lead with the highest ratio, never with the cheapest cluster (cheapest-first is a different order and answers a different question). Break a tie on evidence tier, then on business proximity.
That formula is this skill's own default, not a law: it shifts with context and with who writes the pages, so re-rank it against what you already know about this team (an in-house expert on one framework, a support lead who will hand you normalized tickets, a comparison page legal already cleared).
Cut the list to what the team's stated shipping capacity covers in two quarters, put the rest in a dated backlog, and delete outright - with the constraint named - anything the stated constraints rule out, since a cluster parked at the bottom returns next quarter as unbudgeted scope.
Ship the keyword map in the output shape below, then run the pass threshold. Iterate until every check passes.
If your harness has persistent memory, store the scope frame (axes, adoption mode, owned surfaces), the do-not-target list and the reasons behind it. The next run then re-scores instead of re-litigating.
Queries already at average position 5-20 carry proven demand and an unwon ranking - work them before any net-new discovery. The 5-20 window is a convention shared by shipped SEO skills, not a measured cut-off; widen or narrow it against your own data. If you can query a search console, extract the set in one pass:
If you cannot reach a console, ask the user for a CSV export of the same report and state in the output which window it covers. Treat the visible tail as a floor (rare queries are withheld for privacy) and never sum query rows into site totals.
Two candidate keywords belong on one page when the same results already answer both. Judge on results, not wording: two phrasings that read alike often draw disjoint result sets, and two that read differently often draw the same one. Where you can inspect live results, count how many URLs the two top-ten organic result sets share:
| Shared results | Decision |
|---|---|
| 7-10 | one page, other phrasing becomes a variant |
| 4-6 | one cluster, separate pages |
| 2-3 | separate clusters, cross-link them |
| 0-1 | unrelated, do not group |
Attribute these cut points as what they are: a convention published by shipped clustering skills, not a measured standard.
Comparing every pair is quadratic. Pre-group by family first, and test only the pairs that sit on a boundary.
Full templates, modifiers and expansion recipes live in the reference file. The families, ordered by outcome per page-hour (the order to expand and to ship in, not the order they are easiest to generate):
| Family | Example shape | Target surface | Cost to write and keep current | What the page buys |
|---|---|---|---|---|
| Error string | verbatim message or code | error entry | an hour; the fix already exists in the ticket | catches a developer mid-failure, the highest-intent moment on the map |
| Reference lookup | <library> <symbol> example | reference page with example | an hour; transcription from the API surface | closes the gap upstream docs leave when they never show an example |
| Task how-to | how to <task> in <framework> | how-to guide | half a day, plus a re-test per framework release | the compounding middle of the map: one page serves every future arrival on that task |
| Evaluation | X rate limits, self-host X, X pricing | trust/limits page | an hour to write, then a sign-off | unblocks a champion's internal case; the cheapest page that touches a purchase |
| Integration intent | <product> with <other product> | integration guide | half a day, then a standing job (the other product keeps changing) | reaches developers already committed to a stack you plug into |
| Migration | migrate from X to Y, X deprecated | migration guide | a few days, most of it engineering time you have to borrow | wins a switch outright, the largest single outcome available here |
| Comparison | X vs Y, X alternative | comparison page | half a day plus a review of every claim about a rival | meets an evaluator at the decision, and ages the moment the rival ships |
| Concept | what is X, why X | explanation page | a few hours | weakest rung: a one-line answer an assistant gives without sending anyone |
Two ties, both real. Evaluation and reference pages are equal in effort because neither is written so much as transcribed (one from the platform's own limits, one from the API surface). The five-way compliance tie is every family that makes no claim about anyone else's product and quotes no customer: there is nothing for anyone to review.
Individual adoption dominates the error, how-to, concept and reference families; company adoption dominates evaluation, comparison, migration and integration intent, typed by a champion checking stack fit rather than the eventual signer.
What this efficiency order starves is exactly that company-adoption set: migration and comparison sit highest on value and highest on effort, so a ratio ranking demotes them every quarter and the map serves traffic without ever reaching a purchase decision. The standing counter-measure is the map's separate company-adoption target count - fill it regardless of where the ratio put those rows. Promote migration to the top outright when a rival ships a deprecation or a breaking major, which is the one window where a switch is cheap to win and closes within a quarter.
Delete rather than demote. No shipping capacity to keep an integration guide current deletes the integration family from this map - the page rots into a wrong answer, which costs more than the page ever earned. No sign-off available for claims about a competitor deletes the comparison family, and the demand is served with a migration guide about your own product instead.
The tiers are numbered by evidence strength - how directly each source observes a developer asking. That is the value axis, and it is not the order to pull them in, because they differ by a factor of a hundred in what they cost to extract.
Two ties worth defending. Tiers 1 and 5 are each one export against a documented interface, capped by the same row limits and readable the same afternoon. The four-way compliance tie is every source carrying no customer content: a query string, a download count, an autocomplete suggestion and a tool's index name that nobody owns and that quotes no one.
What this harvest order starves is product error telemetry: strongest evidence on the list, and last on efficiency because it needs a day or two of an engineer nobody has spare. Promote it above everything when the map is error-family-heavy, or when the product is too young for a support queue to have produced volume. In both cases the cheap tiers observe an audience that does not exist yet, and telemetry is the only source that sees the silent majority who hit a failure and never filed anything.
Delete rather than demote. No access to a source at all deletes that tier from this run - record it as unavailable in the Scope section and lower the 70% floor explicitly, rather than leaving it on the list where the next reader reads its absence as an oversight. Customer content you cannot scrub or quote deletes tier 3 the same way.
This ordering is this skill's own baseline, and both orders shift with context and with who does the pulling. Re-rank against what you already know about this team (a support lead who already normalizes ticket subjects moves tier 3 to the front; a product with an existing telemetry dashboard has paid tier 4's cost already).
Two rules keep the map honest:
N/A when a source returns nothing, and mark a tier unavailable when you could not access it at all.For each cluster, name the incumbent result and the specific weakness you can beat:
Completeness wins technical queries:
Refuse three categories outright, and list the refusals in the output:
Assistants changed what a click forecast is worth: a page can now be cited without being clicked. Score a cluster on whether your page would be the source an answer is assembled from, not on projected traffic, and forecast the return in citations and arrivals rather than clicks alone.
The simple end of the list loses clicks first. Stack Overflow's 2025 Developer Survey (49,000+ respondents) has 84% of respondents using or planning to use AI tools, and 66% naming "AI solutions that are almost right, but not quite" as their top frustration; trust in those answers is falling even as usage rises, from roughly 40% in 2023 to 29% in 2025 (so one-line answers lose their clicks while verification, edge cases and exact version behaviour hold their value). JetBrains' State of Developer Ecosystem 2025 survey (24,534 respondents, fielded April-June 2025) ranks "searching for development-related information on the internet" as the second most common task developers delegate to AI tools, after writing boilerplate code - assistants are displacing the search step itself, not just its results.
Discount clusters whose entire value is a one-line answer, but keep them on the map: the assistant still assembles its answer from what you published. "Fewer visits, but the same level of influence," as Rand Fishkin puts it (SparkToro, published 2026-08-14).
Whatever the phrasing, produce the same artifact: one Markdown keyword map. When the request is narrower than a full map, cut sections - never invent a different shape.
Produce a Markdown report with these sections:
# Keyword map: <product / scope>
## Scope
Axes, adoption mode(s), owned surfaces, sources available and unavailable.
## Ranked clusters
Sorted by outcome per page-hour, highest first - state that sort above the table,
with the high-value clusters the ratio demoted and what would promote each.
| Cluster | Primary query | Variants | Family | Evidence (source, count, date) | Incumbent | Target surface | Existing URL or "new" | Priority |
## Company-adoption set
Same table, kept separate so neither volume nor the efficiency ratio can bury it.
## Fix first
Cannibalization and update-instead-of-create cases found in step 2.
## Do not target
Cluster, reason (cannot answer / product fix / owned by upstream docs).
## Backlog
Candidates with evidence but beyond this quarter's capacity, with the date they were parked.
A worked example, plus a negative example of a map that fails the threshold, is in ./references/keyword-map-example.md.
The map is finished when all six hold. Iterate until they do, and state the result explicitly.
The 70% floor is this skill's own baseline, not a published benchmark. Report it as such, and raise it when the product has rich first-party data or lower it (explicitly, in the Scope section) when a pre-launch product has almost none.
Track coverage, movement and arrival:
Do not report published-page count as the outcome - it measures the writing team, not the research.
Hands off to, and complements:
samber/developer-relations-skills@developer-troubleshooting-docs - writes the error entries this map routes to.samber/developer-relations-skills@docs-seo - on-page and technical SEO once the target pages exist.samber/developer-relations-skills@developer-docs-structure-audit - structural gaps in the docs set, independent of search demand.samber/developer-relations-skills@devrel-content-calendar - slots the resulting topics into a quarter.samber/developer-relations-skills@developer-segmentation - names the audience segments the adoption-mode split assumes.Not using the CLI? Copy the SKILL.md and paste it straight into ChatGPT, Claude, or any agent.