The live page no longer contains noindex, but Search Console still reports an exclusion. Compare Google’s last recorded crawl with the time you deployed the change. A saved Google result and your current server response may describe different states.
Request indexing after checking the response. Repeating the request does not make the crawl happen sooner.
Make the discrepancy traceable
A fictional product-page record might look like this:
Change deployed: Monday, 10:00
Live test: Monday, 10:20, status 200
Robots meta: no noindex
X-Robots-Tag: no noindex
Last recorded Google fetch: Sunday
Here the older result does not demonstrate a failed deployment. If Google’s recorded fetch happened after the change, inspect the delivered version more closely.
Check both HTML and response headers. A plugin may remove the meta element while the server still emits X-Robots-Tag: noindex. Different hostnames, cached drafts and responses available only to signed-in users can also explain conflicting observations.
Inspect the remaining signals
Once the instruction is truly removed, check reachability, canonical links and internal discovery paths. Removing noindex does not make a page the preferred address when its canonical points elsewhere. If the canonical is unexpected, inspect its destination before requesting indexing again.
Record your findings, perform a live inspection and request indexing when appropriate, then observe a later recorded crawl. The indexability checker supports the current technical inspection.