Urgent.News

What's breaking now, across thousands of outlets.

Tech

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.

Read the original at dev.to →

More in Tech

regex-engine: Building a regex engine from scratch in Rust, without backtracking

Regular expressions are tools we use without questioning how they work. Then comes a day when a pattern like (a+)+$ meets a long input, and an entire service freezes.

  • regex-engine is a ground-up Rust implementation of regex engine without catastrophic backtracking
  • Developed to handle complex patterns like (a+)+$ efficiently in long inputs
  • Uses automata mechanisms and linear methodology for inputs regardless of pattern complexity

A Wallet Is Not a Risk Score: Why Blockchain AML Needs Context, Not Just Labels

AMLdark · Screen TRC20 USDT addresses for free Live AML screening for Tron-based USDT addresses against OFAC designations, Tether's freeze list and darknet datasets. Free tier included. amldark.com One is an exchange processing a withdrawal. The other is a freelancer receiving payment for completed work.

  • Blockchain addresses are evidence, not complete risk assessments
  • Risk labels hide specific reasons for transaction risk
  • Contextual analysis is crucial for informed AML decision-making

How to Convert MOV to MP4 With FFmpeg: Stream-Copy When the Codec Already Matches, and Re-Encode Only When It Doesn't

Short answer: to turn a QuickTime .mov into an .mp4 , start with -c copy . If the file is already H.264 video plus AAC audio, stream copy remuxes the packets, the first-frame RGB24 md5 stays the same, and the duration does not change. If the video is ProRes, DNxHR, or another codec that MP4 players will not handle, you have to re-encode.

  • Use -c copy to remux MOV to MP4 when codec matches H.264 and AAC.
  • Re-encode needed for ProRes or unsupported codecs in MP4 container.
  • pytest confirms reproducibility of conversion process.

More from Thursday 19 November →