Half the meta descriptions were blank. It depended on how fast the API answered.

Half the meta descriptions were blank. It depended on how fast the API answered.

A marketplace's category pages had meta descriptions pulled from an API and set via vue-meta during SSR. Sometimes they rendered. Sometimes the tag came out empty. CTR varied wildly page to page for no visible reason.

The symptom: roughly 40% of category pages showed Google-generated snippets instead of the intended ones, and those pages had CTR around 1.8% versus 4.1% on pages with proper descriptions.

Turns out a race condition in the SSR data flow. The meta description depended on an async API call, but the server's render sometimes completed and flushed the HTML before that promise resolved. When the API was slow, the meta tag rendered empty; when fast, it filled. Non-deterministic SEO, gated by API latency.

We made the meta-setting data a hard dependency of the server render — the framework now awaits it before responding, with a sensible templated fallback if the API truly fails.

Blank meta descriptions dropped from 40% to under 2% in three weeks. Across the recovered pages, average CTR rose from 1.8% to 3.9%. Organic clicks +71% with no ranking movement — same positions, descriptions that actually showed.

If your meta tag depends on a promise the render doesn't await, you're shipping a coin flip.