ELIKO // SYS
X 000  Y 000 OP_MODE AUTO

LIVE

SEO content machine

One console that runs the SEO of a clinic website, with search data, keyword research, content targets and WordPress on one screen, and every published article checked each night.

2026 · Own product · Business automation, AI

About

SEO work tends to scatter across spreadsheets, tools and logs until nobody can tell whether it is running. The SEO Machine brings it onto one board. Demand comes from Search Console, difficulty from a keyword tool, content targets from a writing assistant, and the live pages from WordPress. Each cell opens the screen that does that step, nothing reaches the live site without a press, and every article is checked again each night.

Why I built it

The clinic's search traffic was mine to grow, and after a few months the work had spread across a spreadsheet, a crontab and a log file, to the point where I could not say whether anything was actually running. That is a bad place for a system to be. I wanted one screen that answers the question every morning, shows every article at every stage, and changes nothing on the live site unless I press the button. The console is that screen, and it has kept the whole pipeline honest ever since.

What it does

One board for the whole pipeline
Every article as a row, every stage as a cell, sorted by what is at stake.
Real demand first
Opportunities come from what the site already ranks for, not from a keyword tool's guesses.
Measured, not guessed
The quality gate counts what can be counted and uses a model only for what needs reading.
A press for every live change
Edits go one widget at a time, the old text is backed up and the cache is cleared.
Checked every night
Every published article is re-checked, and a quiet night is recorded as quiet.
English and Hebrew
The whole console in both languages, right to left included.

How it works

Four sources feed one board. Each cell opens the screen for that step, edits go one widget at a time, only an explicit press publishes, and nightly loops record what they saw.
Four sources feed one board. Each cell opens the screen for that step, edits go one widget at a time, only an explicit press publishes, and nightly loops record what they saw.

Built with

Python · Vanilla JS · SQLite · WordPress · Google Search Console API · Ubersuggest · NeuronWriter · Claude

At a glance

STACK
Python · LLM agents · WordPress
STATUS
live

My role. Designed and built it end to end and set what may reach the live site.

Screens

The dashboard. Every number names where it came from.
The dashboard. Every number names where it came from.
Where everything stands. One row per article, every stage a cell, every cell a link to the step itself.
Where everything stands. One row per article, every stage a cell, every cell a link to the step itself.
A live article read from WordPress with its blocks counted and the date of its last nightly check.
A live article read from WordPress with its blocks counted and the date of its last nightly check.
Answer-engine checks, each one named, with no model involved.
Answer-engine checks, each one named, with no model involved.
The same console in Hebrew. Opportunities ranked by real demand.
The same console in Hebrew. Opportunities ranked by real demand.
Rank tracking with position history and movement per keyword.
Rank tracking with position history and movement per keyword.