sitemap.entry.invalid-url
Every <loc> must be an absolute, parseable URL
errorsite-widespec-required
Why it matters
A sitemap is fetched on its own, with no page behind it, so a relative <loc> resolves to nothing. The entry looks like a declaration and names no address.
What the finding looks like
The message goflag prints, with example values substituted.
error sitemap.entry.invalid-url 2 <loc> values are not an absolute URL: /about, /pricing. A sitemap is fetched on its own, so a consumer has nothing to resolve them against.
How to fix it
The catalogue carries no snippet for a site rule: a cross-page rule builds its remedy from what the crawl found, so goflag attaches the fix to the finding itself rather than to the rule. Run it and read the finding.
Says who?
This rule is spec-required, and it cites the document below. Nothing here is goflag’s opinion of what a good page looks like — if you disagree with a finding, this is what you are disagreeing with.
- Sitemaps XML protocol
sitemaps.org · normative