How to automate SEO articles with Wordstat and Codex
Vlad Voronezhtsev · · 13 min read
An SEO article automation connects Wordstat, one topic registry, project rules, and Codex in a controlled pipeline. A person approves the topic and publication, while the system collects demand, prepares the brief, drafts both language versions, and checks facts, images, links, metadata, and the website build.
What you will build
Demand
Registry
Brief
Article
Review
A controlled pipeline, not an unsupervised publisher
The system handles repetitive work while people keep the decisions. You approve the topic, claims, and publication. Codex reads the project rules, assembles the materials, creates the page, and checks that the website still works.
- works for services, stores, experts, and local businesses
- creates one approved article per run
- remembers published topics and prevents duplicates
- produces Russian and English versions under the same rules
What you need before you start
Website or project
A folder with website files or access to the publishing system.
Codex
The application that reads the project and follows a plain-language command.
Yandex Cloud
An account for Wordstat API access and a separate service account.
30-60 minutes
Time to describe the business, audience, restrictions, and priorities once.
Install Codex and give it the website folder
This pipeline does not require a Chrome extension. File work, checks, and publication happen in the Codex app. You can use the Opten extension separately when you want to improve an individual prompt in the browser.
- 1Open the official Codex app page, download the version for your system, and run the installer.
- 2Sign in with the ChatGPT account that has access to Codex.
- 3Put the website files in one folder. If the site lives in GitHub, ask a developer to help download the project once.
- 4Add a project in Codex and select the website folder. Do not select an entire drive or home folder.
- 5Begin with a read-only inspection. Allow automation changes only after you understand the report.
First command for the project inspection
Inspect this project without making changes. Find where articles, SEO fields, images, language versions, the sitemap, and the build command are stored. Explain the result in plain language. Do not publish the website or edit files.
Where you should stop and take over
The account owner handles sign-in, CAPTCHA, two-factor checks, terms, billing, and secret-key creation. Never paste an API key into chat or commit it to public website files.
Step 1. Wordstat
Find demand before you choose the topic
Start with 5-10 phrases a customer might use for your service. A dental clinic could begin with “dental implants,” “braces cost,” and “toothache at night.” A furniture maker could use “custom kitchen,” “built-in wardrobe,” and “made-to-measure closet.” The system expands these seeds and stores related searches.
Broad frequency
Reveals the size of a topic and related wording. Use it for discovery.
Exact phrase
Helps estimate demand for one formulation. Use it for priority.
A Wordstat number does not equal people, buyers, or sales. It represents query impressions for a period. Frequency helps compare topics, but it does not guarantee traffic.
How to connect Wordstat without coding
- 1Sign in to Yandex Cloud and create a billing account from the official guide.
- 2Create a separate service account for the automation.
- 3Grant only the roles required by the Wordstat API.
- 4Create an API key and save it in the system's secret store.
- 5Ask Codex to test the connection with one sample query.
Step 2. System memory
One topic registry prevents duplicates and disorder
Do not create a fresh brief folder every week. Keep one registry. It shows which topic is queued, deferred, or already published. The queue survives when the application closes, so the next run continues from the correct place.
Step 3. Business context
The brief adapts the same pipeline to any industry
The tools stay the same while the brief changes the content. No technical language is required. Answer like an owner or marketer: what you sell, who buys it, where you operate, why customers choose you, and which promises you cannot make.
- 01Which product or service has priority?
- 02Who is the customer and where are they located?
- 03Which questions appear before a lead or purchase?
- 04Which facts can you support with documents or links?
- 05Where should the reader go: form, call, catalog, or consultation?
- 06Which topics, wording, and competitors are excluded?
A second file describes the website itself
Codex needs to know where articles live, which page component is used, which SEO fields are required, what image sizes are accepted, which command validates the build, and how publishing works. Record these project rules once.
Step 4. Run
After setup, one plain-language command is enough
Write an SEO articleCodex takes the next approved topic, builds its brief from the registry and project rules, creates the article, localizes it, adds images, and runs the checks. Each run creates exactly one article so a person can read and approve it carefully.
Step 5. Control
Automation ends with a verified live page, not a draft
Even a strong draft is not ready to publish. The system must confirm technical integrity while a person reviews meaning and accuracy. Only after both checks does the topic move to published.
Facts
Every number, product claim, and rule has a source. No invented cases.
SEO
Unique title, description, H1, canonical, hreflang, schema, and sitemap.
Mobile
Text is readable, images are not cropped, and controls are easy to tap.
Build
The project compiles without errors and the live URL serves the new page.
Resources
Download the starter kit and complete it in your own words
The ZIP contains a ready-made business brief, topic registry, first-run guide, and publication checklist. Russian and English versions are included. No code is required: complete the files in a regular editor and give them to Codex with the project.
Safe start
Week one: one article, not a giant content factory
- 1Choose one websiteDo not connect every project at once.
- 2Write 5-10 phrasesUse customer language instead of internal jargon.
- 3Approve three topicsCompare demand, business value, and existing pages.
- 4Create one articleRead both versions and complete the checklist.
- 5Check the live URLExpand the queue or add a schedule only after this works.
This pipeline speeds up research and production, but it cannot guarantee rankings, traffic, or sales. Results depend on demand, the website, competition, the product, distribution, and time.
Opten course
Want to build the full content system around one project?
The course connects the task, prompts, copy, images, video, and website into one coherent project you can show to clients and continue developing.
View the course programOfficial instructions
Interfaces, prices, and service limits change. Check the current documentation before setup. The links below were reviewed when this article was published on August 6, 2026.
