Service

SEO for Vue / Nuxt — so Google finally notices you

Google sees an empty shell where your SPA should be? That's fixed with SSR and proper markup — engineering, not magic. Plus copy that people actually read, not just bots.

Discuss SEO What's included

Context

Why SEO for an SPA is
an engineering problem.

A regular SEO specialist won't help here: the root of the problem is how the browser and search engine read a React/Vue app.

Problem	Cause	Engineering solution
Google sees an empty page	The SPA renders content via JS after load	SSR / SSG via Nuxt
Slow loading tanks rankings	A large JS bundle blocks First Paint	Code-splitting, lazy-loading, WebP/AVIF
Duplicates from language versions	hreflang is missing or misconfigured	Correct hreflang + canonical
No rich snippets	Schema.org markup is missing or copy-pasted boilerplate	Service, FAQPage, Breadcrumb, ItemList

01 — When it fits

No traffic — even though the product is good.

SEO for an SPA is first and foremost an engineering problem: rendering, speed, markup. Copy comes after and locks in the result.

Google sees an empty page — your content doesn't exist as far as it's concerned.

Slow loading tanks both rankings and conversion — at the same time.

No meta tags, an ugly OG preview, Schema.org not set up.

The copy was written just to check a box — useless to people and search alike.

02 — What's included

Four layers —
from rendering to copy.

First I put the technical foundation in order, then I close the content gaps with copy.

Rendering

SSR/SSG via Nuxt — the search engine gets ready-made HTML, not an empty shell.

SSRSSGNuxt

Speed

Core Web Vitals in the green zone: image optimization, code-splitting, less JS.

CWVWebP/AVIFsplit

Markup

Meta tags, Open Graph, Schema.org (Service, FAQPage, Breadcrumb), sitemap, hreflang.

SchemaOGhreflang

Content

On-topic copy targeted at search queries — clear for people and correct for search engines.

copywritingsemantics

03 — What you get

Visibility you
can measure.

A technical foundation that makes rankings possible in the first place, plus copy that locks them in.

01
Indexability
The search engine correctly sees and crawls the app's content.
02
Fast loading
CWV in the green zone — better for rankings and for users alike.
03
Correct markup
Meta tags, OG, and Schema.org — clean snippets in search results and social media.
04
On-topic copy
Content targeted at search queries that people actually read, not just bots.

04 — How the work goes

Transparent —
no promises of top rankings.

We talk

I look into the task and context for free. If it's not something I do, I'll say so honestly.

~ 1 hr

I estimate

Timeline, scope, risks, and cost — before we start.

1–2 days

I work in iterations

Regular demos and clear progress at every step.

from 2 weeks

I deliver with the code

I hand over the code and documentation. The project stays yours.

~ 1 hr

05 — Why me

Honest about
what's really
in my hands.

✓
SEO as engineering. Rendering, speed, markup — the foundation without which copy doesn't work.
✓
Bilingual by design. RU + EN with correct hreflang — no cannibalization, no duplicates.
✓
A design foundation. Copy and page structure work for the user, not just for the crawler.
✓
No promises of top rankings. I'm accountable for the technical foundation. Nobody can honestly guarantee rankings — and I say so directly.

06 — Вопросы

FAQ

No — and honestly, nobody can. Rankings depend on many factors outside our control. I'm accountable for the technical foundation: indexability, speed, correct markup, and quality copy. That's what makes a top ranking possible in the first place.

Most often the search engine gets an empty shell, and the content is drawn in afterward by JS. The fix is SSR or SSG via Nuxt: the search engine sees ready-made HTML.

Yes. I write on-topic content targeted at search queries — clear for people and correct for search engines. The technical work and the copy work together.

Yes — RU and EN with correct hreflang, so the language versions don't compete with each other or get flagged as duplicates.

A basic technical audit and fixes — from 2 weeks. Migrating from CSR to SSR/SSG depends on the project, usually from 3–5 weeks. Performance and markup — 1–2 weeks on average. I fix the exact timeline before we start.

Yes. I take on standalone tasks: content only, SSR migration only, Schema.org and meta tags only. It's worth knowing that the technical work and the copy together get results faster — but each part is useful on its own too.

Related services

/audit

Project audit

I go through the application layer by layer and hand over a report with a plan for what to fix and in what order.

/development

Development from scratch

I take a project from mockups to a launched app built on a solid architecture.

Next step

Let's check whether search engines can see your Vue project.

Show me the app — I'll assess the technical foundation and tell you what will get results first. The first review is free.

Discuss SEO See case studies