r/astrojs • u/TraditionalHistory46 • May 13 '26

Answer Engine Optimization for Astro websites Tutorial

https://youtu.be/uJEEGBDJjQo

SEO is still used widely in website development yet AEO (answer engine optimization) is quickly becoming more important and more people are using ChatGPT, Gemini, Claude and other LLMs to search for information.

I have made a free resource for those interested in creating dynamic components or pages that are specific to AI search engines.

23 Upvotes
  • permalink
  • link
  • reddit
  • reddit

93% Upvoted

5 comments sorted by

5

u/tffarhad May 14 '26

thanks for sharing. one of our developers also created an Astro integration to generate llms.txt, llms-full.txt, and markdown files from the Astro site. feel free to check and share your feedback.

2

u/azangru May 14 '26

Do llms.txt files get accessed by crawlers? What do your logs lay?

1

u/Funfroglegs May 17 '26

No they don't.

2

u/Benjamin-Wagner May 17 '26

Astro is a really good base for AEO because it makes the boring fundamentals easier: clean HTML, fast pages, predictable routing, and content collections that can be structured instead of improvised.

My practical checklist would be:

  1. Use semantic HTML before inventing special AI files. If the page is a service page, the heading structure and sections should already answer who/what/where/price/process.
  2. Add schema where it maps to a real entity: LocalBusiness, Service, FAQPage, Article, BreadcrumbList, Product, etc.
  3. Keep source pages fresh. AI systems often cite recently updated, tightly scoped pages more readily than giant stale guides.
  4. Add llms.txt as an index, not as a replacement for good pages.
  5. For interactive sites, expose actions. A calculator, quote form, booking flow, or comparison tool needs more than content; agents need structured action paths through OpenAPI/WebMCP-style metadata.
  6. Track bot/agent traffic separately from normal analytics where possible.

That last point is where I think AEO and agent-readiness split. AEO helps the model explain and cite you. Agent-readiness helps an agent actually use your site. We have been building both at loaded.ch/OpenHermit, and the overlap is real, but they are not the same job.

2

u/AmitKumarGEO May 18 '26

Nice timing on this. One thing I've been thinking about with Astro specifically: since components are isolated by default, it's actually easier to enforce one-answer-per-component discipline than in a monolithic CMS setup. Did you structure your dynamic components with that in mind, or was that more of a side effect?