I ran a check on my own site today and found markup for a feature that stopped existing in May.

Google added a deprecation notice to the FAQ rich result on 8 May 2026, saying it would no longer appear in Search from 7 May. On 15 June they deleted the documentation page entirely. The reason they gave was that the feature is no longer shown in Search results.

My site never noticed. My own /faq route returns 200 today and still serves an FAQPage block with 18 acceptedAnswer entries in it. Twenty route files emit the same schema, plus a helper that builds it for every blog post.

Nothing failed, and that is the part worth sitting with. The FAQPage type is still defined in the vocabulary, so every validator passes it. The build compiles. No test covers whether Google still renders the thing. The only change happened on Google's side, and there is no channel that carries it back to you.

It's so easy to mistake a launch spike for long-term product market fit.

We tend to pour all our energy into the flashy project because it validates our effort immediately with likes and visits. But the quiet products that solve a real, recurring pain point are the ones that actually survive.

I lost months pushing a hyped tool that churned everyone, while a boring utility tool was slowly building a loyal user base in the background.

Are you planning to shift your focus back to the second project full-time?

This isn t a typical post for me, or what you may usually see here, but I heard something today that feels worth sharing.

You are more than what you do.

I hated meetings. Still do. But I noticed the problem was not the meeting itself. It was the scheduling, the setup, the thirty minutes of context before anything useful happened.

So I tried something. Instead of booking time, I sent a voice note. Just me, talking through the thing I needed to say, for two minutes.

I spent two years trying to explain what my product does. Different copy, different angles, different frameworks. Nothing landed the way I wanted.

Then a user described it to me in passing. One sentence, in their own words, using language I would never have chosen.

Before I launch anything, I open it as a stranger.

New browser, no history, no account, no context. I pretend I found this thing in a feed and I have about four seconds of patience. I type the URL cold and see what happens.

AI has the potential to boost your productivity 10x, even 100x. But only if you know how to actually use it.

That s why learning how to integrate it into your daily workflow isn t just useful. It s essential. It s quickly becoming one of the most valuable meta-skills in any role. No matter if you're a copywriter, a dev or a marketer.

Our meter used to treat every change the same. Ask for a new image, one credit. Change the text on an image you already made, one credit. It reads as fair on a pricing page and it quietly taught people to accept whatever came out first, because a fix cost the same as another roll of the dice.

We split the meter earlier this year. Generation costs credits, editing something you already paid for is free. Edits per user went up about 3x in the first week and generations barely moved, so the revenue hit was much smaller than the spreadsheet predicted. What we actually bought was people finishing work instead of abandoning it at 80 percent.

Last month was slow. Nothing was working the way I wanted and every day felt like pushing something uphill.

Then someone sent a one line email saying the tool had saved them an afternoon. Nothing dramatic. No details.

I had a bug that reproduced about once a week and never when I was looking for it. My tests passed. My logs were clean. Then I would get an email from a user describing something that should have been impossible.

I could not see it for a month. And then I caught it because I happened to leave a terminal open overnight and came back to a strange line of output.