Skip to content

SEO

Fixing Page Title without guessing

Stop rewriting every title from a brand brainstorm. Confirm the live title metadata on each affected URL, fix the owning template, and verify crawlers get the new string.

· by Maya Okonkwo

Fixing Page Title without guessing

What a crawler sees on the public surface includes the title string in the HTML it gets. Guessing new title copy for the entire site because one finding fired is how you ship poetic strings that still never make it into the production template. Confirm the live node first.

SlaySlop's Page titles check "Checks for descriptive title metadata on crawled pages." Fixing without guessing means opening the evidence URL, reading the live title metadata, changing the layer that emits it, and confirming the same URL shows the new string.

Outcome you want

Affected URLs expose descriptive titles after deploy. Defaults and empty nodes are gone on the SOW set. A follow-up scan no longer flags the same Page titles evidence on those pages. Meta descriptions still get their own pass if they were weak too.

Boundaries before you edit

Read-only scanner. You edit CMS fields, app head components, or edge HTML rewriters you own. Permission required. Not a ranking promise. Not a license to scrape competitors for title ideas at scale as if that were the fix.

Loading diagram.

Happy path

  1. Copy URLs from the finding list.
  2. Fetch each title from production (or the exact host the scan used).
  3. Identify the emitter: CMS SEO fields, framework head manager, static HTML, edge worker.
  4. Change that emitter once. Avoid parallel temporary hardcodes in three places.
  5. Purge caches that serve HTML.
  6. Re-fetch the same URLs.
  7. Rescan in SlaySlop and confirm the row moved.
bash
# Permissioned before/after
URL="https://www.example.com/pricing"
fetch_title() {
  curl -sL "$1" | tr '\n' ' ' \
    | sed -n 's/.*<title[^>]*>\([^<]*\)<\/title>.*/\1/ip' \
    | head -1
}
echo "observed: $(fetch_title "$URL")"

I want a string that describes the page, not a blank, not scaffolding, not a duplicate of the homepage with no page cue. Brand voice can come from writers. Placement has to come from the template that actually ships.

Pitfalls

Editing staging only. Editing og:title only. Editing the blog layout while the finding was on product pages. Editing titles in a tag manager that runs too late for the initial HTML some crawlers use. Editing by stuffing keywords until the tab looks like an ad.

Another trap: closing the finding mentally because "search engines rewrite titles anyway." Sometimes snippets rewrite. That is not permission to ship empty nodes. Ship descriptive metadata on the public surface. Let remotes do what they do.

Teams also "fix" by changing only the homepage after a glance. The evidence list is usually longer. Walk the list. What an outsider sees on each money URL still matters when the client opens them side by side.

Verify on the public surface

View source or a fetch, not only the component tree in DevTools after hydration. Many crawlers care about the HTML response. If your stack must set titles client-side, know that limitation and still make the initial payload as honest as you can.

When SlaySlop already watches the host, use the Page titles evidence as the acceptance list. Soft CTA: the rescan is shorter than arguing about whether someone remembers updating the CMS.