AI & SEO automation
I design and implement AI-supported SEO mechanisms: from analysing data and SEO rules, through generating on-page elements, to quality validation. I work with modules that have defined inputs and outputs, tests on samples, and integration with publishing and monitoring. The kick-off sets out the use cases, roles, acceptance criteria, access and level of automation.
I start with a kick-off, in which we specify the SEOAI use cases, the priorities and the rules of cooperation. I then collect the required access and input data and prepare a plan of the mechanisms and the approval path. From there I work iteratively: design, quality tests, integration and monitoring.
I establish the use cases and priorities, roles, acceptance criteria, and security and compliance rules, and then collect access to data on traffic, queries, indexing/crawl, content and publishing.
I match the SEOAI mechanisms to the data and structure of the site, define modules with inputs/outputs, and prepare the SEO rules, quality validations and the path for approving results.
I test quality on samples, finalise the review and editing workflow, integrate the results with the publishing process, and monitor quality and errors based on run logs and indexing/crawl signals.
Building AI-supported SEO mechanisms means designing and implementing repeatable SEO processes that use AI for analysis, generating materials and quality control. The scope covers work from analysing data and SEO rules, through generating specific on-page elements, to integrations with the publishing process and monitoring. In practice, the mechanisms are designed as modules with clearly defined inputs and outputs, so that the team can run and assess them in a consistent way. Results generated by AI require validation, because factual errors or inconsistencies with the offer may appear.
As part of this service, a set of SEOAI mechanisms is selected to match the data and structure of the site, and then the quality rules and approval path are prepared. The mechanisms may cover, among other things, keyword analysis, intent mapping, brief generation, on-page recommendations, internal linking and structured data. Once the mechanisms are designed, the plan includes quality tests on samples, finalising the review and editing workflow, and then integration with the stages of work, so that the results can be implemented. The scope and workload depend, among other things, on the number of page types and languages, the quality of the input data, the degree of integration with publishing, the required level of compliance/security and the availability of experts for review.
The kick-off and specifying the scope of the SEOAI project serve to establish the specific use cases, priorities and rules of cooperation, so that the mechanisms can be implemented and assessed safely. At this stage we specify the areas to be supported (e.g. content, on-page, internal linking) and which outputs are to go into the editorial and publishing process. The roles on the client’s side, the acceptance criteria and the risks that may affect the quality and repeatability of the results are established. In parallel, security and compliance rules are defined for sensitive data, citation/sources, copyright, brand tone and content that requires mandatory review.
It is also crucial at the kick-off to secure the foundations for further analytical and design work. Access and input data are essential for delivery, including traffic data and query data, information on indexing/crawl, the content and structure of the site, and access to the places of publication (e.g. content system, repositories). On the basis of these arrangements it is possible to move on to the inventory of data sources and the SEO audit for automation, which show what can realistically be automated and where manual work will be needed. As part of specifying the scope, the level of automation and approval is also discussed: whether materials go to an editorial queue, require expert approval, or can be published after automatic validations.
Data access requirements cover providing the access and input materials that make it possible to design, run and assess SEOAI mechanisms on the site’s real data. In practice, what is needed is traffic and query data, information on indexing and crawl, and the content and structure of the site. In parallel, access is required to the places where the results are to be implemented, that is, to publishing channels such as the content system or repositories. Without these elements it is not possible to carry out a reliable inventory of data sources or to prepare the input sets for later generation and validations.
As part of the work, the input data is organised so that it can be used consistently in repeatable modules. This covers unifying the input formats, cleaning the data and preparing the fields required by the mechanisms, e.g. URL, page type, offer, attributes, keywords and intents. On this basis it is possible to determine which elements of the site and which page types the work concerns and what the outputs will look like. The scope and workload depend on the quality of the input data, the number of page types and languages, and the degree of integration with the publishing process.
An SEO audit for automation consists of identifying the areas of SEO work that can be organised and brought into the mechanisms for generation, recommendations and validation. The starting point is an inventory of data sources, that is, a list and quality assessment of materials such as pages, templates, metadata, product or service data, categories and the current linking. The results of SEO work to date are also verified, in order to assess the consistency and repeatability of the data the mechanisms are to work on. Such an audit does not replace implementation, but it provides the basis for deciding what can be automated in a controlled way.
During the audit, the issues identified include missing metadata, duplication, inconsistent headings, topical gaps, misaligned intents and internal linking problems. The conclusions from this stage are used to select the use cases and to define the boundaries between automation and manual work. Based on the audit’s observations it is also easier to establish which elements will need quality rules and validations, and where additional input data will be required. The result is a list of areas and task types that make sense to implement as SEOAI modules.
Choosing use cases and the level of automation means translating the conclusions from the audit into specific SEOAI mechanisms and rules for using them on your site. At this stage the mechanisms to be built are chosen, such as briefs, topic clusters, link suggestions and category descriptions or product descriptions, together with a definition of where automation makes sense and where manual work is necessary. In parallel, the target scope of the modules is established, with clearly described inputs and outputs, so that they can be run in a repeatable way. The decisions are grounded in the real limitations of the data and site structure and in the client’s priorities.
Establishing the level of automation means specifying what the approval of materials will look like and where review appears in the process. In practice, it is defined whether the results are to go to an editorial queue, require expert approval, or can be published after automatic validations. The level of control is matched to the security and compliance arrangements, including the scope of content requiring mandatory review and the rules on sensitive data and copyright. The scope and method of delivery are also affected by factors such as the number of page types and languages, the quality of the input data, the degree of integration with the publishing process and the availability of experts for review.
Designing SEO prompts and templates means building repeatable formats for tasks and results that will feed the chosen SEOAI mechanisms. The starting point is preparing the data model and input sets, that is, unifying the input formats, cleaning the data and preparing the fields required by the mechanisms. This allows the prompts to work consistently on elements such as URL, page type, offer, attributes, keywords and intents. As a result, every template has a clearly defined context, scope and response format.
This work produces templates for specific tasks, such as a brief, meta title/description, headings, FAQ or elements supporting internal linking, together with instructions and constraints. SEO rules and quality validations are added to the prompts; they check, among other things, intent match, the risk of keyword cannibalisation, consistency with the site architecture, duplication control and the required page elements. The design also takes into account metadata length limits and the requirements arising from the security and compliance rules, including brand tone and the scope of content requiring review. Prompts prepared in this way are the basis for later generating SEO materials in agreed formats and for quality tests on samples.
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.