My Next.js site was completely invisible to ChatGPT, so I built a tool to fix it.
Hey hackers,
I was experimenting with AI crawlers recently and got hit with a harsh reality check: most modern SPAs (React, Next.js) are practically invisible to bots like ChatGPT, Claude, and Gemini.
Because AI bots don't execute JavaScript well, if your site lacks proper SSR, they often just see an empty body tag.
I tested my own company's website expecting a decent result. It had no /llms.txt, no JSON-LD structured data, and pure client-side rendering. It scored a 24/100. 💀
I realized standard SEO isn't enough anymore. We need AIO (AI Optimization). So I spent a few nights building AIO Checker.
Here is how it works:
1. You drop your URL.
2. It scans for 7 key AI-visibility factors (robots.txt permissions, llms.txt, SSR, etc.).
3. It gives you an instant 0-100 score.
The feature I built for myself:
I hate fixing these things manually. So I added a feature that exports a detailed .md audit file. You literally just download it, paste it into Cursor, Windsurf, or Claude, and tell the AI to "fix my codebase based on this audit."
The initial scan is free, and the full export is $4.99.
Would love for you guys to test your own sites. I bet a lot of you will be surprised by what ChatGPT actually sees when it tries to read your landing pages.
Let me know what you score, and please roast the UI/UX so I can improve it!
this is a real gap. been dealing with the same thing building openslop.ai - our docs and landing pages were essentially invisible to AI assistants because of client-side rendering. the fix was straightforward technically (SSR + structured data) but most founders dont even know to check for it.
the audit-to-cursor pipeline is clever. thats basically the workflow every dev is already using - find problem, paste into AI, fix. you just formalized it.
one suggestion on distribution: instead of selling individual scans, consider making the free scan more shareable. let people embed their score badge on their site or share it on twitter. that creates a viral loop where every scan becomes marketing for you. the $4.99 price point is good for impulse buys but discoverability is your real bottleneck right now.
The embeddable badge idea is brilliant for distribution. That's a perfect viral loop, definitely adding it to the roadmap.
Just checked out openslop(.)ai, really cool concept. Did you end up implementing SSR + structured data across all your docs, or just the main landing pages? If you want to see exactly how Claude/ChatGPT are reading your setup right now, run it through the checker. I'd love your technical feedback on the
.mdcode fixes it generates for you.This is a real problem that most devs don't even realize they have. I ran into something similar last year — had a Next.js app with app router and everything was client components. Googlebot handled it fine because it executes JS, but when I checked what ChatGPT was actually seeing via its browsing feature, it was basically pulling from cached snippets and hallucinating the rest.
The llms.txt angle is smart. I've been seeing more discussion about it but almost nobody has actually implemented it yet. It's one of those things where being early matters — if AI chatbots start recommending tools based on what they can actually parse, sites with proper AIO will have a massive advantage.
On pricing — $4.99 feels right for an impulse buy, but I'd consider whether a one-time scan is the right model. Sites change constantly, and AI crawler behavior evolves too. A monthly check-up subscription (even at like $3/mo) might retain better than one-off purchases. Just a thought.
Spot on. Googlebot executing JS gave us all a false sense of security for years. The AI crawlers are way more brutal with SPAs. The llms.txt standard is definitely going to be the new robots.txt.
A monthly subscription for continuous monitoring is a fantastic idea for phase 2. Right now, I just want to validate the core value with a low-friction one-time purchase.
Since you battled this exact Next.js issue, I’d be really curious to see what score your current setup gets today. If you run a scan, check out the new embeddable badge feature on the results page—just shipped it based on feedback from this thread!