According to the official release history, version 18.4 was about "Bug fixes" rather than flashy new UI elements. This is vital for SEO professionals because stability is the bedrock of any reliable data analysis. When you are crawling a site with 500,000 URLs, you don't want the software to crash. 18.4 provided that robust foundation.
: The core update for 18.4 fixes the connection to Google's Lighthouse engine, allowing automated collection of Core Web Vitals (LCP, INP, CLS) alongside a standard site crawl. Operational Modes Explained
, was a critical maintenance update specifically designed to fix breaking changes in the PageSpeed Insights (PSI) API and refine the then-new GA4 integration
: A custom segmentation label or regex filter created by a specific SEO practitioner in their research paper. Screaming Frog SEO Spider 18.4 -Neverb-
to handle massive data sets without performance degradation. Research Element : How to use Custom Extraction (XPath/Regex)
While earlier versions offered Lighthouse integration, bakes Core Web Vitals (CWV) directly into the crawl analysis pipeline. You can now fetch real-world CrUX (Chrome User Experience Report) data and lab-based metrics for every URL in your crawl.
is a robust, desktop-based website crawler built specifically to conduct comprehensive technical SEO audits. The 18.4 patch ecosystem focuses heavily on stabilizing PageSpeed Insights (PSI) API integrations , perfecting Google Analytics 4 (GA4) data blending , and enhancing database storage allocation for large-scale site scraping. According to the official release history, version 18
Before diving into the technical specifications, it’s worth addressing the curious suffix: . While Screaming Frog has historically used version numbers (e.g., 17.0, 18.0), the "Neverb" tag is speculated to be an internal code name referencing a "non-verbal" or "uninterrupted" processing protocol. In practice, -Neverb- represents a shift toward zero-compromise crawling —faster threading, reduced memory leakage, and an unprecedented ability to handle JavaScript-heavy frameworks without losing data.
Even in version 18.4, users could configure the tool to handle massive websites:
: It can execute client-side JavaScript using a headless Chrome browser to see exactly what Googlebot sees. to handle massive data sets without performance degradation
To analyze mobile and desktop site speed metrics simultaneously with technical auditing. 5. Advanced Visualizations (1.2.2)
: Introduced a new Issues tab to replace standard reports, built-in segmentation , and Flesch readability scores .