Vercel does document the behavior mentioned by the assistant: X-Robots-Tag: noindex is added automatically to Preview deployments and outdated Production deployments.

It confirms the behavior exists, but it does not fully explain why the active custom domain would have served the header. The production domain should normally point to the current Production deployment, not an outdated one.

The most useful next check is therefore the deployment timeline:

1. Identify which deployment was assigned to homeinthe.city at the July 24 crawl time.
2. Check whether a promotion, rollback or domain reassignment happened around that crawl.
3. Confirm that the URL shown by Search Console is the exact requested URL, including protocol, hostname and path, rather than a redirecting variant.

I would also run Test Live URL in URL Inspection. If the live test now reports that indexing is allowed, that means the condition was temporary. It will not prove which deployment responded on July 24, but it separates a historical routing or deployment state from a header that is still being generated today.

One additional check would be to inspect the full redirect chain:

1
curl -IL https://homeinthe.city/pt/imoveis/porto-alegre/parkview
2
curl -IL -A "Googlebot" https://homeinthe.city/pt/imoveis/porto-alegre/parkview

If both the live inspection and every response in the redirect chain are clean, I would request reindexing and focus any further investigation on the deployment and domain-assignment history around July 24.