How we optimized noktah.ai for SEO, AIO and speed
The AI audit we ran on our own site, what it did to the numbers, and the almost-free setup we use to keep tracking them.
This site is the whole public face of noktah. If you're reading this, you found it somehow: a link, a search, or maybe an AI assistant sent you here. We want more of the last two, so we pointed an AI agent at our own site and had it answer three questions.
- 01SEO: can search engines find the site, read it, and tell what it's about?
- 02AIO: can AI assistants like ChatGPT, Perplexity and Google's AI Overviews read it, and describe us correctly?
- 03Performance: do the pages load fast, on every kind of device?
This post covers how we audited the site, what changed, and the almost-free setup we use to keep track of it all. You can copy every piece of it.
The setup
We're self-hosting open-seo, an open-source alternative to Semrush and Ahrefs, and we've connected it to Google Analytics, Google Search Console and DataForSEO. Claude Code connects to it through MCP, so we can easily query it for analytics.
We host it on Cloudflare Workers under the free plan. The only metered part is DataForSEO, which charges per request with no subscription. Our instance is locked behind OAuth and MFA, so no, you can't look. Tough luck.
Fortunately, every piece of it is open source, so you can build your own.
We use Lighthouse for local testing, and open-seo runs it too, on mobile and desktop, as part of its site audits.
Measure
Google Analytics
Every visit, and the LCP, INP and CLS it reports
Search Console
What people searched for, and what they clicked
DataForSEO
Rankings, keyword data and Lighthouse runs
Collect
open-seo
Self-hosted on Cloudflare. Site audits, and one place to read the rest
Act
Claude Code
Reads all of it through MCP, and makes the fix
The audit
We ran the SEO, AIO and performance audits with a Claude Code orchestrator agent, and measured with Lighthouse. The orchestrator plans the work, hands the pieces to subagents, and puts together what they bring back.
We gave it seven skills, all open source:
Before and after
We won't bore you with every finding and fix. We'll get right to the juicy numbers.
Performance
96
Median of nine pages on mobile. It was 81 on 22 September.
Largest Contentful Paint
2.4s
▼ 43%vs 22 Sep
Median of the same nine pages, down from 4.2 seconds.
Accessibility
100
On eight of the nine pages, up from 92–96.
Lighthouse performance on mobile
Scores out of 100, before the audit and after it.
- 22 Sep
- 24 Sep
Although there's a significant change, SEO is something that takes some time to see real improvements.
On desktop, every page now scores 100 for performance, with the largest paint landing in 0.5–0.6 seconds.
›Accessibility and LCP, page by page
| Accessibility | 22 Sep | 24 Sep |
|---|---|---|
| Home | 96 | 100 |
| Work | 96 | 100 |
| Newsroom | 96 | 100 |
| About | 92 | 100 |
| Contact | 96 | 100 |
| Garmin article | 93 | 93 |
| Welcome | 96 | 100 |
| Privacy | 96 | 100 |
| Terms | 96 | 100 |
| LCP (seconds) | 22 Sep | 24 Sep |
|---|---|---|
| Home | 5.4 | 5.1 |
| Work | 3.8 | 2.4 |
| Newsroom | 5.7 | 2.5 |
| About | 5.5 | 2.6 |
| Contact | 4.0 | 2.3 |
| Garmin article | 5.8 | 2.3 |
| Welcome | 4.2 | 2.4 |
| Privacy | 4.0 | 2.3 |
| Terms | 3.9 | 2.3 |
