reindexaYou open a Search Console export, select a URL marked as unindexed, and its inspection says it is indexed. It is tempting to conclude that one tool is broken. First establish whether you are comparing the same address, the same type of observation and the same point in time.
A saved list is a snapshot
An exported file does not update when Google's available information changes. The aggregated report and individual inspection may also reflect updates at different times. Google's report documentation describes this possibility. A discrepancy alone does not establish a fixed reporting delay.
Keep two separate fields: the original report reason and the latest inspection result. Replacing the former with the latter removes the evidence explaining why the URL entered your monitoring set.
Check that the comparison is valid
- Copy the complete address, including protocol, hostname, path and parameters.
- Confirm the Search Console property you are using.
- Record the export date and inspection timestamp.
- Look for redirects or a different canonical URL.
- Distinguish Google's stored information from a live test.
A live test checks current accessibility and potential indexability. It does not establish that the URL is already indexed. Google's URL Inspection help explains the difference.
Write an observation you can defend
Suppose a Monday export contains a guide, while Thursday's inspection reports it as indexed. An accurate record says: “Included in Monday's report; observed as indexed on Thursday.” It does not say: “Google indexed it at ten on Thursday.” Ten was your inspection time, not necessarily the event time.
Even when both observations share a calendar date, review their details. Matching dates do not prove that the data came from the same update.
Decide what work is still necessary
If the inspection confirms the expected state, you can change the URL's work priority while continuing to monitor it. You do not need a technical fix merely to remove a URL from an old spreadsheet. If it remains unindexed, keep the investigation open and review technical and editorial evidence.
In Reindexa, the imported report defines the starting set, while later checks show its evolution. Treating those as different observations turns an apparent contradiction into useful information. When reporting to a client, show both dates and explain when a change was detected. A historic export should not be presented as the current state of the entire website.