Internal case study · October 3, 2026
We perfected our website with our AEO auditor
For our AI Search Optimization service we built our own auditor: a tool that measures whether ChatGPT, Perplexity, Claude and Gemini can read, understand and cite a website. Before using it with any client, we ran it on dastanxtech.com. Here’s what it found, what we fixed and the result.
What the auditor measures
Google runs a page’s JavaScript; most AI assistants don’t. So the auditor reads every page twice, the way a person sees it and the way an AI assistant sees it, and compares them. Then it answers the 8 questions an AI asks before recommending a business:
- Can it get into the site, or does robots.txt shut the door?
- Can it read the content without running JavaScript?
- Does it understand what the business is and what it sells (structured data)?
- Can it pull out and quote paragraphs that answer a question?
- Does it know who’s behind the site, and does it trust it (legal notice, profiles, reviews)?
- Can it date the content and tell whether it’s still current?
- Are the SEO basics in order (titles, sitemap, language)?
- Does the site respond quickly and without errors?
Every finding comes with proof: the exact page and the snippet that fails. And before showing anyone a report, we check every finding by hand against the real website.
What was already right
The first audit, on October 1, scored 94 out of 100. The hardest part was already solved: no AI assistant was locked out, every page arrived complete without depending on JavaScript, and the structured data already said who we are and what we offer. That’s exactly where many sites built with visual builders fail.
What it found
- There was no legal notice or privacy policy: nothing said which company is behind the site.
- Articles said when they were published, but not when they were last reviewed.
- The sitemap gave every page the same date, so it couldn’t tell what had actually changed.
- One article title was too long and got cut off in search results.
- There were no client reviews or testimonials.
What we fixed
- We published the privacy page, saying who is responsible and how we handle the data that comes in through the chat.
- Every page now keeps the real date of its last review, used by both the sitemap and the articles’ structured data.
- We shortened the title that was getting cut off.
- We added to robots.txt how AI assistants may use our content (Content-Signal). That took us from level 1 to level 2 on Cloudflare’s agent readiness scanner.
- Then we went one step further: the homepage tells AI agents where the site’s description is (Link headers), and any page can be requested in Markdown, the plain-text format agents prefer.
The result
Today’s audit scores 97 out of 100. Of the five findings, one remains: reviews. That’s normal for a business that’s just starting, and it isn’t fixed with code but with happy clients.
The full report is exactly what a client receives, with the score, the 8 questions, the before and after, and the proof for every finding (in Spanish):
See the full dastanxtech.com report →
Want to know what AI sees when it reads your website?