Transparent by design
The methodology is documented publicly so buyers and technical teams can inspect the factors instead of relying on black-box scoring.
13-Factor Methodology
AEO work is stronger when the scoring model is visible.
AI NYC uses a public 13-factor model that represents our best current understanding of what makes a site easier for answer engines to parse, trust, and cite. AEO is a new field and no methodology is proven, so we publish ours through @ainyc/aeo-audit so teams can inspect it, challenge it, and build on it. Much of the model draws from established SEO and content marketing principles, extended with technical signals specific to AI readability.
Core Principles
The methodology is documented publicly so buyers and technical teams can inspect the factors instead of relying on black-box scoring.
Most of what works in AEO starts with strong traditional SEO and quality content marketing. Good site structure, useful content, and real authority are not new ideas. AEO layers on technical signals like structured data, AI-readable files, and entity clarity that help AI systems consume what is already there. Google's SEO Starter Guide covers many of these fundamentals.
AEO is an emerging field. Nobody knows exactly how AI models select which businesses to cite, and the landscape changes as models are retrained. Our 13-factor model is a working hypothesis based on research and observation, not a guaranteed formula. We update it as we learn.
We focus on the technical and content signals answer engines can actually consume, including schema, AI-readable assets, and clean direct-answer structure.
Answer engines do not rely on your site alone. Third-party mentions, partner pages, directory profiles, editorial coverage, and other outside content help confirm that your on-site entity and service claims are real.
The model is especially useful in markets like NYC, where multiple businesses compete for the same high-intent answer slots.
Factor Model
The 13-factor model comes directly from the public documentation for @ainyc/aeo-audit. That means our client methodology starts with a published scoring model rather than an opaque internal checklist.
For local and location-sensitive work, we also evaluate an optional geographic layer: geographic signals.
The methodology also assumes that outside content matters. Strong structured data on your own site helps answer engines parse you, but third-party mentions, partner pages, directory profiles, and editorial references help them trust that the same entity exists beyond your own domain.
Presence of LocalBusiness, FAQPage, Service, and HowTo schemas.
Word count, heading hierarchy, paragraph structure, and list usage.
llms.txt, llms-full.txt, robots.txt, and sitemap.xml availability.
Author meta, trust pages, credentials, and review-oriented trust signals.
FAQPage schema, question headings, and direct-answer formatting.
External references, authoritative links, and sameAs-style corroboration.
Property depth and richness across the structured data stack.
Naming consistency across schema, title tags, and on-page identity.
dateModified, Last-Modified, sitemap dates, and current copyright signals.
How easy the content is for answer engines to parse and cite.
Direct definitions, step lists, and HowTo-style explanation blocks.
Brand mentions, founder references, and proper-noun density.
robots.txt rules for GPTBot, ClaudeBot, PerplexityBot, and peers.
How We Apply It
If you want the public narrative, read the open-source article. If you want the commercial application, go straight to the NYC agency page or run the free audit.