1
0 Comments

I Retitled 29 Blog Posts This Week and It Felt Like Cheating

I Retitled 29 Blog Posts This Week and It Felt Like Cheating

I retitled 29 blog posts this week and it felt like cheating. We did publish two new pieces, including a step-by-step guide on receiving purchase orders in VNDLY. But the real energy went into sharper headlines, tighter meta descriptions, and a lot of time staring at Google Search Console. If the click-through rate moves even half a point, this will be the highest-ROI work we have done all quarter.

## What shipped this week

The CTR sprint. Our SEO audit flagged a sobering pattern: the blog was earning close to thirty thousand impressions a month, but the click-through rate was sitting around two-tenths of a percent. A big chunk of those impressions came from posts ranking on page one, sometimes position five to ten, with titles so bland they might as well have been labeled Do Not Click. We pulled the real ranking queries for each URL, rewrote the titles to front-load the actual keyword phrase, kept every URL slug untouched so we did not reset rankings, and resubmitted everything to Google. Twenty-nine posts across two batches. We also caught three titles where we had invented numbers that the body did not support. "7 Best" when there were five companies. "6 Tools" when we had no verifiable count. "5 Causes" when the post listed none. Fixing those before they went live was embarrassing and necessary.

Title lint as a weekly habit. We built a script that audits every blog title against a simple ruleset. Does it have a power word or a leading number? Is it under fifty-five characters? Does the meta description land in the right range? It sorts by impressions so we fix the high-traffic weak titles first. Hard issues dropped from thirty-two to ten, and the remaining ten are deliberate keeps. Founder stories and clean how-to posts where forcing a gimmick would read spammy.

Content decay tracking. We started taking weekly snapshots of every post's impressions, clicks, and average position. Right now it just says need more history because we only have one baseline. In about four weeks it should flag posts that are quietly sliding backward so we can refresh them before they fall off a cliff.

Landing page polish and a real conversion fix. We shipped a design pass on the marketing site. Glass header, card hover glow, reduced-motion guards, and a small detail I am almost ashamed to admit. The homepage hero had no call-to-action buttons. None. Just a headline and a video. We added default CTAs in both English and Swedish. It is wild what you stop noticing when you stare at your own site every day. We also fixed a cannibalization pair where two pages were fighting over the same b2b wholesale inventory management query.

Trustpilot welcome emails. New VNDLY tenants now get a welcome email that BCCs our Trustpilot address, which triggers an automatic review invite about a week later. Small, but reviews are the unlock for directory listings and we have been collecting them manually until now.

## SEO and growth notes

The big shift this week was from make more to make existing stuff earn more. We have over a hundred blog posts indexed and a growing stack of landing pages. The content machine works. The constraint moved to click-through rate, cannibalization, and decay. We submitted the reworked pages to Google's indexing API and IndexNow. Now we wait for recrawl, which usually takes days to a couple of weeks.

## What's next

We are in a waiting period now. The twenty-nine retitled posts need two to three weeks to show whether the new titles actually moved the needle. Our content decay tracker will start speaking up in about a month. And we still have two landing pages that Googlebot visits but refuses to index. We do not know why yet. I will report back on all three.

Question for the community: For anyone running a content-heavy site, how do you balance the publish new stuff pressure against the fix what you already have work? Do you schedule optimization sprints, or does maintenance only happen when something breaks?

posted toAvatar for product VNDLY
VNDLY