# GEO: writing for people and for AI answers

# GEO: writing for people and for AI answers

Carlos Eduardo de Souza · 2026-09-30

Search is no longer only a list of links. What changes in content and code when answers come from AI.

Search used to end on a page of links. More and more, it ends on an answer written by AI, with or without a link to you. Content still wins, but it has to be written and built for both readers.

### What changes in the content

 Answers quote sentences that stand on their own. Clear claims, numbers with their source and one idea per paragraph get cited; clever intros do not.

### What changes in the code

- Every text in the HTML the server sends, not only after scripts run.
- Structured data that says what the page is: an article, a service, a FAQ.
- A plain text version of each page and an llms.txt that lists them.

> Write for the person first. Then make sure the machine can read what you wrote.

None of this replaces classic SEO. It adds a second reader with different habits.

## More from the journal

- [Journal](/blog.md)

- [Machine speed, human signature: how we use AI without losing accountability](/blog/machine-speed-human-signature.md): AI drafts a lot in our pipeline. People still decide. Here is where AI sits in each stage, and where it does not.
- [TYPO3, WordPress or headless? Choosing a CMS for a multilingual site](/blog/typo3-wordpress-or-headless.md): Three questions decide it: who edits, how many languages, and what your IT allows.
- [GEO: writing for people and for AI answers](/blog/geo-writing-for-people-and-for-ai-answers.md): Search is no longer only a list of links. What changes in content and code when answers come from AI.
- [React Native in 2026: when one code base is enough](/blog/react-native-in-2026-when-one-code-base-is-enough.md): Where cross-platform wins, and the cases where we still write native modules.
- [Verification and validation: how we check every delivery](/blog/verification-and-validation-how-we-check-every-delivery.md): Done is defined at the start. At the end, we check against it, item by item.
- [Working from Curitiba with teams in Vienna and New York](/blog/working-from-curitiba-with-teams-in-vienna-and-new-york.md): Hours that overlap, rituals that travel, and what we learned about working across time zones.
- [Our origin: from code partner for agencies to AI-first engineering](/blog/our-origin.md): Coopers started in 2013 as the team agencies called when they needed code. What we kept from those years, and what changed.
- [How we build a website, step by step](/blog/how-we-build-a-website.md): Five steps from the first question to the first weeks after launch, and what you see and approve at each one.
- [Monthly maintenance: why a website is never finished](/blog/monthly-maintenance.md): A site nobody looks after gets slower, less secure and harder to find. What monthly maintenance covers, and how we run it.

---
HTML: https://coopers.digital/blog/geo-writing-for-people-and-for-ai-answers