Want to know if this job is worth applying to?
Greater London, England, United Kingdom
Onsite
Not Available
TL;DR:
How people discover Lovable is being rebuilt in real time. They now find software through Google, AI Overviews, ChatGPT, Claude and others, and nobody has the full playbook yet. We're looking for an SEO and AEO specialist who wants to write it for Lovable and turn that visibility into subscribers and revenue. You're technical enough to land your own code and agentic enough to build the tools you need with AI. One sprint you're fixing how lovable.dev gets crawled and rendered; the next you're shipping pages for our highest-intent searches, or an agent that tracks where Lovable shows up in AI answers. Your first instinct is always: will people and answer engines find this, and does it help us grow?
Why Lovable?
Lovable is the software creation platform that gives people the power to act on the problems closest to them. For decades, turning an idea into software required so much capital, technical fluency, and time that many ideas never came to life. Lovable is the counterargument: a platform for all people with ideas, ambition, and problems worth solving. From solopreneurs to small business owners to teams at companies like Adidas and Zendesk, people have built over 60 million projects on Lovable since its launch in November 2024. And we’re just getting started.
We’re building a generational company from Stockholm, with growing teams in London, Boston, New York, and San Francisco. Our team is small, talent-dense, and moving quickly, with a culture rooted in extreme ownership, high velocity, and low-ego collaboration. We look for people who care deeply, ship fast, and are eager to make a dent in the world.
Lovable is one of TIME’s 100 Most Influential Companies and has been recognized on the Forbes AI 50 and CNBC Disruptor 50, reflecting our momentum as one of Europe’s fastest-growing AI companies and one of the most ambitious places to build in this next era of software.
The role
You'll own organic discoverability for Lovable. Answer engines come first, on top of a strong foundation in traditional search. You do the strategy, building and measurement, there's no queue between an insight and a live change.
You'll build most of your tools, pages and agents on Lovable itself, and take what you learn straight to the product team. Millions of apps are published on Lovable and each one needs to be found too, so what works for lovable.dev should become better defaults and guides for our users.
What we’re looking for
5+ years in SEO, AEO or organic growth on a user-facing web product at scale. Results you've driven count for more than years.
Hands-on AEO. You've tracked how AI assistants mention and cite a brand, tested what moves it, and can show the results.
Deep technical SEO. Rendering, crawling, indexing, structured data, sitemaps, canonicals and internal linking at scale. When something breaks, you find out why.
Agentic by default. You use AI coding tools and LLM APIs to build agents, scripts and internal tools that automate audits, monitoring and reporting, without waiting on engineering.
You land code. You know enough web fundamentals (HTML, JavaScript, React, APIs) to work in our codebase, get changes through review into production, and own them after launch. You don't need to be a senior software engineer.
Strong with data. SQL, Search Console, log files, event tracking, and tests that tell you something real.
Good content and product judgment. You know what makes a page worth citing and cut what isn't working.
Motivated by the scoreboard: traffic, citations, subscribers, revenue.
What you’ll do
In one sentence: you'll own how Lovable gets found across search engines and AI assistants, and build the site, systems and tools that turn that into growth.
Set the organic roadmap. Decide where Lovable needs to show up across Google, AI Overviews and AI assistants, which topics and queries matter most, and what we leave alone.
Own the technical health of lovable.dev. Rendering, crawling, indexing, site structure, internal links, structured data and speed are yours. Keep search traffic safe through relaunches and redesigns.
Ship pages that win high-intent search. Use search demand, prompt data and competitor gaps to pick what to build and refresh, then ship hub pages, templates, comparisons and other page systems. Work with content and product marketing on what goes on them.
Get Lovable cited beyond our own site. Find the forums, communities, publications and docs that AI answers lean on for our category, and work with community, PR and partnerships to earn a place there.
Make experimentation cheap and fast. Build the setup that lets the team test page formats, technical changes and distribution ideas in days, keep a record of each test, and double down on what works.
Build the tools search runs on. Replace manual audits, monitoring and reporting with automations and agents, ideally built on Lovable, with a person checking the work where accuracy matters.
Own how we measure organic. Tie rankings, AI citations and organic traffic to subscribers and revenue in the warehouse, so we can invest in organic with the same confidence as paid. Say plainly where the data has gaps.
Help Lovable apps get found. Work with product engineering on SEO and AEO defaults (metadata, social previews, sitemaps, rendering) for the apps our users publish, and share what works as guides.
Share what you learn. Bring findings back to product, and share our results with users and the wider community.
Keep it Lovable. Search should make the site better for people, never worse.
Our tech stack
We're building with tools that both humans and AI love:
Frontend: React
Backend: Golang and Rust
Cloud: Cloudflare, GCP, AWS, Many LLM providers
DevOps & Tooling: Github Actions, Grafana, OTEL, infra-as-code (Terraform)
About your application
Please submit your application in English. It’s our company language, so you’ll be speaking lots of it if you join.
We treat all candidates equally - if you’re interested, please apply through our careers portal.
.png?1742563293){kind=logo}