Field data, not lab scores
Core Web Vitals taken from the sessions your buyers actually had, regressions grouped by the template that caused them, and daily SERP movement joined to the page that owns it. Planned, and not yet built.
Capabilities
The audit half of the suite, as planned: what is broken, which template it belongs to, and proof that it is fixed.
Core Web Vitals by template
URLs grouped by the template that renders them, then field distributions per template and device. Fix the layout, not a random URL.
Crawl diffs
Every crawl compared to the last: new 404s, changed canonicals, lost schema, redirect chains. Only what changed reaches the queue.
Daily SERP tracking
Position plus the anatomy of the result page, recorded daily and tied to the template that owns the ranking page.
An issue queue that closes
Each issue carries the fix. A scoped recrawl confirms the change and the ticket stays open until the field data agrees.
How an audit is meant to close
Crawl once, diff against history, group by template, then prove the repair. None of it exists yet.
- 01CRAWL
Render and fetch
Walk the site on a schedule and resolve every URL to the template that rendered it.
- 02DIFF
Compare to history
Compare the run against the last one and keep only what actually changed.
- 03FIX
One ticket per template
Each regression arrives once, with the URLs behind it and the field impact, instead of once per page.
- 04RECRAWL
Prove the repair
Re-run the affected templates and hold the ticket open until the field data agrees.
Compare
Two ways of auditing a site. No vendor is named and no benchmark has been run.
| CAPABILITY | Lab-score audits | KutayGO SEO Planned |
|---|---|---|
Where the numbers come from What a vital is measured on | A lab run on one machine, one URL at a time | Field sessions from real visitors, with the lab number beside them |
What a regression is attached to The unit of one row | A URL, one row per page | The template that rendered it, one row per template |
Rank data What a position is joined to | A position per keyword | The position tied to the page and the template that hold it |
Closing an issue When it counts as fixed | Marked done by hand | Held open until a recrawl and the field data agree |
History What you can look back at | The latest run | The diff between any two runs |
Transparent pricing
Every tier is the same product; what changes down the ladder is how many domains it covers. The prices are confirmed and current. Nothing here is on sale: there is no checkout, no trial you can start and no payment route behind this page, so every button below joins the waitlist instead.
Lira prices are shown to visitors whose address places them in Turkey. That decides what is displayed and nothing more: the lira price is paid with a Turkish card, and the country of the card is what settles it at checkout. There is no checkout yet.
EUR AND USD CARRY THE SAME FIGURE ON PURPOSE · HELD AT PARITY
Starter
One domain. For a single site you own end to end.
- 1 domain
- Template-level crawl, and the diff between two runs
- Core Web Vitals from field sessions, beside the lab numbers
- Daily SERP positions tied to the template that owns them
- Slack alerts and API access
Pro
Three domains on one workspace and one invoice.
- 3 domains
- Template-level crawl, and the diff between two runs
- Core Web Vitals from field sessions, beside the lab numbers
- Daily SERP positions tied to the template that owns them
- Slack alerts and API access
Scale
Ten domains. For an agency or a group of brands.
- 10 domains
- Template-level crawl, and the diff between two runs
- Core Web Vitals from field sessions, beside the lab numbers
- Daily SERP positions tied to the template that owns them
- Slack alerts and API access
Max Scale
A hundred domains and past it, on the same workspace.
- 100+ domains
- Template-level crawl, and the diff between two runs
- Core Web Vitals from field sessions, beside the lab numbers
- Daily SERP positions tied to the template that owns them
- Slack alerts and API access
Enterprise
LET'S TALKA scope agreed with you, and a named contact who owns it.
- Domain count agreed with you
- Log-file ingestion, after a privacy review
- Audits that run on a pull request and comment what they found
- SSO, SLA, DPA, audit exports
- A named contact who owns the account
One workspace, four modules, the same ladder on each
Every module is priced on the ladder above and none is on sale yet. The three others are described on their own pages, each with its own status.
Questions teams ask us
Join the SEO waitlist
SEO has not been written. If you want to hear when it is real, this is where that will happen, once there is something behind the form.
This page is a plan, not a product
Every finding above is drawn and the module is unwritten. When that changes, this page changes with it.