Which schema types actually matter for AEO?

Get the entity graph right before adding page types: one Organization node with a stable @id, referenced by everything else, rather than duplicate organization declarations scattered per page. Engines resolving "who is this" reward consistency; conflicting nodes on different pages are how a brand ends up as two half-known entities.

Use the type that matches what the page IS. Google's guidelines reserve QAPage for forums with user-submitted answers — a company answering its own question is FAQPage. Mislabeled schema is worse than missing schema, because it signals either carelessness or manipulation to the systems reading it.

Validate against what parsers actually see: JSON-LD with malformed syntax fails silently, and a page can carry six schema blocks of which zero parse. Test with Google's Rich Results tooling or by parsing your own JSON-LD in CI — we audit customer sites by parsing the markup, never by guessing from prose, for exactly this reason.