## **⚠️ What this warning means**

A recent site audit can show inaccessible-sitemap issues, and the 0–1000 Technical Score (also called Site Health) can drop sharply, even when your pages look unchanged. The sitemap warning and the score are calculated separately. This article explains what each one means and what you can check before you contact support.

## **✅ Confirm your files are public**

Open your robots.txt and sitemap URLs in a browser, or use an external checker that is not Search Atlas. If those tools can read the files, the site itself is likely fine. In the case support reviewed, October 5 scans and outside checks still saw the sitemap and robots.txt while later Search Atlas scans warned that the sitemap was inaccessible.

- Confirm robots.txt loads and lists your sitemap URL.
- Confirm that sitemap URL opens and returns your URL list.
- Compare the warning with an earlier audit that read the same files successfully.

## **🤖 Why the audit can still flag the sitemap**

Support can recrawl the site and compare the crawler result with a normal browser request. Search Atlas flags a sitemap as inaccessible only after it requests that file and the request fails or the XML cannot be read. If robots.txt loads, the Sitemap URLs declared in it are queued to be fetched. A file that Search Atlas never requests is not marked inaccessible. If your browser can open the sitemap but the audit still flags it, the failure is in how Search Atlas fetched it, not something you fix by rewriting robots.txt or moving the sitemap.

You cannot manually dismiss the inaccessible-sitemap flag. Leave publicly reachable files unchanged, then run a new audit. The new crawl requests the sitemap again, and a successful fetch clears the flag. If the new audit still reports it, contact support.

## **📊 Why the health score can fall at the same time**

Support confirmed a scoring change around the week the score fell. Non-indexable pages were temporarily scored as zero and included in the site average, which lowered Technical Score even when the indexable pages had not changed. That score is tracked separately from the sitemap warning. After the scoring correction, the site average stopped counting those non-indexable pages, and a score can return above 900 when the indexable pages warrant it.

Do not treat the score drop and the sitemap warning as one site error. The score change came from the updated scoring rules. The sitemap warning means Search Atlas requested that sitemap and the fetch failed or the file could not be read.

## **🛠️ What you should do**

1. Verify robots.txt and the sitemap with a browser or an external tool.
2. If both load, leave the files in place. Editing them will not fix a crawl that never requests the sitemap.
3. Note the date the warnings and the score change started, and whether an earlier audit still read the sitemap.
4. If the warning remains after a new audit, ask support to recrawl the site and review the sitemap fetch result, including the status recorded for that sitemap, against the file you can open in a browser.

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.