Common Meta Description mistakes that still ship

I still reach for curl first when someone says the SEO plugin is configured. Curl does not care about the plugin UI. SlaySlop's Meta descriptions check "Finds missing or weak description metadata." The mistakes below still ship because teams treat the CMS field as proof of rendered HTML.

I have shipped at least one of these myself on a Friday deploy. The pattern is usually the same: the editor tab looks busy, the live tag does not.

Outcome if you catch these early

Money pages publish unique, non-empty description metadata. Theme and CMS agree. You stop debating SERP rewrites before the tag exists. Portal notes name an owner instead of "we'll tweak copy later."

Boundaries

Read-only observation. Permissioned scans. Not a pentest. Not a promise that engines will quote you. SEO and AEO siblings stay separate: titles, canonicals, structured data, crawl rules. Meta descriptions answers the missing/weak description-metadata question on the public page set.

Mistake 1: field filled, theme silent

Editors type a summary. The theme never prints <meta name="description">. View-source tells on you. So does a scan that reads live pages. Fix the partial or the SEO plugin hook before you rewrite marketing copy for the tenth time.

# Permissioned
curl -sL "https://www.example.com/" | rg -i 'name=["'\''"]description["'\''"]' || echo missing

Mistake 2: one stub for every template

"Welcome to Acme" on fifty URLs is present and still weak. Uniqueness matters when the report lists the same sentence across routes. Replace the shared default with page-level summaries, or accept that the check will keep calling the pattern out.

Mistake 3: homepage only

Launch checklists love the root URL. Pricing and docs routes ship empty. Sample the URLs that pay the bills. Agencies get surprised on handoff calls when the portal highlights interior templates the deck never mentioned.

Mistake 4: confusing OG with description

og:description looks polished in a debugger. name="description" is absent. Fix both if your stack needs both; do not claim one covers the other without proof in the rendered HTML.

mistake: og_only
symptom: social debugger green, meta description missing
fix: emit name=description from the same source of truth

Mistake 5: keyword salad

Stuffing every product noun into the tag produces "present" metadata that still reads as weak to humans reviewing the report. Write a summary a person would recognize on a pricing page. The glossary says missing or weak; salad often lands in weak.

Mistake 6: staging truth, production blank

You verified staging. Production CDN serves an older theme. Handoff on the wrong host is not an SEO strategy. Match the scan target to the hostname the client will see Monday morning.

Mistake 7: treating SERP text as markup proof

Engines rewrite snippets. A nice SERP line does not prove your tag exists. The check observes HTML. When someone pastes a Google result as "proof we have descriptions," ask for view-source on the same URL.

How I verify without folklore

I dump the Meta descriptions findings, curl a short list of money URLs from a clean network path, and open the CMS only after HTML evidence is clear. Then I fix the rendering path or the content field, publish, and rescan the same host. Request/response thinking stays simple:

ask: rendered description metadata on money URLs
compare: CMS fields vs theme output
follow_up: rescan same host

If the scan and curl disagree, I check caching and whether I hit a different locale or trailing-slash variant. That disagreement is useful. Guessing which UI is "more true" is not.

Related next step

If Meta descriptions is noisy, fix the theme partial first when the tag never renders. Soft links: Meta descriptions and SEO and AEO. Soft close: a permissioned SlaySlop crawl beats a folder of plugin screenshots when you need missing/weak evidence on the live surface.