OnCrawl is a technical SEO crawler and log analyzer that offers deep diagnostic capability for enterprise and agency work in Canada, though pricing in EUR and limited local support create friction points for Canadian practitioners evaluating it against North American alternatives.
OnCrawl performs three core functions that overlap but remain distinct from standard crawlers. First, it crawls your site like Googlebot, mapping structure, status codes, directives, and page-level signals. Second, it ingests and parses server logs to show what Google actually crawled versus what you intended, surfacing crawl budget waste and orphaned pages. Third, it layers behavioral data from Google Analytics or Adobe Analytics onto crawl results, letting you see which technically sound pages actually drive traffic and which high-traffic pages have technical flaws. The log analysis component is where OnCrawl differentiates itself most clearly. You upload raw access logs or connect via API, and the platform segments bot traffic by user agent, maps it to your site architecture, and highlights discrepancies. A bilingual site serving Ontario and Quebec might discover Googlebot heavily crawling outdated English parameter URLs while ignoring newer French category pages, or that Bingbot consumes disproportionate server resources on low-value facets. The rendering comparison feature runs a standard crawl and a JavaScript-rendered crawl in parallel, then diffs the results to show content visible only after JS execution, critical for React or Vue-based Canadian SaaS sites and large e-commerce platforms.
OnCrawl pricing is tiered by monthly page crawl limit and log line volume, quoted exclusively in EUR with payment processed through European billing. The entry tier typically covers up to one million URLs crawled per month and a modest log allocation, suitable for mid-sized agency clients or single large sites. Higher tiers raise URL limits to five million, ten million, or custom enterprise volumes, with log analysis capacity scaling accordingly. For Canadian agencies invoicing clients in CAD, the EUR pricing introduces exchange-rate uncertainty and makes month-to-month cost predictability harder. A subscription that costs €299/month fluctuates between roughly CAD 440 and CAD 470 depending on the EUR-CAD rate, and credit card foreign transaction fees add another layer. Annual prepayment in EUR can lock the rate and sometimes yields a discount, but requires upfront capital and denominated budgeting. There is no official Canadian reseller offering CAD invoicing or local payment rails, so all transactions route through the French parent company. This contrasts with tools like Ahrefs or Semrush, which offer CAD pricing tiers and Canadian billing addresses. For agencies working with government or institutional clients in Ottawa or university contracts that require CAD-denominated quotes and GST/HST handling, the EUR-only structure creates administrative friction and occasionally disqualifies OnCrawl from procurement processes.
OnCrawl's segmented crawling approach lets you isolate specific subdirectories, protocols, or URL patterns and run targeted audits without burning your monthly page quota on the entire domain. A Toronto e-commerce site might crawl only the product catalog and checkout flow at high frequency while sampling blog archives less often. The JavaScript rendering mode uses headless Chrome to execute client-side frameworks, then compares the raw HTML response to the fully rendered DOM. The diff highlights elements injected by JavaScript—product schema, review widgets, lazy-loaded images, dynamically inserted internal links—that Googlebot may or may not see depending on render budget and timing. For Canadian SaaS companies using Next.js or Nuxt with partial server-side rendering, OnCrawl surfaces which pages rely on client hydration for critical SEO content and which successfully deliver that content in the initial HTML. You can filter the crawl results by render status to find pages that return 200 in raw crawl but 404 post-render, or pages where canonical tags appear only after JavaScript execution. The platform also tracks redirect chains separately for raw versus rendered paths, catching cases where a JS router issues a client-side redirect that search bots may not follow.
The log analyzer requires you to upload Apache, Nginx, or IIS logs in standard combined or custom formats, or connect via SFTP or S3 bucket for automated ingestion. OnCrawl parses user agent strings to separate Googlebot, Googlebot-Mobile, Bingbot, and other crawlers, then maps each request to your site's URL structure and crawl data. The resulting dashboards show crawl frequency by section, status code distribution from the bot perspective, and orphaned URLs that bots discovered but your internal linking never referenced. A common finding for Canadian agencies is that bots waste significant crawl budget on parameter-heavy filter URLs or outdated paginated archives, while strategic landing pages in newer site sections receive minimal bot attention. The platform calculates active pages—those crawled by Google in the log window and found during the site crawl—and highlights inactive pages that exist in your sitemap but haven't seen a bot visit in weeks. You can overlay traffic data to identify high-value pages receiving infrequent crawls and low-value pages consuming disproportionate bot requests. For large Canadian retailers or classifieds sites generating millions of URLs through facets and regional variants, this visibility helps prioritize noindex decisions, robots.txt blocks, and internal link equity redistribution.
OnCrawl connects to Google Analytics via API to pull session, pageview, and goal completion metrics for each crawled URL, then joins that data to technical signals in a unified dataset. You can segment crawl issues by traffic tier, finding critical errors on high-traffic pages versus low-impact orphans, or identify technically perfect pages that receive zero organic visits and may signal content-market mismatch. The Google Data Studio connector pushes OnCrawl dimensions and metrics into custom dashboards, letting you blend crawl health, log analysis, and rank tracking in one view. A Vancouver agency might build a client-facing Data Studio report showing crawl error trends, bot visit frequency by category, and orphaned page count alongside Search Console impressions and GA conversions, all auto-refreshing as OnCrawl runs scheduled crawls. The API also supports custom exports to BigQuery or internal BI tools, useful for agencies managing dozens of client sites and aggregating technical health scores. Setup requires OAuth authentication, GA property access, and careful URL normalization to ensure OnCrawl's crawled URLs match GA's pageview paths, especially for sites using hash routing or heavy parameter rewriting.
Canadian agencies typically compare OnCrawl to three alternatives: Screaming Frog Spider plus standalone log tools, Botify, and Sitebulb. Screaming Frog offers one-time license purchase in CAD and runs locally, giving unlimited crawls without monthly page caps, but lacks native log analysis and requires separate tools like Splunk or custom scripts to parse server logs. Botify provides similar log-plus-crawl functionality at enterprise scale with North American sales support and CAD quoting, but starts at significantly higher annual minimums than OnCrawl and targets larger in-house teams. Sitebulb delivers richer visualization and automated audits in a desktop app with CAD pricing, but handles logs only through third-party export and lacks the GA overlay. OnCrawl sits in the middle: more integrated than Screaming Frog, more accessible than Botify, but with less polished UX than Sitebulb and the EUR billing friction. For agencies in Ottawa, Toronto, or Montreal managing 10-30 mid-market clients, OnCrawl makes sense if log analysis and JS rendering are frequent diagnostic needs and the team has technical chops to configure log ingestion. Solo consultants or smaller shops often find Screaming Frog plus manual log sampling more cost-effective, while enterprise teams with million-URL sites and developer resources lean toward Botify or custom tooling.
Getting OnCrawl operational requires server log access, which varies by hosting environment common in Canada. Sites on managed WordPress hosts like WP Engine or Kinsta often lack direct log access or provide only recent excerpts, forcing you to enable logging via plugin or request extended log retention from support. Canadian government and institutional sites on legacy IIS or locked-down shared hosts may face compliance or access barriers that delay log ingestion. Cloud-hosted sites on AWS, Google Cloud, or Azure require configuring log export to S3 or Cloud Storage buckets, then granting OnCrawl read permissions via IAM roles, a process straightforward for technical teams but daunting for marketing-only groups. OnCrawl recommends uploading at least 30 days of logs for meaningful crawl budget analysis, which can mean multi-gigabyte files for high-traffic Canadian e-commerce or media sites. Bandwidth and upload time become considerations, especially for agencies working remotely from rural or regional offices. The platform supports gzip-compressed logs to reduce transfer size. Crawl configuration includes user-agent spoofing, custom headers, authentication for staging environments, and rate limiting to avoid overwhelming origin servers, all essential for Canadian SaaS platforms with protective WAF rules or rate-limiting CDN configs.
OnCrawl quotes all pricing in EUR and processes payments through European billing infrastructure. There is no CAD pricing tier or Canadian payment option, so agencies must handle EUR-CAD exchange rate fluctuation and foreign transaction fees. For Canadian agencies requiring CAD-denominated vendor invoices for accounting or client pass-through, this creates administrative friction compared to tools with North American billing entities.
OnCrawl crawls and analyzes bilingual sites like any multi-language setup, respecting hreflang tags and subdirectory or subdomain structures. The log analysis can segment bot crawl activity by language path, showing whether Googlebot allocates crawl budget proportionally between English and French sections. You can configure separate crawl projects for each language or crawl the entire domain and filter results by URL pattern to isolate issues in Quebec-targeted French pages versus ROC English pages.
OnCrawl delivers the most value for sites exceeding 50,000 URLs with active faceted navigation, heavy JavaScript rendering, or complex URL parameter usage where log analysis and render comparison provide diagnostic depth that simpler crawlers miss. Agencies managing a portfolio of such clients, or in-house teams at large Canadian retailers, publishers, or SaaS companies, typically justify the cost. Smaller sites under 10,000 pages or agencies with mostly SMB clients often find better ROI with Screaming Frog or Sitebulb.
OnCrawl integrates with Google Analytics, Adobe Analytics, and server logs from any standard web server format, so it works with typical Canadian hosting on AWS, Google Cloud, Azure, cPanel, or Shopify Plus environments that expose logs. The main requirement is API access to analytics properties and log file availability, which some managed WordPress or restrictive government hosting setups limit. Data Studio and BigQuery connectors support the BI workflows common in larger Canadian agencies and enterprise teams.
Screaming Frog offers unlimited local crawls via one-time CAD license purchase and faster setup, but lacks integrated log analysis and behavioral data overlay. OnCrawl provides log parsing, JavaScript rendering comparison, and GA integration in one platform with cloud-based scheduled crawls, but costs more monthly and bills in EUR. Agencies doing frequent log diagnostics or managing client sites with complex rendering choose OnCrawl; those needing ad-hoc deep crawls with manual log review prefer Screaming Frog's lower cost and local control.
OnCrawl operates primarily from France with support and sales handled by European teams in CET timezone. There is no dedicated Canadian office or regionally localized support hours, so agencies in Toronto, Vancouver, or Montreal coordinate via email or scheduled calls that may fall outside standard North American business hours. Documentation and platform interface are in English, but real-time support responsiveness during Canadian work hours is less immediate than North American SaaS vendors provide.