↑↓ selectEnter openEsc close

    1. Elbuz

    Elbuz extension for Chrome: install and check it

    16 min readUpdated

    The Elbuz extension for Google Chrome opens site pages in your browser and passes them to Elbuz. This lets the parser collect data without server mode and see the site with your cookies.

    When you need this:

    • Server loading is not enabled — collection runs through your Chrome, free of charge.
    • The site blocks servers — your browser gets pages like a regular visitor.
    • The source card shows a red “Install extension” link — shown only when the extension does not respond.
    • Elbuz says “Chrome extension is outdated” — collection keeps working; you update from the same archive.

    Where to start: install the extension from the archive.

    What the extension does

    Who needs the extension and who doesn't

    A gets pages of another site in one of two ways: the Elbuz server downloads them, or your own browser opens them. In the second case, the Elbuz extension for Google Chrome connects Elbuz and the browser. Without it, browser mode doesn't work: nothing can open the page, so collection skips the site or doesn't start.

    Browser mode is not a rare case but the main path: server is enabled separately, while the extension works for any account.

    You don't always need the extension. One choice in the source settings decides it — what opens the pages.

    The rule is simple: if your browser opens the pages, the extension is required; if the Elbuz server downloads them, you don't need it at all. The third case is native sources: they work through a ready-made data exchange and don't open pages, so they don't need the extension either.

    How to set up the parser itself and its rules is covered in the article on site parsing. Server mode is turned on by the “Use server to load data” module. You also need it for scheduled collection: browser mode requires you to be at the computer with Chrome open, so it won't run by itself at night.

    The “Use server to load data” checkbox in the Additional tab of the site data import settings, with the neighbouring page loading options
    1Use server to load data
    1. Use server to load data — when this is on, the server fetches the site and the browser extension is not needed.

    Content search through Google has the same choice — the “Run the search on” field. “Elbuz server” works without the extension; queries and pages are paid. “My browser” opens Google and sites through the extension, queries are free, but the search window must stay open, and it opens at most 3 tabs at once. If Google asks for an “I’m not a robot” check, the extension leaves that tab next to the app: pass the check there (what to do with a captcha). Learn more: Elbuz server or your browser.

    The site shows “Just a moment…” (a Cloudflare check). In regular Chrome it usually passes by itself: the extension waits up to 12 seconds and then takes the product page. If it doesn't pass, content search by sites pauses the run with the “… asks for a verification (captcha)” banner, and the tab with the check opens in the parsing window: pass the check there and the run resumes by itself. In search through Google, such a site is simply skipped.

    The practical takeaway that saves time: if collection has to run at night without you, don't fight the extension — turn on server mode. The extension is for debugging and for sites that won't serve a page to a server but will serve it to your browser, because your browser has your cookies and history.

    How to tell it is missing

    You don't need to look for anything: Elbuz checks the extension itself and shows a sign only when it gets no response.

    The parser source card shows a red “Install extension” link with the tooltip “Install the extension for Google Chrome browser to download data from the site”. If you see the link, the extension is not responding. If you don't, it is responding, and there is nothing to do.

    Site data import settings window, Links tab, with the button bar above the links grid
    1Settings window title
    2Place where the extension link appears
    1. Settings window title — the site data import settings of the source.
    2. The spot in the Links tab button bar where the extension link appears when the browser extension does not respond.

    The “Product content search” window gives details in a “Browser search is unavailable” message: “The Elbuz extension for Chrome is not responding. Without it there is nothing to load pages with: cascade sites in “Browser” mode will be skipped. If the extension has just been updated, reload the page — until then the connection to it is lost.”

    If you click start in this state, Elbuz won't begin collection and tells you what to do: “Search not started: the Elbuz extension for Chrome is not responding while the browser page loading mode is selected. Install or enable the extension — or switch step 3 to server-side fetching.”

    At start, the extension is checked only when the browser loads the pages and the set includes non-native sites. The “Check again” button in the refusal window repeats the start from the very beginning.
    YesNo, by browserNoYesYesNo“Check again”“Start search” clicked“How pages are loaded” —“By the Elbuz server”?Normal startwithout extension checkSet includesnon-native sites?Extension check —two attempts of 2 secondsResponded?Normal start“Browser search is unavailable” —search not started
    • Action or result
    • Decision: the path depends on the answer

    The “Install extension” link appears even though the extension is installed — and you go to install it a second time. Reload the Elbuz page first.

    The extension's background handler sleeps when idle and takes half a second to several seconds to wake up. Elbuz asks twice, two seconds each, but after an extension update or a very long idle period that may not be enough. One page reload fixes it; if not, the extension really is disabled or removed.

    The two top branches decide whether to check the extension at all. The red link appears at only one end of the diagram — when neither of the two attempts got a response.
    YesNoYesNoYesNoYesNoParser sourcesettings opened“Use server to load data”turned on?Extension not checked,no linkNative source?Request to the extension,wait 2 secondsResponded?Link does not appearSecond attempt,2 more secondsResponded?Red link“Install extension”
    • Action or result
    • Decision: the path depends on the answer
    Red Install extension link with its tooltip in the Links tab
    1Install extension link
    2Tooltip
    1. Install extension link — shown when the Elbuz browser extension did not respond.
    2. Tooltip — explains that the extension for Google Chrome is needed to download data from the site.

    Installing from the archive

    You install the extension manually from an archive, not from the Chrome Web Store. This is not a workaround: Elbuz offers no other way. The “Install extension” link in the source card and in the content search window opens these instructions, and the archive itself comes from the “Download the extension” button on the “Chrome extension is outdated” banner.

    1. Download the archive: elbuz.com/downloadz/jumper_extension.zip.
    2. Unzip the archive into a folder that you won't delete or move. Chrome doesn't copy the extension; it keeps a reference to this folder. Remove the folder and the extension stops working.
    3. Open the Chrome menu (three dots in the top right) → “Extensions” → “Manage Extensions”. The address chrome://extensions opens the same page.
    4. Turn on “Developer mode” — the switch in the top right corner of the extensions page. Without it, the button from the next step won't appear.
    5. Click “Load unpacked” and select the folder from the unzipped archive — the folder itself, not individual files inside it.
    6. Reload the Elbuz page.

    Don't delete the extension folder after installation, and don't move it elsewhere. Chrome refers to it every time it starts; if the folder is gone, the extension is silently disabled and the red link comes back in Elbuz — with no hint that the moved folder is the cause.

    How to make sure it works

    The sign of success is the same, only reversed: the parser source card has no red “Install extension” link, and the content search window has no “Browser search is unavailable” message.

    This is a more reliable check than the Chrome extensions page: there the extension may be enabled but not responding to Elbuz — for example, after an update, until the page is reloaded. Elbuz shows not whether the extension is installed, but whether it responds.

    Domains: Elbuz keeps the list itself

    The extension doesn't work with every site; it works with a list of allowed domains. You don't have to maintain it by hand: when you open the source settings, Elbuz adds that site's domain to the extension itself, and removes it when you close the window.

    This is worth knowing for one reason: if collection suddenly stops seeing pages of this particular site, close and reopen the settings window — the domain will be added again.

    Updates and outdated versions

    The extension reports its version to Elbuz starting from 2.3.4. Older versions don't report anything about themselves, so instead of a number the warning says “older than 2.3.4”.

    The content search window expects version 2.4.6. When an older one is installed, the “Chrome extension is outdated” warning appears: “Installed version such-and-such, this window expects 2.4.6. The extension updates manually: download the archive and reinstall it in Chrome.”

    An outdated extension doesn't break the run. The old way of communicating still works and collection continues — only the new features silently don't work. That is why it is a warning, not a block, and you don't need to stop working because of it.

    Elbuz also says plainly what fails on old versions: “Old extension version: exact tab accounting is unavailable, working more conservatively. Update the extension to 2.3.6 or newer”. In practice, this means the search runs slower.

    Updating is the same installation from the archive: download a fresh archive, unzip it over the same folder, and click the update button on the Chrome extensions page. The extension doesn't update automatically because it isn't installed from the Web Store.

    Scenarios

    Collection has to run at night, with nobody at the computer

    Task: supplier pages need to be collected on a schedule when nobody is in the office.

    What to turn on: in the parser source settings — “Use server to load data”; in the “Product content search” window, in the “How pages are loaded” field — “By the Elbuz server (paid, works without a browser)”.

    What you get: Elbuz doesn't check the extension for such a source, and the settings have no red “Install extension” link. Content search in server mode starts without the check. What won't happen: the “By the Elbuz server” option isn't in the list until server loading is enabled. Sites without server loading set up are skipped in server mode.

    Server loading is not enabled

    Task: parse a site without the paid server mode.

    What to turn on: leave the “Use server to load data” switch off; in the “How pages are loaded” field — “By browser (Chrome extension, free)”, the only option in the list until the server is enabled. Install the extension from the archive as described above.

    What you get: your Chrome opens the pages through the extension. What won't happen: if the extension doesn't respond, the search won't start — Elbuz shows the “Browser search is unavailable” window, and the source settings show the red “Install extension” link.

    The search set has only native sources

    Task: run content search on a computer without the extension when all selected sources are native.

    What to turn on: nothing extra — “How pages are loaded” can stay on “Browser”.

    What you get: Elbuz sees no sites in the set that need a browser and starts the search without the check; the “Browser search is unavailable” banner isn't shown. Native source settings don't show the “Install extension” link either. What won't happen: as soon as even one non-native site gets into the set, the extension check comes back.

    The extension was turned on without closing the search window

    Task: the “Product content search” window shows “Browser search is unavailable”, and you have just installed or enabled the extension in another tab.

    What to turn on: the “Check again” button on the same banner. Or just “Start search”: in browser mode, Elbuz asks the extension on every start.

    What you get: if the extension responds, the banner disappears and the search starts. If not, “Check again” in the refusal window repeats the whole start — no need to click “Start search” again. What won't happen: if the extension was just updated, only reloading the Elbuz page restores the connection, as the banner says.

    If something goes wrong

    The red “Install extension” link is there, although the extension is installed
    Cause. The extension's handler was asleep and didn't respond within the two attempts — most often after an extension update or a long idle period. What to do. Reload the Elbuz page. If that doesn't help, check on the Chrome extensions page that the extension is enabled and its install folder is still in place.
    The extension disappeared by itself, although nobody removed it
    Cause. The folder it was installed from was renamed, moved or deleted — Chrome keeps a reference to it, not a copy. What to do. Reinstall from the archive and this time put the folder where it will stay.
    “Chrome extension is outdated”
    Cause. The installed version is older than the one the window expects. What to do. Update manually — download the archive again and reinstall. Collection keeps working: the warning doesn't block the start.
    The search runs noticeably slower than before
    Cause. An old extension version doesn't keep exact track of tabs, so Elbuz plays it safe; it also happens that the extension doesn't free tabs. What to do. Update the extension. The exact message is: “The browser extension is not freeing tabs, continuing with our own count. If the search is slow, update the extension”.
    “The browser refused to open the search window”
    Cause. Chrome blocked opening a separate window. What to do. Nothing is broken: pages open as tabs in the current window, just slower. If speed matters, allow Chrome to open windows for this site.
    Collection starts, but sites are skipped
    Cause. Browser mode is selected while the extension doesn't respond — then cascade sites in “Browser” mode are skipped. What to do. Either install the extension and reload the page, or switch step 3 to server-side fetching.

    FAQ

    Do I have to install the extension for the parser to work?

    No. You need it only when your browser opens the pages. If the “Use server to load data” module is on, the Elbuz server downloads the pages and the extension is not needed at all. Native sources never need it: they don't open pages.

    Why isn't the extension in the Chrome Web Store?

    Elbuz offers it as an archive for manual installation — the interface has no other way. That is also why there are no automatic updates: you download the fresh version and reinstall it yourself.

    Elbuz says the extension is not responding, but it is installed. What's wrong?

    Most often it was asleep and missed two attempts of two seconds each. Reload the Elbuz page. If the message stays, check on the Chrome extensions page that it is enabled and its install folder is in place: Chrome keeps a reference to the folder, not a copy.

    Can I work with an outdated version?

    Yes, collection runs. An outdated version doesn't break the run — only the new features silently don't work, and the search may be slower. That is why Elbuz shows a warning instead of blocking the start.

    One employee installed the extension — does it work for everyone?

    No. The extension lives in a specific person's browser on their computer. Everyone who sets up parsers in browser mode installs it for themselves.

    Does the extension work in other browsers?

    No. Elbuz checks for and offers only the extension for Google Chrome; the interface has no other.

    Where to find it and who has access

    Menu
    Directories → Processing price lists → List of price lists
    Where you see the status
    parser source card: the red “Install extension” link
    Other entry points
    the “Product content search” window — the “Browser search is unavailable” message, including for Google with “My browser”
    Access right
    none of its own: the extension lives in your browser, not in Elbuz
    Prepare
    Google Chrome and permission to install extensions in it

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free