Does your sitemap list addresses search engines will skip?

This search visibility check flags sitemap entries search engines are likely to skip, such as http addresses on an https site, the www twin of your address, duplicates, relative paths or other sites.

What does this check look at?

It looks at whether your sitemap lists insecure, duplicate, relative or other-site addresses. Google asks for fully-qualified, absolute URLs in sitemaps. Listed pages are never requested. 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?

Listed pages are not requested, and it is about search visibility only. 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

Point the generator at your canonical address and let it build every entry from that.

My sitemap has entries search engines will skip: [paste the problem from the report]. Fix my sitemap generator so every entry is an absolute https address on my canonical host (the same www or non-www form my site redirects to), each page is listed once, and no other site's pages are included. Show me a sample of the new entries.

How to check

Say Atlas, our example app at atlas.example, builds its sitemap from an old base address that still uses http. Every entry points at the insecure twin, and the check adds one card.

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.