News &
insights

The WebYes blog is for time-bound pieces on web quality in the Netherlands: when the free scan goes live, how we certify, what sits in an annual report, and which product choices sit behind that. It is not a news aggregator and not an SEO factory of thin posts.

Each article should stand on its own. We explain what changed, why it matters for site owners, and how it relates to the four pillars of certification. When we name standards, we link to primary sources.

Categories help you filter: product (scan, badge, subscription), news (announcements), report (measurements and year overviews). Choose 'All' to browse chronologically.

The knowledge base is evergreen: what CSP is, how WCAG 2.2 works, how to test Core Web Vitals. We revise those pages when the standard or our engine changes. The blog marks moments: a launch, a methodology change, a public figure.

Read the blog when you want to know what is happening now. Go to the knowledge base when you need to understand a finding from a scan. Articles link to guides; guides link back to relevant posts without repeating the same paragraphs.

Looking for the hard mark rule (average ≥ 80, pillar ≥ 60)? That lives on the how-it-works page and in product copy. Blog posts may mention the rule; they do not replace that page.

We write about what site owners actually hit in the scan: slow LCP on landing pages, missing security headers, tap targets that are too small, accessibility failures machines do or do not see. No generic '10 tips for a better website' without measurable context.

Product posts explain choices you see in the UI: why six pages in the free scan, why fifteen in the full audit, why a sixty-minute dedupe window, why re-audit around thirty days. Those numbers are product facts; we do not reinvent them per article.

Report pieces cover datasets and methodology. We only show percentiles above a minimum sample; that explanation lives on the methodology page. A blog post may name that threshold; it does not invent a sector ranking on thin data.

Just scanned? Open the article or guide that matches your weakest pillar. Security low? Start with headers and TLS pieces. Speed the problem? Read about Web Vitals and lab versus field. The blog adds 'why we measure it this way'; the knowledge base adds 'what the metric is'.

Badge and public profile belong to a paid mark. Posts about the badge explain that status is live and that visitors can open the report themselves. That is not a marketing claim without proof: the report is the evidence.

Accessibility stays an honest story: automated checks cover part of WCAG 2.2 AA. Blog posts repeat that limit when we touch a11y, so nobody reads a mark as full legal conformance.

We publish when there is something to say, not to fill a calendar. Prefer one dense article with sources over five thin updates. Substantive posts list Sources when we claim external facts.

Typical references: web.dev for Core Web Vitals, W3C for WCAG, internet.nl for Dutch internet standards, Digitoegankelijk for legal frames. WebYes product figures are cited as product facts.

Missing a topic or spotted a factual error? Email [email protected]. We fold corrections into the article; we do not silently rewrite without matching the live scan.

No repeated 'top 10 SEO tips' without scan context. No sector leaderboards on samples that are too small. No promises that a badge doubles organic traffic. The blog stays close to measurable web quality and to what you can verify in the report.

Affiliate reviews of hosting or page builders do not belong here unless we share a concrete measurement you can repeat. Partners and sponsored mentions stay on the pages meant for them, not hidden inside editorial posts.

If a topic fits better as an evergreen guide, we publish it in the knowledge base and link from a short blog note. That keeps this index chronological and the knowledge base thematic.