# Repair — Google found 64 of my pages and did not come back: what Validate Fix moved, and the five it did not

A flowingkhaos fix · monitoring · updated 17 Oct 2026
Source: https://flowingkhaos.com/fixes/validate-fix-19-to-80-indexed/repair

## The Footer Fix, the Same Hour, and the Test Still Open

I finished the read at 16:37 UTC on 2026-10-15, and you can check the next part in git. By the end of the hour the footer of every page on clevrstart carried a Services list in its own language: seven links in English, eight in French, commit 694d211, built by Vercel and verified live on /about and /fr/about. The day before, the four legal pages, which emitted a relative canonical and no hreflang, had been fixed in commit 605cba5 and verified live. From the read to a live repair, under an hour, because the data, the fix and the deploy go through one door.

Still open: Request Indexing on the five service pages, plus /services and /fr/services/referencement-local, which the API lists as unknown even though both answer 200. That is a click in URL Inspection, one URL at a time, and I have not made it yet. The time I click is the start of the clock.

La Teva Web's 2026 indexing guide reports that [Request Indexing is a queue, not a guarantee](https://www.latevaweb.com/en/indexing-on-google-2026), and I agree; it is also the only lever left once the page and its links have changed, which is why it comes last and not first. What I will not do is validate the crawled status again. Validation re-checks a decision; the request asks for a new one.

For an owner reading this on a site someone else built, the shape of the repair is the same whatever the stack: one page per service that a customer actually searches, each one linked from pages Google already holds, in the language the customer uses. That is the structure the [Local SEO plan](https://www.clevrstart.com/info/local-seo-plan) shows, with one page per cluster of searches and the Business Profile set to match, for a business that does not want to run this loop itself; this fix is the loop run on my own site first.