## **🧭 What This Article Covers**

If you notice a page alternating between **Indexable** and **Not-Indexable** status in Search Atlas, this guide walks you through the most common causes and the steps to resolve them permanently.

## **⚠️ Why Indexability Status Keeps Changing**

Indexability flipping is almost always caused by one or more **conflicting signals** on the page or server. Google re-crawls pages on its own schedule, and each crawl can return a different result if the underlying signals are inconsistent. Common root causes include:

- **Conflicting noindex directives** — a `noindex` meta tag exists in some page states (e.g. logged-in vs. logged-out, A/B test variant, or CMS draft mode) but not others.
- **Inconsistent canonical tags** — the canonical URL changes between crawls, making Google treat the page as alternately authoritative or duplicate.
- **robots.txt blocking and unblocking** — deployment pipelines or CDN rules that toggle robots.txt entries across environments (staging vs. production).
- **Conditional server responses** — the server returns a **200** for some user agents and a **403/404/503** for Googlebot, depending on caching or bot-detection rules.
- **JavaScript rendering delays** — a client-side script injects a `noindex` tag after the initial HTML loads, so the directive appears only when JS renders fully.
- **CMS workflow settings** — publishing, scheduling, or preview modes that temporarily alter meta robots values.

## **🛠️ Step-by-Step Troubleshooting**

1. **Audit the page in Search Atlas On-Page Audit.** Navigate to **Left sidebar → Content → On-Page Audit**, enter the affected URL, and check the **Indexability** section. Note every flag raised — pay particular attention to meta robots, canonical, and HTTP status warnings.
2. **Inspect the live page source.** Open the URL in a browser, right-click, and select *View Page Source*. Search for `noindex`, `nofollow`, and `canonical`. Then repeat the check using a tool that renders JavaScript (such as Google Search Console's *URL Inspection → Test Live URL*) to see the rendered DOM. Compare both versions.
3. **Check your robots.txt.** Visit `yourdomain.com/robots.txt` and confirm the affected URL or its directory is not disallowed. If you use separate staging and production environments, verify the correct robots.txt is being served in production.
4. **Review server response codes.** Use Google Search Console's *URL Inspection* tool to see the HTTP response Googlebot receives. If it differs from what a browser sees, investigate your CDN, WAF, or bot-detection configuration.
5. **Check for A/B testing or personalisation scripts.** If you run split tests or personalised content, ensure the **control variant** — and every variant — does not conditionally inject a `noindex` tag. Use the *Fetch as Google* option in URL Inspection to confirm what Google actually sees.
6. **Audit your CMS publishing workflow.** In WordPress, Shopify, or similar platforms, check that draft, scheduled, or preview states cannot be accessed by Googlebot. Restrict preview URLs with a password or IP allowlist rather than a `noindex` tag on the live URL.
7. **Stabilise the canonical tag.** Ensure the canonical tag on the page always points to the same, final URL — including consistent use of **www vs. non-www**, **HTTP vs. HTTPS**, and **trailing slashes**.
8. **Re-run On-Page Audit after each fix.** Return to **Left sidebar → Content → On-Page Audit** and re-audit the URL to confirm all indexability flags are resolved before requesting re-indexing.

## **✅ Confirming the Fix**

Once you have resolved the conflicting signals, take these final steps to accelerate stabilisation:

- Submit the URL for re-indexing via **Google Search Console → URL Inspection → Request Indexing**.
- Monitor the page's indexability status in Search Atlas over the following 7–14 days to confirm it stays consistently **Indexable**.
- If you made changes to robots.txt, re-submit your sitemap in Google Search Console so Googlebot picks up the updated rules promptly.

## **💡 Prevention Tips**

- Use a **staging subdomain with HTTP authentication** rather than a `noindex` tag to protect pre-production pages.
- Add indexability checks to your **pre-deployment QA checklist** so meta robots and canonical tags are verified before every release.
- Schedule regular **On-Page Audits** in Search Atlas to catch any regressions early.

## **🙋 Still Need Help?**

If you have followed all the steps above and the page indexability is still flipping, our team is ready to investigate with you. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.