An indie hacker built a flawless Next.js site about AI and got no search traffic

Boris, an indie hacker and Telegram bot developer, spent almost a year building Neuro.PRO, a personal site about AI and neural networks built on Next.js. He got the technical side right: a well-designed UX, original content, no templates and no rewrites. Organic search traffic: zero.

What Neuro.PRO is

Boris deliberately skipped site builders and stock templates from the 2010s. Everything was written by hand, with help from AI, and the focus was on usefulness to readers rather than volume for its own sake. He envisioned the project as a major personal resource on AI: not a news aggregator, but a practitioner's perspective.

By web development standards, the site turned out strong. Next.js delivers fast load times, the structure is clear, and the mobile version works as it should. Everything the technical SEO guides recommend was done. And yet search engines ignore the site.

Why good code doesn't equal traffic

SEO isn't just load speed and correct meta tags. Ranking at the top takes three things at once: a solid technical foundation, content with real search demand, and domain authority built through external links. If even one is missing, the site stays invisible.

Neuro.PRO has the classic set of problems that young projects face:

• No backlink profile — without backlinks, Google doesn't treat the domain as authoritative, no matter how good the content is
• A competitive niche — "AI" and "neural networks" are dominated by TechCrunch, Forbes, Habr and dozens of outlets with link profiles built over many years
• Content without search demand — a personal perspective is valuable to a loyal audience, but it doesn't always match what people search for on Google
• Time lag — Google is slow to trust new domains; six months to a year before the first rankings is the norm, not the exception
• Share of AI-generated text — algorithms have learned to detect text with heavy AI involvement, and even original pieces can get demoted

The AI niche is especially brutal here: new sites with similar content appear every month, while established players have been accumulating backlinks for years. A new domain without a distribution strategy has very little chance of breaking into organic search.

What should have been done differently

What makes Boris's anti-case valuable is that he doesn't hide the failure but breaks it down honestly, which is rare in a world where people usually write only about their successes. His experience suggests a few principles for anyone planning a content project in a competitive niche.

SEO strategy before code. Keyword research, a competitor map and choosing a sub-niche are the foundation. Doing them after launch means retroactively rebuilding the entire content architecture.

Links matter more than code. Guest posts, mentions on topical sites, collaborations: without external links, even a technically flawless site won't earn authority in Google's eyes.

Volume and consistency. One or two pieces a month aren't enough for a search engine to see the site as active. Growth requires a publishing cadence the algorithm will notice.

"I decided right away that I wouldn't use any site builders, templates from the 2010s or dull rewrites.

We write everything by hand, polish the UX and focus on being useful to people," Boris writes.

What it means

The Neuro.PRO story is typical of developers who build a product by the rules of their profession rather than the rules of search engines. A technically perfect site is only half the job. The other half is distribution, a backlink profile, and content that answers a specific search query. For indie hackers without a marketing background, that turns out to be the hardest part.