Ìwé ayípadà

16 May 2026

• TI TÚNṢESPA 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.

May 15, 2026

• TUNTUNResearch 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.
• TUNTUNRepository website-quality check. GitHub repo scans can now flag template image issues and missing quality automation with evidence tied to source files.
• TUNTUNDeployment 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.

May 14, 2026

• TUNTUNPerformance-delivery module. Browser scans now estimate resource weight, script count, third-party pressure, and font volume.
• TUNTUNMobile/i18n/PWA module. Viewport, language, hreflang, and manifest basics now have dedicated findings.
• TI DÁRA SÍIRendered 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.

May 13, 2026

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

May 12, 2026

• TUNTUNRepo 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.
• TUNTUNRuntime-markup module. Browser scans now capture console errors, failed requests, and low-content renders so broken app shells show up in reports.

May 9, 2026

• QUALITYCross-origin scope handling. Browser crawls now keep page snapshots scoped to the submitted origin and avoid carrying owner headers across unrelated hosts.
• TI TÚNṢEOwner-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.
• TI DÁRA SÍISearch presentation scoring improved. Title, snippet, favicon, canonical, and Open Graph checks now grade rendered pages instead of raw HTML only.
• TI DÁRA SÍIForm checks improved. Labels, placeholder-only fields, autocomplete hints, and mobile input metadata now produce clearer findings.
• TI DÁRA SÍIMedia-quality checks improved. Image alt text, dimensions, and likely hero-image loading mistakes now appear in a dedicated media category.

May 7, 2026

• TI TÚNṢELive monitoring signal cleanup. External listing and DNS/certificate changes are now framed as website-monitoring events instead of scan vulnerabilities.
• TUNTUNGitHub 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.
• TUNTUNTemplate pattern checks. Repo scans now look for repeated source-level causes of rendered page quality issues.
• TI TÚNṢEFallback-route false positives reduced. SPA and edge fallback responses are compared against baselines before FixWeb reports broken rendered pages.
• TI TÚNṢERepo scan false positives reduced. Template checks now ignore comments, documentation snippets, and clearly server-only examples where possible.
• TI TÚNṢEStructured-data checks added. Rendered JSON-LD syntax errors and missing homepage entity schema now surface as content findings.
• TI TÚNṢEAccessibility baseline added. Language, main landmarks, skip links, unnamed buttons, and tap-target signals are now checked on rendered pages.
• TI TÚNṢERuntime-markup checks tightened. Browser console errors, failed requests, and low-content renders now produce clearer evidence and fewer false positives on SPA fallback routes.
• TI TÚNṢEDomain verification handles apex ↔ www redirects correctly and is clearer about which value goes in the TXT-record Host field.

Format

Entry kọ̀ọ̀kan ní tag kí o lè skim:

• TUNTUN Check, surface, tàbí feature tuntun.
• TI DÁRA SÍI Ìhùwàsí tó wà ti dára síi — péye síi, yára síi, yege síi.
• TI TÚNṢE Bug tí a ship, tí a sì pa rẹ̀ run lẹ́yìn náà.
• QUALITY Quality, privacy, or platform hardening changes.

Ṣe o rí ohun kan tó bàjẹ́ tí kò sí níbí? Fi email ránṣẹ́ sí support@fixweb.app.