You do not need a blog for AEO — what you need is a set of answer pages, each targeting a specific user question with the answer as its literal first sentence — the container (blog, knowledge base, glossary, product pages) matters far less than whether each URL cleanly answers a question the audience asks.
Google's helpful-content guidance is agnostic on format. It asks whether the page serves a real user need, whether the author has expertise, and whether the site itself is trustworthy. A well-structured product FAQ, glossary hub, or documentation page satisfies those criteria at least as well as a blog post.
The failure mode for blogs is scale for its own sake — publishing hundreds of thin posts to chase keywords. Google's guidance on scaled content abuse now explicitly targets that pattern. AEO amplifies the risk because answer engines quote sentences — thin, filler content has nothing to quote.
The practical structure that works: a small number of hub pages (topic overviews, glossary index, service pages) and a curated set of spoke pages (one per question), tightly cross-linked. Volume grows only when demand for new questions is real.
Publishing cadence matters less than publishing depth. A page that fully answers a question wins over ten pages that each cover a fragment.