Incomplete sitemap address

sitemaps.sitemap_invalid_loc
Priority
Low
Severity
Warning

What we look for

These entries in a sitemap (the file that lists your pages for search engines) are not complete addresses starting with http:// or https:// and a domain, as the sitemap format requires.

Why it matters

Search engines skip entries that are not full addresses, so the pages behind them are not listed through the sitemap.

How to fix

Write every entry as a full address, such as https://example.com/page, in the settings of the CMS or plugin that builds the sitemap.

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: sitemaps.sitemap_invalid_loc
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "sitemaps.sitemap_invalid_loc"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=sitemaps.sitemap_invalid_loc
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "sitemaps.sitemap_invalid_loc"
}