Vuk Stojković
HOME  /  EXPERIENCE

Experience

Three engagements, three different technical problems. What the situation was, what I owned and what the hardest part of the job turned out to be.

Technical SEO across a portfolio of 20+ sites

Nexplay Media SA
Technical SEO Executive · 2026—present

The situation. Twenty-plus WordPress sites in the crypto and iGaming verticals, each with its own stack, publishing pace and migration history. No single audit covers them all, so what is needed is a repeatable system.

What I own. Technical audits through Screaming Frog, JetOctopus and Lumar; log analysis to understand crawl behaviour and optimise crawl budget; implementing and validating hreflang networks; resolving redirect chains, broken links and canonical conflicts.

The hardest part. Preventing SEO regression on a portfolio that never stops changing. That means QA before and after deploys, staging verification and validation of SEO-critical elements during migrations, all through the dev teams’ ticketing systems.

Log analysis Crawl budget Hreflang SEO QA Migrations AI in report analysis
20+ sites

A portfolio run in parallel, with different stacks and publishing rhythms

Log-level insight

Decisions from server logs, not from assumptions about what Googlebot does

No regression

A QA cycle before and after deploys, with verification on staging

International SEO across multiple markets

Clickout Media
Technical SEO Executive · 2024—2026

The situation. Several WordPress sites targeting different markets and languages. Incomplete hreflang networks, redirects inherited from old structures, and indexation that was unpredictable from site to site.

What I owned. Implementing technical SEO tasks across the portfolio, working on hreflang structures and international SEO, and systematically resolving redirect, broken-link and indexation issues.

The hardest part. A task-driven environment where a recommendation counts only once implemented. Working through ticketing systems and spreadsheets, aligning SEO and dev teams on priorities that shifted weekly.

Hreflang networks Indexation Redirect clean-up Working with dev teams
Multiple markets

Language and regional versions aligned through validated hreflang sets

Parallel work

Tasks across several sites at once, in a structured task system

Implemented

Focus on recommendations that reach production, not on the length of the audit

Technical tasks to specification

Finixio
Junior Technical SEO, freelance · 2022—2024

The situation. Other people’s audits, clear specifications and WordPress sites where a change has to be right the first time. There was no room for improvisation.

What I did. Executing technical SEO tasks to specification, optimising the WordPress backend (canonicals, redirects, hreflang) and implementing changes based on SEO audits.

What I learned. Precision and the discipline of working to a brief: what an audit looks like from the implementer’s side, and why a vaguely written recommendation never reaches production.

WordPress backend Canonical Redirects Audit implementation
To specification

Changes made exactly as defined, with no improvising on production

Backend focus

Work at the level of the WordPress setup, not just inside an SEO plugin

The foundation

Where the routine of technical SEO turned into practice

Tools and skills

What I work with daily, not a list of everything I have ever opened

Crawl and diagnostics

Screaming Frog
JetOctopus
Lumar
Server log analysis

Analytics and data

Google Search Console
Google Analytics 4
Ahrefs
Semrush

Areas

Crawl, indexation, log analysis
Hreflang and international SEO
WordPress SEO
On-page and technical audits

Way of working

QA and SEO validation
Tickets, staging, deploy checks
AI for analysing technical reports
AI as support in content work

Got a site with a similar problem?

Send a URL and describe what worries you. I look at the site before the call and tell you what I see.

Send an email See engagement plans