Google indexed 30 of my 547 pages. Here's what was wrong with my React SPA.
I run GAGPedia , a free fan-made calculator and guide site for the Roblox game Grow a Garden: trade (Win/Fair/Loss) checks, plant values with mutation multipliers, pet XP tools, a codes page and some strategy guides. It's a Vite + React + TypeScript single-page app on Vercel, with game data in Supabase. After eight months live, Search Console looked like this: 547 URLs in the sitemap, 30 indexed…
Google indexed only 30 of 547 pages for GAGPedia, a fan-made calculator and guide site for the Roblox game Grow a Garden. The issue stemmed from thin programmatic content, outdated React components, and unoptimized SEO practices. The site's eight-month-old presence showed 30 indexed pages out of 547 URLs in the sitemap, with 39 clicks from Google and roughly ten times more from Bing.
The first fix involved indexing non-unique pages by adding a Googlebot-only noindex meta tag. This improved rankings for the site's calculators and hub pages. The second fix addressed long, summary-only articles, which crawled but didn't index. By server-rendering the React components at build time, the site's actual content was indexed and improved to 800-2,400 words.
The third issue was a flash of unstyled content during page loads, which was fixed by hiding static HTML for JavaScript-capable browsers. The fourth problem was an unnecessarily large bundle, consisting of massive Supabase client code. The solution imported the client on demand, reducing the bundle size from 210 KB to 152 KB. The fifth issue involved informing Bing of new content deployment, which was solved by adding IndexNow support.
Finally, an audit script was updated to handle Windows file path issues, ensuring zero errors across the 549 pages.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.