Two robots meta elements expressing different intentions make configuration hard to maintain. Google applies the more restrictive rule when instructions conflict: adding index does not cancel noindex. Inspect every relevant signal in the actual response.
This fictional HTML illustrates the conflict:
<meta name="robots" content="index,follow">
<meta name="robots" content="noindex">
Record both elements and any X-Robots-Tag response header. Inspect the original source and, where scripts modify it, the resulting browser document as well.
Isolate changes away from production
Preserve the current configuration and reproduce the finding on a protected copy. Inspect WordPress visibility settings, SEO extensions and the theme. Multiple SEO extensions may produce overlapping output, but their presence alone does not prove which caused the problem.
Change one source on the test environment and compare output again. Inspect pages, posts and products separately. A deliberate draft exception should not disappear accidentally during a global correction.
Assign responsibility for each content type. Remove duplicate generation at its source instead of layering another contradictory signal over it. After deployment, repeat the same requests without signing in. Include intentionally excluded pages as comparison cases so that the fix does not expose drafts to search.