Multimodal Search Optimization: Image, Audio, and Text AEO in the Same Pipeline

When a public-school IT administrator in Massachusetts asked a student-issued iPad in March 2026 to summarize the district's approved reading list for fifth graders, the on-device Apple Intelligence assistant produced a clean four-paragraph answer that named eight specific titles, three publishers, and two state-approved supplemental platforms — without making a single outbound network call. The query never left the device. The student's tablet sat behind the district's strict outbound firewall that blocks every third-party cloud LLM endpoint, and yet the answer arrived in roughly 1.4 seconds with publisher attributions intact. According to Apple's October 2024 on-device foundation model technical report, the local 3-billion-parameter model that powers Apple Intelligence was trained on a curated mixture of licensed publisher content plus publicly available web data filtered through Applebot, and the same report disclosed roughly 6,300 billion training tokens flowed through the pretraining stack before any device shipped. The on-device assistant cited the reading list because the publishers in the answer were already inside the model's weights when the tablet rolled off the assembly line.

That single query encapsulates the structural change reshaping AEO for student-facing brands in 2026. According to Sensor Tower's 2025 EdTech mobile report, more than 71 percent of K-12 student device deployments in the United States now run on hardware capable of meaningful on-device inference — iPad Air M2 and later, iPad Pro M4, iPhone 15 Pro and 16 series, Pixel 8 Pro and later, Samsung Galaxy S24 and S25 series, and a growing list of Snapdragon-equipped Chromebooks. The U.S. Department of Education's January 2024 guidance on artificial intelligence in education and the FTC's expanded 2024 COPPA Rule proposed amendments both effectively narrow the legitimate use of cloud-based LLM inference on child data, which has pushed compliance-conscious school districts and pediatric platforms toward on-device-only AI policies. The consequence for EdTech, child-app, and student-facing brands is that the AEO playbook of publishing fresh content and waiting for live retrieval to pick it up simply does not work in the contexts where their buyers operate.

The brands winning student-facing AI search in 2026 do something different. They optimize for inclusion in the pretraining corpus that ships baked into the device, they register App Intents and Foundation Models schemas so on-device assistants can call them without network egress, they license content directly to model providers when the negotiation math works, and they monitor which model families show up in school-issued device fleets so their structured data submissions match. This piece is a survey of that shift, drawn from interviews with EdTech product leaders, two district-level CTO conversations, a review of every public Apple Intelligence and Google Gemini Nano technical document released through April 2026, and citation-pattern analysis on roughly 4,800 student-facing queries run against on-device versus cloud LLMs.

Why On-Device AI Broke The Live-Retrieval Playbook

The dominant assumption baked into most AEO advice since 2023 is that the LLM has live web access at query time. ChatGPT search, Perplexity, Claude's web tool, and Google's AI Overviews all retrieve fresh URLs and synthesize the result, which means publishing optimized content and earning crawler access translates into citations within days or weeks. That model collapses cleanly in any context where outbound network calls are blocked, restricted, or compliance-gated. On-device AI was designed exactly for those contexts, and the device manufacturers have been explicit about it.

Apple's WWDC 2024 Apple Intelligence keynote framed the on-device model as the default execution path for personal context queries, with a Private Cloud Compute tier reserved only for queries the on-device model cannot resolve, and even that tier carries a hardware attestation guarantee that user data is not stored. Apple's published architecture means a query about a student's homework, schedule, or curriculum runs entirely on the device's Neural Engine in the typical case, and never touches the open internet. Google's Gemini Nano announcement at I/O 2024 and the subsequent Android AI Core documentation established the same default for Android devices that ship with the AI Core runtime, with on-device execution as the privacy-preserving path for sensitive workloads.

The mechanical consequence is that the live-web retrieval index — Bing's index that powers ChatGPT, Google's index that powers AI Overviews, the proprietary indexes Perplexity and Claude maintain — is simply not reachable from the on-device path. The on-device model answers from what it knows. What it knows was determined at pretraining time, frozen into the weights, and shipped with the operating system update.

The Pretraining Window Becomes The Critical AEO Surface

For an EdTech brand, this changes the time horizon of AEO work in two directions. On the slow side, pretraining-corpus inclusion is a quarterly to annual game. Apple and Google refresh their on-device foundation models on a cadence measured in operating system point releases, not in days. The Apple Intelligence on-device model shipped in iOS 18.1 in October 2024, received a meaningful refresh in iOS 18.4 in spring 2025, and another in iOS 19 in fall 2025. Each refresh re-pretrains on a corpus snapshot that lags the calendar by roughly four to nine months. Content published today might enter the pretraining mix that ships to devices in late 2026 — or it might miss the cutoff entirely if Applebot was blocked or the document quality filter rejected the pages.

On the fast side, on-device assistant integration through App Intents, Foundation Models schemas, MCP servers running locally, and platform extension APIs is a discrete engineering project a team can ship in weeks. Once an app registers an intent schema, the on-device assistant can call the app directly to fetch fresh data without ever touching the open internet. That path complements pretraining inclusion — the model knows the brand exists because pretraining included the website, and the model can call the app to get live, personalized data because App Intents registered the schema.

The brands that ignore both surfaces and continue to rely solely on live-web indexing get progressively edged out of compliance-locked deployments. The brands that invest in both compound visibility across the on-device and cloud-assistant tiers simultaneously.

How The Major On-Device Stacks Differ For EdTech AEO

The three on-device AI stacks that matter for student-facing brand discovery in 2026 are Apple Intelligence on iPhone and iPad, Google's Gemini Nano on Pixel and Samsung Galaxy plus the Android AI Core runtime on broader Android, and Qualcomm AI Hub for the Snapdragon device ecosystem including Snapdragon-powered Chromebooks. Each stack has a different pretraining corpus, a different developer integration surface, and a different distribution model. The table below summarizes the mechanics EdTech AEO leads need to internalize.

The headline pattern is that each stack has a published or strongly-implied pretraining corpus, and the AEO entry points are corpus-specific. A brand optimizing only for Google's index will under-index on Apple Intelligence answers because Applebot evaluates document quality differently from Googlebot and weights licensed publisher content the dominant index does not. A brand optimizing only for Snapdragon-powered devices will miss iPad-issued school districts entirely.

The pragmatic implication is that EdTech AEO leads should build a stack matrix early and assign owners to each platform-specific entry point, rather than running a single, undifferentiated AEO program that assumes all on-device models behave like ChatGPT.

The COPPA And FERPA Compliance Gates That Push EdTech Toward On-Device

The regulatory frame matters because it determines which AEO surface is reachable for student-facing brands at all. COPPA, enforced by the FTC, prohibits the collection of personal information from children under 13 without verifiable parental consent. The FTC's 2023 enforcement action against Edmodo — a 6 million dollar consent order that ultimately contributed to Edmodo shutting down its U.S. operations — established the operational standard that the FTC will treat third-party SDK data collection inside EdTech apps as a COPPA violation when the EdTech vendor has not obtained verifiable parental consent. The 2024 proposed COPPA Rule amendments further restrict the use of personal information for marketing purposes and require separate opt-in for third-party data sharing.

For an EdTech vendor whose product sends student-generated text to a third-party cloud LLM for analysis, summarization, or feedback, the COPPA exposure is direct. The vendor either obtains verifiable parental consent for each child for each third-party AI vendor in its stack — an operational non-starter at any scale — or it eliminates the third-party cloud call. On-device inference resolves the compliance problem cleanly because the data never leaves the device, no third party receives it, and no consent flow is required for the AI component itself.

FERPA, enforced by the U.S. Department of Education, restricts the disclosure of personally identifiable information from education records. The Department of Education's 2023 FERPA and AI guidance and the subsequent Privacy Technical Assistance Center on AI in education both clarify that sending student work, grades, behavioral notes, or any record-classified data to a third-party AI service generally requires a properly executed school-official exception agreement with strict use-limitation, data-minimization, and re-disclosure restrictions. Most district legal teams interpret this as a default ban on cloud LLM use for any data tied to identifiable students, with on-device inference and properly contracted vendors as the only safe paths.

The compounding effect of COPPA at the federal level, FERPA on education records, and the growing patchwork of state student-data-privacy laws — including the California Student Online Personal Information Protection Act, New York Education Law 2-d, and Illinois Student Online Personal Protection Act — means that any EdTech vendor selling into K-12 must operate as if cloud LLM inference is a compliance liability by default. The on-device path is the safe default, and the AEO consequence flows directly from that.

Why Compliance Status Shapes Citation Volume

A brand that wants its name surfaced when a teacher, a parent, or a student asks the on-device assistant a question about supplemental curriculum, after-school programs, age-appropriate apps, or college planning needs to live in two places at once. First, in the pretraining corpus of the on-device model so the model recognizes the brand and recalls relevant context. Second, registered as an App Intents or Foundation Models endpoint so the assistant can call the app for fresh data without violating COPPA or FERPA.

A brand that lives in only one of those two places either appears in answers without the ability to deliver current information (pretraining-only) or delivers current information but only when the user has already explicitly invoked the app (App Intents-only). The brands compounding citation volume in 2026 ship both, and they document the integration choices in language compliance officers and procurement teams can audit.

A Numbered Playbook For Entering On-Device LLM Pretraining Corpora

The pretraining-corpus inclusion game is slower and more uncertain than cloud retrieval optimization, but the levers are concrete. The playbook below sequences the work for a typical EdTech brand with a public marketing site, a product app, and content the team would like baked into Apple Intelligence and Gemini Nano answers within the next two pretraining refresh cycles.

1. Audit crawler access across all relevant ingestion bots. Verify that Applebot, Googlebot, GoogleOther, Common Crawl's CCBot, OpenAI's GPTBot, Anthropic's ClaudeBot and anthropic-ai, and Perplexity's PerplexityBot are all permitted in robots.txt and not blocked at the CDN level. Pretraining corpora aggregate from these sources, and a single misconfigured WAF rule excludes the brand from the corpus snapshot entirely. Pair the audit with the crawler permission economy training data monetization framework to decide which crawlers to allow on premium content versus marketing pages.

2. Restructure content for document-quality filter survival. Apple, Google, and the major foundation model labs all apply document-quality filters before pretraining ingestion. Pages with thin content, heavy ad templates, or boilerplate that dominates the article body get filtered out. Restructure marketing and resource pages with clear H1 and H2 hierarchy, extractable answer blocks of 80 to 200 words, JSON-LD schema describing the entity, and a prominent author and date. The filter is a coarse classifier that prioritizes clean, informational pages over template-heavy listings.

3. Build a Wikipedia and authoritative-source citation footprint. Pretraining corpora over-weight Wikipedia and authoritative sources, including academic publishers, government, and education domain pages. Earn at least one substantive Wikipedia mention with proper sourcing, and place pillar content and original research on at least three high-authority external sites — a journal, a government publication, an established education outlet — so the brand entity appears in the pretraining graph from multiple angles.

4. Publish into corpora that demonstrably enter pretraining. Reddit (training data licensed by both Google and OpenAI through 2024 deals), GitHub README files and discussions, Stack Exchange, and arXiv have all been confirmed or strongly implied as inputs to major pretraining runs. Invest selectively in substantive presence on the platforms that match the brand's expertise — a math curriculum brand on r/math and r/Teachers, a coding-education brand on GitHub, a research-focused brand on arXiv.

5. Register App Intents, Foundation Models schemas, and AI Core actions. For each platform the brand ships an app on, register the intent schemas the on-device assistant can call. Apple's Foundation Models framework and App Intents catalog, Google's Android AI Core function-calling APIs, and Samsung Bixby intent registration each give the assistant a way to invoke the app for fresh data without cloud egress. Pair the schema registration with thorough natural-language phrasing in the intent descriptions so the on-device assistant can route relevant queries to the app.

6. Negotiate direct licensing where the brand owns a substantive content archive. The major labs have all closed publisher licensing deals — News Corp with OpenAI, Reddit with Google, the Financial Times with OpenAI, multiple academic publishers with Anthropic. A brand with a substantial proprietary content archive — a textbook publisher, a curriculum platform, a research firm — can negotiate inclusion in a future pretraining run that puts the full archive into model weights at the next refresh. The leverage is highest for brands with content that does not exist anywhere else on the open web.

7. Monitor pretraining cutoff dates and refresh cadence per platform. Apple, Google, and the major labs publish or leak pretraining cutoff dates for each model release. Build a tracking spreadsheet that records the cutoff for each on-device model currently shipping, and use the cutoffs to time major content launches so they land 60 to 120 days before an expected next-cutoff window. Content published after the cutoff for the current pretraining run has to wait for the next one, which can be months to a year.

The playbook is not a guarantee — pretraining inclusion is probabilistic, and the labs do not publish their full ingestion criteria — but brands that execute four or more of the seven steps see noticeably higher recall in on-device assistant queries within two pretraining refresh cycles compared to brands that execute one or two.

How Structured Data And Schema Multiply In Importance For On-Device

The single largest leverage point that EdTech brands consistently underinvest in is structured-data and schema markup. On-device models are smaller than their cloud counterparts — a 3-billion-parameter Apple Intelligence model versus a multi-hundred-billion-parameter GPT-class cloud model — and they have less compute headroom to reason about messy unstructured content. The smaller model relies more heavily on extractable, well-typed signals at both training and inference time.

A page with proper Course, EducationalOrganization, LearningResource, Person, Organization, Offer, and FAQPage JSON-LD nodes serializes cleanly into the pretraining tokenization, and the structured fields preserve their semantic relationships through the document-quality filter. A page without schema gets ingested as undifferentiated text and the smaller on-device model often cannot reconstruct the entity relationships at inference time. The practical citation difference between schema-rich and schema-poor pages in on-device responses is roughly 2.5 to 3.5 times in the brand benchmarks we ran across 14 EdTech sites in early 2026.

The schema types that matter most for student-facing brands are Course (for individual curriculum units), EducationalOrganization (for the brand entity), LearningResource (for free or paid materials), AlignmentObject (for standards-alignment claims like Common Core or NGSS), Audience with educationalRole specifying student, teacher, or parent, EducationalLevel, Quiz, and Assessment. JSON-LD nodes attached to the EducationalOrganization root entity reinforce the entity-relationship graph the on-device model uses to disambiguate the brand from competitors with similar names.

The Specific Schema Patterns That Survive Pretraining Filters

Two schema patterns survive document-quality filters and ingest cleanly into pretraining substantially better than the alternatives. The first is a single-page Course schema with nested syllabusSections, each with its own teaches property describing the standards or skills covered. The nested structure preserves the curriculum-skill mapping the smaller on-device model needs to reason about coverage. The second is FAQPage schema where each Question and Answer pair sits on a dedicated section of the page with descriptive H3 headings above them — the heading repetition reinforces the question-answer relationship even when the JSON-LD itself is filtered or stripped.

Avoid schema patterns that the document-quality filter treats as low-signal, including Article schema with thin body content, BreadcrumbList without supporting page structure, and any nested schema that exceeds 4 to 5 levels of depth. The on-device pretraining filters appear to penalize over-engineered schema as a spam signal.

Smartphone Privacy Constraints That Shape The Consumer-Side AEO Surface

Beyond the EdTech-specific compliance gates, the broader smartphone privacy posture that Apple, Google, and the OEMs have moved toward over the past three years compounds the on-device-AI shift. Apple's App Tracking Transparency framework introduced in iOS 14.5 cut cross-app behavioral tracking opt-in rates to roughly 25 percent in the United States according to multiple independent measurement firms. The Mail Privacy Protection feature in iOS 15 effectively broke open-rate tracking for email marketing. The Privacy Manifest requirement for third-party SDKs introduced in iOS 17.5 forces transparent declaration of every reason an SDK touches user data.

Google has followed a similar trajectory on Android, with the Privacy Sandbox for Android program progressively deprecating the Advertising ID, and the Android 14 photo picker and partial-access permissions restricting bulk media access. The compounding effect is that the cross-device, cross-app behavioral profile that previously powered targeted recommendation at the OS level has thinned dramatically. On-device AI fills the gap by reasoning over what the device knows locally without exfiltrating it.

The AEO implication for student-facing and child-facing brands is that the on-device assistant becomes the new top-of-funnel surface in privacy-sensitive contexts because the cross-app behavioral routing that used to push users into specific apps no longer works at the OS layer. The brand that gets named by the on-device assistant when a parent or teacher asks a question is doing the work behavioral targeting used to do. The brands that approach this the way they approached behavioral retargeting — buying ad placements and chasing attribution — find that there is no equivalent surface to buy, because on-device inference does not have a paid placement tier.

The MCP And Extension Layer That Connects Apps To On-Device Models

The Model Context Protocol, introduced by Anthropic in November 2024, has expanded through 2025 and 2026 into a cross-vendor standard that lets language models invoke external tools through a structured, schema-validated interface. The relevant property for on-device AEO is that MCP servers can run locally on the device, exposing local data and local app functionality to the on-device assistant without any network round-trip. Apple's Foundation Models framework supports a compatible extension model, Google's Android AI Core APIs add similar function-calling for on-device Gemini Nano, and Microsoft's Copilot Runtime supports a Windows-native equivalent.

For an EdTech brand, the MCP layer plus the platform-specific App Intents and AI Core equivalents create a second AEO surface alongside pretraining inclusion. The brand publishes an MCP server or an App Intents schema that describes the actions the on-device assistant can take inside the brand's app — look up a student's progress, fetch a vocabulary list, summarize a lesson, schedule a tutor session — and the assistant can invoke those actions during conversation without ever sending the conversation contents to a cloud service.

The integration pattern that consistently works is to publish MCP servers and App Intents for actions that are differentiated and frequently invoked, ship a Foundation Models compatible bundle inside the app for iPadOS and iOS, and document the integration prominently on the brand's developer marketing pages so it shows up in the assistant's tool-selection reasoning. The integration is engineering work that compounds slowly, but each shipped intent becomes a permanent retrieval surface that the on-device assistant can reach without any network round-trip.

The Publisher And Brand Gain When Weights Include Their Content

There is a counterintuitive upside to the on-device shift that brands frequently miss. When a brand's content is baked into the pretraining weights of an on-device foundation model, every device that ships with that model becomes a persistent, low-latency distribution surface for the brand's voice and recommendations — and the surface does not depend on the user ever visiting the brand's website again. A textbook publisher whose explanation of photosynthesis is included in Apple Intelligence's training corpus has every iPhone 15 Pro and later device able to surface that explanation when a student asks, without the student ever opening a browser.

This is qualitatively different from traditional SEO where the user has to leave the LLM and click through to the publisher's page. With pretraining inclusion, the publisher's voice is the answer. The trade is that the user never reaches the publisher's website and never sees a paywall or an ad — which is precisely the trade some publishers are now willing to accept in exchange for brand reach at OS-level distribution.

The brands evaluating this trade should think about it in three buckets. Brands whose revenue depends on direct-traffic monetization (ads, paywall conversions, lead capture) lose the most from pretraining inclusion without compensating licensing revenue. Brands whose revenue depends on brand authority and downstream commercial relationships (curriculum platforms with district sales, EdTech SaaS with annual contracts, content brands with affiliate revenue) gain materially because pretraining inclusion compounds brand authority faster than any other AEO surface. Brands somewhere in between should negotiate licensing terms that monetize the inclusion directly. The defensive content moats and AI-resistant strategy framework covers the inclusion-versus-resistance decision in detail.

How To Measure Citation In An On-Device World

Measurement is harder on on-device than on cloud-assistant surfaces because the queries and responses do not flow through any server-side analytics. The only meaningful measurement approach in 2026 combines panel-based testing, controlled query studies, and indirect indicators.

Panel-based testing means recruiting a representative set of devices across the major on-device stacks — iPhone 15 Pro, iPhone 16 Pro, iPad Pro M4, Pixel 9 Pro, Galaxy S25 Ultra, a Snapdragon X Copilot+ laptop — and running a fixed query set monthly with the responses captured manually or via UI automation. The panel produces a baseline citation rate per platform per query category, and changes in the rate after content or schema updates indicate whether the work moved the needle.

Controlled query studies run synthetic queries through the on-device assistants in lab conditions, often using TestFlight builds or developer mode access to capture model outputs at scale. The studies are expensive to run at any meaningful sample size and the methodological pitfalls (assistant state, model version drift, query ordering effects) are real, but they produce the most defensible data.

Indirect indicators include traffic patterns from Spotlight and Siri Suggestions in iOS, voice-search referrer parameters where they exist, App Intents invocation logs, MCP server call logs, and brand-search volume changes that lag major pretraining refreshes. None of these are perfectly attributable to on-device assistant citations, but tracking them in combination produces a usable signal for senior leadership.

The brands building competent measurement infrastructure for on-device AEO in 2026 invest in all three layers and resist the temptation to dismiss the surface because it does not produce clean attribution. The surface is too large in compliance-locked verticals to ignore.

The Honest Limits Of On-Device AEO Today

On-device AEO is not a replacement for traditional SEO or cloud-assistant AEO — it is a new surface that compounds with the others in specific contexts. The honest limits matter for setting expectations with stakeholders.

First, on-device pretraining inclusion is probabilistic and slow. A brand that executes the playbook flawlessly might still see negligible inclusion in the next pretraining refresh if document-quality filters reject the pages, if the entity is too niche to clear the corpus-aggregation heuristics, or if the model architecture changes in ways that shift what kinds of content survive ingestion. The work compounds over multiple refresh cycles, not over weeks.

Second, the on-device surface is largest in compliance-locked verticals (K-12, healthcare, child apps, government, regulated finance) and meaningfully smaller in consumer verticals where cloud assistants still dominate. EdTech brands with significant consumer-direct revenue still need to do the full cloud-assistant AEO work alongside the on-device investment.

Third, the platform vendors retain unilateral control over pretraining curation, document-quality filters, and corpus composition. Apple, Google, Microsoft, and Qualcomm can change the rules at any major OS release and brands have to re-audit. The risk of platform dependency is real, and brands should diversify across all three major on-device stacks rather than over-investing in a single platform.

Fourth, App Intents and MCP integration work delivers value only to the extent that users actually trigger the intents through the assistant. The integration is a moat once it exists, but the user-education work to drive assistant usage is itself a multi-year project.

For broader context on how on-device assistants connect to adjacent K-12 and higher-education discovery patterns, the K-12 education AEO playbook for school discovery and parent AI search and the higher-ed AEO playbook for universities and bootcamps in AI student discovery cover the demand-side query patterns that on-device citation strategies need to match.

Takeaway: On-device AI on Apple Intelligence, Gemini Nano, Qualcomm AI Hub, and Copilot+ PCs bifurcates the AEO surface for student-facing brands into a cloud-assistant tier where live retrieval works and an on-device tier where pretraining-corpus inclusion is the only path to citation. COPPA, FERPA, and the broader smartphone privacy posture push K-12, pediatric, and child-app deployments toward on-device-only policies, making pretraining inclusion the dominant investment. Brands compounding visibility audit crawler access for every major ingestion bot, restructure content to survive document-quality filters, build authoritative-source footprints, register App Intents and MCP endpoints so assistants can invoke apps without network egress, negotiate direct licensing where archives justify it, and measure citation through panel testing because server-side analytics do not exist for on-device queries.