<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HealthPixel Check blog</title><description>A free tool for health-care marketing and compliance teams: see what a website sends to advertising and analytics platforms, before and after cookie consent.</description><link>https://healthpixelcheck.org/</link><language>en-us</language><atom:link href="https://healthpixelcheck.org/rss.xml" rel="self" type="application/rss+xml"/><item><title>How HealthPixel Check works: what we measure on a health-care website, and what we can&apos;t see</title><link>https://healthpixelcheck.org/blog/how-healthpixel-check-works/</link><guid isPermaLink="true">https://healthpixelcheck.org/blog/how-healthpixel-check-works/</guid><description>The method in plain words: up to five browser runs, condition-naming pages, trackers behind first-party subdomains, and what a check can&apos;t see.</description><pubDate>Sat, 07 Nov 2026 00:00:00 GMT</pubDate><dc:creator>Denis Alekseev</dc:creator><category>methodology</category><category>tracking technologies</category><category>health-care websites</category><author>research@healthpixelcheck.org (Denis Alekseev)</author></item></channel></rss>