When I started developing my esoteric portal, there was never a question of "what framework to use." As a developer, I knew that if a project aimed for organic traffic and complex server-side logic, standard client-side React setups (like Vite) were out of the question immediately.
Here is my honest breakdown of why Next.js was the only logical choice from day one.
1. The Blog as a "Necessary Evil" for SEO
The main irony of my project is that I didn't initially need a blog in the traditional sense. I was building an interactive esoteric tool, not a magazine. But Google has its own rules: without fresh, text-based content and proper article structure, your site is just a set of scripts in a vacuum to their algorithms.
Creating the blog became a separate "pain" dictated solely by search engine requirements. And this is exactly where Next.js shined. Thanks to Dynamic Routing, I was able to quickly deploy a post system that is indexed perfectly, without distracting me from the main functionality of the site. Google is happy, and I got a steady influx of traffic to my core interactive tools.
2. SEO as a Foundation, Not an Afterthought
Using pure client-side React (SPA) for a content-driven site is a self-inflicted wound. I chose Next.js because of Server-Side Rendering (SSR). It was crucial for me that search engine bots receive a fully rendered HTML document with my texts and meta-tags immediately. As a result, I got perfect indexing without having to configure complex third-party pre-rendering services.
3. The Magic of API Routes: Backend Without the Backend Hassle
This is, perhaps, the killer feature for a solopreneur. When I needed to implement AI-driven interpretations (using the ChatGPT API), security became a major concern. Exposing API keys on the frontend is a terrible idea.
Thanks to API Routes in Next.js, I didn't have to deploy a separate server on Express or Nest.js. I just created serverless endpoints right inside the same project.
Security: All heavy requests and keys are hidden safely on the server.
Simplicity: One repository, one Vercel deployment, zero extra infrastructure to maintain.
4. Performance on Steroids: Tailwind CSS + Framer Motion
I wanted the site to look premium and feel incredibly fast.
Tailwind CSS allowed me to keep styles under control right within the components. No more messy CSS files and endless class name conflicts slowing down page loads.
Framer Motion added that "magic" touch of smoothness. Interactive elements and page transitions look expensive, yet everything works stably within the Next.js ecosystem.
5. Data Flexibility (JSON Over Heavy Databases)
At this stage, I decided not to overburden the project with a heavy database. Using local JSON files in conjunction with the Next.js Static Site Generation (SSG) architecture allowed me to quickly populate the site with content while maintaining blazing-fast performance and simplicity in backups.
Conclusion
Choosing Next.js on day one saved me months of refactoring in the future. I got powerful SEO, a built-in backend, and the ability to focus on the product, not on configuring bundlers and servers.
I’m currently applying these principles to my own project, Witch's House, to ensure maximum search visibility. You can check out the live result here:
Top comments (0)