The gsc-telemetry digest on 24 June flagged the same six pages it had been flagging for weeks. Five legal surfaces (disclaimer, privacy policy, terms, cookie policy, accessibility statement), plus the stamp-duty calculator. All showing “URL is unknown to Google.”
PR #153 was the code review of those six surfaces. The audit came back clean. HTTP 200 on all six. index, follow in the robots meta. Canonical pointing at itself. Each page included in the sitemap. The prerender layer had a blocking issue that the same PR cleaned up. Worth shipping regardless, but not the reason Google hadn’t found the pages. The pages were technically correct before that fix landed.
Google still hadn’t crawled them.
What the technical audit establishes
A technical SEO audit has a defined scope: HTTP status, crawlability, indexability, canonical logic, structured data, render blocking. PR #153 covered all of it. Nothing was broken on any of the six surfaces.
What a technical audit doesn’t establish is whether Google has a reason to visit. Technical correctness is a necessary condition for indexing. It is not a sufficient one.
Google’s crawler follows links. It discovers pages by traversing a graph of hyperlinks from already-indexed content. A page with correct technical signals and no indexed inbound prose links can sit perfectly formed and permanently unknown. The crawler has to arrive first. Technical correctness doesn’t create a route.
The shared problem
All six pages had one thing in common: they existed only in the site footer.
Footer links appear on every page of the site, but they carry a different crawl weight than body-prose links. Google has indexed enough sites to know that footer links (privacy policies, disclaimers, legal boilerplate, accessibility statements) are structural navigation. They don’t signal topical relevance. An editorial link placed in the body of an article, where a writer chose deliberately to connect two pieces of content, carries a different signal.
A page reachable only via footer links has no body-prose crawl path. It may get indexed eventually. In this case “eventually” had been several weeks. The operator signals sent earlier in Phase 1.6 (sitemap canonical fix, twelve Request-Indexing nudges via GSC, IndexNow submission) were legitimate steps. They weren’t substitutes for a prose crawl path. Telling Google a page exists via every channel available doesn’t change the crawler’s priority if nothing indexed links to it in body prose. The two propositions produce different signals: this page exists, versus indexed editorial content thinks the page is worth following.
The legal pages and the stamp-duty calculator carry additional context. YMYL content (financial calculators, legal disclaimers, tax guidance) is assessed differently by Google. The trust signals it looks for on these surfaces include whether the site treats the content seriously, not just whether it’s technically accessible. A disclaimer buried in a footer, linked from no article, doesn’t signal editorial seriousness. A disclaimer referenced in the body of an article that cites it while covering legal caveats does.
The fix
The companion work to PR #153 was editorial: body-prose internal links from six already-indexed articles pointing at /disclaimer and the stamp-duty calculator.
Not footer links. Not navigation links. Prose links. Sentences in the body of published articles where the link target was contextually appropriate. A disclaimer referenced in articles that covered legal caveats on YMYL financial content. The stamp-duty calculator linked from articles that covered property transaction costs. Six source articles. Two target pages.
The mechanism is crawl-weight transfer. When Google crawls one of those six already-indexed articles and follows the new prose link, it arrives at /disclaimer or the stamp-duty calculator with a higher priority signal than the footer link had been generating. The target pages move from “somewhere in the footer graph” to “linked from indexed topical content.” That shift is what the technical fixes couldn’t produce.
The Phase 1.6 sequence
The 20 June operator push ran first: ga-telemetry observability, sitemap canonical fix, twelve Request-Indexing nudges, IndexNow live. That was the right first move. Operator signals are fast to send and a technical fix is faster than an editorial campaign. You check that layer first.
The 8-pillar content map closed on 23 June, with fourteen articles across a two-day push. That wasn’t incidental to the indexing problem. Those articles were the source material for the prose links I added on 24 June. Without a body of indexed articles covering IHT, stamp duty, and YMYL calculators, there would have been nowhere to put the links. The content build and the indexing fix were sequenced correctly, even if the sequence wasn’t planned that way from the start.
The 24 June work was diagnostic first, editorial second. Audit to confirm there’s nothing technically wrong, then act on the thing the audit can’t solve: the crawl path. The prerender fix and FAQ helper cleanup that shipped in the same PR were real improvements to the stuck pages. They weren’t the mechanism that would move the indexing needle. That distinction mattered when deciding where to spend the next two hours.
The failure mode
There is a specific failure mode in SEO work where a technical audit comes back clean and the conclusion becomes “the site has done everything right, now wait.” Sometimes that’s correct. Often it means the audit checked a necessary layer but not a sufficient one.
For footer-only pages on a site in its early indexing phase, the answer is almost always the same: they need a body-prose crawl path from already-indexed content. Not an IndexNow ping. Not a manual GSC submission. A sentence in a published article where the link is contextually appropriate and the source page already carries Google’s trust.
The work doesn’t touch the pages that need indexing. It requires reviewing the pages that are already indexed and finding where a genuine link to the stuck page fits naturally. Six source articles. Two hours.
The Phase 1.6 lesson is narrow: technical correctness is necessary but not sufficient, and when the technical audit is clean, the next diagnostic question is whether indexed content links to the stuck pages in body prose. In this case the answer was no, and the fix was adding those links. The audit to confirm there was nothing else wrong took longer than the fix itself.
