Italian SEO and GEO for brands and agencies
I handle two things that the Italian market almost always treats as one: the words Italian customers search with, and the words AI assistants use when they talk about you in Italian. The first is keyword research done in Italian, not translated from German. The second is a review of what ChatGPT, Gemini and Perplexity actually answer when an Italian customer asks about your product.
Who it is for
The service is for people whose Italian pages are live and bringing in less than they should.
- Brands with a published Italian site that gets little organic traffic from Italy.
- SEO and GEO agencies that cover the technical side and need a native speaker for keywords, content and AI answers.
- Marketing teams who want to know what AI assistants tell Italian customers about their products, before hearing it from a customer.
The problem I find most often
A keyword list translated from German or English produces correct terms that almost nobody searches for.
People searching in Italian have their own habits, and they do not match the German ones. Sometimes Italian uses English where German stays German: people search for “scarpe running”, not “scarpe da corsa”, while German searches for “Laufschuhe”. Sometimes it runs the other way. Neither can be deduced from the source; both have to be checked against the Italian market.
The same holds one level up. An AI system can cite your page and render it with a calque or in the wrong register, and that text reaches your customer presented as a neutral answer. Getting cited is a technical problem. Getting cited in Italian that holds up is a linguistic one, and that is the part I handle.
What you receive
- Italian keyword map: search terms per page, with intent and priority, built on Italian search behaviour rather than on translated German terms.
- On-page work: rewritten titles, meta descriptions, headings and FAQs, or the recommendations if you would rather your team applied them.
- AI answer review: your customers' questions put to the main assistants in Italian, each answer assessed for accuracy, language and brand voice, and each issue linked to the page it most likely comes from.
How I work
Scope. Which pages and products matter, who you compete with in Italy, which questions Italian customers actually ask.
Italian keyword research. I start from how people search in Italy, comparing Italian competitors and the language that reaches your customer service. I look at German keywords to understand intent, not to translate them.
On-page work. Titles, descriptions, headings, FAQs and body copy adjusted to the map, without losing the brand voice. The language-bound technical checks belong here too: hreflang, Italian slugs, Italian metadata and structured data text.
AI answer review. I put your customers' questions to the main assistants, repeating each question several times because answers vary between runs. I record what they say about you: wrong or outdated facts, calques, tone that is off.
The method is public and you can run it yourself: Do AI systems cite different sources in Italian and German?
What I need from you
- Read access to Search Console, if you have it. Without it I still work, but page prioritisation becomes an estimate.
- The list of pages and products that genuinely matter for the Italian market.
- Whoever can approve copy changes, because on-page work touches already published text.
Scope and timing
Agreed per project, based on the number of pages and markets. An AI answer review on a narrow scope starts from about €550 (excl. VAT) and closes within a few days. A keyword map with on-page work across a full e-commerce site takes several passes, planned before we start.
What I do not do
I do not handle site-wide technical SEO: indexing, site speed, server configuration and URL structure stay with your developer or agency. I do the language-bound technical checks and stop there, because that is where my competence ends and theirs begins.
I do not sell guaranteed rankings or traffic forecasts. What I can commit to is the method and the documentation of what I found.
Frequently asked questions
Does GEO actually work, or is it a fashion?
Some practices have evidence behind them and some do not, and the two are worth keeping apart. That these systems retrieve parts of a page rather than whole pages, that consistent terminology helps a text get cited, and that sources shift with the language of the query are all documented findings. That an llms.txt file influences source selection is not: I recommend it because it costs little, not because its effect has been measured.
Is translating the German pages that already rank enough?
There is no evidence for it. The reference study on AI citations tested German but not Italian, so behaviour in the Italian market has to be checked case by case rather than inferred.
Can I commission only the AI answer review?
Yes, and it is the fastest way to find out whether this concerns you at all. It is also the most honest starting point: if the assistants never mention you in Italian, the problem sits upstream of keywords.
Do you work alongside our SEO agency?
Yes, and that split works best. They hold the technical side, I hold the language. I also work white-label, with deliveries under the agency's name.
Why not just correct the text with a free AI tool?
Because the part that matters for search is not correctness. An AI tool can make a page read more smoothly, but it does not know which terms Italian users actually type: that takes search data, not a language model. GEO adds one more limit. Asking an assistant to correct your text tells you nothing about what that assistant, or the others, answer when your customers ask a question in Italian. You only find that out by asking the questions and recording the answers, which is the review described above.
Related pages
- Do AI systems cite different sources in Italian and German?
- How to write Italian that AI systems can cite (in Italian)
- GEO glossary for Italian content
Send me one Italian page and I will tell you what a native reader notices. Book a free review.