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

Open
#702 1 comment 1 reaction 1 assignee View on GitHub

@BethMassi is already working on this.

Since Apr 11, 2026.

Assessment

This issue has not been assessed yet.

Description

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. #681
  • Add Article/TechArticle + BreadcrumbList + dateModified JSON-LD to (at least) the top 25 docs pages. #681
  • Publish FAQ #690 #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 (we can do this manually through ahrefs console for now)

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.
    • We're set up in ahrefs now so we can now monitor everything from there.
Dominant language
MDX
Stars
195
Forks
87
Avg merge
1d 22h
Merged PRs (30d)
73

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/aspire.dev

All issues in microsoft/aspire.dev

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.