SEO professionals
Repeat commercial keyword research across your projects with explicit checks and retained evidence.
One reusable skill package.
Commercial keyword research in your AI workspace.
Get the research instructions, Python helpers and validation rules. Apply the skill to your own projects with your own approved data sources.
This is a package enquiry, not a research commission. Release contents, your setup and delivery terms are confirmed before payment. The button opens a package-specific email; you can also copy the enquiry below.
Instructions, scripts, validators, setup documentation, workbook specification and examples in the agreed release.
A commercial semantic-core workbook: reviewed queries, intent clusters and decisions for existing or proposed pages.
You are buying a reusable agent toolkit, not a promise that Dima automatically researches your website for you.
Repeat commercial keyword research across your projects with explicit checks and retained evidence.
Use a consistent research, cluster-review and handoff method. Client-project usage terms are confirmed before payment.
A fit if you can work in an AI environment, connect data and review business decisions. Not a URL-in, finished-research-in-a-minute promise.
The package combines research instructions, Python helpers, validation checks, setup documentation and worked examples. We confirm the included files and environment requirements before purchase.
| Package part | What it gives you |
|---|---|
| Instructions · SKILL.md | The commercial research sequence and decision rules. |
| Scripts and agent configuration | Python helpers for source processing, SERP groups and supporting actions; agents/openai.yaml. |
| Validators and tests | Discovery, intent, page-decision and JEV receipt checks. |
| Setup documentation | Environment requirements, data preparation, first offline check and research launch. |
| Output specification | One hierarchical workbook, page actions and query-level JEV marks. |
| Worked examples and context | A teaching commercial conflict, offline fixtures and sample output structure. |
Illustrative example: how engine-repair queries become clusters and page decisions.
Auto repair: confirmed services, target market and the existing engine-repair page.
engine repair · engine diagnostics · diesel engine repair. In your project, each query retains its data source and measurement date.
All three queries enter one proposed cluster, although diesel repair may represent a separate commercial service.
Every query is reviewed. Diesel repair moves to a distinct candidate; JEV independently checks the complete final cluster membership again.
The current URL gets keep/update; diesel repair gets create only after separate page gates. Otherwise section/review_data.
The retained iNevidimka query excerpt below demonstrates sourced data and page ownership. It does not substitute for a full commercial research run.
Not just a list of words: raw queries become clusters, then clusters become page decisions.
Real excerpt from iNevidimka research. Snapshot: October 26, 2026; Google Ads US. Volumes come from the saved core, not a fresh measurement. Grouping and page ownership below show editorial decisions based on that data.
Topic → Skills page → that page’s queries with search volume. Homepage, About and other utility pages are outside this research excerpt.
/ai-for-seo/Update/ai-for-seo/keyword-research/This excerpt contains only queries with retained source volumes. It illustrates one branch of the page architecture, not the full keyword universe. Do not sum close variants as independent demand.
For every branch: page name, URL, hierarchy, query list with volume, action and priority. Page creation requires separate approval.
Do not turn 90 + 10 into a traffic forecast. Close variants may overlap in provider data. No KD or CPC values are claimed for these rows.
ai keyword research · keyword research with ai
Different wording alone is not a reason for two URLs.
ai keyword research tool
Software demand does not prove demand for our package. A separate page is not approved.
/ai-for-seo/keyword-research/Three CSV views and source notes. Sample output only, not the skill package or a full validated workbook.
The workflow checks market coverage, query grouping and page decisions before handing over the semantic core.
The agent examines relevant competitor service pages as well as your existing site, so the research can identify missing commercial topics.
A served-location allowlist and provider-aware equivalence checks stop unrelated places and repeated phrase metrics from inflating the core.
A complete membership audit reviews retained queries. The separate JEV check covers 100% of retained queries against their actual final cluster.
Technical SERP groups, customer tasks and page decisions are separate layers. A subservice does not automatically become a standalone URL.
Manual delivery starts with a package enquiry. The supported environment and exact installation steps are confirmed for the release you receive.
Name your AI environment and available data. Confirm the included files, delivery route and usage terms before payment.
Unpack into the agreed workspace and load SKILL.md in the selected agent using the release guide. Follow the setup guide for the AI workspace agreed before purchase.
Use the documented Python environment and dependencies to run the supplied checks. This tests local processing and guardrails, not paid data collection.
Confirm the business, market and commercial scope, then authorize specific provider batches. The agent follows the skill, preserves evidence and returns the workbook.
Automated checks establish the conditions they actually test. They do not guarantee that every commercial recommendation is right.
The skill targets commercial keyword research. Informational content needs a separate layer. Decisions require review; research does not include writing or publishing pages and does not guarantee rankings or leads.
| Requirement | Source / tool | What the $50 covers |
|---|---|---|
| Required | Tool-enabled AI environment and Python | The package does not include a model subscription or universal installation. |
| Required | Keyword/volume data and comparable Google SERPs | Approved sources or suitable saved exports; accounts and paid requests are separate. |
| SERP option | XMLRiver or a configured DataForSEO route | Use XMLRiver or an available DataForSEO connection agreed for your workspace. Provider accounts and requests are separate. |
| Required for final delivery | JEV responses for every retained query | Instructions and receipt validation, not provider credits. |
| Required for the workbook | Commercial SEO Semantic Core format and template resource | The workbook specification is included; confirm any additional template files before purchase. |
| Optional | GSC, Ahrefs/Semrush and additional sources | Your authorized environment or exports; a tool mention is not a shipped universal adapter. Search volume and keyword difficulty keep their provider context; Google Search Console records observed site visibility, not market-wide demand. |
A reusable package for your AI workspace. Not a one-off keyword research service delivered by Dima.
The next step is a $50 package enquiry. Before payment, confirm the included files, environment fit, delivery method, usage rights, updates, support and applicable refund terms. Checkout and automatic delivery are not connected here.
Need the research done for you?Model access, keyword/SERP APIs and JEV usage are separate.
I would like the AI Keyword Research Skill package for $50. My AI environment: [environment]. Data: [sources or exports]. Projects: [own/client]. Please confirm release contents, setup, delivery, usage rights and support/update terms. This is a package enquiry, not a research commission.
No. You receive the agreed reusable package. Your semantic core is the output of running it in your environment with your data. Research carried out by Dima is a separate offer.
No. The price is for the package. Model access, keyword/SERP data, JEV and actual paid requests are authorized and paid separately.
Tell us whether you plan to use the package on your own or client projects. We confirm permitted use and redistribution terms before payment.
No such promise is made. Installation and a test run must be checked in the specific environment with its dependencies and data access. The supported setup is confirmed for the delivered release.
No. It shows the structure of a research deliverable. It is not the installable package and does not contain the full skill instructions, scripts and validators sold as the separate $50 product.
We confirm support and update terms for your package before payment. Ask which updates and help are included in your quote.
Cookies, briefly. Essential ones run the site; analytics cookies (Google) only switch on if you say yes. Details in the Privacy Policy.