Observed Signal · May 18, 2026 · Technical Guide · Source: DEV Community · Impact: 2/5 · Sentiment: Positive
Fixing Vue.js SPA SEO: Invisible to Google
A developer recounts how a Vue.js 3 + Vite client-side SPA (CitoyenNote) initially appeared to Google as a single, non-descriptive page and none of its 80+ municipality pages were indexed. The author describes a six-step technical fix to make SPA pages indexable: improve the static index.html head, use @unhead/vue (useHead()) for dynamic meta tags, add a robots.txt, provide a dynamically generated sitemap from the Go (Echo) backend, include JSON-LD structured data (AggregateRating), and ensure server-level routing fallback/404 handling. The post explains CSR limitations versus SSR/SSG and reports the practical outcome: 80+ pages were indexed within two weeks after submitting the sitemap to Google Search Console. Published 2026-05-18.
Practical, actionable guidance to make client-side SPAs indexable by search engines. Relevant to publishers, web developers and sites relying on organic search, but it is a developer how-to rather than industry-shifting platform news.
Track Google Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Project was a Vue.js 3 + Vite client-side SPA named CitoyenNote using Pinia for state management.
- Initially Google returned only the homepage (title 'Document') and none of the 80+ municipality pages were indexed.
- Author implemented a six-step SEO fix: improved index.html head, @unhead/vue for reactive meta tags, robots.txt, dynamic sitemap endpoint, JSON-LD structured data (AggregateRating), and server fallback/404 routing.
- Backend uses a Go API (Echo framework); author added a /sitemap.xml route that builds a dynamic sitemap from the database.
- After submitting the sitemap to Google Search Console, 80+ pages were indexed within two weeks.
Connected Companies & Entities
3 Entities mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Case study: Google indexes 72 pages in 2 months
Serhii Kalyna published a first-person case study (May 8, 2026) describing early SEO and indexing behavior observed for Convertify, a new site built with Rust + Next.js. At ~2 months the site had 72 indexed pages, ~90 impressions/day, an average position of 40.8 and essentially 1 click. Key interventions that produced measurable early changes were migrating from a client-side SPA to Next.js static site generation (SSG), adding dense internal linking, and applying FAQPage JSON-LD schema. The author outlines an observed timeline for new-site behavior (initial crawl, low-volume query testing, then gradual stabilization over 2–12 months) and reports that short-term backlink efforts had little effect.
SEO Mistakes Killing Developer Projects
A developer describes debugging a React app that Googlebot saw as a blank page and outlines common SEO mistakes in developer-built projects. The post highlights four frequent issues: empty or generic <head> metadata, reliance on client-side rendering (which can be invisible to crawlers), lack of structured data (JSON-LD), and missing or stale sitemap.xml files. It gives concrete fixes and code examples: add meaningful meta tags, use SSR/SSG or prerendering (Next.js examples and tools like prerender.io or vite-plugin-ssr), include JSON-LD for rich results, and generate/submit sitemaps at build time. The article mentions tools and libraries such as react-helmet-async, Next.js <Head>/metadata, prerender.io, vite-plugin-ssr and the @power-seo npm package, and recommends testing with JavaScript disabled to emulate Googlebot's view.
SEO in 2026: Half Your Traffic From ChatGPT
A technical case study describing a 2026-focused rewrite of a SaaS public surface to capture AI-driven discovery (ChatGPT and other LLM-based crawlers). The author extended an existing PageMeta component to emit JSON-LD (schema.org) and hreflang, published an llms.txt and explicit robots.txt blocks for major AI crawlers, replaced a static sitemap.xml with a sitemap index plus three dynamic sitemaps served from the backend, wired IndexNow pings on publish for non‑Google engines, added Web Vitals real-user monitoring (sampled 10%) shipping logs to CloudWatch, and generated per-route HTML snapshots (meta-only) post-build to serve route-specific meta tags without Puppeteer. The post lists tests, trade-offs, and next steps (edge SSR for dynamic pages, alerts for LCP regressions).
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.