Skip to content
goflag
Documentation
Rule catalogue

sitemap.field.invalid

<changefreq> and <priority> must hold the values the protocol defines

warningsite-widespec-required

Why it matters

Both fields are ignored by Google either way, so a wrong value costs nothing directly. It is reported because a value outside the protocol is a generator that was never checked — and the same generator writes the <loc> values that do matter.

What the finding looks like

The message goflag prints, with example values substituted.

warn sitemap.field.invalid 1 entry carries a field outside the protocol's values: https://example.com/a — priority 1.5. Google ignores both fields either way — so this is worth fixing or deleting, never worth trusting.

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 documents 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.