Back to articles
We Built 3 Websites. None of Them Ranked.

We Built 3 Websites. None of Them Ranked.

via Dev.to WebdevJoshua Gutierrez

We launched three products this year at Axion Deep Labs. Three websites. All built on Next.js, all statically exported, all "optimized for SEO." Except they weren't. Not even close. Here's every real mistake we made and how we found out the hard way. 1. Our Entire Website Was Invisible to Google This one still hurts. Next.js has a file called loading.tsx . Drop it in your app directory and it shows a loading spinner while the page hydrates. Great for UX. Terrible for SEO. That file creates a Suspense boundary around ALL page content in the static HTML export. When Google's crawler hit our site, it didn't see our homepage, our service pages, or our blog posts. It saw a loading spinner. On every single page. We spent days fixing heading hierarchy, anchor text, meta descriptions. None of it mattered. The crawler was looking at an empty page the whole time. The fix was deleting one file. Lesson: Don't trust your source code for SEO. Run the build, open the actual HTML output, and look at w

Continue reading on Dev.to Webdev

Opens in a new tab

Read Full Article
4 views

Related Articles