AI visibility
First we define the scope of the content work: the number of topics and URLs, new materials or updates, the formats (FAQs, guides, comparisons, definitions, descriptions) and the level of implementation support and verification required. I then audit how ready the content is for generative answers and prepare a map of topics, questions and entities linked to specific URLs.
I start the cooperation by collecting users’ questions and query variants and checking where the content does not give a clear answer. I then put the topics and entities in order, so that definitions and naming are consistent across pages. On that basis I plan the rewrites and additions and implement them in stages.
I collect problem, comparison and how-to questions and map them to sections of the page in order to point out missing or imprecise parts of the answer.
I define the key concepts, attributes, relationships and synonyms and standardise the definitions and naming, so that the pages describe the topic compatibly.
Based on the mapping and the model, I prepare editorial decisions and briefs, and add to, rewrite or update the content where information around important concepts is missing.
Kick-off and defining the project scope consists of gathering information about the offer, the audience and the topic priorities, and clarifying what type of content is to be created or rebuilt. At this stage we establish the languages in which the materials are to work and the way of cooperating: who is responsible for preparing information on the client’s side and what content approval will look like. In parallel, we put the priorities in order, so that it is clear from the start which topics and user needs matter most. The result is a shared, operational starting point for the audit and the further work.
During the kick-off, decisions are made that directly determine the scope of the work and the number of URLs handled. We establish, among other things, whether we are preparing new content or updating existing materials, what the level of implementation support is to be, and what level of legal or industry verification is required. We also clarify the preferred formats (e.g. FAQs, guides, comparisons, definitions, descriptions) and which of them are a priority at a given stage of the project.
Access and input materials for the analysis cover everything needed to start reviewing the content and prepare recommendations for publication. In practice this means access to the CMS or to the publication process, and data about the content, such as URLs and the site structure. Brand guidelines and product information are also essential, so that the content is consistent with the company’s communication. Another important element is a contact for a subject-matter expert who can verify the accuracy of the content.
The completeness of these inputs affects how smoothly it is possible to move from analysis to preparing changes and publishing. The URLs and structure information provided make it possible to work on specific pages instead of relying on assumptions. The brand guidelines and product information are the basis for standardising the terminology and the way the offer is described in subsequent materials.
The decisions that affect the content scope determine how many topics and URLs the cooperation will cover and what type of work will be carried out. The arrangements concern whether new content is to be prepared or existing materials updated. The level of implementation support is also clarified, which shapes how the materials are prepared for publication. In addition, the required level of legal or industry verification is agreed, where applicable.
The scope is also affected by the chosen content formats, because they determine the structure of the page and the kind of information that has to be provided. In practice, it is established whether the priority will be formats such as FAQs, guides, comparisons, definitions or descriptions, and which of them are to be created first. These decisions organise the work in the backlog and make it easier to assign topics to specific URLs. As a result, the following stages (audit, architecture and briefing) are based on clear assumptions.
A content audit for readiness for generative answers consists of reviewing the existing materials and indicating what needs clarifying or rebuilding. The completeness, clarity and structure of the answers are verified, so that the content can be clearly interpreted and summarised. The consistency of definitions and naming is checked, as is whether the information is up to date, including the presence of sources where they are needed. The trust elements that support the credibility and readability of the message are assessed too.
The audit includes an intent analysis and an analysis of user questions, and mapping them to the sections that can be cited in answers. In parallel, topics and entities are modelled: the key concepts, attributes, relationships and synonyms are identified, and the definitions are then put in order to avoid inconsistencies. The result is a map of topics and entity coverage that links questions, related concepts and required information to specific URLs. This map shows the gaps and indicates the pages that need to be reworked to better answer users’ real needs.
Analysing user intent and questions consists of collecting typical questions and query variants and translating them into specific content elements on the page. In practice, I organise the questions according to whether they are problem, comparison or how-to questions, so that it is clear what information has to appear in the answers. I then map these needs to the sections that can be cited in generative answers. This shows where the content is insufficient and which passages need clarifying.
The result of the analysis is a list of questions assigned to specific sections and planned answer passages, which makes it easier to prepare a structure for citing and summarising. I also point out the places where it is worth stating conditions, limitations or steps explicitly, so that the answers are unambiguous. Mapping prepared in this way is the input for further editorial decisions and for the briefs, because it shows which elements should be in the content in order to answer real queries. The analysis takes query variants into account, so that a single page can cover more than one way of phrasing a question.
Modelling topics and entities for content consistency consists of defining the key concepts, their attributes, relationships and synonyms within a given domain. On that basis I put the definitions and naming in order, so that different pages do not describe the same phenomenon in a contradictory or incompatible way. The aim is consistency, which makes it easier to summarise the content and select passages for answers. A side effect is also faster verification of whether the site has information gaps around important concepts.
This stage produces an organised picture of what information should appear for specific topics and which elements must be named consistently. This directly supports the later preparation of the coverage map and the decisions on whether given materials need updating or creating from scratch. Modelling also helps to divide the content into pieces that define concepts and pieces that answer users’ questions in a specific context. This makes it easier to plan how the pages are to cover the topic together without duplicating or diluting definitions.
Feedback from clients and industry people I have worked with on SEO projects.

I had the chance to work with Kuba at Kulturalnie o SEO, an event I organise. Kuba did a great job as a speaker and received high marks from the audience. He showed professionalism and broad knowledge. In other projects at Vestigio, Kuba shows enormous commitment, a willingness to explore and implement new ideas, and excellent organisation of his work.

You talk to me, not a salesperson
I work as a freelancer: the same person reads your message, prepares the quote and then runs the project. No sales team in between.