I have a rule in my blog that noindexes a category page while it has zero posts in it, and drops it from the sitemap at the same time. I wrote it on 18 July. It is one line: robots index false when the post count is zero.

On 13 August Google crawled one of those category pages while it was still empty. It picked up the noindex, and Search Console filed it as Excluded by noindex tag.

A post landed in that category some time after that. I checked the page today. It returns 200, it serves no robots meta at all, it lists its post, and it is back in the sitemap alongside the other 270 URLs.

Search Console still says Excluded by noindex tag. Last crawl 13 August. Fifteen days of a verdict about a version of the page that no longer exists, and nothing in the report tells you the reason is a snapshot from the last crawl rather than a current read.

I often get asked why someone's forum was rejected.

First of all, I need to clarify that I m not an internal member of the Product Hunt team, so I do not influence these decisions.

When we launched Flexprice, I thought Product Hunt success was about chasing upvotes.

I was wrong.

It s really about momentum, community, and showing up prepared.

Here are a few lessons we learned the hard way but I hope they save someone a few gray hairs before their launch day:

A note before we start: What follows is fiction. A thought experiment set in an alternate world that only looks like ours by accident. Any resemblance to real labs, real bosses, or real workplace policies is the reader s imagination doing the heavy lifting. With that out of the way.

We ve seen this movie before

We've been building our product for more than two years, and one thing I've realized is that a product can be functional long before it feels finished.

The major features may already work, but small inconsistencies, unclear onboarding, unfinished empty states, minor bugs, or confusing copy can still make the whole experience feel early.

A couple of years ago, a designer would hand off a Figma file and that was pretty much the end of their involvement. Everything after that belonged to developers, and a lot of nuance got lost in between: wrong spacing, animations that didn't quite work, "that's not how it looked in the mockup."

That line is blurring now. AI tools like Cursor, Lovable, or Claude Code let designers go beyond drawing an interface and actually build a working prototype with real code. Not production-ready, but enough to:

• Test a hypothesis in hours instead of sprints

• Show the team a clickable, living interface instead of a static image

• Shorten the distance between an idea and real user feedback

I've been working this way myself for the past year: designing and, in parallel, taking things far enough that a developer isn't left interpreting a mockup, they're refining something that's already close to functional. It changes the role itself, from "the person who draws things" to "the person who brings the product closer to reality."

Drop a link to your dev-first product launch in the comments.
Let's support developer tools
Upcoming dev-first product launches:

• @Producta launched on March 4

• @Pieces for Developers launched on March 5

• @MotherDuck launched on March 13

• @Portkey launched on March 17

• @Bucket launched on March 18

• @Novu launched on March 18

• @Tinybird launched on March 18

• @Lamatic.ai launched on March 24

• @Inferless launched on March 25

• @Meilisearch launched on March 25

• @Pulse launched on March 26

• @Atono launched on March 27

Had to download an invoice from a SaaS tool I use.

Simple enough right? Except the billing section was hidden inside a profile settings dropdown buried under an "Account Health" tab.

The interface looks incredibly polished. Modern fonts, pristine layout, clean icons. But finding a single PDF took way longer than it should have.