Start with one stable identity

The English and Arabic pages describe the same person through separate crawlable documents and one stable Person identifier.

The site uses Ahmed AlDhraif in English and أحمد الظريف الشامسي in Arabic. Each language has its own URL, title, description, canonical URL, and reciprocal language link.

Structured data must agree with what a visitor can read. The Person node therefore points to the same official profiles and approved public relationships shown by the website rather than adding hidden claims for search engines.

Keep the source label beside the claim

Independent reporting, project-owned records, and interview statements answer different verification questions, so the website labels them separately.

An independent source is controlled by an outside publisher. A first-party source is published by Ahmed or a connected project. An attributed statement records what Ahmed said in an interview but does not present that statement as independently proven.

The distinction helps readers judge evidence without asking them to trust a logo wall or an unsupported biography.

  • Independent: an outside publisher controls the page.
  • First-party: Ahmed or a connected project controls the page.
  • Attributed: the wording remains tied to the person who said it.

Publish only after the record passes its gates

Drafting can be assisted, but publication, indexing, and distribution require an approved record and a successful technical release.

Every Insight needs a distinct purpose, source references, English or Arabic ownership, valid publication dates, and an approval receipt. Unapproved records stay outside public indexes, feeds, sitemaps, and structured data.

After publication, the site can generate metadata, Article schema, feeds, sitemap entries, social previews, and change notifications from the same record. This reduces drift because one approved source controls every output.

Treat corrections as part of the public record

A correction should identify the exact page, disputed statement, and supporting source before the main content and modification date change.

Substantive corrections update the visible copy and structured data together. Cosmetic deployments do not receive a new editorial date, and a publication notification is never treated as proof that a search engine indexed the page.