Titles, share cards and structured data from verified facts

Before anyone visits a page, they meet it somewhere else: as a search result, or as a link pasted into a chat. Both are built from a few lines at the top of the page. These are those lines on my speculative AllWeb redesign, and each one has a job.

The title is written for the person searching. It says what the event is, where and when: AllWeb 2026, in the capital of Albania, on 6 November, a marketing, business and innovation conference. The description helps them decide whether to click: who it's for, the day, the city, and what they'll find there. The share card is a picture of the page itself. A script opens the page, crops the hero to twelve hundred by six hundred and thirty pixels, and saves it. Run it again whenever the hero changes. On a review build, every one of these tags points at the review address. A card that points at the client's own domain would look as if they had published it.

Structured data describes the page to search engines and AI answers, in a fixed vocabulary. Here it gives the event's name, its dates, that it happens in person, and its city. Every one of those facts needs a row on the claims list. The name, the date and the city come from the brief's facts list, copied from AllWeb's own site. Describe only what's on the page. This page has no questions section, so it has no FAQ data. Then read it back. A checker, or a short script like this one, should parse it and repeat what the page says.

Record it for each page: the title, the description, the share card, and every structured fact with its row on the claims list.

Write titles for searchers, make cards from the page, and mark up only verified facts.