Sitebulb Review 2026: Desktop, Cloud & Audit Limits

The Desktop pricing page distinguishes Lite and Pro, with monthly and annual subscriptions. Saved October 8 research verified the advertised 15% annual saving but could not resolve the dynamic price amounts. This review therefore supplies neither guessed dollar figures nor annual invoices calculated from older articles. Cloud has its own pricing page and configurable hosted plans. Confirm currency, billing period, taxes, capacity, and included access together; a starting headline without those details is not the price of your actual deployment.

Lite and Pro are real Desktop tiers, not interchangeable labels for an assumed unlimited package. Before choosing, map each required analysis, report, and export to the current entitlement table. A trial is an evaluation window, not a permanent free plan; use our free SEO tools guide if ongoing zero-cost use is essential. Annual billing deserves consideration only after the workflow has been evaluated. The advertised percentage alone does not establish a refund right, a particular renewal amount, or a Cloud discount, and none is assumed here.

The download requirements specify 64-bit Windows 10 or 11, or macOS Sonoma and later, with both Apple Silicon and Intel Mac installers. At least 4GB of usable/free RAM is required, with 8GB recommended. That wording matters: a machine with 8GB installed may have substantially less available while other applications run. Meeting the minimum does not promise a particular crawl size or completion time. Audit data, rendering, concurrent applications, and local storage needs should be considered before treating an existing laptop as dedicated crawling infrastructure.

The Desktop versus Cloud explanation documents browser access, desktop integration, recurring audits, and team access to the same hosted crawl data. Cloud therefore addresses more than keeping a laptop awake: it can provide a common audit for distributed reviewers. However, no project limits and no crawl credits do not mean infinite simultaneous processing, storage, or URLs per audit. Ask which capacity and users the selected plan includes, and verify client-facing permissions. This review did not test role isolation, concurrent editing, or whether every intended recipient needs paid access.

Sitebulb's audit settings distinguish crawling the website, adding XML sitemap URLs, and checking a supplied URL list. At least one source is required. List-based checks do not follow links from those pages, and the documented list workflow is restricted to the start URL's subdomain. That is useful for a controlled set of changed pages, but it is not equivalent to discovering a whole site. Label the source and scope in the report so a limited release check cannot be mistaken for a comprehensive audit.

Additional sitemap and authorized Analytics or Search Console URLs can reveal pages that internal-link discovery missed. They cannot establish that every orphan URL has been found: source coverage, account access, and selected date ranges still matter. The technical-audit setup guide recommends explicit source selection and documents limits for Chrome instances and HTML URLs per second. Agree safe rates with the site owner, clarify subdomains and exclusions, and investigate unexpected crawl growth before increasing capacity. A crawler should not turn faceted navigation or calendar paths into an uncontrolled workload.

The Chrome Crawler matters when useful content is created after the initial HTML response. Sitebulb's audit documentation specifically notes that extracting a JavaScript-inserted product price requires the Chrome Crawler. For an evaluation, select representative product, category, and article pages, then check whether the expected text and links are actually present after rendering. Missing content may require investigation of blocked resources, access conditions, or page behavior rather than an immediate SEO recommendation. Compare this same sample with Screaming Frog instead of comparing product screenshots or unrelated crawl settings.

Rendering also changes resource requirements. Sitebulb warns that enabling every audit option increases processing and that performance and accessibility checks are CPU-intensive. Select the checks needed for the decision, and disclose what was not collected. A matching Chromium family does not make an audit identical to Google's rendering pipeline, crawl scheduling, or indexing decisions. Nor does a successful rendered page establish satisfactory real-user performance. Use the crawl to identify and reproduce technical observations; separately investigate search-engine evidence and user measurements before claiming a JavaScript or speed change solved the underlying business problem.

The setup guide exposes separate options to save disallowed URLs, crawl disallowed URLs, and crawl links with nofollow directives. These choices affect what Sitebulb collects; they do not change the website or grant permission to inspect a restricted area. Saving a discovered blocked URL is different from fetching its content. For an authorized diagnostic crawl, document any override and keep it distinguishable from the normal-access baseline. Otherwise, an apparently complete report can hide the fact that an ordinary crawler would encounter a different set of restrictions.

Interpret each signal according to its job. Nofollow describes a link relationship, robots.txt controls crawling, and noindex concerns indexing. A canonical indicates a preferred URL; it neither redirects a visitor nor guarantees the search engine will choose that URL. When reviewing a canonical finding, inspect the source page, target response, intended duplicate relationship, internal links, and sitemap consistency. Do not remove every directive to make the report greener. Equally, a crawler marking a page as potentially indexable is not evidence that Google has indexed it. Confirm the relevant search outcome separately.

Sitebulb's Hints and crawl maps can make technical findings easier to explain, but the buyer still needs a prioritization method. Group affected URLs by template, inspect representative examples, identify the likely business exposure, and specify an acceptance check. One shared navigation defect affecting important landing pages can warrant attention before many isolated cosmetic warnings. A useful ticket names the observed behavior, expected behavior, evidence, and responsible owner. Automated severity can help organize that work, but it should not replace judgment about intentional behavior or the risks of changing a shared template.

Optional Search Console data adds clicks, impressions, CTR, and queries for the connected property and chosen period. That context can help prioritize affected pages without inventing an expected traffic uplift. Plausible Analytics addresses a different question: what visitors actually do on the website. Keep technical checks, search performance, and visitor measurement distinct when reading our small-business SEO tools guide. After implementation, repeat the relevant crawl checks and inspect appropriate outcome data. A lower issue count is useful evidence of changed implementation, not proof that the change caused more revenue or better rankings.

The Data Exports Settings documentation identifies two different outputs. Most tabular exports are CSV files, with some formatted Excel workbooks spanning multiple worksheets; these include Hint and URL datasets. The separate .sbp share file can be imported by another Sitebulb user to access the entire audit. A spreadsheet is therefore not a substitute for a reopenable project. Decide whether the recipient needs a remediation list, independent analysis data, or the complete audit context, then include the applicable date and crawl configuration with the handover.

Custom export destinations are configured per project, not automatically for every new project. The documented workflow can save files to a local folder or an approved shared drive and combine exports with scheduled audits. Check the destination, recipient access, and successful creation of both required outputs during evaluation. Audit files may expose nonpublic paths or extracted content, so treat sharing as a data-access decision. Keep an agreed retention and deletion process for exported copies; removing access to a hosted audit should not be assumed to revoke copies already downloaded elsewhere.

Use our SaaS evaluation framework to define one bounded comparison: the same authorized pages, crawl sources, rendering requirements, representative problems, and report recipient. Against Screaming Frog, examine whether Sitebulb's explanations and shared workflow produce a deliverable your team can use. If the missing capability is recurring position monitoring rather than technical diagnosis, reassess SE Ranking or an existing research subscription instead. Judge demonstrated workflow fit rather than assuming a specialist crawler replaces every tool carrying an SEO label.

Desktop is a reasonable shortlist when one auditor has suitable hardware and manageable local work. Cloud deserves evaluation when hosted schedules, shared data, or capacity are the actual constraint. Before committing, secure the applicable quote, confirm feature entitlements, inspect a representative export, and identify who will resolve the findings. Our SaaS spending guide helps assess overlap without counting hypothetical productivity as cash savings. Sitebulb's documented capabilities support a serious technical-audit evaluation; this documentary review does not establish measured speed, complete discovery, or a guaranteed search result.