Stale meta description kills 56 impressions at position 2

On valuefy.app, a blog post about SaaS valuation multiples ranked at positions 1–5 for 22 distinct queries — including "saas company valuation multiples 2026" at position 2.5 with 8 impressions — yet generated zero clicks over a 28-day period. Aimiten traced the failure to a single metadata mismatch: the post's title tag and H1 correctly targeted 2026, but the meta description snippet visible in Google's search results referenced "reshaping SaaS valuation multiples in 2024." The description was also truncated mid-word, ending in "e...", compounding the credibility problem. A searcher querying a 2026 topic, seeing a 2024 snippet, simply clicked a competing result instead.\n\nThe audit also surfaced two additional pre-existing bugs. First, curling the SaaS blog post revealed two `H1` tags — a template-level error present in all blog posts but absent from tool pages — which sends mixed topical signals to Google alongside the already-broken meta description. Second, a duplicate `og:title` bug — a static `index.html` baking in a generic site-wide tag that conflicts with the React Helmet page-specific tag — remained unfixed six weeks after being first reported, present on both the homepage and the IRR calculator page (`2` matches each on `curl`).\n\nAimiten frames the root cause as a process problem rather than a one-off mistake: the daily Claude Code automation ran on a fixed schedule, touching six calculator pages (IRR, Cap Table, Dilution, Vesting, Funding, and Churn Rate) with verified benchmarks and worked examples, none of which showed meaningful GSC traction. The automation optimized by routine rather than by signal, missing the highest-leverage opportunity — a top-ranking page losing all its clicks to a trivially correctable metadata error.

Topics