Structured signals that tell machines who you are, where you work, what you sell, and why you are credible.
What is schema markup, in plain terms?
Machine-readable evidence behind your pages. A human sees your bio; a crawler sees structured RealEstateAgent, Person, Organization, Review, Listing, FAQ, and WebPage data confirming who you are, where you work, and why you are credible.
Why does it have to be server-rendered?
Because most AI crawlers do not run JavaScript. Espo ships the structured data in the first HTML response, so ChatGPT, Perplexity, and Google read it on every visit — a detail many “SEO-optimized” sites get wrong.
What is an entity graph?
The consistent web of links that lets machines reconcile you across the internet — your site, social profiles, review profiles, and brokerage pages all pointing at the same identity. AI engines need that reconciliation before they recommend you by name.
What is llms.txt?
A plain-text file AI engines read directly — an honest summary of who you are, what you offer, and what is on your site. Espo maintains one as part of the AI-search groundwork, and keeps it in sync as your site grows.
Will schema alone get me recommended by AI?
No — and anyone promising that is selling snake oil. Schema makes your real proof legible to machines. The proof itself — listings, reviews, local pages, results — still has to exist. Espo builds both.