Ranking Recovery · Part 7
You fixed it three weeks ago and the report has not moved
The removal rule works. You have checked it from outside. The sitemap is submitted. And Search Console shows the same numbers it showed last week, or the week before. The chart is flat. It is easy to conclude that nothing you did had any effect.
In most cases the work is fine and the report is late. Search Console is not a live view of Google. It is a summary, compiled on a delay, of things Google did some time ago. During a recovery that delay is the main source of worry, and understanding it prevents the worst mistake you can make at this stage: undoing a correct fix because it did not appear to work.
Three separate delays
What you see in a Search Console report has passed through three waits, each stacked on the last.
The crawl delay. Google has to come back and request an address before it knows anything changed. For important pages that is days. For obscure spam addresses it can be months.
The processing delay. After fetching, Google has to process what it found and update its records. This is usually quick but not immediate.
The reporting delay. The reports are refreshed on their own schedule. The Pages report is typically a few days behind and sometimes pauses altogether. Each report shows a “Last updated” date. Read it before you read anything else.
Add those together and a fix made today may not be reflected for two or three weeks, even when everything is working.
Google Search Console not showing data, or showing old data
Different reports lag by different amounts.
| Report | Typical delay | Worth knowing |
|---|---|---|
| Performance | Two to three days | The most recent days fill in late and can change |
| Pages (indexing) | Several days; pauses occur | Check the “Last updated” date on the report |
| URL Inspection (stored) | As old as the last crawl | Shows the last visit, not today |
| URL Inspection (live test) | None | The only real-time view you have |
| Validation of a fix | Up to two weeks or more | Fails as a group if one address still has the issue |
| Security Issues review | Days to a couple of weeks | One review at a time |
The one entry with no delay is the live test. When you need to know what is true now, that is where to look.
Why the totals go up after you clean up
This catches nearly everyone. You remove the spam, and the count of not-indexed addresses climbs.
It is good news in disguise. An address Google had only heard about was invisible in your reports. When Google finally requests it and is told it is gone, it is recorded as “Not found.” The total rises because Google is working through the backlog and writing down each answer. A climbing “Not found” count made of spam addresses is the sound of the cleanup being heard.
The same applies to old addresses surfacing months later. After any large change to a site, Search Console keeps turning up addresses from the past in waves, long after you thought the list was complete. Expect it.
What to trust instead
If the reports are weeks behind, what tells you the truth today? Three things.
The live server. Ask an address for its status code from outside your own browser. This is fact, not report.
Your server logs. The access log records every request Google’s crawler makes and what it was answered. If the log shows Googlebot requesting a spam address and receiving 410 this morning, that address is being dealt with, whatever the report says. Reading your logs daily is covered in the hardening series.
The search results themselves. A site: search shows roughly what is indexed right now.
From the case file. The owner pulls his logs every day and reads them by crawler: which of Google’s crawlers came, what each one asked for, and what it was told. The reports tell him what Google concluded some time ago. The log tells him what Google is doing now. When the two disagree, the log is right and the report will catch up.
The danger of fixing what is not broken
The lag creates a specific trap. You make a correct change. Nothing appears to happen. So you make another change. Then another. By the time the first one shows up in the reports, you have altered three more things and can no longer tell which mattered — or whether one of the later changes broke the first.
The discipline is dull and it works.
- Make one change.
- Verify it on the live server straight away.
- Write down the date and what you changed.
- Leave it alone for at least two weeks.
- Keep verifying the live answer during those two weeks, because rules break.
The fourth step is the hard one. Doing something feels better than waiting. During recovery, waiting on a verified fix is usually the right work.
When it really is stuck
Sometimes the report is flat because something is wrong. These are the signs that the problem is real and not a delay.
- The live test on a spam address does not return 410.
- The live test on a real page reports that crawling or indexing is not allowed.
- Your logs show no visits from Google’s crawler at all for a week or more.
- The “Last crawled” date on your important pages has stopped advancing.
- A row such as Server error or Blocked by robots.txt is growing.
Any of those is worth acting on today. A flat chart with a correct live test is not.
Keep your own record
Search Console keeps limited history, and its charts smooth over the detail you will want later. Once a week, screenshot the Pages report with the date visible, and save it in a folder. In two months you will have a record of the recovery that no report can reconstruct, and you will be able to see movement that was invisible week to week.
Search Console tells you what Google decided. A separate question is what Google can see on the site right now. The Free Visibility Snapshot gives a current reading of how Google sees your pages, independent of how far behind the reports are.
See what Google seesFree · the Free Visibility Snapshot™ · a narrow look at four signals, not an audit
Back: What Is a Sitemap, and Why It Matters After a Hack
Next: Why Is My Website Marked as Unsafe? Clearing Warnings After a Hack
Hub: Ranking Recovery Blog Series
ProVAE builds and recovers websites in Douglas, Georgia, serving South Georgia.