Answer engine optimization feels shapeless when you start. There is no ranking report to open and no single number to chase, so teams either stall or try to do everything at once. A month of structured work solves the first problem and prevents the second.
This checklist splits that month into four weeks. By day 30 you will have a clear position, a measurement setup you can trust, better pages and a routine. For background on any step, the AEO guide goes deeper.
Thirty days buys you the setup, not the results
Changes in how AI engines describe and recommend your brand usually take longer than a month to appear. The 30 days is for doing the groundwork properly, so that the months after it are worth measuring.
Say this out loud to whoever expects a report at the end of the month. A flat line on day 30 is normal. A missing baseline on day 30 is the real failure.
Week 1: decide what engines should say
Week 1 turns a vague goal into something measurable: one positioning sentence, the claims behind it, and the prompts you will track.
Write one positioning sentence
- Category. Use the words buyers use, not internal product language.
- Audience. Who the product is for, as specifically as you honestly can.
- Reason. Why it is the right choice for them.
- Sign-off. Get marketing, product and sales to agree, so the brand is described one way.
List the claims you want repeated
- Write down the facts an engine should get right: capabilities, integrations, pricing model, who it serves and who it does not.
- Next to each claim, note the page on your site that supports it.
- Flag claims with no supporting page, or that different pages state differently.
Build the prompt set
- Category prompts. What a buyer asks when looking for a product like yours.
- Comparison prompts. You against named competitors, and alternatives to them.
- Problem prompts. The symptom a buyer describes before they know the category exists.
- Branded prompts. A few, kept separate, as an accuracy check.
Take the wording from sales calls, support tickets and community questions rather than keyword tools. Our guide on which prompts to track explains how to build a set that holds up.
Week 2: find out where you stand
Week 2 produces the baseline. Run the prompt set in each engine, record how you appear, and write down every source the engines cite.
Take the baseline across engines
- Run every prompt in each engine you care about, such as ChatGPT, Gemini, Perplexity, Claude and Grok.
- For each answer, record whether you were named, where in the answer, and who was named instead.
- Keep the full answer text, not a yes or no, so you can reread it later.
- Report category and branded prompts separately, and each engine separately.
AI answers vary from run to run, so a single pass is a rough picture. Repeat the runs over several days for a steadier baseline. Noma does this automatically, asking each prompt once a day in each of the five engines it tracks, from a fresh session, and storing the full answers.
Map the cited sources
- List every URL cited across your prompts.
- Group them: your pages, competitor pages, review sites, publications, communities, documentation.
- Mark the sources that recur. Those are the ones shaping answers in your category.
Check sentiment and accuracy
- Tone. When you are named, is the description positive, neutral, hedged or negative?
- Errors. List every wrong fact with the engine, the prompt and the sources cited for that answer.
Week 3: fix the pages you control
Week 3 makes your important facts easy to find, easy to quote and consistent across your site.
Direct answers
- For each prompt, identify the page on your site that should answer it.
- Put a one or two sentence answer directly under the relevant heading.
- Create comparison, pricing or use-case pages where nothing answers the prompt today.
- Resolve the contradictions you flagged in week 1.
Structured data
- Organization schema for the company, and Product or SoftwareApplication schema for product pages.
- FAQ schema only where the questions and answers genuinely appear on the page.
- Validate the markup and confirm it matches the visible content.
llms.txt
- Publish an llms.txt file at the root of your site.
- Point it to the pages that best explain what you do: product, pricing, documentation, comparisons.
If you have not written one before, the llms.txt guide walks through the format.
Headings, bylines and freshness
- One H1 per page, with a logical H2 and H3 structure beneath it.
- Headings phrased as buyer questions where that reads naturally.
- Author bylines on guides and articles, with a line on the author’s expertise.
- A last-updated date on key pages, changed only when the content actually changes.
- Stale facts updated, starting with pricing and feature pages.
Crawler access
- Check robots.txt, firewall and bot protection settings for rules that block AI crawlers you want.
- Check server logs to confirm those crawlers are reaching your key pages.
Week 4: work on the sources you do not control
Week 4 starts the slower work: earning inclusion in the third-party pages engines cite and correcting wrong facts where they originate. Then you re-measure and set a monthly routine.
Third-party sources
- Take the recurring sources from week 2 and check whether you appear in them, and how.
- Complete and update your profiles on the review sites that come up.
- Ask genuine customers for reviews. Never buy or fabricate them.
- Contact authors of comparison articles that leave you out, with accurate information.
- Make sure partner directories, marketplaces and integration listings describe you correctly.
Corrections
- For each error from week 2, find the source that contains the wrong claim.
- Confirm your own page states the correct fact clearly.
- Ask the third-party publisher to fix it, or edit the listing yourself if you control it.
- Re-run the prompt once the source has changed.
Re-measure and set the rhythm
- Re-run the full prompt set in every engine, with exactly the same prompts as the baseline.
- Note what changed, but read little into it. Most of this month’s work will not have shown yet.
- Put a monthly review on the calendar covering visibility, position, sentiment and cited sources per engine.
Mistakes that waste the first month
Most first months go wrong in predictable ways, and almost all of them trade a trustworthy baseline for a quick sense of progress.
- Skipping the positioning sentence. Without it, the prompt set drifts toward whatever the team hopes to rank for, and page fixes pull in different directions.
- Tracking only branded prompts. You will appear in nearly all of them, so the numbers look healthy while category and comparison answers go unexamined.
- Fixing pages before measuring. Changes made before the baseline cannot be separated from the starting point, so you lose the ability to see what they did.
- Publishing volume instead of answers. A burst of new blog posts rarely helps as much as rewriting the openings of the pages that should already answer your prompts.
- Ignoring the sources. Owned pages are the comfortable part. The third-party pages engines cite are often what decides whether you are named.
- Reporting a result on day 30. Promising movement in a month sets up the whole program to look like a failure when the real changes arrive later.
How do you know if AEO is working?
Watch the trend on your fixed prompt set over several months, engine by engine. More frequent and more favorable mentions, and more citations of your own pages, are the signal.
Do not change the prompt set to improve the numbers, and do not judge progress on a single day’s answers. Measuring the same thing the same way is what makes the results believable when they arrive.
What to keep doing after day 30
In rough order of return on effort:
- Review each engine monthly and pick the single largest gap against competitors.
- Decide whether that gap is an owned-page, third-party or accuracy problem, and work on that.
- Keep product facts current on your own pages whenever pricing, features or positioning change.
- Keep chasing corrections and inclusion in the sources engines cite.
- Log the date of every significant change, so later movement can be tied to a cause.
- Add prompts only in deliberate batches, and never remove one because the answer is unflattering.
The first month is the easy part to plan. The months after it are where AEO actually pays off, and they only work if the setup was honest.