Organic Growth & SEO Strategy
Enterprise SEO strategy, prioritization, measurement and organic growth.
SEO, analytics
and team leadership
SEO is the core discipline. The page shows what I own, the tools I use and the cases that demonstrate each capability.
Leadership scope
What I own as a Head of SEO
Technical SEO & Architecture
Large-scale catalogs, crawl and indexation, platform changes and release reliability.
Product & Engineering Leadership
Requirements, prioritization, implementation support and release validation.
Team & Operating Systems
Team leadership, capacity management, automation and cross-functional execution.
Area 01
SEO
SEO
SEO strategy & organic growth
What the team gets
An agreed priority plan: what to do first, why it matters and how the outcome will be measured.
How I work and the tools I use
Set SEO direction using demand, site state and team capacity.
When this is especially useful
When technical fixes, content and catalog development all compete for limited resources.
What I take ownership of
Connect search demand, site evidence and business goals; build the SEO plan and KPIs, align dependencies with engineering and revisit priorities as evidence changes.
SEO strategyPrioritization and KPIsCompetitive analysisOrganic growth
Working context: SEO roadmap · KPIs · e-commerce · competitive analysis
SEO
Technical SEO & release reliability
What the team gets
Reproducible defects and actionable requirements instead of a vague “organic traffic dropped.”
How I work and the tools I use
Verify technical page behavior and define requirements that affect crawling, canonicalization and indexability.
When this is especially useful
On large sites with frequent releases, redirects, filter parameters and multiple page templates.
What I take ownership of
Check HTTP behavior, redirects, canonical policy and indexability; define the expected state and validate it after release.
IndexationRedirectsRobots and canonicalsPost-release validation
Working context: HTTP · redirects · robots · canonicals · Screaming Frog · automated checks
SEO
Semantic demand & large-catalog architecture
What the team gets
Clear landing-page rules: when a new page is justified, when an existing page is enough and how to avoid duplicate inventory.
How I work and the tools I use
Connect search demand to categories, tags and filter pages in a large catalog.
When this is especially useful
When one category is too broad for demand but exposing every filter combination would create duplicate search inventory.
What I take ownership of
Cluster queries by intent, choose the right page type and validate internal linking and cannibalization risk.
Keyword researchClusteringTags and facetsInternal linking
Working context: Key Collector 4 · KeyAssort · A-Parser · semantics · internal linking
Area 02
Answer optimization (AEO)
AEO — search answers
Answer-focused content (AEO)
What the team gets
Content with clear answers, supported facts and explicit applicability — useful regardless of the search interface.
How I work and the tools I use
Structure content so a direct answer remains clear, supported and useful when extracted from the full page.
When this is especially useful
When the user needs a concrete answer but the page is indirect, overly long or missing important conditions.
What I take ownership of
Define the question and intent, structure the answer and verify that extracted passages retain meaning and evidence.
Questions and intentsAnswer structureFact extractabilitySearch-answer validation
Working context: question analysis · answer structure · technical accessibility · SERP validation
Area 03
AI search visibility (GEO)
GEO / AI Search
Generative search visibility (GEO)
What the team gets
A clear measurement plan: what to capture before changes, what to compare after and what evidence is needed for a decision.
How I work and the tools I use
Design a measurement program for brand presence, citations and factual accuracy in generative answers.
When this is especially useful
When a company needs more than anecdotal screenshots to understand its presence in AI search.
What I take ownership of
Define query samples, commercial-fact availability requirements and repeatable before/after measurement.
Prompt scenariosVisibility and citationsSource analysisChange validation
Working context: AI-answer measurement · citations · response sampling · ChatGPT · Gemini · Perplexity
Area 04
Artificial intelligence (AI)
AI
AI in analytics, content & automation
What the team gets
Faster drafts and testable hypotheses without treating model output as evidence by itself.
How I work and the tools I use
Use language models for synthesis, content preparation and repeatable workflow steps with explicit validation.
When this is especially useful
When the work involves many observations, structured drafting or a candidate automation workflow.
What I take ownership of
Prepare the source data, task and quality criteria; separate generation, evidence checking and the final human decision.
Hypothesis generationExploratory analysisQuality controlAutomation chains
Working context: ChatGPT · LLMs · Codex · Claude Code · human review
Area 05
Python and automation
Python / automation
Python & SEO automation
What the team gets
Repeatable data collection, transformation and validation without redoing the same manual steps.
How I work and the tools I use
Use Python as a working tool for repeatable checks and data processing, with existing libraries and AI-assisted development.
When this is especially useful
When the task can be described as a repeatable algorithm: fetch data, join sources, detect anomalies or prepare an output.
What I take ownership of
Define the algorithm and acceptance criteria, assemble or adapt the solution and validate it on real data.
Data collectionTransformationValidationIntegrations
Working context: Python · APIs · n8n · AI-assisted development · A-Parser
Area 06
Analytics and data (BI)
Analytics / data
Search analytics & BI
What the team gets
Prepared evidence for a concrete decision: where the change happened, what might explain it and what to investigate next.
How I work and the tools I use
Combine search, page and assortment data to investigate changes by category and demand cluster.
When this is especially useful
When a top-line chart shows movement but does not explain which pages or demand areas are responsible.
What I take ownership of
Define the required dimensions, sources and comparison rules; design views for specialists and leadership.
ClickHouseSuperset / DataLensClusters and rankingsDecision dashboards
Working context: ClickHouse · Superset · DataLens · A-Parser Enterprise · web analytics
Area 07
Product and engineering
Product & engineering
Product & engineering collaboration
What the team gets
A clear delivery brief: expected behavior, constraints and acceptance criteria.
How I work and the tools I use
Turn SEO requirements into implementable product and engineering changes and validate the result after release.
When this is especially useful
When the solution depends on CMS behavior, templates, catalog logic, backend or frontend code and a generic SEO recommendation is not enough.
What I take ownership of
Explain the problem and risk, compare implementation options, define acceptance criteria, run SEO UAT and verify the real post-release behavior.
CMS requirementsServer-side renderingEngineering briefsRelease validation
Working context: CMS · SSR · backend · technical requirements · release validation
Area 08
Leadership and mentoring
Leadership
SEO leadership & mentoring
What the team gets
Clear priorities, regular outcome review and explicit ownership inside SEO and across partner teams.
How I work and the tools I use
Set priorities and operating rhythm for the SEO team and help specialists take ownership of increasingly complex areas.
When this is especially useful
When demand exceeds capacity, execution depends on several departments or team members need support with complex technical decisions.
What I take ownership of
Use KPIs and work reviews, explain decision logic, give feedback and progressively transfer ownership through real cases and validation.
Priorities and KPIsOperating reviewsMentoringCross-functional work
Working context: KPIs · roadmap · case reviews · feedback · operating standards · cross-functional collaboration
Practical advantage for an employer
Working toolkit
I have a familiar toolkit for keyword research, parsing, technical checks and analytics. It helps me start faster and assemble a practical workflow without unnecessary setup.
Search analytics
Google Search Console
Indexation diagnostics and analysis of queries, pages and organic-search changes.
Web analytics
GA4
Analysis of user behavior and commercial actions after organic-search visits.
Technical SEO
Screaming Frog SEO Spider
Crawling and validation of redirects, metadata, canonicals, indexability and other technical signals.
Market research
Ahrefs
Search-demand, backlink and competitive analysis.
Automation
Python
Repeatable data processing, validation, integrations and SEO workflow automation.
Analytics and BI
ClickHouse + DataLens
Storage and analysis of large SEO datasets with dashboards for specialists and management.
Parsing and data
A-Parser Enterprise
Large-scale collection of search and web data for analytics and automated checks.
Keyword research
Key Collector 4
Collection, cleaning and operational processing of large keyword sets and search demand.
Clustering
KeyAssort
Keyword clustering for catalog architecture, categories and landing pages.