Can search engines read your sitemap?

This search visibility check flags a sitemap that does not follow the sitemap format, for example broken XML, the wrong root element, no entries or the wrong content type. Search engines may ignore it.

What does this check look at?

It looks at whether your sitemap follows the sitemap format closely enough for search engines to read it. A Pulse also reads your sitemap, the list of pages you give search engines.

Pulse and Deep scans both run it.

What does a result mean?

It is about search visibility only and never affects your grade. A clean result means nothing was found in what the scan read. It does not prove the problem is absent from parts the scan never sees.

How serious is a finding?

This is information only. It claims no weakness, so it carries no verdict, and you decide whether anything should change. Confidence starts high, because a response from your site shows the thing itself. The report lists what to fix by how directly someone could use it, not by the severity label. Sitemap cards are not security issues and never change your grade.

Fix it with your AI

Hand-written sitemaps are the usual cause. A generator gets the format right every time.

My sitemap fails validation: [paste the problem from the report]. Replace any hand-written sitemap with one generated by my framework or site builder. Make sure it is UTF-8 XML served as application/xml, uses the urlset (or sitemapindex) root with the standard sitemap protocol namespace, escapes ampersands in addresses, and is split into a sitemap index if it is very large. Show me the result.

How to check

Say Atlas, our example app at atlas.example, serves its sitemap with a stray character that breaks the XML. The check adds an information card, and regenerating the file fixes it.

Run a Pulse scan from your Lockpick account to see it for your site. Pulse or Deep explains what each scan reads, and the full list of checks shows the rest.