Posts tagged “Structured Data”
JSON-LD for machines: Article, FAQPage and Person types, dates and authorship fields, and which of them AI systems read before citing you.
JSON-LD has two readers. Indexers such as Google parse it while processing a page and use it to understand what the page is and who wrote it. The converters that turn a page into text on its way to a model drop almost all of it, so a fact stated only in the markup rarely reaches the answer. State each fact in the visible text and generate the markup from that text.
The posts here cover the canonical setup for an article and which of its fields survive the trip to a model, the two fields AI systems lean on when deciding whether to trust a source, freshness and authorship, and how to check your own markup by hand instead of paying a tool to look at it for you.
4 articles
Skip the AI Visibility Checker: Audit Your Site by Hand
Run the same eight checks a paid AI visibility checker runs, for free: llms.txt, robots.txt, JSON-LD, and real 2026 baselines to compare your site against.
· 13 min read
GEO vs SEO vs AEO — What Actually Changes in Your Workflow
I scanned 93 pages ranking for AEO and GEO queries to see whether the people explaining the difference follow their own advice. Only 25.8% did.
· 11 min read
Recency and Authority — Two Fields AI Uses to Trust You
Before quoting your article, AI runs two checks — is it fresh, and who wrote it. Both ride on machine-readable signals. Here's the canonical setup.
· 8 min read
JSON-LD for AI Search: Which Fields Actually Get Read
Five HTML-to-text converters kept at most 4 of 413 JSON-LD-only values across 40 ranking pages. See which fields reach a model and which to repeat in text.
· 24 min read