Screaming Frog Review: How I Run It on B2B SaaS Accounts
A Screaming Frog review from B2B SaaS client audits: 2026 pricing, what the free version cuts, how I set up a crawl, the MCP, and who needs it.
What is Screaming Frog? The desktop crawler I have run since day one
Screaming Frog SEO Spider is a desktop website crawler. You install it on your own computer, point it at a site, and it requests every page the way a search engine bot would, then lays out each URL beside its status code, title, meta description, headings, canonical, directives, internal links, and anything else you tell it to extract. Screaming Frog is also the name of the UK search marketing agency that builds it, founded in 2010.
I have used the Screaming Frog crawler since my first days in SEO, at my first agency, and I still hold a paid seat. My verdict for this Screaming Frog review: nothing really replaces it. It is the tool I reach for in three situations, an initial technical audit on a new account, a big content audit, and a deep technical issue that needs every URL in front of me.
Screaming Frog puts you inside the site. The Semrush and Ahrefs audits look at it from the outside.
Screaming Frog is good for turning a website into a spreadsheet you can sort, filter, and join to your own data. That is also why Screaming Frog has a learning curve. A spreadsheet of 40,000 rows does not tell you which ten rows matter.
I run SEO for B2B SaaS companies, and this review comes from client audits. Prices were checked on Screaming Frog’s pricing page on November 19, 2026, against version 25, released November 3. If you want a person to run the crawl and turn it into a ranked fix list, that is my SEO and GEO audit.
Do you need Screaming Frog for a small site?
Most small sites do not need Screaming Frog on day one: a small site with a clean build can start with Google Search Console and add Screaming Frog later. Search Console reports the errors that actually cost you traffic, straight from Google: pages that are not indexed, crawl errors, broken structured data, and Core Web Vitals. If you also keep an eye on meta data and broken links from the start, you can go a long way on a marketing site of a few hundred pages with no dedicated crawler.
Google draws a similar line. Its crawl budget guide is written for sites with more than a million pages, or more than 10,000 pages that change daily, and says that for everyone else, “keeping your sitemap up to date and checking the Page Indexing report regularly is adequate.” That guidance is about Google’s crawling, but the practical point carries over: most small sites have no crawl problem worth a paid tool.
The site earns Screaming Frog when one of these is true:
- You are starting an account. The initial technical audit needs every URL, every redirect, and every directive in one place.
- You are auditing a lot of content. Hundreds or thousands of articles, each needing a keep, refresh, consolidate, or cut decision.
- Something is broken and Search Console cannot say why. A section dropped out of the index, a crawled, currently not indexed backlog keeps growing, or a template is leaking duplicate URLs.
- The site is big, built on JavaScript, or mid-migration. At that point, sampling pages by hand stops working. My guide to redesigning a website without losing SEO covers the redirect checks.
The free stack that covers the rest is in my list of free SEO audit tools.
Screaming Frog pricing in 2026: how much does a license cost?
Screaming Frog pricing is $279 per license per year in the US (£199 in the UK, €245 in Europe), and the free version crawls up to 500 URLs. The Screaming Frog cost drops with volume once a team buys five or more licenses at a time.
| Licenses bought at once | USD per license per year | GBP | EUR |
|---|---|---|---|
| 1 to 4 | $279 | £199 | €245 |
| 5 to 9 | $265 | £189 | €235 |
| 10 to 19 | $249 | £179 | €219 |
| 20 or more | $235 | £169 | €209 |
| Free version | $0, capped at 500 URLs per crawl | £0 | €0 |
The Screaming Frog license terms are short. Each Screaming Frog license lasts one year and has to be renewed. Licenses are per user, so two people need two licenses. A five-person team pays $1,325 a year at the Screaming Frog price for that tier, and a ten-person team pays $2,490.
The paid crawl limit is listed as unlimited, with a footnote: the real ceiling depends on your computer’s memory and storage. On a site with hundreds of thousands of URLs, your machine runs out before the license does.
For a sense of scale, a full year of one license costs about the same as two months of the Semrush SEO plan at $139 a month, or a little over two months of Ahrefs Lite at $129. My Semrush vs Ahrefs comparison has the full suite prices.
Is Screaming Frog free? Only up to 500 URLs
Screaming Frog is free for crawls of up to 500 URLs, and to get Screaming Frog for free you download the SEO Spider and run it with no license key. The Screaming Frog free version is fine for a quick look at a tiny site. For real client work it is close to useless, because the 500-URL cap ends most crawls early and the free tier cuts the features I use most.
Here is what the free version keeps and what it cuts, per the feature table on the pricing page:
| Free version includes | Paid license only |
|---|---|
| Broken links, errors, and redirects | Crawl configuration and saved crawls |
| Page titles and meta data | JavaScript rendering |
| Meta robots and directives | Search Console, GA4, and PageSpeed Insights connections |
| hreflang and exact duplicates | Near duplicates and semantic similarity |
| XML sitemap generation | Custom search, custom extraction, and structured data validation |
| Site visualisations | AI integration (OpenAI, Gemini, Anthropic, and Ollama) and the MCP server |
| A 500-URL crawl limit | Scheduling, crawl comparison, command line, and support |
List mode does work on the free version, within the same 500-URL cap, which makes it handy for checking a short list of URLs or a small XML sitemap. Everything that connects the crawl to your own data sits behind the paid license, including the Search Console, GA4, and PageSpeed Insights connections.
How to use Screaming Frog: how I set up a crawl on a B2B SaaS site
To use Screaming Frog on a B2B SaaS site, pick the job, turn on JavaScript rendering, connect Search Console and GA4, confirm database storage, crawl the section under review, then export and decide.
- Decide the job first. An initial technical audit, a content audit, and a deep technical investigation need different settings and different exports.
- Turn on JavaScript rendering. Under Configuration, Spider, Rendering, switch to JavaScript. A lot of SaaS marketing sites build navigation, tabs, and even body copy with JavaScript, and a text-only crawl misses it. The rendered crawl also shows what AI search cannot see: Vercel’s 2024 analysis with MERJ found that “none of the major AI crawlers currently render JavaScript,” so copy that exists only after rendering is invisible to the crawlers behind ChatGPT and Claude.
- Connect the Google Search Console and GA4 APIs. Under Configuration, API Access, connect both. Every crawled URL then arrives with its Search Console clicks, impressions, CTR, and position, plus GA4 sessions and engagement. This is the step that turns a crawl into a content audit.
- Confirm database storage before a big crawl. Database storage is the default, and the Screaming Frog FAQ says crawls in that mode auto-save, so losing power does not lose the crawl.
- Crawl the section you are auditing. For a content audit I crawl a specific section, such as the blog or the resources hub, so the export holds only the pages under review. When I already have the exact URLs, list mode takes them directly.
- Export, then decide. The internal, response code, and API tabs export to a spreadsheet. From there it is sorting, joining, and judgment, and that part is still the work.
The full audit sequence those exports feed is in my SEO audit checklist.
Which Screaming Frog features are worth paying for?
Three Screaming Frog features do most of the work on my accounts: the Search Console and GA4 connection for content audits, the Gemini integration for alt text, and the separate Log File Analyser for AI crawlers.
Search Console and GA4 data for content audits
My favorite Screaming Frog setup is the Search Console and GA4 connection combined with a section crawl. You see the historical traffic behind every URL in one row: its clicks, impressions, and sessions next to its title, word count, status, and internal links. For a content audit, that row is the whole decision.
Those per-URL inputs are the same ones a content-audit scoring model runs on. On a 929-page programmatic audit for a creator-tools account, Search Console clicks carried 30% of each page’s score and analytics sessions 25%, and the model sorted the section into keep, improve, consolidate, and cut. The method is in my guide to an SEO content audit at scale. Without traffic attached, every page in a crawl looks equally important. With it, the pages to cut become obvious fast.
Gemini integration for alt text at scale
Screaming Frog’s AI integration connects the crawl to OpenAI, Gemini, Anthropic, or Ollama through your own API key, then runs a prompt against each page or image. I use it with Gemini to write image alt text at scale. Screaming Frog’s AI prompts tutorial shows how to limit the prompt to images flagged for missing alt text, so you only pay for the images that need it.
The Gemini alt text still needs a review pass. The model sees the image and can miss the context of the page around it, so a person checks the alt text before it ships.
Screaming Frog Log File Analyser for AI crawlers
The Screaming Frog Log File Analyser is a separate app that reads your server logs and shows which bots requested which URLs, and how often. On an employee-experience SaaS account, I used it to see which articles and which PDFs ChatGPT and other AI crawlers hit most.
That view answers a question no rank tracker can: which of your assets AI systems are actually reading. The most-requested articles and PDFs are the ones to keep current, and the list is a starting point for deciding what to refresh first.
OpenAI documents its crawlers by job: GPTBot collects training data and OAI-SearchBot fetches pages for ChatGPT search, and a site that blocks OAI-SearchBot “will not be shown in ChatGPT search answers.” Separating those user agents in the logs tells you whether ChatGPT is reading a page to train on it or to answer with it. The Log File Analyser is free for 1,000 log lines and one project, and $139 a year after that. My list of LLM SEO tools covers how it fits next to the other AI-crawler checks.
Screaming Frog MCP: useful for crawl questions, still a work in progress
Screaming Frog shipped its own official MCP server in SEO Spider version 24, which lets an assistant such as Claude control the crawler and query the crawl data in plain language. Version 25 added MCP debugging tools, full list mode support over MCP, and a JSON config an assistant can edit. The MCP needs a paid license.
I have set up the Screaming Frog MCP for technical audits, and I find it useful for investigating crawl data: asking follow-up questions of a crawl without building another pivot table. A full audit workflow on top of it is still a work in progress for me, and nothing is perfect yet. My comparison of the best AI for technical SEO covers the MCP setup, the OpenAI and Gemini page checks, and where each one fits in an audit. The rest of the tools that plug into Claude are in my AI SEO tools stack.
What are the downsides of Screaming Frog?
The downsides of Screaming Frog fall in four places: the learning curve, the desktop app, per-user licensing, and a crawl that leaves priorities to you.
- The learning curve and the interface. Dozens of tabs, hundreds of filters, and configuration menus nested inside configuration menus. It comes with time. Your first few crawls will feel like a cockpit.
- Screaming Frog runs on your computer. The largest site I have crawled had more than 900,000 URLs. My computer shut down partway through, and I lost the whole crawl. A desktop crawler is only as strong as the machine under it. Database storage, the default mode, auto-saves crawls and is the one Screaming Frog recommends for crawling at scale on an SSD, so check it is on before anything that size.
- Licenses are per user, per year. A team that shares crawls still pays for every person who runs one.
- Screaming Frog reports facts and leaves the priorities to you. A crawl will flag 3,000 missing meta descriptions on pages nobody visits next to one noindex tag on a pricing page. The crawler gives both the same weight. Google’s indexing verdict also lives in Search Console, though Screaming Frog can pull URL Inspection data for up to 2,000 URLs per property per day through the same API connection.
Is Screaming Frog better than Semrush or Ahrefs for site audits?
For depth, Screaming Frog is better than the Semrush and Ahrefs site audits by a wide margin. It is like being inside the site, where the Semrush and Ahrefs audits look at it from the outside. You choose exactly what gets crawled, how it renders, what gets extracted, and which of your own data gets joined to it. The suite audits give you a fixed checklist and a health score.
| Screaming Frog SEO Spider | Semrush Site Audit | Ahrefs Site Audit | |
|---|---|---|---|
| Where it runs | Your computer | The cloud | The cloud |
| Depth and control | Full configuration, custom extraction, JavaScript rendering | Fixed checks with some settings | Fixed checks with some settings |
| Your own data joined in | Search Console, GA4, PageSpeed Insights | Inside the Semrush project | Inside the Ahrefs project |
| Best for | Initial audits, content audits, deep investigations | Ongoing monitoring after releases | Teams already working in Ahrefs |
| Price | $279 per user per year | Part of a Semrush plan | Part of an Ahrefs plan, with a free tier for verified sites |
On Screaming Frog vs Ahrefs specifically, they do different jobs. Ahrefs owns keyword and backlink data, which a crawler of your own site cannot see, so most teams that run technical work need both. For ongoing monitoring between deep audits, a suite audit such as Semrush Site Audit keeps a history of new, fixed, and returning issues after each release.
What are the best Screaming Frog alternatives?
The best Screaming Frog alternatives fall into three groups (other crawlers, suite site audits, and free tools), and I have not found one that replaces Screaming Frog for deep work. The checks I would run on any of them in a trial are in my guide on how to choose a site audit tool.
- Other crawlers. Sitebulb is the closest alternative, a crawler with desktop and cloud versions that puts more weight on prioritized, explained findings. Lumar and Botify are cloud crawlers built for enterprise sites and teams, priced through sales.
- Suite site audits. Semrush and Ahrefs, covered in the table above, for monitoring inside a tool you already pay for. My verdicts on both suites are in the Semrush review and the Ahrefs review.
- Free tools. Search Console, Ahrefs Free, and Bing Webmaster Tools cover a small site’s basics at no cost.
Screaming Frog vs Sitebulb
Screaming Frog vs Sitebulb comes down to raw control on one side and guided findings on the other. Sitebulb is known for explaining and ranking what it finds, which suits a team that wants the crawler to suggest priorities. Screaming Frog gives you more configuration and more raw data to work with. I have not run Sitebulb or Lumar on a client account, so I will leave the head-to-head to people who have. For an audit that has to go deep, nothing I have used replaces Screaming Frog.
Is Screaming Frog worth it?
Screaming Frog is worth it for anyone who runs initial technical audits, large content audits, or deep technical investigations, which covers most in-house SEO leads, consultants, and agencies. The license is $279 a year. It is not worth it yet for an owner of a small, clean site, who will get more from Search Console and a habit of checking meta data and broken links.
If you would rather hand the crawl, the data joins, and the prioritization to someone who runs them every week, that is what my SEO and GEO audit for B2B SaaS companies covers. For the wider category, every tool I use is in the SEO tools hub, and the technical SEO guide covers what a crawl should check.
Screaming Frog FAQ
Is Screaming Frog an SEO tool?
Screaming Frog SEO Spider is an SEO tool, specifically a technical SEO crawler that audits a website’s pages, links, and directives. Screaming Frog the company is a UK search marketing agency, and it also makes the Log File Analyser.
What is an SEO crawler?
An SEO crawler is software that visits every page on a website by following its links, the way Googlebot does, and records what it finds on each URL: status codes, titles, headings, canonicals, directives, and links. SEOs use crawlers to find technical problems at the scale of a whole site.
What is the latest version of Screaming Frog?
The latest version of Screaming Frog SEO Spider is version 25, released November 3, 2026, with a 25.1 bug-fix release on November 4. Version 25 added JSON config files, MCP debugging tools, custom dashboards, configurable issues, and an auto-throttle that slows the crawl when a server returns 429 or 503 errors.
How do I install Screaming Frog?
Download the SEO Spider from Screaming Frog’s website and install it like any desktop app. It runs on 64-bit Windows 10 and 11, macOS 11 or later, and Linux through Ubuntu and Fedora packages. Enter a license key in the app to lift the 500-URL cap.
Why is it called Screaming Frog?
Screaming Frog is named after a frog that stood up for itself after being cornered by two cats in founder Dan Sharp’s back garden, per the company’s own story.
How much does Screaming Frog cost for a team?
A team pays $279 per user per year for one to four licenses, $265 each for five to nine, $249 each for 10 to 19, and $235 each for 20 or more. Every person who runs crawls needs a license.
Does Screaming Frog work on JavaScript sites?
Screaming Frog crawls JavaScript sites with JavaScript rendering turned on, which requires a paid license. Rendering is slower than a text-only crawl, so on a large site, test it on one section first.