Sourcing, minus the retyping

Recruiting Chrome Extensions That Send Candidates to Your ATS Without the Retyping

How many times does a recruiter type one candidate's name in a week? Once in the ATS, once in the hiring manager's spreadsheet, once in a message, and once more when the ATS made a second record because the first entry spelled it differently.

November 18, 2026 · 9 min read

acmetalentpartners.com · pre-submission check
A recruiting extension, checked before store submission
Privacy policy link missing from the dashboard field
  • PassPermissions limited to storage, context menu and activeTab
  • PassHost access only to the agency's own server
  • PassCandidate data sent over encrypted connections
  • PassFirst-run screen discloses what is collected
  • PassCandidate fields cleared from storage after save
  • FailPrivacy policy linked in the dashboard fieldempty
Illustrative: a sample pre-submission check for a fictional staffing agency's extension

The short answer

A recruiting Chrome extension lets a recruiter save the candidate on screen to the company's or agency's applicant tracking system through its API, check for an existing record first, attach the job opening and a note, and log the source. It reads only pages the recruiter chooses and respects each site's terms. Custom builds from DataCram start at $1,500, depending on complexity.

On this page
  1. The candidate who exists three times in your ATS
  2. Where the candidate comes from decides what the tool may do
  3. One click, one candidate, one clean record
  4. Candidate data is personal data, and the store treats it that way
  5. Small and honest: lessons from the GatorCrawl build
  6. Rolling the tool out to a desk of recruiters
  7. Price, ownership and the ATS extension you may already have

The candidate who exists three times in your ATS

Every applicant tracking system has a ghost population. Jonathan, Jon and J. Smith, all the same senior estimator, each with a different phone number and none with the note that he was interviewed in March and said he would move for the right offer. Somebody created each record in good faith, at speed, between calls. The ATS did its job. The data entry did not.

A recruiting extension attacks the data entry. The recruiter is already looking at the candidate: a résumé attached to an email, a portfolio site, a referral message, an application on the company's careers page. One click opens a panel with the name, contact details and the open roles. The extension checks the ATS for a match before it creates anything. If Jon already exists, the recruiter adds a note to Jon.

If your ATS vendor already offers a browser tool that does this, try it first and keep your money. Custom earns its fee when the agency runs more than one system, has its own fields and pipeline stages, needs candidates routed to a particular recruiter or client, or wants the extension to feed the CRM as well as the ATS. Sales teams with the same problem should read our sales prospecting extensions page instead.

Where the candidate comes from decides what the tool may do

Recruiters work on many sites, and each one has terms of use. Some professional networks and job boards may restrict automated collection of profile data. We do not summarize their terms here; they change, and reading them is a job for you and your counsel. If a site's terms forbid an extension reading or saving its pages, ours will not.

The safe ground is wide. Candidates send résumés by email. They apply through your careers page. They link portfolios and personal sites. Referrals arrive in messages. Hiring managers forward names. Every one of those can go into the ATS with one click and no question about anybody's terms, and for some teams those sources are where the serious candidates come from anyway.

One click, one candidate, one clean record

  1. 1

    Invoke on the current page

    The recruiter clicks the toolbar icon or right-clicks a highlighted name. Google's activeTab documentation explains that access is granted at that moment and lasts "while the user is on that page".

  2. 2

    Read what is visible

    A content script picks up the name, email, phone and any highlighted text from the page. Nothing else on the page is stored.

  3. 3

    Search before creating

    Your server looks for a match in the ATS by email, phone and name, and shows the recruiter any likely duplicates first.

  4. 4

    Attach the role and a note

    The recruiter picks the opening, the stage and the source, and types the one sentence that will matter in six months.

  5. 5

    Write through the API

    The server creates or updates the candidate through the ATS's API, links the opening, and confirms with a link to the record.

Dark green chalkboard with chalk arrows converging from scattered doodled envelopes into one box, a black-and-white halftone cutout of a paper folder in front
Candidates arrive from many places; the extension sends each one to a single record.

The ATS connection goes live the same day, through its API, once the extension is built. If your team also needs the candidate pushed to a CRM for client billing or to a spreadsheet the hiring manager insists on, the server can do that too, as an API integrations job. Moving candidates between stages automatically, or sending an email when a stage changes, is workflow automation.

Candidate data is personal data, and the store treats it that way

A recruiting extension handles names, contact details and work histories. The Chrome Web Store has specific rules for any extension that touches user data, and a tool built for recruiters should meet them even when it is published privately for your own team. Google's policy pages, read in November 2026, set out the requirements below.

Chrome Web Store user data rules that apply to a recruiting extension, as of November 2026
Google's wordingIn a recruiting build
Privacy policy"If your Product handles any user data, then you must post an accurate and up to date privacy policy."A policy that says what the extension reads, where it sends it and who can see it
Disclosure and consentBefore installation it must "Prominently disclose what user data will be collected and how it will be used."The listing and a first-run screen say plainly what happens to candidate data
Limited UseCollect, use or transmit only data "necessary for the extension's disclosed single purpose"Candidate fields for the ATS, nothing about the recruiter's browsing
Secure transmission"Purple Copper" is the violation for an extension "not transmitting user data securely."Encrypted connections to your server, every time

Sources: the privacy policy rule, the disclosure requirements, Limited Use and Google's troubleshooting page for the violation names. Employment and privacy law are separate questions for your counsel; DataCram builds the tool and writes the disclosures within your review. The extension permissions and privacy page covers the store side in depth.

Small and honest: lessons from the GatorCrawl build

GatorCrawl Keywords is our own keyword research web app, and we wrote its Chrome extension too. A keyword tool and a recruiting tool look nothing alike on screen, but the store listing makes a promise worth copying word for word in spirit: "The extension talks only to your GatorCrawl Keywords account. It contains no ads and no tracking, and it doesn't record your browsing history." A recruiter's browser is full of people who never agreed to be tracked. The extension should be as quiet.

Two permissions, named

GatorCrawl asks for "storage" and "contextMenus", plus access to its own app's address. A recruiting build adds activeTab and stops there.

Tokens accepted from one place

Its service worker accepts a sign-in token "only from the configured app origin". Ours accept tokens only from your ATS connector's sign-in page.

Memory that expires

GatorCrawl keeps results in chrome.storage.session for an hour. A recruiting tool keeps candidate data for seconds, just long enough to send it.

Logic on the server

Every GatorCrawl lookup goes through the web app's API. Every candidate save goes through your server, where duplicate rules can change without a store review.

The full GatorCrawl build story explains the manifest, the content script on Google results and the options page that connects the account. You can see the product on the GatorCrawl Keywords site, where the extension is "Included with every plan."

Rolling the tool out to a desk of recruiters

Most recruiting extensions are private. Private visibility in the Chrome Web Store restricts installs to the users you name, and Google's enterprise publishing page adds that "domain-published extensions usually get through the review process more quickly." When recruiters use managed Chrome through Google Workspace, an administrator can push the extension to every desk with the force-install setting in Google's admin help.

  • Plan permissions before launch. Google's permission warnings page says that when an update adds a permission with a warning, "the extension will be disabled until the user accepts the new permission." A desk of recruiters finding their tool switched off on a Monday is avoidable.
  • Prefer optional permissions for later features. Google notes Chrome "won't disable it for your users if the upgrade adds optional rather than required permissions."
  • Turn on 2-Step Verification for the developer account. Google requires it "prior to publishing an extension or updating an existing extension."
  • Keep the account in the company's name, so the tool does not leave with whoever set it up.

The internal team extensions page goes further on private rollouts, and browser extension security covers why developer accounts deserve the same care as the ATS admin login.

Price, ownership and the ATS extension you may already have

Our price for a custom extension starts at $1,500 and depends on complexity, and you see a fixed written estimate before any work begins. Saving to one ATS with duplicate matching is the simple end. Two or three ATSs, a CRM push, routing by client, a side panel and a Firefox or Edge version make it bigger. The permission plan, the privacy wording and the store submission come included; changes after launch are priced separately when you ask. Extension pricing breaks the factors down.

The code and the listing are yours. Publish under a developer account in the agency's name, which is what we recommend. Its registration fee is $5 as of November 2026, per Chrome's What's new page. Google reviews every submission and sets the timing, so we promise no date. If your ATS's own browser tool covers the job, or your team adds only a few candidates a week, skip the custom build.

DataCram has built for the web since 1999 from San Antonio, Texas, working with teams across the country by phone, video and a shared project page. Agencies sit within our professional services work. The custom Chrome extension development page sets out the full offer, the browser extensions hub lists every kind we build, and about us and our work say who we are. Or tell us which ATS you run and where candidates go missing.

Questions owners ask about custom browser extensions

That is governed by LinkedIn's terms, which change and which you should read with counsel before anything is built. If they forbid an extension reading or saving profile pages, we will not build that. We build one-candidate-at-a-time capture from sources that are yours to use: emailed résumés, careers page applications, portfolio sites and referrals.

If the ATS has an API your subscription can reach, we can connect it. Candidates travel from the extension to your server, where duplicates are checked, and on to the ATS through that API. The link is live the same day the extension is finished. No usable API? You will hear that from us first, before any invoice.

It searches before it creates. Your server looks up the candidate by email, phone and name and shows the recruiter any likely match. The recruiter chooses to update the existing record or create a new one. The matching rules live on your server, so you can tighten them later without publishing a new extension version.

Chrome's policy says any product that handles user data "must post an accurate and up to date privacy policy," and Google's distribution page says all visibility settings have the same policy requirements. A recruiting tool handles candidate data, so plan on a policy and clear disclosures either way. We write them as part of the build, within your counsel's review.

Yes, with planning. If an update adds a permission that triggers a warning, Chrome disables the extension until each user accepts it. Declaring future needs as optional permissions avoids that, because Chrome does not disable an extension for optional ones. Logic that lives on your server can change without any extension update.

Builds start at $1,500, and the final figure depends on complexity; the written estimate is fixed before we begin. Saving candidates to one ATS with a duplicate check sits near the start; more systems, routing and other browsers add to it. Store submission and privacy disclosures are included, and updates after launch are quoted.

Keep reading

Free · No obligation

Stop typing the same candidate twice

Tell us which ATS you use and where candidates come from. You get a fixed written estimate back, or a pointer to the ATS feature that already covers it.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote