Correct canonicals, sitemap entries, links, and HTTP status don't guarantee indexing; Google can crawl a page and still decide not to index it yet.

PageSpeed Insights can pass for one URL even while Search Console fails the broader Core Web Vitals URL group.

It’s usually a recrawl and processing delay: Google may update the homepage site name before it applies the same choice to internal results.

Internal UTMs can add a campaign touchpoint for later key events even though GA4 keeps the existing session attribution set by `session_start`.

Yes. By default, reordered query parameters create separate Cloudflare cache entries; use a Cache Rule's query-string sorting only where order is safe to ignore.

GA4 can show `(not set)` because the landing page comes from the session's first page view; a page view sent later doesn't fill that missing starting value.

It can, but only if the server cron depends on the same failing self-request or isn't actually running wp-cron.php successfully.

Cloudflare can return `HIT` after a purge once its edge cache refills, while visitors still see old CSS from their browser cache, a service worker, or an unpurged cache-key variant.

A canonical tag consolidates parameter-URL duplicates; it can reduce duplicate crawling over time but does not stop Google from crawling those URLs.

Yes, but preserve WordPress's reply-target behavior; don't simply remove `replytocom` from live Reply links.