Lumar (formerly Deepcrawl) is an enterprise technical SEO platform that Canadian agencies and in-house teams use for large-scale site audits, JavaScript rendering analysis, and continuous monitoring. This review covers its core capabilities, Canadian pricing context, and whether it fits typical SEO workflows north of the border.
Lumar is a cloud-based technical SEO platform designed for enterprise and agency workflows. Unlike desktop crawlers you run once and export, Lumar schedules recurring crawls, stores historical data, and flags delta changes between audits. This makes it valuable when you manage a portfolio of sites or a single large property that ships code weekly. The platform renders JavaScript using Chromium, so it captures what Google actually sees on client-side frameworks like React or Vue. You can segment crawls by subdomain, path, or custom rules, which matters for Canadian sites serving bilingual content under /en/ and /fr/ paths or managing regional subfolders. Lumar also ingests server log files to compare what Googlebot requested versus what your crawler found, surfacing orphaned pages or crawl-budget waste. The target user is a technical SEO who understands status codes, canonical chains, and hreflang logic and needs reproducible audits rather than one-time snapshots.
Lumar's crawl engine handles sites in the hundreds of thousands of URLs without choking, which separates it from tools that time out or require desktop RAM upgrades. You set crawl limits, user-agent strings, and rate limits to mimic Googlebot's behaviour or respect server capacity. The JavaScript rendering mode is critical for Canadian SaaS and e-commerce platforms built on Shopify, Next.js, or headless CMSs where product grids and navigation load client-side. Lumar runs a two-pass crawl: raw HTML first, then rendered DOM, so you can diff what's missing pre-render versus post-render. This exposes cases where internal links only appear after JS execution or where lazy-loaded content never gets indexed. You can also compare mobile versus desktop rendering and spot viewport-specific issues. The platform flags render timeouts and console errors, which helps diagnose why certain pages don't rank despite being crawlable in theory.
Lumar bills in USD on annual contracts, and pricing isn't public; you request a quote based on crawl volume and feature tier. Mid-market plans typically start around six to seven thousand USD annually, which translates to roughly eight to nine thousand CAD depending on exchange rates. Larger portfolios or higher crawl quotas push annual spend into five figures USD. For Canadian agencies, this means running currency conversion past finance and justifying the cost against billable hours saved or client retention from catching issues early. Lumar doesn't offer a monthly pay-as-you-go tier in the way some SaaS tools do; the expectation is annual commitment with a defined crawl quota. If you exceed your monthly URL limit, overages apply or you negotiate an upgrade. Compared to Sitebulb's one-time desktop license or Screaming Frog's modest annual fee, Lumar sits in a different budget category—it's a platform investment, not a point tool.
Lumar connects to Google Search Console, Google Analytics, and Adobe Analytics to overlay crawl data with performance metrics. You can see which crawled pages actually receive impressions, compare indexation status against what Lumar found, and identify coverage gaps. The log file analyzer ingests Apache, Nginx, or CDN logs so you can track Googlebot's real requests, compare them to your sitemap, and spot URL parameters or query strings that waste crawl budget. For agencies managing clients on bilingual Canadian sites, this matters when Googlebot crawls /fr/ pages less frequently or when regional CDN configs serve different response codes to different geographies. Lumar also offers API access on higher tiers, so you can push crawl results into reporting dashboards or trigger alerts in Slack when critical issues appear. The Looker Studio connector lets you build custom client reports without exporting CSVs manually. These integrations reduce the friction between audit and action, especially when you need buy-in from non-technical stakeholders who want visualizations rather than raw crawl tables.
Screaming Frog and Sitebulb are excellent for ad-hoc audits and smaller sites, but Lumar's differentiator is scheduled automation and historical tracking. If you audit a client site quarterly and want to know what changed between crawls—new redirect chains, dropped canonicals, hreflang errors introduced by a CMS update—Lumar stores every crawl and diffs them. This continuous monitoring model catches regressions the day they deploy rather than weeks later when rankings drop. For Canadian e-commerce sites running frequent promotions or SaaS platforms shipping features bi-weekly, that early warning system justifies the cost. Lumar also handles multi-domain portfolios more gracefully; you can manage dozens of properties under one account with separate crawl schedules and alert rules. Screaming Frog requires manual project switching and lacks native cloud scheduling. Sitebulb is stronger on visualization and PDF reports for client presentations, but it's still a desktop tool. If your workflow is one-person spot checks, Lumar is overkill. If you're scaling technical audits across a portfolio or supporting a dev team that needs CI/CD integration, Lumar fits.
Lumar's interface assumes you already know what canonical tags, rel-alternate-hreflang, and log file analysis mean. There's no hand-holding wizard or beginner mode. New users often find the segmentation rules and custom extraction settings overwhelming compared to Screaming Frog's straightforward tabs. Documentation is thorough but technical; expect to spend a week acclimating if you're coming from simpler tools. The platform also doesn't do content analysis or keyword tracking—it's purely technical infrastructure. You won't get on-page SEO scores or readability metrics; pair it with Clearscope, Surfer, or your own content workflow. Crawl speed is solid but not always faster than a local Screaming Frog run on a powerful machine, especially for sites under ten thousand URLs. The value comes from scheduling and history, not raw speed. For Canadian agencies evaluating Lumar, the real cost isn't just the annual fee but the onboarding time and the need for a team member who can interpret the data and translate it into dev tickets.
Lumar fits Canadian agencies and in-house teams managing large or complex sites where technical debt accumulates quickly and where historical comparison prevents repeat mistakes. The USD pricing and annual commitment mean it's a capital decision, not an impulse buy. If you run a portfolio of e-commerce or content sites, support bilingual properties with intricate URL structures, or work closely with dev teams that deploy often, Lumar's automation and integrations save more time than the subscription costs. For solo consultants or small teams doing occasional audits, Screaming Frog or Sitebulb will cover most needs at a fraction of the price. Lumar doesn't replace those tools entirely—many practitioners use Screaming Frog for quick checks and Lumar for ongoing governance. The platform's strength is turning technical SEO from a periodic fire drill into a continuous quality-control process, which matters most when the cost of a missed issue exceeds the cost of the tool.
Lumar typically offers a demo and a short trial period during the sales process, but there's no public free tier or open self-serve trial. You'll need to contact their sales team, explain your use case, and they'll provision a limited trial account. The trial usually includes a subset of features and a capped crawl quota so you can test on a real site before committing to an annual contract.
Lumar lets you create segmentation rules to crawl and report on /en/ and /fr/ paths separately, which is useful for comparing hreflang implementation, canonicals, and indexation between languages. You can also set up separate scheduled crawls for each language segment or crawl the whole site and filter reports by path prefix. The platform will flag hreflang errors, missing return tags, and language-region mismatches, which are common on Canadian bilingual sites.
Lumar invoices in USD, so Canadian buyers pay the CAD equivalent based on exchange rates at the time of payment. If you're on an annual contract, you'll typically pre-pay or pay quarterly in USD, and your bank or payment processor handles the conversion. This means budgeting requires a small currency-risk buffer since the CAD-USD rate fluctuates. Some agencies negotiate multi-year pricing to lock in rates and reduce admin overhead.
Lumar's value becomes clear around ten thousand URLs and up, especially if you deploy code frequently or manage multiple domains. Below that threshold, Screaming Frog's one-time license cost and desktop speed are usually sufficient. The tipping point isn't just page count—it's whether you need historical audits, scheduled crawls, log file analysis, and API integrations. If you're a solo consultant doing quarterly audits on small business sites, stick with Screaming Frog. If you're an agency or in-house team babysitting a portfolio or a high-velocity dev environment, Lumar pays for itself in caught regressions.
Lumar doesn't have provider-specific integrations, but it works with any site regardless of hosting. For log file analysis, you export logs from your server, CDN, or Cloudflare and upload them to Lumar. Cloudflare's Logpush can send logs to cloud storage, which Lumar can ingest automatically if you configure it. The platform is agnostic to hosting geography, so whether your site is on Canadian data centers or global CDNs doesn't affect functionality.
Lumar and Oncrawl occupy similar enterprise niches—both do scheduled crawls, log analysis, and JavaScript rendering. Lumar's interface is more streamlined and its integrations with Google tools are tighter, while Oncrawl offers deeper data science features like clustering and predictive models. Pricing is comparable, both in USD annual contracts. Canadian teams often choose based on which platform's workflow fits their existing stack. Lumar feels closer to traditional crawlers; Oncrawl leans toward analytics and segmentation. Neither is objectively better; it's a workflow and team-skill match.