Menu

6 Sneaky Bugs That Were Hurting My Next.js Site's SEO
📰

6 Sneaky Bugs That Were Hurting My Next.js Site's SEO

HackerNoon·Mr Sanzid·about 1 hour ago
#7FxPRhfz
#hackernoon#technology#phones#phone#google
Reading 0:00
15s threshold

I run TechTweak , a site with specs, prices and side-by-side comparisons for around 600 smartphones. It is a fairly ordinary stack: Next.js (App Router) on Vercel, MongoDB through Mongoose, images on Cloudinary, and articles written in Markdown.

For months it looked healthy. Builds passed, pages loaded, there were no errors in the logs. Then I spent a few weeks going through Google Search Console reports and checking pages one by one, and I found a set of bugs that had one thing in common: none of them ever threw an error. They just produced slightly wrong output, quietly, at scale.

If you run a content-heavy site, there is a good chance you have at least one of these.

1. A comma inside a URL broke every single image save

Symptom: I added photos to a phone in the admin panel, and the page still showed no image. Adding more photos did not help.

Cause: The admin form sends image URLs as one string.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.