Build notes3 sections · 2 min readBy Dezső Mező · Published October 3, 2026.mdSEOAEOSchema.orgJSON-LD
The markup below is what runs on this site: an organisation node, per-page entities, FAQ blocks, and review data that only states what can be verified. The interesting part is less the syntax than deciding what a machine may quote.
01One graph, not scattered snippets
Every schema node on this site shares a single @id graph: the organisation, the founder, the website, each page and each case study. Answer engines reconcile entities across pages far better when the same subject keeps the same identifier everywhere.
02Only mark up what the page says
Review and rating markup that names numbers the page does not show is exactly the kind of claim structured data loses trust over. Every testimonial in the JSON-LD here is a named, linked review a visitor can also read.
03Translated routes need translated canonicals
A Hungarian page canonicalised to the English URL tells every engine the English version is the real one. Canonicals, hreflang and sitemaps all emit the localised slug here, so /hu/kapcsolat is the Hungarian answer, not an alias.
What to take away
- Share one @id graph across every page.
- Mark up only claims the page itself makes.
- Localise canonicals, not just content.
- Speakable selectors and fresh dates help assistants quote you correctly.
More from the lab
Browse all entries
The AI-search visibility checklist we run on this site
What we did for the AI crawlers
One site, three languages, zero duplicate-content problems
Move the site, keep the rankings
Want this looked at on your own system?Start a conversation
