The Striking-Distance Audit: Fixing Titles Before Writing Anything New
Objective: Given a real 40-row rank export and a manual crawl of the pages currently sitting on page 2 of Google, audit title tags, URL slugs, and meta descriptions against the lesson's rules, then use the lesson's own CTR-by-position numbers to estimate what fixing them is actually worth.
Zillow's organic growth engine runs on pages precisely matched to what searchers type, from the Zestimate tool down to individual page templates. You've inherited a 40-row rank export for a Zillow-style content team, and your manager wants to know: which pages are close enough to page 1 that a title-tag rewrite alone could push them there, without touching a single backlink?
Four checks against the same export: title length and keyword position, URL cleanliness, meta description quality, and a final honest estimate of what a fix is worth in clicks, sourced numbers only, no invented precision.
Which page-2 pages can be pushed to page 1 with a title, URL, or meta fix alone, and what is that fix honestly worth in clicks?
Before you start
What you'll need
- —Basic HTML/page-source familiarity, viewing a <title> tag
- —Access to a crawler tool or the ability to view page source manually
- Title Rewrite
- when Google ignores a page's authored <title> tag and generates its own version in search results, common with titles over roughly 60 characters.
- CTR (Click-Through Rate)
- the percentage of people who see a result in search and click it, driven heavily by title and meta description, not by ranking position alone.
Free path (everything below is enough to finish)
Free, and the only source of your site's actual click-through rate per query, which no third-party estimate can replace.
The free tier's 500-URL cap is enough for a full audit of most page-2 candidate lists in one pass.
Paid upgrades (optional, faster/deeper)
Every step above is completable with Search Console and a manual page crawl at zero cost. Screaming Frog's free 500-URL crawl covers most real sites; paid tools only save time at larger scale.
The free path (manual crawl + Search Console) is complete for auditing a handful of pages; Surfer earns its cost once you're running this audit across dozens of pages every month.
The process
4 steps
Step 01 of 04
The lesson's Title Tag rules: include the primary keyword in the first 3-4 words, keep it under 60 characters, and give a reason to click. Titles over 60 characters are 57% more likely to be rewritten by Google (Ahrefs, 2021).
Pulled from a manual crawl of three pages in this export, which titles are Google-rewrite risks, and does that correlate with their current rank?
Procedure
- Pull the live <title> tag text for each URL in the rank-11-to-20 band
- Count characters for each one
- Check whether the target keyword appears in the first 3-4 words
- Flag anything over 60 characters as a rewrite risk
rank 11 project management software comparison
title: "Complete Guide to Choosing the Best Project Management Software
Comparison Tool for Your Team in 2026" (103 chars, high rewrite risk)
rank 12 best project management software 2026
title: "Best Project Management Software 2026 | Top Picks Reviewed" (61 chars, borderline)
rank 13 project management software demo
title: "Request a Free Project Management Software Demo Today" (55 chars, keyword not in first 3-4 words)
rank 3 project management software login (for contrast, already page 1)
title: "Sign In | Project Management Software Login" (45 chars, short, ranks fine as a navigational query)Healthy
Titles under 60 characters with the target keyword in the first 3-4 words, like the rank-3 example.
Unhealthy
A 103-character title that reads like a run-on sentence, Google is very likely already silently rewriting it to something the team never approved.
What this means
The rank-11 page's oversized title is a plausible reason it hasn't broken into page 1: Google may be showing a rewritten version the team has no control over. The rank-12 page's 61-character title is one small edit away from being safe.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| A title is 100+ characters | Cut it to under 60 characters with the keyword in the first 3-4 words, don't just trim the end, rewrite it | 30 min |
| A title is 60-70 characters, borderline | Trim filler words first ("Complete Guide to", "Everything About") before rewriting from scratch | 5 min |
Step 02 of 04
The lesson's URL Slug rule: keep it short, readable, and keyword-included, e.g. /blog/on-page-seo, not a query-string or version-suffixed path. Clean URLs earn 45% higher CTR than ones that aren't.
Pulled alongside the same crawl, which URLs already follow the clean-slug pattern the lesson recommends, and which look like the query-string trap?
Procedure
- Record the full URL for each of the three pages audited in Step 1
- Flag any query strings, version suffixes, or ID-based paths
- Check whether the target keyword actually appears in the path itself
rank 11 /resources/project-management-software-comparison-guide-updated-2026/
(79 chars, keyword present but buried under trailing filler)
rank 12 /blog/best-project-management-software-2026/
(51 chars, clean, keyword-led, matches the lesson's example pattern exactly)
rank 13 /pmsoftware/demo?ref=nav&utm_source=internal
(query-string URL, keyword not readably present in the path at all)Healthy
A short, keyword-led path with no query string, matching the rank-12 example.
Unhealthy
A URL carrying tracking parameters or a version suffix ("-updated-2026", "?ref=nav") that tells a searcher nothing about the page's topic before they click.
What this means
The rank-13 page's URL not only fails the clean-slug rule, it actively looks like an internal navigation link rather than a page worth clicking from search results, on top of the title problem flagged in Step 1.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| A ranking page's URL has a query string or tracking parameter | 301-redirect to a clean, keyword-led slug and update internal links to point at the new URL directly | dev ticket |
| A URL has the keyword but buried under extra filler words | Shorten to the keyword phrase alone where a redirect is low-risk (few backlinks pointing at the old URL) | half day |
Step 03 of 04
The lesson is explicit that the meta description is not a direct ranking factor, but it drives click-through rate. Google rewrites it 63% of the time (Ahrefs, 2020), but the original still influences what gets shown, so it's still worth writing well.
Two meta descriptions from the crawl, one 19 characters, one 240. Which is more likely to survive as-written, and which is doing nothing for CTR either way?
Procedure
- Pull the meta description for the rank-11 and rank-13 pages from Step 1
- Count characters against the ~155-character guideline
- Check whether either includes the target keyword and a concrete reason to click
rank 11 "Compare project management tools." (35 chars, too short, no benefit stated)
rank 13 "Book a live walkthrough of our project management platform, see how
teams use boards, timelines, automations, integrations, reporting,
and more, all in a single guided 20-minute session with our team." (240 chars, will be truncated/rewritten)Healthy
A meta description in the 120-155 character range that states the keyword and a concrete reason to click, e.g. what the visitor gets in the next 30 seconds.
Unhealthy
Either extreme: a 35-character description that wastes the space, or a 240-character one Google will cut off mid-sentence, losing the actual call to action.
What this means
Neither example is doing its job. The 35-character one isn't a ranking penalty, but it's a wasted CTR opportunity. The 240-character one is actively likely to be truncated or rewritten, per the lesson's cited 63% rewrite rate, meaning the team's actual chosen call-to-action may never reach the searcher.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| A meta description is under 60 characters | Expand it to 120-155 characters: state the keyword plus a concrete benefit of clicking | 5 min |
| A meta description runs past 155 characters | Cut to the single strongest sentence, put the call-to-action first, not last, since that's what gets truncated | 5 min |
Step 04 of 04
The lesson cites Backlinko 2022 data: position 1 gets a 27.6% average CTR, position 2 gets about 15%, and the top 3 results combined capture 54.4% of all organic clicks on a page.
Using only the lesson's cited numbers, what's the honest click estimate if 'project management software comparison' (1,900 vol, rank 11) moves onto page 1 versus moves all the way to #1?
Procedure
- Take the keyword's monthly volume from the export (1,900)
- Apply the lesson's #1 CTR figure (27.6%) as the only precisely-sourced scenario
- For the rank-11 (page 2) scenario, note that it falls outside the 54.4% the top 3 capture combined, and state that as a range, not a fabricated precise percentage
1,900 monthly searches for 'project management software comparison'
At rank 11 (page 2): outside the top 3 that capture 54.4% of clicks combined —
realistically a low-single-digit share of the 1,900 searches; the lesson does
not cite a precise page-2 CTR, so this stays a range, not a fake-precise number
At position 1 (27.6% CTR, directly sourced): ~524 clicks/mo, a real estimate the
lesson's own cited number supports directlyHealthy
Presenting ~524 clicks/mo as a sourced estimate (grounded in the lesson's cited 27.6% figure) while explicitly flagging the page-2 estimate as a range, not a citation.
Unhealthy
Inventing a precise page-2 CTR percentage (e.g. "rank 11 gets 2.3% CTR") and presenting it to leadership as if it came from the same source as the position-1 number.
What this means
The lesson only gives hard numbers for positions 1, 2, and the top-3-combined. Anything about position 11 specifically is a reasonable estimate, not a citation, and the difference matters when you're asking someone to approve engineering time.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| The team wants an exact clicks-gained promise before approving the title rewrite | Give the range for the current position and the sourced ~524/mo figure for position 1, don't manufacture false precision to make the pitch sound stronger | 5 min |
| Leadership is skeptical a title rewrite alone can move rank 11 to rank 1 | Reset expectations explicitly: fixing the title fixes CTR at whatever position the page holds, ranking movement itself needs the on-page fix plus time for Google to re-crawl and re-evaluate | 5 min |
Analyze your findings
What to look for
- Length risk
- Is the title or meta description long enough to be truncated or entirely rewritten by Google?
- Keyword placement
- Does the target keyword appear early, in the title and the URL path, rather than buried at the end?
- URL cleanliness
- Is the path readable and keyword-led, or does it carry query strings, tracking parameters, or version suffixes?
- Sourced vs estimated
- Is a click estimate backed by a cited CTR figure, or is it an honest range where no precise number exists?
Make the call
The rank-11 page has a 103-character title with the keyword buried mid-sentence. The rank-13 page has a clean 55-character title but the keyword isn't in the first 3-4 words. Which fix should be prioritized first?
Recommendation · Priority: High
“Prioritize the rank-11 'project management software comparison' page first: a 103-character title puts it at high risk of a Google-generated rewrite, and at 1,900 monthly searches, moving into position 1 would yield an estimated 524 clicks per month based on the lesson's cited 27.6% CTR figure. Trim the title to under 60 characters with the keyword in the first 3-4 words, then correct the URL and meta description issues on the rank-13 page in the same sprint, since none of these fixes require a backlink or new content, only a rewrite and a redirect.”
Common mistakes
What trips people up
Trimming an oversized title from the end instead of rewriting it — a mechanical trim leaves filler words in place and often still buries the keyword; the rule requires the keyword in the first 3-4 words, not just under 60 characters.
Redirecting a query-string URL without updating internal links — the crawl alone doesn't fix ranking if internal navigation still points at the old, unclean URL.
Presenting a page-2 CTR estimate with false precision — the lesson only cites hard numbers for positions 1, 2, and the top-3-combined; inventing a specific percentage for rank 11 misrepresents how confident the estimate really is.
Assuming a title or meta fix alone will move ranking position — these changes improve CTR at whatever position a page holds; actual rank movement still needs Google to re-crawl and re-evaluate the fixed page.
Final deliverable
An audit sheet ranking every page-2/3 row by (proximity to page 1) x (title/URL/meta defect severity), with the top 3 fix candidates called out and a sourced-vs-estimated click projection for each.
See a reference example
Care.com's own inherited audit surfaced a similar pattern: 'daycare cost calculator' sat at rank 9 behind a 94-character title with the keyword buried at the end. Trimming it to 52 characters with the keyword in the first four words was the single highest-leverage 30 minutes spent that sprint, done before any new content got written.
Success criteria
You're done when you can:
- Correctly flagged the 103-character title as a high rewrite-risk before flagging the 61-character borderline one
- Identified the query-string URL as the clean-slug violation, not the buried-keyword one
- Distinguished the 35-character meta description problem (wasted space) from the 240-character one (truncation risk)
- Presented the rank-11 click estimate as a range and the rank-1 estimate as a sourced ~524/mo figure, without inventing false precision for the in-between positions
Key takeaway
A page sitting on page 2 or 3 often needs cleanup, not new content: a shorter title with the keyword up front, a clean URL, and a meta description written for a click can be the fastest available SEO win. The real skill is honest measurement, cite the CTR numbers you actually have and flag the rest as a range, not a guess dressed up as data.