Adding a domain to GA4’s unwanted-referral list only affects events GA4 receives after the change, so the old referral can still be sitting in your reports.

An active GA4 Developer traffic filter can intentionally keep debug-mode events in DebugView while excluding them from Realtime and other reports.

A template part saved in the Site Editor becomes a database override, so it takes precedence over edits to the theme file until you clear that customization.

A browser can load a sitemap even when Googlebot cannot fetch it; test the exact submitted URL in Search Console and check robots rules, URL correctness, and server availability.

When the Navigation block differs live versus in the editor, the common cause is editing a different menu, header template part, or page template than the live page uses, with caching as the next thing to check.

No referring sitemap on a URL can be normal even when the submitted sitemap is successful; it means Google did not attribute that URL’s discovery to a sitemap.

A consent-banner change can create a direct-traffic spike because GA4 may lose the referral or cookie data it needs to attribute visits; direct means no clear source was available.

A Pages Function that works on pages.dev but 404s on a custom domain is usually a custom-domain/DNS attachment issue, or a route that is not included in the deployed Function routing rules.

`Cache-Control: no-store` does not control a service worker's Cache Storage, so an old response can still be served by the worker until its cache logic removes or bypasses it.

Usually it means GA4 is recording the event, but Google Ads either hasn’t imported it yet or can’t tie it back to a Google Ads click.