Problem
A technically clean site can still be weak answer-engine evidence.
Public sites can expose metadata, schema, sitemap, robots, and llms.txt while still lacking answer-ready FAQ depth, named expertise, visible trust proof, or service/location coverage. A split diagnostic keeps technical crawl hygiene separate from capped AEO/content authority so clean tags do not mask thin evidence.
When to use it
- You want to know whether bots can access and parse the site.
- You need to check whether answer engines have enough FAQ, EEAT, service, location, review, and curated llms.txt context to cite confidently.
- You want a compact diagnostic before deciding which site signals to fix next.
- You want to compare technical and AEO readiness using a single public-site analysis.
Non-goals
- Not a search ranking, AI citation, traffic, or revenue predictor.
- Not permission to scan private, internal, or customer sites you do not own or control.
- Not a full SEO suite, content generator, or automatic site patcher.