GEO: Plan to surface the Aspire brand in AI search through organic visibility

[BethMassi]

Phase 1

Goal: make Aspire easier for search engines and LLMs to identify, parse, and trust.

• Add Organization and WebSite JSON-LD to the home page. Add Schema.org JSON‑LD structured data to Aspire docs for AI search discoverability #681
• Add Article/TechArticle + BreadcrumbList + dateModified JSON-LD to (at least) the top 25 docs pages. Add Schema.org JSON‑LD structured data to Aspire docs for AI search discoverability #681
• Publish FAQ Add Aspire FAQ #690 Add FAQ page and homepage FAQ link #701
• Update titles, meta descriptions, and H1s so each page clearly targets one user intent.

Phase 2

Goal: increase the number of questions Aspire can win organically.

• Review troubleshooting page(s).
  • Perhaps start with aspire update or teach people about --debug or aspire diagnostics and then move to integration troubleshooting.
• Add page-specific FAQs to the highest-traffic docs pages.
• Add more tables, checklists, and "quick answers" to install, first-app, and AI-agent pages.
• Add IndexNow submission to the docs release pipeline

Phase 3

Goal: make Aspire the source AI systems quote, not just a site they can crawl.

• Publish at least 3 case studies that show measurable results using Aspire.
• Synchronize brand language and links across GitHub, Learn, blog posts, and talks.
  • This is done across the channels we own.
  • Next step is to refer to Aspire from relevant Microsoft Learn docs as that has very high domain authority.
  • Publish brand assets and usage guidelines, design language, and intro decks to aspire-brand repo
• Refresh pages monthly based on real prompt testing and Search Console performance.
  • Set up a worklow agent to test basic prompts to see if Aspire was cited.