Common Page Title mistakes that still ship

Launch week has a special talent for exposing title mistakes. The site is "up." The client opens pricing, docs, and blog in one window. Three tabs say the same brand name. Nobody needs a 40-page SEO PDF to feel embarrassed. Process that survives launch week catches this earlier.

SlaySlop's Page titles check "Checks for descriptive title metadata on crawled pages." The mistakes below are the ones I still see after code review thought titles were "someone else's job."

Outcome if you catch these early

You hand over URL-specific titles on the pages that matter, with an owner for the template. Uptime stays a separate conversation. Quality of metadata is not the same as whether the host answers ping.

Boundaries

Read-only public scan. Permission required. Not a content rewrite engagement by itself. Page titles sits with SEO metadata. Closing a title finding does not fix Meta descriptions or a broken sitemap.

Mistake: scaffolding titles in production

Create Next App, Vite App, WordPress site, Home. They survive because nobody opened a fresh browser profile against production. Staging looked fine with a hard-coded preview title. Production still pulled the framework default from an env the deploy forgot.

# Permissioned check: fail the build if scaffolding strings appear
URL="https://www.example.com/"
title=$(curl -sL "$URL" | tr '\n' ' ' | sed -n 's/.*<title[^>]*>\([^<]*\)<\/title>.*/\1/ip' | head -1)
echo "title=$title"
echo "$title" | grep -Ei 'create next app|vite app|wordpress site|^home$' \
  && echo "FAIL: scaffolding or useless title" || echo "ok enough to keep reviewing"

Automate the boring rejection. Do not rely on the launch call as your linter.

Mistake: one title to rule every money page

Homepage title reused on pricing, customers, and docs. Convenient for the CMS default. Terrible for recognition in search results and in the client's own bookmarks. Descriptive means the page can be told apart. Brand can stay; page purpose should still appear.

Mistake: locale and alternate routes left behind

/fr/pricing still emits the English title. Printable PDF routes inherit Untitled. Campaign landers inherit the blog layout title. Crawlers hit those URLs. So do clients with translated bookmarks.

Mistake: checking the H1 or og:title instead

Visible H1 can be perfect while <title> is empty. og:title can be set for social cards while document title lags. Document semantics and social tags matter. They are not this check. Page titles asks about title metadata on crawled pages. Read that node.

Mistake: treating a quiet homepage as site-wide proof

Apex looks great. App marketing pages under /product/* still ship defaults. Agencies often demo / only. Ask for the SOW URL list and sample those. Uptime green on / does not invent titles elsewhere.

What good ops looks like

Owners on templates. A short QA script in the release checklist. A SlaySlop rescan after deploy with Page titles opened beside Meta descriptions. Soft product fit: one report keeps both metadata rows next to the routes that failed, which beats two spreadsheets and a guess.