A Hands-On Walkthrough of a Screaming Frog Technical Audit

Screaming Frog is one of those tools that intimidates people on first use. You launch a crawl, the rows start filling up, and within a few minutes you're looking at tens of thousands of URLs with column headers you've never seen before. It's easy to get lost.

The good news is that you don't need to understand every column to get real value out of it. The key is knowing which specific questions you're trying to answer before you start, and then finding those answers rather than trying to interpret everything at once.

Setting up the Crawl

Before running a crawl on a large site, configure a few settings to make the output more useful.

In the Configuration menu, check that you're crawling with JavaScript rendering enabled if your site relies on JavaScript to load content (most modern sites do to some extent). Without this, Screaming Frog will miss content that only appears after scripts execute.

Connect your Google Analytics and Search Console accounts in Configuration > API Access. This pulls in traffic and ranking data so you can see which pages are actually visited, not just which ones exist. This is one of the most useful features in Screaming Frog that people consistently overlook.

Set a crawl speed appropriate to your server. The default is aggressive enough to cause problems on smaller hosting setups during peak traffic times. Dial it back if you're auditing a live site.

What to Look for: Redirects First

Start with redirects. In the left panel, select "Response Codes" and filter for 3xx responses.

What you're looking for:

• Redirect chains — a URL that redirects to a URL that redirects to another URL. Every hop in a chain costs crawl budget and dilutes link equity. Any chain longer than one hop should be fixed to redirect directly to the final destination.
• Redirect loops — a URL that redirects back to itself or creates an infinite loop. These show up as crawl errors.
• Redirects from pages with significant inbound links — check whether the destination page is the right one, and whether any link equity is being lost.

The internal link analysis can show you which internal links are pointing to redirected URLs. Updating those links to point directly to the final destination is a quick win.

Duplicate Content and Canonical Issues

In the Content tab, look for duplicate page titles, duplicate H1 tags, and pages with missing or duplicated meta descriptions. These are signals that the site may have content duplication problems.

Go deeper by looking at the Canonicals section. Screaming Frog shows you which canonical tags are present, whether they're self-referencing (a page pointing to itself, which is fine and recommended), and whether any pages have canonical tags pointing to different URLs.

Watch for:

• Pages that have no canonical tag at all
• Pages where the canonical points to a URL that itself has a different canonical (a canonical chain, similar to a redirect chain)
• Pages that have a canonical pointing to their own URL but also have indexation blocked in robots.txt — a contradictory setup

Title Tags and Meta Descriptions at Scale

The overview report for title tags is one of the most useful quick checks in Screaming Frog. It shows you:

• Pages with missing title tags (these should be zero)
• Pages with titles that are too long and will be truncated in search results (above roughly 60 characters)
• Pages with titles that are too short and may not be descriptive enough
• Duplicate title tags

Same for meta descriptions. Google doesn't guarantee it will use your meta description, but having relevant, unique descriptions for every important page is worth doing.

The bulk export for these is straightforward. Export the list, sort by issue type, and fix the worst offenders first — starting with missing titles (highest priority), then duplicates, then length issues.

The Page Depth Report

Screaming Frog shows you how many clicks each page is from the start URL you chose for the crawl. Pages at crawl depth 6 or deeper are worth examining.

If important pages are buried deep in the site architecture — landing pages, key product pages, important guides — they're harder for search engines to find and give less weight to. The fix is usually to add links from shallower pages: from the homepage, from high-traffic hub pages, or from relevant blog content.

The depth report becomes much more useful when combined with the Search Console integration. A page with significant search traffic that's sitting at crawl depth 7 is a structural problem worth prioritizing.

Broken Internal and External Links

The Response Codes filter for 4xx errors shows you broken links — URLs that your site links to that return a 404 or similar error.

Broken internal links are a user experience problem and a mild crawling problem. Fix them by either updating the link to point to the correct URL, or removing the link if the destination no longer exists.

Broken external links are worth fixing too, though they're lower priority. A link that points to a page that no longer exists doesn't provide the reader value it once did.

Images: the Often-missed Technical Problem

The Images tab in Screaming Frog shows several useful things: images without alt text, images with very long filenames, images that are too large, and images that return errors.

Alt text matters for accessibility and provides context to search engines about what an image shows. Every significant image on an important page should have a descriptive, specific alt tag — not "image1.jpg", not keyword-stuffed text, but a brief description of what the image actually depicts.

Large images are often the single biggest contributor to poor LCP scores. If you find images over 500KB that could be served at the same visual quality in WebP format at a quarter the file size, fixing those will have a more immediate performance impact than almost any other change.

Hreflang for Multilingual Sites

If your site serves content in multiple languages or for multiple regions, check the hreflang implementation. Screaming Frog has a dedicated Hreflang tab that shows you the hreflang tags present on each page and flags common errors like missing return tags, incorrect language codes, and pages that specify a regional URL that doesn't exist.

Hreflang errors are surprisingly common and can cause significant problems: search engines may serve the wrong language version to users, or may have difficulty understanding which version to rank in which market.

After the Crawl: Making the Output Useful

The risk with Screaming Frog is ending up with a huge list of technical issues and no clear sense of what to fix first.

Prioritize by impact:

1. Crawl errors and redirect loops (stop the bleeding)
2. Missing titles and broken internal links (basic hygiene)
3. Redirect chains pointing from high-traffic pages (link equity)
4. Depth problems affecting important pages (discoverability)
5. Image optimization for top-traffic pages (performance)
6. Duplicate content and canonical issues (search clarity)

Not everything the tool flags needs to be fixed. A 404 on a page nobody links to and nobody visits is not worth the same effort as a 404 that sits at the end of a redirect from your homepage. Use the Analytics integration to weight issues by the traffic involved.