A noindex can live in two places, and a page can carry one in the header while looking clean in the HTML. We read both: the meta robots tag in the markup and the X-Robots-Tag on the response.
Nothing on this page is asking Google to exclude it. That rules out the single most common cause of a page vanishing after a deploy.
This page is explicitly asking search engines not to index it. Nothing else matters until that is removed: no amount of linking or submitting overrides it.
The one everybody checks is the meta robots tag in the HTML. The one that catches people out is the X-Robots-Tag HTTP header, which is set by the server or the CDN and never appears when you view source. A page can look perfectly clean in the browser and still be telling Google to stay away. We read both.
If robots.txt disallows the URL, Google never fetches the page, which means it never sees the noindex either. That combination is how a page ends up excluded and stuck: the instruction to remove it cannot be read. Check the robots rule first if both are in play.
Once it is gone, Google has to crawl the page again before anything changes, and that happens on its schedule rather than yours. Nothing you submit shortens that reliably. What you can do is make sure something already indexed links to the page, so there is a reason to come back.
None of these tools can tell you whether Google has indexed a page. They read your page and your server, which is enough to prove a page is blocked and never enough to prove it is indexed. That answer only exists inside Search Console, which is what Seomely connects to.