Aleksandar PerisicFull-stack Web Developer & AI Engineer
All writing
·3 min readAEOSEOStructured Data

Your next visitor is a language model

People don't ask Google who to hire anymore, they ask an AI. If your site only renders in a browser, you're invisible to the thing doing the asking.

I rebuilt this site with one visitor in mind that most sites forget: the language model. Someone asks ChatGPT or Claude 'who can bring AI into my product,' and a model, not a person, decides whether my name comes up. That visitor never sees my layout. It reads my markup.

Here is the uncomfortable part. Most sites render their real content in the browser, after JavaScript runs. A human waits the extra half second and never notices. A model often does not wait at all. It reads the HTML that came off the server, and if the facts about you live only in client-rendered components, it sees an empty shell and fills the gap with a guess.

SEO was built for crawlers that index and rank. AEO, answer engine optimization, is for models that read and answer. Different job, different plumbing. A search crawler is patient and forgives a messy page. An answer engine wants the fact stated plainly, on the server, in a shape it can quote without guessing.

Here is what that looks like on this site. Every page server-renders its facts first, then enhances. Each one carries JSON-LD: a Person and site graph on the homepage, an Article record on every post with author, job title, publish date, and canonical URL written in machine-readable form. This very post ships that markup, so a model quoting it knows who wrote it and when. And every indexable page declares its own single canonical URL, so nothing on the site quietly competes with itself to be the one answer.

The part that took me longest to accept: I am not doing this for the model's benefit. I am doing it so the model cannot get me wrong. Left to guess, it will confidently put you at the wrong company, in the wrong city, with the wrong title. Structured data is not a growth hack. It is you refusing to let a machine paraphrase you badly to the exact stranger who was ready to hire.

Here is the test for your own site. Turn JavaScript off and reload. Whatever survives is what a language model reads about you. If the facts that matter are gone, they are missing from every AI answer about you too, and you never see the visitor you lost.

Hiring, or stuck mid-build?

Based near Munich, open to senior in-house roles, remote in Germany, plus select Toptal engagements.
Prefer email? hi@aleksandarperisic.com.

Article record
aleksandarperisic.com · writing · your-next-visitor-is-a-language-modelillustrative dashboard
Back to Writing.app
Your next visitor is a language model
2026-08-123 min readAEO · SEO · Structured Data

I rebuilt this site with one visitor in mind that most sites forget: the language model. Someone asks ChatGPT or Claude 'who can bring AI into my product,' and a model, not a person, decides whether my name comes up. That visitor never sees my layout. It reads my markup.

Here is the uncomfortable part. Most sites render their real content in the browser, after JavaScript runs. A human waits the extra half second and never notices. A model often does not wait at all. It reads the HTML that came off the server, and if the facts about you live only in client-rendered components, it sees an empty shell and fills the gap with a guess.

SEO was built for crawlers that index and rank. AEO, answer engine optimization, is for models that read and answer. Different job, different plumbing. A search crawler is patient and forgives a messy page. An answer engine wants the fact stated plainly, on the server, in a shape it can quote without guessing.

Here is what that looks like on this site. Every page server-renders its facts first, then enhances. Each one carries JSON-LD: a Person and site graph on the homepage, an Article record on every post with author, job title, publish date, and canonical URL written in machine-readable form. This very post ships that markup, so a model quoting it knows who wrote it and when. And every indexable page declares its own single canonical URL, so nothing on the site quietly competes with itself to be the one answer.

The part that took me longest to accept: I am not doing this for the model's benefit. I am doing it so the model cannot get me wrong. Left to guess, it will confidently put you at the wrong company, in the wrong city, with the wrong title. Structured data is not a growth hack. It is you refusing to let a machine paraphrase you badly to the exact stranger who was ready to hire.

Here is the test for your own site. Turn JavaScript off and reload. Whatever survives is what a language model reads about you. If the facts that matter are gone, they are missing from every AI answer about you too, and you never see the visitor you lost.

Status
Published
Source
Original
Topic
AEO, SEO, Structured Data
References
Schema.org · Google structured data