A page closed off from indexing earns nothing, no matter how good it is. When it happens across a template it is usually a staging flag that survived the move to production. There is a second, worse version of this: the tag lands on a template and closes off every page that template produced, so the site loses a whole section without anything appearing broken. That is why indexgap reports it as critical and collapses it when it fires site-wide — a hundred identical findings would hide the single line that caused them.
The finding reads:
critical noindex the page is closed to indexing — unless that is deliberate, there will be no trafficRemove the robots meta tag if closing this page off was not intended. If it was, leave it and ignore this finding.
Collapsed when it fires template-wide. If it appears on 90% or more of the pages — or of one language version — of a site with at least 20 pages, it is a property of the template and is reported once, with the count, instead of once per page.
pipx install indexgap
cd your-project
indexgap init
indexgap checkThen indexgap brief turns
every finding on this page into a work order in indexgap-briefs/,
with the thresholds the result has to satisfy and the command to check it.