“AEO” is often sold as a separate switch that makes a website appear in AI answers. In practice, the strongest foundation is still excellent technical SEO plus content that is clear, original, attributable and easy to extract without losing its meaning. This guide explains what I implement in WordPress and what I refuse to promise.
No plugin or schema block can guarantee rankings, citations or inclusion in an AI-generated answer. The goal is to remove technical ambiguity and publish information worth retrieving.
Start with crawl and index control
Search engines and AI-powered search systems cannot use pages they cannot reliably discover or interpret. Confirm that important pages return a successful status, are internally linked, have a self-referencing canonical URL and are not blocked by robots directives.
- Use clean, stable permalinks.
- Keep one preferred URL for each page.
- Submit the WordPress XML sitemap in search-console tools.
- Noindex thin search, date and author archives when they add no unique value.
- Fix broken internal links and redirect obsolete URLs deliberately.
Write a distinct search summary for every important page
The title, visible H1, excerpt and meta description should describe the same page without being identical boilerplate. A good article excerpt explains the reader outcome; it should not simply repeat the first paragraph.
Use semantic page structure
One descriptive H1, useful H2 sections, lists, tables and code examples help humans scan the page and help machines identify its parts. Headings should represent questions or decisions, not visual styling.
Show authorship and evidence
Technical advice is more useful when readers can see who wrote it, when it was updated and which implementation supports the claim. Link to an author/profile page, relevant project or repository where appropriate. Do not create fake reviews, credentials or performance numbers for perceived authority.
Use structured data that matches the page
Structured data is a machine-readable description, not a place to add invisible marketing claims. A professional engineering site can reasonably use:
| Page | Useful schema |
|---|---|
| Homepage/profile | WebSite, Person, ProfilePage |
| Technical article | BlogPosting and BreadcrumbList |
| Project archive | CollectionPage |
| Normal page | WebPage |
| Visible FAQ | FAQPage only when the same questions and answers appear on the page |
Avoid publishing SoftwareApplication, review or rating markup unless the visible page contains accurate supporting information and meets the relevant eligibility rules.
Build internal topic paths
One isolated article is less useful than a connected body of work. Link plugin architecture articles to REST, debugging and quality-gate articles. Link engineering pages to the project or case study that proves the implementation. Use descriptive anchor text rather than repeating “click here.”
Make the article genuinely useful
AI-assisted drafting can accelerate research and editing, but scaled generic pages create repetition and no distinctive value. Add real decisions, examples, trade-offs, checklists and limitations. Remove paragraphs that could appear unchanged on any website.
Consider AI discovery files carefully
An llms.txt file can provide an experimental plain-text overview for systems that choose to read it. It does not replace robots.txt, sitemaps, normal HTML, canonical tags or high-quality content. Treat the human-readable page as the source of truth.
Technical implementation checklist
- Unique title, H1, excerpt and meta description
- Canonical URL and correct robots directive
- XML sitemap discovery
- Open Graph and social image fallback
- Accurate contextual JSON-LD
- Breadcrumbs and internal related-reading links
- Visible author and updated date
- Fast, responsive, accessible reading experience
- No duplicated or fabricated content
- Analytics and search-console measurement
How to measure progress
Track indexed pages, impressions, queries, clicks, crawl errors and the performance of individual articles. For AI search, record referral traffic and manually verify citations when they appear, but do not treat anecdotal screenshots as a complete measurement system.
The engineering standard
A technically optimized page still needs a reason to exist. My standard is simple: a reader should leave with a clearer decision, a safer implementation or a reusable workflow. SEO and AI search readiness should improve access to that value, not substitute for it.
Related implementation
See how the ideas map to working code.
The public repository connects the article’s architecture, security, REST, blocks, CLI, privacy, testing and CI concepts to working code.