// docs / changelog

Historia zmian

What's changed in the FixWeb scan engine — new checks, accuracy improvements, and false-positive fixes. Newest entries first.

16 May 2026

NAPRAWIONESPA fallback false positives reduced. Path probes now compare suspicious responses against random-path baselines so client-side routers are not reported as broken pages by default.

NOWEResearch backlog checks. FixWeb shipped additional website-quality modules for crawl/indexation, search presentation, semantic structure, structured data, media, performance, accessibility, forms, i18n/mobile/PWA, runtime, owner journeys, and repo quality.
NOWERepository website-quality check. GitHub repo scans can now flag template image issues and missing quality automation with evidence tied to source files.
NOWEDeployment preview handling improved. Passive scans now treat generated deployment URLs as crawl targets and report website-quality evidence without mixing in legacy security-header scoring.

NOWEPerformance-delivery module. Browser scans now estimate resource weight, script count, third-party pressure, and font volume.
NOWEMobile/i18n/PWA module. Viewport, language, hreflang, and manifest basics now have dedicated findings.
ULEPSZONERendered crawl improved. Browser snapshots now capture forms, landmarks, images, headings, structured data, hreflang alternates, console errors, failed requests, and resource timing for every sampled page.

NOWERepo crawl-control check. GitHub repo scans can now flag missing robots.txt and sitemap files in common source locations.
NOWEMedia and image-source checks. Repo and URL scans now connect rendered image issues back to likely template causes.
NOWEWebsite-quality guardrail check. GitHub repo scans can now flag missing Lighthouse, axe, pa11y, web-vitals, or equivalent quality automation.

NOWERepo website-quality checklist. GitHub repo scans can flag template-level issues such as missing crawl-control files, image elements without alt or dimensions, and absent quality automation.
NOWERuntime-markup module. Browser scans now capture console errors, failed requests, and low-content renders so broken app shells show up in reports.

QUALITYCross-origin scope handling. Browser crawls now keep page snapshots scoped to the submitted origin and avoid carrying owner headers across unrelated hosts.
NAPRAWIONEOwner-depth scan path clarified. Verified-domain scans can carry a short-lived owner header into the browser crawl and purge it when the scan completes.
ULEPSZONESearch presentation scoring improved. Title, snippet, favicon, canonical, and Open Graph checks now grade rendered pages instead of raw HTML only.
ULEPSZONEForm checks improved. Labels, placeholder-only fields, autocomplete hints, and mobile input metadata now produce clearer findings.
ULEPSZONEMedia-quality checks improved. Image alt text, dimensions, and likely hero-image loading mistakes now appear in a dedicated media category.

NAPRAWIONELive monitoring signal cleanup. External listing and DNS/certificate changes are now framed as website-monitoring events instead of scan vulnerabilities.
NOWEGitHub repo scans. Connect a repo and FixWeb checks source templates, crawl-control files, metadata patterns, image usage, and website-quality automation without ever loading your deployed site. See Scan types.
NOWETemplate pattern checks. Repo scans now look for repeated source-level causes of rendered page quality issues.
NAPRAWIONEFallback-route false positives reduced. SPA and edge fallback responses are compared against baselines before FixWeb reports broken rendered pages.
NAPRAWIONERepo scan false positives reduced. Template checks now ignore comments, documentation snippets, and clearly server-only examples where possible.
NAPRAWIONEStructured-data checks added. Rendered JSON-LD syntax errors and missing homepage entity schema now surface as content findings.
NAPRAWIONEAccessibility baseline added. Language, main landmarks, skip links, unnamed buttons, and tap-target signals are now checked on rendered pages.
NAPRAWIONERuntime-markup checks tightened. Browser console errors, failed requests, and low-content renders now produce clearer evidence and fewer false positives on SPA fallback routes.
NAPRAWIONEDomain verification handles apex ↔ www redirects correctly and is clearer about which value goes in the TXT-record Host field.

Każdy wpis ma tag, żebyś mógł szybko skanować:

NOWE Nowe sprawdzenie, powierzchnia albo funkcja.
ULEPSZONE Istniejące zachowanie stało się lepsze — dokładniejsze, szybsze, jaśniejsze.
NAPRAWIONE Błąd, który wysłaliśmy, a potem naprawiliśmy.
QUALITY Quality, privacy, or platform hardening changes.

Widzisz coś, co się zepsuło i nie jest tu odnotowane? Napisz na support@fixweb.app.