## **🔍 What “not indexable” means**

A non-indexable page contains a setting or technical signal that tells search engines not to include it in their results. Search Atlas may identify this issue on pages created by the platform, existing WordPress pages, or both.

Page creation and search engine indexing are separate processes. A page can be published successfully but still remain unavailable to search engines until its settings, content, links, and technical signals meet indexing requirements.

## **📄 Why a page created by Search Atlas may not be indexable**

Common causes include:

- The page is saved as a draft, private page, or pending review.
- A **noindex** setting is enabled in WordPress or an SEO plugin.
- The page is blocked by the robots.txt file.
- The page has a canonical URL pointing to another page.
- The page is not linked from other important pages on the site.
- The page has little or duplicate content.
- The website, page, or post type is excluded from search engine settings.
- The site is protected by a maintenance mode, password, or access restriction.
- Search engines have not crawled the page yet.

## **🤖 Why the AI agent may not fix it automatically**

The AI agent can identify issues and recommend tasks, but it does not automatically change every setting. Some fixes can affect many pages, remove intentional exclusions, change SEO plugin settings, or alter important website behavior. For this reason, the agent may ask you to review or complete a task before applying a change.

Automatic actions can also be limited by WordPress permissions, plugin settings, connection status, or the type of issue detected. Installing the Search Atlas plugin connects the platform to WordPress, but it does not guarantee permission to change every SEO, indexing, server, or theme setting.

## **🛠️ How to review a non-indexable page**

1. Open Site Audit, go to Page Explorer, and filter by "Not indexable" (or open the Indexability issue group). Open the affected page and note the exact reason shown, such as robots.txt, meta robots, HTTP header, canonical mismatch, or a non-2xx status code. If the agent has also recommended a task for that page, compare the task with this reason.
2. In WordPress, confirm that the page is published and publicly accessible.
3. Check the page’s SEO settings for a **noindex** directive.
4. Review the canonical URL and confirm it points to the page’s preferred URL.
5. Check the robots.txt file and confirm the page is not blocked.
6. Confirm that the page is included in your XML sitemap when appropriate.
7. Add relevant internal links so search engines can discover the page.
8. After making changes, request a fresh check or allow time for search engines to recrawl the page.

## **✅ When not to remove the restriction**

Not every non-indexable page needs to be indexed. Login pages, checkout pages, duplicate URLs, filtered pages, thank-you pages, staging pages, and thin utility pages are often intentionally excluded. Removing the restriction from these pages can create duplicate or low-value search results.

## **🚀 Best next step**

Use the agent’s task details to identify the exact page and reason. Review the recommended change before applying it, especially if the task affects an entire post type or site-wide SEO setting. If the page should be indexed but the issue remains after the recommended changes, confirm that the WordPress connection is active and that the connected user has sufficient permissions.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.