One system, shipped in versions, the way AI models are. DT 1.5 is the version running now: it reads your site the way search engines and AI assistants do, tells you what is broken in plain language, and drafts the fix. You approve, it ships. That is the whole loop.
Most AI products blur this line on purpose. We refuse to. Green means you can use it today. Amber means it is in development and does not exist for you yet, no matter how good it sounds.
A real crawl of any URL you give it, on demand: page metadata, headings, robots.txt and AI-crawler rules, schema.org structured data, llms.txt, and sitemap coverage. Findings ranked by severity, written in plain language.
Where the audit finds missing structured data, DT 1.5 drafts the exact patch from your real page content. The suggestions are deterministic, built from what is actually on your site, not language-model guesswork.
Every drafted fix lands in a queue where you approve or reject it. The workspace, task states, and approval flow are real in the dashboard today.
Checking how your business appears inside ChatGPT, Perplexity, and AI Overviews answers. In development for the dashboard; runs on your own AI provider key when it ships, bring your own key.
Wasted-spend flags, pacing checks, and drafted exclusion lists. In development. DT 1.5 does not run or manage ad campaigns today.
Consistency checks across your listings and drafted on-voice responses. In development. DT 1.5 does not manage your brand today.
DT 1.5 never acts on its own. It is built around one rule: the system proposes, you decide.
Give it your URL. It crawls your site live, the way Google's and OpenAI's crawlers do.
Findings come back ranked and translated. Not "missing JSON-LD", but "AI assistants cannot read your product pages, here is why it matters".
Drafted fixes wait in your queue. You see exactly what would change before it does. Reject anything, no questions.
Approved fixes are yours to apply, with each patch ready to paste. As lanes roll out, more of this closes into one click.
AI models earn version numbers by getting measurably better between releases. We hold DT to the same standard: DT is the agent and system, 1.5 is the version you are using, and the capability board above is its honest spec sheet. When the ads, branding, and content lanes clear our bar, the version number moves and the board moves with it.
To be precise about what DT 1.5 is not: it is not a foundation model MGO trained. It is the agent that does the work, and where that work needs a language model it runs on the leading models you bring with your own key, the way Claude Code and Codex do.
What never changes between versions: the approval gate, the plain language, and the refusal to claim capabilities that do not exist yet.
No, and we will not pretend it is. DT 1.5 is MGO Data's agent and system: the thing that does the SEO, AI-SEO, and drafting work. The audits and schema drafts are deterministic, no language model involved at all. Where DT 1.5 does need a language model, it runs on the leading models you connect with your own API key, the same bring-your-own-key model as Claude Code and Codex. Your keys go provider-direct and are never sent to MGO.
Real. The dashboard runs a live crawl of whatever URL you enter and the findings come from your actual pages. When the live service is unreachable it falls back to a recorded sample of our own store, and it is labeled as such on screen.
No, and that is the point. Every finding is written for a founder, not a developer. Where a fix is technical, DT 1.5 drafts it for you so you can hand it to whoever touches your site, or paste it yourself.
Not today, and we will not imply otherwise. The ads lanes are in development. If you need ads handled now, that is what the human team is for.
They are two different things. The team is people doing the work for you, by application. DT 1.5 is software you drive yourself. The team uses DT 1.5 as a tool; DT 1.5 does not pretend to be the team.
The audit takes about a minute and does not ask for your card.
Open the DT 1.5 dashboard