Answer engine optimization, or AEO, is a handy name for making a page useful when someone asks a search engine or AI assistant a question. The part I can control is the page. I can give it a clear answer, show a reproducible example, make the important text easy to find, and check whether search crawlers can reach it. I can also spend an afternoon counting appearances of a keyword. Only one of those activities helps a reader fix a broken signup form.
1. Start with the question a person would actually ask
Look at emails, comments, and notes from your own work. Capture the original question and the circumstance around it. “What should a thank-you page say before email confirmation?” is a better starting point than “thank-you page SEO.” The first gives you a situation, a decision, and a person waiting for an answer. Write it in your working notes, including whether the reader is about to subscribe, confirm, or open a file.
Draft the direct answer in two or three sentences. “Tell the reader to check their inbox, name the sender and subject, and explain that confirmation comes before delivery. Add a recovery instruction if the message stays missing.” Then work out the exceptions. If the download is available now, the page can give it immediately. If the provider handles verification on another page, the instructions need to describe that real flow. See my thank-you page guide for ways to explain the difference.
Put the direct answer near the top. Follow it with the details someone needs to act, such as a sample message, a screenshot you took, or the first check to run. A clear answer can be read on its own, and the surrounding page should still explain the conditions under which it applies.
2. Add something only your page can supply
A summary of several existing tutorials may help orient a reader. Give them a reason to keep yours open. Show a small test you actually ran. If you tested a signup flow, record what you clicked, the order of the screens, and how you verified delivery. Remove personal details. Explain what you’d try if the outcome differed. Use your own notes rather than asking a tool to fill in what might have happened.
For example, write a sample for a fictional brand and label it. Then show two versions: one when confirmation is pending, another when the download is ready. Identify which line changes and why. The example becomes useful to quote, link to, and adapt because the reader can see the underlying decision. A paragraph claiming your approach is “optimal” has far less to offer.
Keep an eye on the gap between description and evidence. A product page supports what the vendor lists. Your own test supports what you observed in the account and settings you used. The provider’s official documentation supports what it documents at the time you checked. Attribute each accordingly. My guide to using Claude for specific marketing jobs includes a prompt to separate supplied facts from unanswered questions.
Give the reader a result they can reproduce, and a date they can check.
3. Make the page legible in the browser and the source
Use a specific title, one main headline, and headings that follow the order of the task. Put the essential answer and example in readable page text. Write meaningful links from related pages. “Set up a SendSteed test list” gives a reader a clearer destination than “learn more.” Test the page with the keyboard and at a narrow width. If the answer exists only in a picture or a widget that loads later, include a text explanation that stands on its own.
Check status, canonical, robots settings, and internal links for your published URL. A public article should open directly at its intended address and be reachable from a related page. Include it in the sitemap if you want it discovered. Keep confirmation screens and private resources separate from public pages. Use the controls your hosting and search providers describe. A directive intended for crawler behavior is different from permission to access private content.
Add structured data when it accurately describes visible material. Article markup can describe the author, date, and headline. FAQ markup should match questions and answers visible on the page. The markup can help machines interpret the page. Treat any enhanced result as something the search provider decides, and check its documentation before expecting a particular display.
4. Read what the search providers actually say
Google Search Central’s AI features guidance says existing SEO practices still apply for its AI search features. Start with those: accessible pages, helpful content, relevant internal links, and text that matches what the page shows. Read the Google optimization guide for the provider’s current recommendations. An answer may be eligible and still never appear for a given query.
For ChatGPT search, consult OpenAI’s crawler documentation. It describes OAI-SearchBot and distinguishes it from other crawlers and user-triggered requests. If search discovery matters for a public page, check that the directives and hosting setup permit the access you intend. Inspect the real response, including headers, redirects, and any access screen. A private preview can be useful for editing and still be inaccessible to public discovery until it launches.
Use search results as observations. Write down the question, date, and what appeared, and repeat later if you have a reason. AI responses can vary with wording, location, product behavior, and timing. If someone quotes the page, check whether the quotation and source link convey the intended answer. A few appearances don’t tell you how many people found the page useful. The people who follow the steps or reply with a specific question can tell you more.
5. Give one answer page a month of attention
Choose an existing question page or publish a new one. In week one, write the direct answer and capture a working example. In week two, ask a reader to try it and fix the place where they pause. In week three, link to it from two relevant pages and check crawler access. In week four, review what people asked and whether the title and first paragraph still reflect the useful part of the page.
Keep a small changelog. Write the date, detail changed, source checked, and reason. If you added a new example, link straight to the section from your related guide. If you removed a tool recommendation because a plan changed, update the places that still refer to it. My first email list guide is an example of a page whose technical instructions need to match the real account flow. The weekly Radar routine gives you a simple way to capture those changes as you work.
A small page audit you can finish today
Open one published guide and read only its title and first screen. Can you tell whose question it answers? Jump to the strongest example. Can someone reproduce it from the text? Open the linked source and check the particular detail you use it for. Finally, find a relevant article on your site and make sure there is a plain link between the two. Those four checks can improve a guide even if no AI system cites it this week.
Handle questions that need more than one answer
Some questions have two correct answers depending on the reader’s situation. Put the condition in the heading or first sentence. For example, “If confirmation is pending, send the reader to their inbox. If confirmation is complete, show the resource link.” Follow each case with the source or test that supports it. A reader should be able to choose a branch without reading your whole article.
When you revise a fact, also check the related passages. Changing a headline to say a free plan supports a feature is easy. Removing an old claim in a table, caption, or FAQ takes a second read. Update the visible date only when you have actually checked the details it represents. A precise page is easier to maintain when every claim has a home.
Frequently asked questions
- Can a site guarantee an AI citation?
- No. Eligibility, discovery, and selection are separate steps. Improve the page and observe what happens for the questions you serve.
- Do I need a special AI file?
- Follow each provider’s current crawler documentation. Start with accessible HTML, clear links, and standard search controls.
- Should I add FAQ schema everywhere?
- Use it when the page contains genuine, visible questions and answers. Check the search provider’s eligibility rules for any enhanced display.