
Look first, then write
Like building a house, there is a plan first. We check what people search for, what they ask AI and what competitors already cover.
No filler. We plan which content your website needs so it gets found in Google and cited as a source by AI systems, and we measure what every piece brings.


I only write what someone actually asks.
In plain wordsA content strategy defines which pages and texts your website needs, which question each page is for and how it has to be built so Google finds it and AI systems cite it. Writing comes after that.

Like building a house, there is a plan first. We check what people search for, what they ask AI and what competitors already cover.

No new page without its own search intent. So your pages do not compete with each other, and each answers one question really well.

The answer comes first, claims are backed by numbers and sources. So an AI can take over a sentence without sounding vague.
Many pages are written before anyone checks whether people search for them. That can be clarified upfront, and that is exactly the job of a content strategy.
The lever comes before writing: if you know which question a page should answer and which sources AI uses for it today, you write with more focus.
Sources: 96.55%: Ahrefs Search Traffic Study. Up to 40%: Princeton GEO, Aggarwal et al., KDD 2024, effect strongly depends on the topic. +25.7%: AirOps 2026. 95%: measurements in the Atziry platform, December 2025 to October 2026.
Derived from what we really deliver in projects. Not included is the coding on your website, but the specs are written so your team can implement them directly.
| Aspect | Deliverable |
|---|---|
| Data foundation | Crawl of your website and your key competitors, entities and relations as a knowledge graph |
| Content architecture | URL matrix and keyword map per language, clear page roles |
| Technical specs | Internal links, canonical, hreflang and structured data as instructions for developers |
| Content | Page copy and articles with sources, written separately for each language |
| Editorial plan | Multi week plan with formats, voice rules and verified occasions |
| Measurement plan | Metrics per page role and reporting in the platform |
Five steps from data to measurement. Every piece has a measurable purpose.

Search data, questions asked to AI, competitor content and real customer voices from forums, comments and reviews.
Result: topics with demand

Page roles, topic clusters, internal links and a plan for when each piece gets updated.
Result: URL matrix and keyword map

New texts and reworked existing pages, with your own numbers, sources, comparison tables and FAQ with Schema.org.
Result: pages worth citing

Get visible where AI systems look for sources: industry portals, comparisons, directories.
Result: mentions beyond your website

Rankings, AI citations and leads per page in the platform. So you see which text works.
Result: metrics per page role
Three findings that would hardly have stood out without the view and went straight into the implementation rules.
All 9 internal links ran from a subpage to the home page. The subpages did not link to each other.
Only 10 of 24 pages had structured data. Of all pages, the ones where conversions are measured had none.
Pages covering the same entities without linking to each other are flagged by the platform as a suggestion.
For social too: the platform analyzes posts, shows which openers and formats perform better than usual and says when the data is too thin for a conclusion.

An app with a website in German, English and Spanish, two established competitors, hardly any visibility. Anonymized, the client agreed. We do not report results yet because implementation is ongoing.




Everything in one workspace, traceable.
In the first call we show where competitors get cited and you do not, and which pages pay off first. Free, no obligation, 30 minutes.
Your contact: Aredi Dragusha, [email protected]