SEO / AEO requirements

Each Founder File emits `Article` (CreativeWork variant) schema with `learningResourceType: "Guide"` + `educationalLevel` + `inLanguage`. The reader page emits the longest-form structured-data payload on the platform, which makes Founder Files the AEO ground truth for "how do I {action} as a MENA founder" queries.

Per-file emission contract

<title>

`{File title} | StartupHub.today Founder Files`. Editor-authored, includes file number when impactful.

JSON-LD @type

`Article` with `learningResourceType: "Guide"` and `educationalLevel`. Long-form content carries `wordCount` when computed.

author

Locale-aware author from the editorial team. Renders as `Person` schema with the editor’s display name.

publisher

Always `{ @type: Organization, name: "StartupHub.today" }`.

inLanguage + alternateName

Current locale’s inLanguage + every other available language as an alternate.

mentions[]

Cross-module Thing references. The "max 3 opportunities" emission here is what makes the file → opportunity AEO chain work.

Reader page is the AEO surface

The reader page (NOT the details page) is what AEO crawlers should index for "how to ..." queries. The bodyHtml is the answer; the cross-module mentions are the citation graph. The details page is a marketing surface for sharing — it sets og:type=article but redirects search-driven traffic to the reader for the deep answer.