What's newin WebScore

Search Console totals now match Google

Fixed

Fixed — The Search Console summary added up only your top 20 queries, so total clicks, impressions and CTR could be dramatically understated — one site showed 9,000 impressions where Google reported over 125,000. Totals now come straight from Search Console ungrouped, so they match what you see in Google's own dashboard.

Fixed — Average position was the plain average of your top 20 queries' positions. It's now Search Console's impression-weighted average — the same number Google reports.

v2.1.30 — released August 4, 2026

Every scan now finds your broken links

NewImproved

New — Scans now follow the links on your page — plus a sample of pages from your sitemap — and report the ones that are dead. Internal 404s are flagged as high priority (they strand visitors and waste crawl budget); dead outbound links are reported too, with the exact URL and what it returned, so you can fix or drop them.

Improved — The link check is deliberately conservative: it never counts a link as broken just because a site's bot protection answered 403 or 429, and a flaky external host is reported as unverified rather than dead. It also runs on a strict time budget, so adding it doesn't slow your scan down or delay anyone else's.

v2.1.29 — released August 3, 2026

Security scans now hunt for leaked files

NewImproved

New — Every security scan now checks whether secret-bearing files are being served from your web root — .env.production, .env.local, environment backups, wp-config.php.bak, config.json with credentials in it, database dumps (backup.sql / dump.sql), AWS credentials, .npmrc auth tokens and docker-compose.yml. Anything found is reported as critical, with the reminder that these paths are scanned constantly by bots, so exposure means the credentials are already gone. This joins the existing .git and .env checks.

Improved — The file checks can't be fooled by sites that answer "200 OK" to every URL: each hit has to actually look like the file it claims to be, and if the site returns content for paths that can't exist, the checks are skipped instead of inventing findings.

v2.1.28 — released August 3, 2026

Scan accuracy: no more phantom contrast failures

Fixed

Fixed — The color-contrast check couldn't read modern CSS colors (oklch/oklab — what Tailwind v4 sites use), so it treated those backgrounds as white and reported white buttons as "white text on white". Colors are now resolved exactly as the browser paints them, translucent backgrounds are composited over their real backdrop instead of assumed-white, unmeasurable gradient backdrops are skipped, and decorative aria-hidden text is no longer judged. Sites built on modern palettes stop losing accessibility points to phantom failures.

Fixed — The SEO check no longer counts decorative images with an intentionally empty alt attribute (the correct WCAG markup) as "missing alt text" — only images with no alt attribute at all are flagged.

v2.1.27 — released August 3, 2026

Magic links survive email security scanners

FixedImproved

Fixed — Clicking a sign-in link could land on "expired or already used" seconds after the email arrived — email security tools (Outlook SafeLinks, corporate gateways) pre-open links and were consuming the single-use token before you could. Sign-in emails now open a confirmation page first, so only your click uses the link.

Improved — Magic-link sending is now rate-limited per address, per network and platform-wide, so nobody can flood an inbox with sign-in emails or burn through sending quota — and the error page now explains that links work exactly once and how to get a fresh one.

v2.1.26 — released August 3, 2026

Get updates by email

An email when WebScore ships something new, and nothing else. Unsubscribe any time.