9 Easy-to-Miss Crawl Reports in Screaming Frog and DeepCrawl That Pack Serious SEO Punch
Technical SEO audits often focus on the obvious issues--broken links, missing meta tags, duplicate content. But the difference between a good audit and a great one lies in the reports that most practitioners overlook.
Introduction
Screaming Frog and DeepCrawl contain numerous diagnostic reports that can uncover hidden problems, opportunities for optimization, and patterns that directly impact search visibility. This guide explores nine frequently-missed crawl reports that deliver disproportionate SEO value.
The reports covered here fall into four categories: crawl behavior analysis, indexation management, content quality signals, and rendering verification. Each section explains why the report matters, what specific findings to look for, and how to translate discoveries into actionable fixes. Most of these reports require minimal configuration but provide insights that most audits simply don't capture.
By mastering these diagnostic capabilities, you can move beyond surface-level audits to uncover technical debt, indexation issues, and content accessibility problems that silently erode search performance over time.
The 9 High-Impact Reports
These nine reports represent the diagnostic capabilities that separate thorough technical audits from superficial ones. While basic audits capture titles, meta descriptions, and broken links, these reports reveal deeper patterns affecting crawl efficiency, indexation accuracy, and ranking potential. Each report addresses a specific dimension of technical SEO health that standard checklists simply don't measure.
Report Categories
- Crawl Behavior Analysis: Understanding how search engines interact with your site through redirect chains, crawl budget allocation, and rendering patterns
- Indexation Management: Ensuring correct URL targeting through canonicals, hreflang, and parameter handling
- Content Quality Signals: Verifying structured data, image optimization, and content accessibility
- Rendering Verification: Confirming Google can see what users see through JavaScript rendering analysis
Each report category addresses problems that compound over time. Redirect chains accumulate during migrations. Structured data gaps widen as content scales. Hreflang errors multiply with international expansion. These reports provide the visibility needed to address issues before they become ranking obstacles.
1. Custom Extraction Report
What It Is and Why It Matters
The Custom Extraction feature in Screaming Frog allows you to define XPath or CSS selector queries to extract specific data elements from pages beyond the standard crawl output. While basic audits capture titles, meta descriptions, and headers, custom extraction opens the door to mining any structured data present in your HTML or JavaScript-rendered content.
This report becomes essential when auditing sites that rely heavily on structured data, testing for specific content patterns, or validating that key elements exist across page templates. For example, you might extract product prices from e-commerce pages, review ratings from template components, or event dates from calendar listings. The extracted data can then be filtered, sorted, and analyzed alongside other crawl metrics.
Many SEO issues remain hidden because standard reports don't surface the specific content elements that matter for your site type. A publisher needs to verify that article timestamps appear correctly. An e-commerce retailer needs to confirm that pricing and availability data renders properly. A service business needs to check that contact information appears consistently across location pages. Custom extraction makes these targeted audits possible.
Configuration and Use Cases
Setting up a custom extraction requires understanding either XPath or CSS selector syntax, but the investment pays dividends across multiple audit scenarios. For structured data verification, you can extract JSON-LD script blocks and validate that specific schema types exist where expected. This is particularly valuable for e-commerce sites that need Product markup, Recipe sites that need Recipe schema, or local businesses that need LocalBusiness markup.
The extraction feature also supports content auditing at scale. If you've migrated content and need to verify that specific paragraphs, disclaimers, or legal text survived the transition, custom extraction can pull these elements and generate a compliance report. Similarly, if you're auditing for content freshness, you can extract publication dates and compare them against your content lifecycle policy.
Practical Application
When auditing a large e-commerce site, custom extraction can verify that product pages contain both price and availability information. The extraction query //span[@class='price'] combined with //span[@class='availability'] reveals pages where either element is missing. Cross-referencing these findings with your XML sitemap shows which problematic pages are actually being submitted to search engines--these are high-priority fixes because Google is trying to index content that doesn't meet quality standards.
For lead generation sites, extraction of form elements confirms that contact forms exist and have proper action URLs. Pages missing forms may be technical orphans that look complete to visitors but fail to generate conversions. The crawl reveals these gaps before they impact business metrics.
Our technical SEO services often use custom extraction to audit large-scale sites efficiently, identifying specific element gaps across thousands of pages in a single crawl.
2. Structured Data Report
Understanding Schema Validation
The Structured Data report in Screaming Frog goes beyond simply detecting the presence of schema markup. It parses JSON-LD, Microdata, and RDFa to validate that the markup follows schema.org specifications and surfaces warnings about implementation issues. Google increasingly relies on structured data to understand content context and generate rich results, making this report essential for sites that depend on enhanced search appearance.
Common issues surfaced by this report include missing required properties for specific schema types, deprecated markup usage, type mismatches (such as providing a string where a URL is expected), and syntax errors that prevent parsing entirely. The report also identifies schema that appears on pages but doesn't match the page's apparent purpose--Product markup on category pages, for instance, or LocalBusiness markup on blog posts.
Structured data issues often escape notice because they don't break page functionality. The page looks correct to visitors and may render properly in search results for a time. But Google's validation is strict, and invalid markup can result in rich result eligibility being revoked without explicit notification. Regular structured data audits catch these regressions before they impact search performance.
Schema Type Coverage Analysis
The Structured Data report provides a breakdown of which schema types appear across your site and on how many pages. This coverage analysis reveals strategic opportunities. If your site contains hundreds of product pages but only a handful have Product schema, you're missing significant rich result potential. Similarly, if your editorial content doesn't use Article or BlogPosting markup, you may be forfeiting enhanced listing features in search results.
Beyond coverage percentages, the report identifies concentration patterns. Sometimes schema exists only on older content, indicating that implementation stopped at some point. Sometimes schema exists only on new content, suggesting that legacy pages were never retrofitted. Neither pattern is ideal--both represent missed opportunities that compound over time as more pages are published without markup.
Error Patterns and Fix Prioritization
Structured data errors fall into predictable categories, and the report helps you identify which patterns dominate your implementation. Missing required properties is the most common issue--for Product schema, this often means price or availability is omitted. For Organization schema, missing address or contact information appears frequently. For Event schema, missing start date or location causes validation failures.
The report should be used in conjunction with Google's Rich Results Test to validate that your markup actually qualifies for enhanced display. Sometimes markup passes Screaming Frog's validation but fails Google's more stringent requirements. This dual verification ensures you're not just technically correct but actually eligible for the rich results you're targeting.
Our content strategy services incorporate structured data audits as part of comprehensive content optimization, ensuring markup supports rather than hinders search visibility.
3. hreflang Report
International Targeting Validation
For sites serving multiple markets or languages, hreflang implementation is critical but frequently problematic. The hreflang report identifies pages that reference alternate versions without reciprocal links, pages with missing or invalid hreflang annotations, and cases where language/region targeting doesn't align with actual content. These issues can result in the wrong content appearing in search results for international users, diluting your global SEO efforts.
The report surfaces reciprocal linking errors where Page A points to Page B as its alternate but Page B doesn't return the reference. This asymmetric situation confuses search engines and may result in neither page being shown for the targeted audience. The fix requires coordinating hreflang implementation across all alternate versions, which the report helps you identify.
Invalid hreflang values--misspelled language codes, incorrect region designations, or syntax errors--also appear prominently. These annotations are ignored entirely by search engines, meaning the affected pages aren't included in international search results at all. The report lists specific pages and their invalid annotations, enabling targeted fixes.
Language and Region Matrix Analysis
Beyond individual errors, the hreflang report provides a matrix view of your international targeting. This visualization reveals gaps in your language coverage. If you target English speakers in the UK, US, Canada, and Australia but have no hreflang annotations for Irish or South African English, the report highlights this gap. Similarly, if you have content for Spanish speakers but no x-default annotation to capture untargeted visitors, the report surfaces this missing element.
The matrix also reveals over-targeting situations where you've created more language variants than necessary. Sometimes organizations create separate variants for minor regional differences that don't justify distinct content. These redundant variants split ranking signals and complicate site architecture without delivering meaningful user value. The report helps you consolidate or eliminate unnecessary variants.
For large international sites, the hreflang report becomes a governance tool. New page templates should include proper hreflang annotations from launch, not as a retrofit project. The report can be incorporated into QA processes to catch hreflang issues before they reach production.
4. Page Speed Report
Core Web Vitals Integration
The Page Speed report in Screaming Frog, enhanced by Core Web Vitals data integration, provides performance metrics for every crawled URL. While external tools like PageSpeed Insights and Lighthouse provide deeper analysis for individual pages, the crawl report offers comparative visibility across your entire site. This site-wide perspective reveals which templates and content types have performance problems, enabling prioritized optimization efforts.
The report displays Largest Contentful Paint (LCP), First Input Delay (FID), and Cumulative Layout Shift (CLS) values where available, along with traditional metrics like load time, render blocking resources, and JavaScript execution time. Pages are sortable by any metric, so you can quickly identify the worst performers or filter for pages that fail Core Web Vitals thresholds.
Performance issues compound--they affect user experience metrics that Google uses as ranking signals, and they impact engagement metrics that influence organic visibility. A page that loads slowly sees higher bounce rates, lower time on site, and fewer conversions. The crawl report quantifies these problems site-wide, making the case for performance investment.
Performance Correlation Analysis
When combined with other crawl data, the Page Speed report enables correlation analysis. Are your slowest pages also the ones with the most JavaScript errors? Do pages with many external requests show higher latency? Are specific content management system templates consistently underperforming? These patterns inform your optimization strategy by identifying root causes rather than symptoms.
The report also supports performance regression monitoring. After deploying new templates, adding tracking scripts, or modifying styling, you can run a before-and-after comparison to quantify performance impact. If new features slow page load significantly, you can make informed decisions about trade-offs or identify specific elements causing the regression.
For enterprise sites with many contributors, the Page Speed report serves as a quality gate. Performance budgets can be defined, and pages exceeding thresholds can be flagged for review before publication. This proactive approach prevents performance degradation from accumulating over time.
Our web development services integrate Core Web Vitals optimization into every project, ensuring performance is considered from the initial design phase rather than as an afterthought.
5. JavaScript Rendering Report
Client-Side Content Verification
As Google increasingly relies on JavaScript for content rendering, understanding what the search engine actually sees becomes essential. The JavaScript Rendering report shows the content and markup that Googlebot receives after executing JavaScript, compared against the raw HTML that tools can extract without rendering. Discrepancies between these views reveal content that may not be indexable.
Common issues include content loaded dynamically via JavaScript that search engines may not execute properly, navigation elements generated client-side that may not be crawled consistently, and schema markup injected through JavaScript that may be missed by search engines. The report surfaces these discrepancies so you can implement progressive enhancement or server-side rendering for critical content.
The report also identifies resources blocked to Googlebot that are required for rendering. If your JavaScript or CSS files are disallow in robots.txt, Google may not render pages fully, affecting how your content is indexed and how rich results are generated. The rendering report shows which resources are inaccessible to crawlers.
Hydration and Core Content Analysis
For Single-Page Applications and sites using JavaScript frameworks like React, Vue, or Angular, the rendering report reveals what's often called the "hydration gap"--the delay between initial HTML delivery and full JavaScript execution. During this gap, search engines see minimal content. If the gap is too long, important content may not be indexed.
The report helps you identify core content that appears late in the rendering process or doesn't appear in the rendered output at all. Product descriptions loaded via API calls, reviews fetched dynamically, or pricing information rendered client-side all may be invisible to search engines. The fixes typically involve server-side rendering, static generation, or ensuring critical content appears in the initial HTML response.
Our web development team specializes in JavaScript framework optimization, implementing server-side rendering and static generation solutions that ensure search engines can fully index your content.
6. Redirect Chain Report
Crawl Budget Preservation
Redirect chains--where URL A redirects to URL B which redirects to URL C--consume crawl budget without delivering value. Each redirect adds latency and uses up the limited resources that search engines allocate to crawling your site. The Redirect Chain report identifies these chains so you can flatten them to direct redirects where possible.
The report shows the full chain for affected URLs, making it easy to identify multi-hop redirects. Often, chains result from accumulated technical debt--URLs were redirected during a site migration, then those destination URLs were redirected again during a subsequent change, and so on. The report surfaces these accumulated redirects so you can audit and consolidate them.
Redirect chains also impact user experience. Each hop adds latency for visitors following old links or having bookmarks updated. Direct redirects are faster and preserve more referrer value. The report helps you prioritize flattening based on traffic to redirected URLs, focusing first on chains affecting high-value pages.
Legacy Redirect Cleanup
Over time, sites accumulate redirects that no longer serve a purpose. A URL redirected five years ago may now point to content that's since been removed entirely, with the redirect maintained "just in case." The Redirect Chain report reveals these zombie redirects that consume crawl budget without delivering any value.
Cleanup requires investigating each chain to understand its purpose. Some redirects protect legacy URLs that still receive traffic from old links or bookmarks--these should remain. Others point to content that's been superseded and could be consolidated. The report provides the data you need to make informed decisions about which redirects to maintain and which to remove.
For large sites with thousands of redirects, the report enables batch cleanup. You can export chains affecting high-traffic pages first, then work through lower-priority URLs systematically. The goal is a redirect structure that's lean, purposeful, and efficient.
When planning site migrations, our technical SEO consulting includes redirect mapping that prevents chain accumulation from the start, avoiding the technical debt that accumulates over years of redirects.
7. Canonicals Report
Self-Referencing and Cross-Domain Issues
The Canonicals report surfaces issues with canonical tag implementation that standard crawls often miss. Self-referencing canonicals are expected on most pages--each URL should point to itself as canonical unless there's a legitimate reason to point elsewhere. The report identifies pages missing self-referencing canonicals, which may indicate template errors or CMS configuration problems.
Cross-domain canonicals present a different challenge. Sometimes sites incorrectly point canonicals to different domains, often during testing or staging. These errors prevent the correct URL from being indexed entirely. The report shows cross-domain canonicals so you can identify and fix these potentially catastrophic errors.
The report also surfaces internal canonical chains where multiple URLs point to a common canonical that then points elsewhere. This chain pattern creates confusion about which URL should be indexed and can result in crawl budget being wasted on URLs that will never be indexed.
Parameter Handling and URL Variations
For sites with significant URL parameters (filtering, sorting, pagination, session tracking), the Canonicals report reveals whether parameter-handling is consistent. URLs with parameters should either have self-referencing canonicals or point to a clean canonical that represents the parameterized URL's intent. Inconsistent handling can result in parameter URLs being indexed alongside clean URLs, diluting link equity.
The report helps you audit parameter handling at scale. If some filtered views have self-referencing canonicals while others point to the base page, you have an inconsistent implementation that needs standardization. This consistency is essential for clean indexation and proper ranking signal consolidation.
Pagination presents particular challenges. Many sites use rel="next" and rel="prev" annotations or point paginated pages to the first page as canonical. The Canonicals report shows how your pagination is actually implemented, enabling verification that Google can properly understand multi-page content sequences.
Our e-commerce SEO services frequently use canonical auditing to resolve duplicate content issues that arise from filtered navigation, faceted search, and parameter-heavy URLs.
8. Image Report
Alt Text Coverage and Quality
The Image report extends beyond basic image metadata to analyze alt text presence, quality, and consistency. Sites that rely heavily on imagery--e-commerce, photography, design--need comprehensive alt text to ensure accessibility and image search visibility. The report shows coverage percentages and flags pages with missing or inadequate alt attributes.
Beyond presence, the report can assess alt text quality. Generic alt text like "image1.jpg" or "picture" provides no value. The report can filter for such patterns, enabling targeted improvement. You can also identify alt text that's keyword-stuffed, which may trigger spam signals, or alt text that's duplicated across many images, suggesting template-level issues.
Image optimization directly impacts both accessibility and image search performance. Google's image search drives significant traffic for many sites, and proper alt text is essential for visibility. The report makes image optimization systematic rather than ad-hoc.
Large Image and Performance Impact
The Image report also surfaces large images that may impact page performance. If high-resolution images are loading on pages where smaller versions would suffice, this impacts Core Web Vitals and user experience. The report shows image dimensions and file sizes, enabling identification of optimization opportunities.
Lazy loading implementation appears in this report as well. Images below the fold should be lazy-loaded to improve initial page load, but above-the-fold images should load immediately. The report helps verify that lazy loading is implemented correctly and consistently across templates.
Our conversion rate optimization services incorporate image optimization as part of holistic page performance improvement, ensuring visual assets support rather than hinder user experience and search visibility.
9. Outlink Analysis Report
Internal Linking Patterns
The Outlink Analysis report reveals how your site links internally, showing link counts, anchor text distribution, and destination patterns. This analysis helps identify orphaned content (pages with few or no internal links), over-linked pages that concentrate too much link equity, and anchor text patterns that may indicate optimization opportunities or risks.
Internal linking directly impacts how link equity flows through your site. Pages with many internal links receive more ranking signals from linked pages. The Outlink report surfaces pages that may be underlinked relative to their importance, as well as pages that are overlinked and may be diluting signals that could flow to other priorities.
Anchor text analysis reveals how your site talks about itself. Are your internal links using keyword-rich anchor text or generic "click here" text? Are branded anchors consistent or varied? These patterns influence how Google understands your site's topical focus and can be optimized to reinforce priority topics.
Link Equity Distribution Visualization
For large sites, the Outlink report helps visualize link equity distribution. Pages with extremely high link counts may be receiving more equity than they need, while important pages with low link counts may not be receiving enough. This visualization informs internal linking strategy and helps you build connections to priority content.
The report also identifies linking patterns that may indicate problems. If a key landing page has no internal links, it won't rank regardless of its content quality. If orphaned pages exist throughout your site, they may not be indexable at all. These structural issues are invisible without link analysis.
Our content strategy team uses internal linking audits to inform content planning, ensuring new content is connected to existing pages and that link equity flows toward priority conversion pages. Understanding how to leverage quality backlinks alongside strong internal linking creates a comprehensive link profile that supports your SEO goals.
Integrating Reports into Your Audit Workflow
Sequential Analysis Process
These nine reports work best when used sequentially as part of a comprehensive audit workflow. Start with the JavaScript Rendering report to understand what search engines actually see. Then move to the Canonicals and hreflang reports to verify indexation configuration. Next, analyze the Redirect Chain report to clean up crawl path inefficiencies. Finally, use the Structured Data, Image, and Page Speed reports to assess content quality and presentation.
Each report informs the next. Discovering significant rendering issues may prompt deeper investigation of JavaScript-specific optimizations. Finding extensive redirect chains may reveal migration debt that needs systematic cleanup. The reports are interconnected, and their combined insights provide a comprehensive view of technical SEO health.
Trend Monitoring and Baseline Establishment
These reports aren't just for one-time audits--they're valuable for ongoing monitoring. Establish baseline measurements during your initial audit, then re-run reports periodically to track progress. Are redirect chains decreasing over time? Is structured data coverage improving? Are Core Web Vitals thresholds being met more consistently?
Trend monitoring turns technical SEO from a periodic project into continuous optimization. When you can measure improvement, you can justify continued investment. When you can identify regression early, you can fix problems before they impact rankings. The reports provide the data for this ongoing practice.
Both Screaming Frog and DeepCrawl offer scheduling capabilities and APIs for integrating crawl data into existing workflows. This enables continuous monitoring rather than one-time audits. Set up monthly crawls and compare results against your baseline to maintain technical SEO health over time. For organizations using AI-powered SEO tools, these crawl reports provide the foundational data that AI systems analyze for optimization recommendations.
DeepCrawl-Specific Advantages
Enterprise-Scale Crawling
DeepCrawl (and platforms like Sitebulb Enterprise) offers advantages for large-scale audits that Screaming Frog's desktop-based approach can't match. DeepCrawl handles millions of URLs without the memory limitations of local crawling, enables distributed crawling across multiple servers, and provides APIs for integrating crawl data into your existing workflows.
The platform's reporting often includes additional dimensions not available in Screaming Frog, including historical comparison, team collaboration features, and custom dashboard creation. For organizations managing large sites or multiple properties, these enterprise features justify the investment beyond the free or lower-cost alternatives.
DeepCrawl's JavaScript rendering capabilities have historically been more robust than Screaming Frog's, making it the preferred choice for sites with heavy JavaScript dependencies. If your audit reveals significant rendering challenges, DeepCrawl may provide more accurate views of what search engines see.
Integration and Automation
DeepCrawl's API enables integration with other tools in your SEO stack. Crawl data can flow into data warehouses, BI tools, or custom dashboards. Scheduled crawls can trigger alerts when metrics exceed thresholds. This automation transforms technical SEO monitoring from manual project work into continuous observation.
The platform also supports team workflows, enabling multiple analysts to work from the same crawl data with role-based access controls. This collaboration capability is essential for large organizations where technical SEO work spans multiple teams or agencies. Custom permissions ensure analysts can access relevant data without compromising sensitive information.
For enterprise clients managing multiple properties, DeepCrawl provides centralized reporting across domains. This visibility enables consistent technical SEO standards across your entire digital presence, identifying patterns that span individual site audits.
Our enterprise SEO services leverage DeepCrawl's automation capabilities to maintain continuous monitoring for large-scale sites, ensuring technical issues are identified and addressed before they impact search performance.
Conclusion
The nine reports covered here represent high-value diagnostic outputs that most audits overlook. Custom extraction, structured data validation, hreflang verification, page speed analysis, JavaScript rendering verification, redirect chain tracking, canonical auditing, image optimization, and internal link analysis together provide a comprehensive view of technical SEO health that goes far beyond broken links and missing meta tags.
These reports require more expertise to configure and interpret than basic crawl outputs, but the insights they provide justify the investment. The problems they surface often have outsized impact on crawl efficiency, indexation accuracy, and ranking potential. Mastery of these reports separates thorough technical audits from superficial ones.
Incorporate these reports into your standard audit workflow. Establish baselines, track progress over time, and use the insights to prioritize optimization efforts. The reports are not one-time discoveries but ongoing monitoring tools that support continuous technical SEO improvement.
Technical SEO mastery comes from understanding these deeper diagnostic capabilities. The difference between good and great audits lies not in covering more checklist items, but in revealing hidden patterns that affect how search engines interact with your site. These nine reports provide that visibility.
Frequently Asked Questions
How often should I run these crawl reports?
For active sites, monthly monitoring is recommended. After major site changes or migrations, run comprehensive audits immediately. Establish baseline measurements and track trends over time.
What's the difference between Screaming Frog and DeepCrawl?
Screaming Frog offers a desktop-based solution ideal for smaller sites and ad-hoc audits. DeepCrawl provides enterprise-scale crawling with API integration and team collaboration features for larger organizations.
Can these reports be automated?
Yes. Both tools offer scheduling capabilities and APIs for integrating crawl data into your existing workflows. This enables continuous monitoring rather than one-time audits.
How do I prioritize issues found in these reports?
Prioritize issues affecting high-traffic pages first, then issues that impact crawl efficiency, and finally content quality issues. Use an impact vs. effort matrix to guide decisions.
Sources
- Search Engine Land - 9 easy-to-miss crawl reports - Industry-leading SEO publication covering nine specific crawl reports that are frequently overlooked
- Altitude Marketing - Advanced Screaming Frog Tactics - Comprehensive guide on advanced tactics including custom extraction, API integration, and configuration optimization
- Mavlers - SEO Experts' Top 9 Screaming Frog Features - Expert-curated list of essential Screaming Frog features that professionals rely on
- Screaming Frog Official User Guide - Official documentation for tool configuration and report options
Technical SEO Audit Checklist
A comprehensive checklist for conducting thorough technical SEO audits.
Learn moreSchema Markup Best Practices
Learn how to implement and validate structured data for rich results.
Learn moreCore Web Vitals Optimization Guide
Improve your page speed and user experience metrics for better rankings.
Learn more