NameToProfile logo
Browser Extension Support

Company Extractor — Support

Last updated: 2026-07-15

Quick Start

  1. Register and create an API key from nametoprofile.com/register.
  2. Install the Company Extractor from the Chrome Web Store.
  3. Open the extension popup and save your API key during setup.
  4. Log in to LinkedIn and open any company page, e.g. linkedin.com/company/<slug>.
  5. Click the extension icon in the Chrome toolbar.
  6. Pick the fields you want in the Fields panel and click Extract Data.
Supported scope: The extension works only on LinkedIn company pages under linkedin.com/company/*. It does not support Sales Navigator, profile pages, messaging pages, search result pages, or unrelated sites.

How the workflow behaves

  • Clicking Extract Data reads structured data from the company page you're viewing.
  • If you aren't already on the /about sub-page, the extension navigates there automatically so all fields (industry, founded, specialties, etc.) are available, then extracts.
  • The Data Preview panel populates with the extracted values. Each value shows a small source badge (LD, DOM, LBL, or RGX) — see the Source badges section below for what each one means.
  • Use Copy Row to paste a single tab-separated row directly into Excel or Google Sheets, or export to Excel (.xlsx), CSV, or JSON.

Extracted fields

The extension can extract up to 13 fields from a company page: Name, Company ID, Logo, Summary, Overview, Website, Industry, Company Size, Followers, Headquarters, Founded, Specialties, and Employees on LinkedIn. You can toggle optional fields in the Fields panel.

Source badges in the preview

Each extracted value in the Data Preview panel shows a small badge indicating where the value was obtained from:

  • LD — parsed from JSON-LD structured data embedded in the page. Most stable source.
  • DOM — read via a CSS selector against the rendered page DOM. Used as a fallback when JSON-LD doesn't expose the field.
  • LBL — located by matching a label in the page (e.g. finding the text "Founded" and reading the adjacent value). Used when CSS selectors drift after a page-layout update.
  • RGX — extracted via a regular expression scan against the page body. Last-resort fallback for fields that no structured or label-based lookup could find.

Stored locally

The extension stores your API key, your field preferences, the most recently extracted profile (used by Copy Row), and any active bulk capture session in Chrome local storage, so your settings and in-progress work survive popup closes and service-worker restarts. Nothing is uploaded except the NameToProfile API calls described below — free account checks, plus the company snapshot sent only when you score.

Account scoring (sends company data to the API)

Extraction, preview, copy and export all run in your browser. The one exception is account scoring: when you pick an approved ICP brief and click Fast score or Deep AI score on a company, the extension sends a snapshot of that company (name, industry, type, size, headquarters, locations, founded year, specialties, follower / employee counts and funding) to the NameToProfile API to score it against your brief.

  • Fast score — 1 credit (deterministic).
  • Deep AI score — 20 credits (LLM second opinion).
  • Results are cached 24 hours per company per brief — a cache hit costs 0 credits.
  • Requires an approved brief — create one under ICP Briefs.

API key usage

Apart from scoring, the extension uses your API key only for free, non-consuming calls: /v1/auth/validate, /v1/usage, /v1/usage/check, and /v1/briefs (to list your approved briefs). Extraction and export never send company data to our servers — only scoring does, and only when you click.

Export formats (single profile)

Excel (.xlsx) — a file with a header row plus one data row and auto-fitted column widths.
CSV — properly quoted for values that contain commas or line breaks.
JSON — structured output including extractedAt and pageUrl metadata plus every selected field.
Copy Row — a single tab-separated string copied to your clipboard, ready to paste into any spreadsheet cell. Each field lands in its own column automatically.

Bulk Capture

The popup has a Bulk tab for capturing data from multiple companies without manually clicking Extract Data on each one.

  • Click Start Session in the Bulk tab. The extension verifies you have at least 250 free credits on your NameToProfile account via a non-consuming entitlement check (POST /v1/usage/check). This check does not deduct credits — it only confirms you are entitled to run a bulk capture.
  • While the session is active, visit the supported company pages as you normally would. Each company page you open is automatically captured and added to the bulk queue (duplicates are de-duplicated by company ID).
  • Click Stop Session in the Bulk tab at any time to end the capture. Stopping a session is always allowed and requires no entitlement check.
  • After stopping (or at any point during the session), export the captured companies as a single bulk Excel (.xlsx), bulk CSV, or bulk JSON file. Each row in the exported file is one captured company, with the same field columns as the single-profile export.
  • Click Clear Session to remove all captured companies from the queue. This does not affect your NameToProfile credit balance.

Note on credits: the 250-credit threshold is an entitlement gate only. The extension does not consume NameToProfile credits for extraction or bulk exports — all scraping runs locally in your browser. The check exists to limit bulk capture to accounts with sufficient entitlement headroom.

Useful Links

Data handling notes

All company data is extracted and processed inside your browser. The extension reads the company page you're viewing via standard Chrome extension APIs and either parses embedded JSON-LD structured data or falls back to CSS selectors on the rendered DOM. Extracted data is stored only in your local browser and is never sent to NameToProfile or any third party. See the Privacy Policy for full details.

Clear data behavior

Clearing extension data via the popup removes the last extracted profile, the history of recent extractions, and your field preferences, but keeps the saved API key in place. Use the Settings screen to remove the API key separately if needed.

Login required

You must be logged in, in the same browser window, for the extension to access the company page you're viewing. The extension does not handle authentication — it relies on your normal logged-in session.

Troubleshooting

Extract Data button is disabled

  • Open a supported company page under linkedin.com/company/*.
  • Make sure you are logged in.
  • Then reopen the popup and try again.

Fields show em dashes ("—")

  • An em dash means neither the JSON-LD nor the DOM selector matched for that field on the current page.
  • Scroll the company page so the About module loads, then extract again.
  • The page layout occasionally updates — if a field persistently fails, report it to support.

Excel export fails or does nothing

  • The Excel library is bundled inside the extension package — .xlsx export works offline and does not need any network access.
  • If Excel export still fails, make sure the popup has focus and try again. If the issue persists, use CSV or JSON export instead and email support with a screenshot.

Invalid API key or missing key

  • Open Settings inside the popup and verify the saved API key.
  • If needed, generate a new key from your NameToProfile dashboard and save it again.
  • Rotating your API key on the dashboard invalidates the old key immediately.

The page shows a login wall or CAPTCHA

  • The extension cannot extract data if the page has shown a login wall — log in again in the same tab.
  • Rapid repeated extractions may trigger the site's bot-detection or CAPTCHA flow.
  • Use the extension at a normal browsing pace. If you hit a CAPTCHA, solve it on the page and retry.

Copy Row pastes into a single cell

  • Make sure you are pasting into a cell in Excel or Google Sheets (not into a word processor).
  • Spreadsheets automatically split tab-separated values into columns when you paste — Copy Row uses tab separators.

Company ID looks like a slug

  • The company page exposes numeric company IDs inconsistently.
  • For companies with vanity-slug URLs, the extension falls back to the slug string (e.g. microsoft) instead of a numeric ID.
  • Some pages expose more than one numeric ID (for example, a parent company and a regional entity). In that case the extracted value is a comma-separated list of all IDs found on the page.
  • All of these formats are valid for identifying the company.

FAQ

Which pages are supported?

The extension supports company pages only. It does not support Sales Navigator, personal profile pages, messaging pages, or search results.

Does the extension send page content to NameToProfile?

No. All extraction runs inside your browser. The extension reads the company page you're viewing via standard Chrome extension APIs and parses it locally. The only network calls to NameToProfile are free API-key-validation calls (/v1/auth/validate, /v1/usage, /v1/usage/check) that do not transmit any page content.

Does the extension use credits?

No. The extension only calls free endpoints on the NameToProfile API. Your credit balance is unaffected by the extension's normal extraction and export operations.

Why do I need a NameToProfile API key at all?

The API key is used only to verify that you have an active NameToProfile account. This makes the extension available to registered users and lets us coordinate support requests through a single account identifier.

Does the extension scrape or automate browsing?

No. The extension reads data from the company page you have already opened in your own logged-in browser session. It does not browse on your behalf, crawl multiple pages automatically, or bypass any access control.

What happens if the page layout changes?

The extension first tries JSON-LD structured data (which is stable) and falls back to CSS selectors. If the page updates its markup and a particular field stops working, that field will show an em dash ("—") until we ship an extension update. Please report persistent failures to info@nametoprofile.com.

Where is my data stored?

All extracted data, your field preferences, and the history of recent extractions are stored only in your local Chrome profile using chrome.storage.local. Nothing is uploaded anywhere except the free API key validation calls mentioned above.

How do I contact support?

Email info@nametoprofile.com with a screenshot of the extension popup, the company page URL, and the exact error if available.

Contact Support

For setup help, extraction issues, export problems, or API-key related questions for the Company Extractor.

Email: info@nametoprofile.com

Need direct help?

Send your account email, the company page URL, a screenshot of the extension popup, and the exact error if available.

Email Support

We use privacy-friendly analytics to improve the site. No personal data is sold. You can opt out.