Technical SEO Lead | Based in EU
Hostinger
| Company | Hostinger |
| Category | Marketing |
| Location | Warsaw |
| Remote | Remote |
| Employment | Not stated |
| Level | Lead |
| Salary | Not stated by the employer |
| Posted | 29 May 2026 |
| Last verified | 6 Aug 2026 |
| Source | Employer ATS (ashby) |
Description
TECHNICAL SEO LEAD | BASED IN EU
Join Hostinger, and we’ll grow fast! 🚀
We’re shaping the future of online success — powered by AI and driven by people. With 900+ talented professionals and over 4 million clients in 150 countries, we help creators and entrepreneurs bring their ideas to life faster and easier than ever before.
Our mission: To provide tools that help individuals and small businesses succeed online faster and easier.
Our culture: Guided by 10 company principles https://www.hostinger.com/principles
Our formula for success: Customer obsession, innovative products, and talented teams.
YOUR ROLE AT HOSTINGER
Hostinger operates at real scale — millions of pages, dozens of locales, products launching constantly, and an engineering team that moves fast. Technical SEO at this level isn't a checklist. It's infrastructure. And right now, we need someone to own it.
As Technical SEO Lead, you'll be the person who makes sure Hostinger's organic foundation is solid, scalable, and ready for what search looks like today — and tomorrow. That means being as comfortable in a staging environment before a major launch as you are presenting a roadmap to stakeholders. It means connecting crawl budgets to billings and knowing which technical debt is actually costing us traffic.
This is a senior IC role — no direct reports, high cross-functional influence. The craft is the job.
Curious to learn more? Connect with your team: Orit Mutznik https://www.linkedin.com/in/oritsimu/
YOUR DAY-TO-DAY
Diagnose and fix
- Run continuous technical audits across Hostinger's large-scale, multilingual site — and own the fix end-to-end, not just the ticket.
- Lead pre- and post-migration audits for domain migrations, re-platforming, URL restructures, and CMS or framework changes.
- Investigate performance anomalies (traffic drops, ranking shifts, crawl issues) and resolve them before they compound.
Own the roadmap
- Build and drive the technical SEO roadmap — prioritized by commercial impact, sequenced with Product and Engineering planning cycles.
- Build SEO QA into pre- and post-launch workflows: review staging environments, prevent regressions, catch issues before they cost rankings.
- Build the business case for technical SEO projects — owning the impact, effort, and prioritization rationale end-to-end.
Build for scale
- Design and maintain technical SEO automations: indexability monitoring, sitemap validation, hreflang checks, redirect monitoring — using GSC API, DataForSEO MCP, and n8n.
- Own technical SEO best practices documentation so DRIs across SEO, Content, and Localization can enforce consistent standards without reinventing them.
- Run technical SEO split tests and advise on methodology for broader specialist testing initiatives.
Stay ahead
- Own Hostinger's technical readiness for AI-powered discovery — structured data for LLM citation, AI bot crawlability, and monitoring how AI crawlers access content at scale.
- Translate technical wins into language stakeholders care about — not "847 crawl errors fixed" but "we unlocked X pages blocking organic traffic to [product].
YOUR SKILLS AND EXPERIENCE
Must-haves:
- 5+ years of hands-on technical SEO on large, complex websites — with a track record of diagnosing real problems and shipping real fixes.
- Multi-locale SEO at scale.
- Deep expertise across the full technical stack: crawlability, indexation, site architecture, structured data, Core Web Vitals, JS rendering, hreflang, and multilingual SEO.
- Experience leading pre- and post-migration audits — you know what breaks, why it breaks, and how to stop it.
- Commercially minded: you prioritize by business impact, connect technical work to acquisition and billings, and never present a finding without a "so what".
- Confident working with engineering teams — you can scope a ticket, validate the fix, and explain the trade-off to a non-technical stakeholder