AEO & GEO Optimization: What to Fix This Week
A hands-on 7-day worklist for getting your pages cited by AI answers, plus the mistakes that quietly cost you.
If you searched for how to do AEO and GEO optimization, you probably already know the definitions. The hard part is what comes next: which files and which sentences do you actually change today? This article is a worklist, not a glossary. If you need the concepts first, start with our complete guide to SEO, AEO and GEO.
What are you actually changing when you optimize for AEO and GEO?
Three things: writing sentences that can serve as an answer, structuring the page so machines read it without guessing, and leaving evidence worth citing. It is less about keyword density and more about rebuilding a document into a citable shape.
- Direct answers: two or three sentences right under a question-style heading, conclusion first. A paragraph that begins with "we'll explain below" rarely gets quoted.
- Facts as units: prices, timelines, coverage areas and conditions with numbers, units and an as-of date — not "affordable pricing."
- Structured data (JSON-LD): Organization, Article, FAQPage. The rule that matters is exact agreement with what's visible on screen.
- Rendering: turn JavaScript off and check whether the body text still exists in the HTML. If the text disappears, so does your chance of being cited.
- Crawler policy: use robots.txt and llms.txt to state access rules and point to your key pages.
- Sources and dates: cite primary material, and show published and updated dates.
How far can you get in one week?
At one or two hours a day, you can rebuild one or two revenue-critical pages and establish a measurement baseline within a week. Finishing a single high-value page beats half-rewriting the whole site.
- Day 1 — Collect 20 questions customers actually asked. Inbox threads, call notes and search query reports are your sources.
- Day 2 — Map questions to pages. One page, one question. A page covering five questions answers none of them sharply.
- Day 3 — Write a three-sentence direct answer at the top of each page, and convert headings into questions like "How long does production take?"
- Day 4 — Build a fact table: price, timeline, what's included, what's excluded, tax treatment, as-of date.
- Day 5 — Write JSON-LD and clear every error in a validator.
- Day 6 — Check the page with JavaScript disabled, then tidy robots.txt and llms.txt.
- Day 7 — Ask ChatGPT, Gemini and Claude the same 20 questions and log whether your brand is mentioned or cited. That log is your baseline.
What mistakes show up most often?
- Raising keyword density without writing an answer — no quotable sentence, no quote.
- Putting ratings or reviews in JSON-LD that appear nowhere on the page. Mismatches erode trust.
- Publishing pricing and specs only as images or PDFs.
- Leaving stale numbers with no update date.
- Judging results by feel, with no baseline to compare against.
How does SAENRU handle this?
Our own site is the example. It is raw HTML with JSON-LD and llms.txt embedded, so the body copy and factual data stay readable even without JavaScript. Applying that same approach to other projects is what our SEO, AEO and GEO consulting does.
- Measured diagnostic report: KRW 190,000, 5 business days — covering Google and Naver search through to citation in AI answers. The fee is fully credited if you proceed to a build contract.
- Build package: from KRW 3,600,000 — structure, markup and document formats actually rewritten.
- Monthly operations: from KRW 1,470,000 per month — repeat measurement against your question set, plus content updates.
- No site yet? SAENRU Studio builds websites from KRW 2,700,000 (about 2 weeks) and web app MVPs from KRW 8,700,000 (4–6 weeks), handed over as a full GitHub repository. All prices exclude VAT.
There is no shortcut in AEO and GEO, but there is an order: gather questions, write answers, make them machine-readable, then measure. This week, just finish one page properly.