🧭 Overview
If a page in Search Atlas repeatedly flips between Indexable and Not Indexable status, this usually points to an unstable technical configuration on the page itself — not a bug in the platform. Search Atlas reflects the live state of your page each time it crawls, so if the underlying signals are inconsistent, the reported status will be too.
This article walks you through the most common causes and how to fix them.
🔍 Where to Find Indexability Status
You can review and monitor your page's indexability status inside the On-Page Audit tool:
- In the left sidebar, click Content.
- Select On-Page Audit.
- Enter or select the URL you want to investigate.
- Review the Indexability field in the audit results.
Run the audit on two separate occasions a few hours apart. If the status changes between runs, one or more of the issues below is likely the cause.
⚠️ Common Causes of Indexability Flipping
1. 🏷️ Inconsistent Robots Meta Tag
A page may serve a noindex directive to crawlers under certain conditions — for example, when a user is not logged in, when A/B testing is active, or when a caching layer serves a different version of the page. To investigate:
- Fetch the page directly in a browser while logged out and inspect the
<meta name="robots">tag in the page source. - Use Google Search Console's URL Inspection tool to see what Googlebot actually received.
- Check whether any CMS plugins (e.g., SEO plugins on WordPress) conditionally add noindex based on page status, category, or user role.
Fix: Ensure the robots meta tag outputs a consistent value (index, follow) regardless of user state, cache state, or test variant.
2. 📄 Unstable Canonical Tag
A self-referencing canonical tag is required for a page to be considered fully indexable. If your canonical tag points to a different URL intermittently — or is missing on some page loads — Search Atlas may alternate between classifying the page as indexable and not indexable.
- Check the
<link rel="canonical">tag in the page source on multiple loads. - Confirm the canonical URL exactly matches the page's primary URL (including or excluding trailing slash, www, and HTTPS — whichever is your canonical format).
Fix: Hardcode a consistent, absolute canonical URL in your page template so it never varies between requests.
3. 🤖 Robots.txt Blocking the Crawl Intermittently
If your robots.txt file is served from an origin that experiences downtime or slow responses, crawlers may be blocked on some requests and allowed on others. Search Atlas interprets a blocked crawl as Not Indexable.
- Verify your robots.txt is accessible at yourdomain.com/robots.txt and loads consistently.
- Check that the Disallow rules do not include the URL path you are auditing.
Fix: Ensure your robots.txt is cached and served reliably. Remove any Disallow rules that inadvertently match the page you want indexed.
4. 🔀 Redirect Chains or Temporary Redirects
A page that returns a 200 OK on some requests but a 301, 302, or 307 redirect on others will flip indexability status. Temporary redirects (302, 307) in particular signal to crawlers that the destination is not the canonical page.
- Test the URL with a server header checker tool to confirm it consistently returns a 200 status code.
- Look for redirect logic tied to geolocation, device type, or login state that may be routing crawlers differently.
Fix: Consolidate redirects and ensure the target URL always returns 200 OK without intermediate hops.
5. 🧩 JavaScript-Rendered Content and Render Timing
If critical indexability signals — such as the robots meta tag or canonical tag — are injected by JavaScript after the initial page load, crawlers may or may not process them depending on render timing. This creates non-deterministic indexability outcomes.
- View the page source (not the rendered DOM) to confirm these tags are present in the raw HTML.
- If you are using a JavaScript framework, ensure your SEO tags are rendered server-side or pre-rendered.
Fix: Move robots meta and canonical tags into the static server-rendered HTML so they are always present on the first byte of the response.
✅ Recommended Resolution Steps
- Run the On-Page Audit for the affected URL and note every flagged issue.
- Check the robots meta tag, canonical tag, robots.txt, HTTP status code, and page source for inconsistencies.
- Fix the root cause in your CMS, hosting configuration, or codebase.
- Re-run the On-Page Audit after your changes are live to confirm the status has stabilised as Indexable.
- If the page is already in Google's index but flagged incorrectly, use Google Search Console → URL Inspection → Request Indexing after resolving the issue.
💬 Need More Help?
If you have followed all the steps above and the indexability status is still flipping, 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.