One or more of the pages SaaSMaestro watches tells search engines not to index it. Google drops such pages from its results, along with the search traffic they bring.
What it means
A “noindex” directive, in a robots meta tag or an X-Robots-Tag header, asks search engines to leave the page out of their results. That’s right for pages such as thank-you pages, but a mistake on the home page or a busy landing page.
What triggers it
Once a day, as part of Uptime monitoring, SaaSMaestro loads the home page and the five busiest landing pages from GA4 over the last 28 days, and reads their robots meta tag and X-Robots-Tag header. Any that contain “noindex” raise one High issue listing up to three of them. The day a page switches to noindex, a timeline note is added too.
Common causes
- A “discourage search engines” or “hide from search” setting left on after launch or maintenance.
- Staging settings copied to the live website during a deploy or migration.
- An SEO plugin setting, or a server or CDN rule adding an X-Robots-Tag header.
How to fix it
- View the page’s source and look for a robots meta tag containing “noindex”; check the response headers for X-Robots-Tag too.
- Remove the directive in your CMS, SEO plugin, template or server settings, unless the page is meant to stay out of search.
- In Search Console, inspect the page and request indexing to speed things up. See Pages not in Google’s index.
When it clears
The issue goes at the next daily check that finds no noindex on the watched pages, or once a page is no longer among the busiest.
After 7 days without the problem, the action drops off the board. If you marked it done and the problem is still detected 14 days later, it returns as “Fix didn’t work”.