How to Claim a Company Page on Toolradar

Who can claim, and what a claim gives you

A claim gives one signed-in person owner access to one company record on Toolradar. The owner can edit the company's products, see its analytics, answer reviews, and manage the team and badges from the company dashboard. A company that is already claimed shows "Already Claimed" on its claim page, with a link to the public profile.

Use a work address on the company's own domain, or prove control of the domain itself. A personal address, a brand name or an agency's address does not show that you may manage the listing.

You can claim when you can prove one of three things: you control the company's website (DNS, file or meta tag), your verified account email sits on the company's domain, or you hold a work address on that domain and can read its inbox. A personal address (Gmail, Outlook, Yahoo, iCloud and similar providers) is refused for a manual claim, because it cannot show control of the company.

Creating a listing and claiming it cost nothing. Toolradar also sells advertising and content services, separately and never as a condition of being listed (vendor page).

Before you start

Have these ready, so the steps take minutes rather than days:

• The official company website and the domain it runs on, for example lumenops.example.
• Access to one of: the company's DNS settings, its web server (to upload one file), or the editor for its homepage head (to add one meta tag).
• A work email on the company domain, and access to its inbox, if you want the email route.
• Your job title, and your LinkedIn profile URL if you have one. The form marks LinkedIn as extra context, not a requirement.
• The names of the colleagues who should keep access, so you can set up the team after approval.

Check that the company record is the right one. The claim page shows the company name and domain. If the name or domain does not match your organization, do not claim it: use contact to report the record instead. The public claim page lists what a claim gives you and links to this guide.

The steps, from sign-in to approval

1. Open the claim page at /companies/<company-slug>/claim, or use the "Claim this Profile" button, or the "Unclaimed" label, on the company's public page, and check that the company name and domain shown there match your organization.
2. Sign in. The claim page requires an account. If you are signed out, Toolradar sends you to sign in and brings you back to the claim page for the same company.
3. Read the heading on the claim page. It reads "Claim" followed by the company name, with the line "Verify that you work at" the company name "to manage this company profile." The page offers "Verify instantly" first and "or request manual review" below it.
4. Try the "Verify instantly" box first. If your signed-in email is verified and sits on the company domain, press "Verify with my @yourdomain.com email". Otherwise, add one of the three records shown (DNS TXT, the file at /.well-known/toolradar-verify.txt, or the homepage meta tag), then press "Check now". Success shows "Verified. You now manage this profile." and the page moves you to your company dashboard.
5. If instant verification is not possible, fill in the form under "or request manual review". Enter the work email (required), your job title, your LinkedIn profile (optional) and any notes, then optionally answer "How did you hear about us?" and press "Submit Claim Request". The screen confirms the submission and asks you to check the address you entered for a verification link.
6. Open the confirmation link in that inbox. It leads to a page with a Confirm button. Toolradar acts only on that click, not on the link being opened, so mail scanners cannot confirm a claim for you. Until you confirm, the request stays out of the admin review queue, and it is closed automatically if the link expires.
7. Wait for the decision. Once the address is confirmed, a Toolradar admin reviews the request. On approval you get an email and an in-app notification. A rejection arrives as an email that carries the reviewer's reason, with an in-app notification, and the reason also appears on the claim page. A reason is required on every rejection.
8. After approval, the request becomes an owner membership on the company, and the company shows as claimed. Open the company dashboard at /company to start.

Verification options: which one to use

Table: Route | What you do | How it is decided | Use it when

Domain control is the fastest route. A DNS record can take up to an hour to become visible, so the page says to try again later rather than to repeat the press. The manual route is the fallback for cases the instant routes cannot cover, such as a mobile app whose maker cannot publish on the parent web domain.

Why a claim is refused or delayed, and the fix

These are the refusals and delays the claim flow can show.

• A personal email was entered. A manual claim with Gmail, Outlook, Yahoo or iCloud is refused. Fix: enter the work address on the company domain.
• A disposable address was entered. Temporary addresses cannot verify a claim. Fix: use a permanent work address.
• Your account email is not on the company domain. The "Verify with my @yourdomain.com email" button appears only when your signed-in email is verified, is not a personal or disposable address and sits on the company domain. Fix: use the DNS, file or meta route, or the manual form with a work address on the domain.
• The token was not found. The page says the DNS record, the file or the meta tag was not found yet. Fix: add the record exactly as shown, wait a while for DNS, then press "Check now" again.
• The confirmation link was not used in time. A link is valid for 7 days. A claim whose link expires unused is closed, and the claim page then says so and shows the request form again. Fix: send a new request from the claim page and open the new link promptly.
• The confirmation email could not be sent. The request is removed and the screen says "We could not send the confirmation email to that address. Please check it and try again." Fix: check the address spelling and try again later.
• The company is already claimed. The claim page shows "Already Claimed". Fix: ask the administrator of the existing account in your organization. If nobody can identify one, contact Toolradar with the company record URL and the official domain.
• The domain belongs to a team member already. The setup route says the domain is already claimed by a team member and asks you to be invited from the company dashboard's team page. Fix: ask that person to invite you.
• You already have a request for this company. A pending request, or one an admin rejected, blocks a second one. A request that timed out unconfirmed does not. Fix: wait for a pending request to be decided, or contact Toolradar about a rejected one.
• You have three pending claims. A user can hold at most 3 pending claims. Fix: wait for one of them to be decided.
• You sent too many requests. Claim requests are limited to 5 per 10 minutes. Fix: wait 10 minutes.
• A work email was entered but never confirmed. An admin cannot approve it without an explicit override. Fix: click the confirmation link first.

What you can do after approval

Once the request is approved, the company dashboard shows the owner's menu. The main items are:

Table: Area | What it is for

Leads and Post updates appear only for companies Toolradar has enabled them for. Sponsored placements appears for every verified company while Toolradar has that tab open. The other items appear for every verified company.

A dofollow link on Toolradar comes only from the badge program. A badge is placed on the vendor's own site, Toolradar checks the link, and a link that qualifies is set to dofollow. Paid dofollow upgrades are discontinued. An approved claim does not change the ranking, and the Toolradar Data ranking score takes no advertising input.

Common mistakes

• Claiming with a personal address and expecting an admin to accept it. The manual form refuses personal providers.
• Adding the DNS record to the website host instead of the domain's DNS zone, so the record is never found.
• Pressing "Check now" minutes after adding a record, then assuming the method failed. Allow time for DNS.
• Letting the confirmation link expire, then clicking an old copy of it.
• Submitting a second claim for the same company after an admin rejection, which the claim page does not allow (a request that timed out unconfirmed can be sent again).
• Forwarding a verification email or link to an agency or a freelancer as a way to hand over access. Give access through the team page instead.
• Treating an approved claim as proof that every product detail is correct. The company dashboard shows what the listing says, and the product data still needs a source for each correction.
• Trying to claim a product that is not listed. Submit it first, as described in how to list software.
• Expecting a claim to change a product's ranking or to bring an AI assistant recommendation. A claim is an access decision, not a ranking input.

Example (fictional company)

Example (fictional company): Lumen Ops, a scheduling tool for field teams, runs on the domain lumenops.example. Maria, its product manager, finds the record at /companies/lumen-ops, but her login is a personal Gmail address, so the verified-email route is closed to her. She signs in and opens the claim page, then asks the IT contact to add the DNS TXT record shown under "Verify instantly".

The IT contact adds the record to the company's DNS zone. Maria presses "Check now" twenty minutes later and sees "We could not find the verification token yet", because DNS had not propagated. She waits, presses "Check now" again, and sees "Verified. You now manage this profile." The page sends her to /company, where she is the owner, and she invites a colleague from the team page. Had the DNS record not been an option, she would have used the manual form with her work address on the domain and clicked the link in her inbox within 7 days.

What our claim records show

Our data: at 16:40 UTC on 5 November 2026, Toolradar's read-only database snapshot contained 202 claim requests created from 1 January through 5 November 2026: 95 currently approved, 95 rejected and 12 pending. The aggregate CSV and method show the query and date window. These are request statuses at one moment, not independent companies or completed verification steps.

A company can have requests from different users. The snapshot does not say why any request was approved or rejected, when a decision occurred, how long review took or whether a company was ultimately claimed through another route. Pending requests may later change status. Older requests and requests created after the window are excluded. Do not use these counts as an approval probability or a promise about a new request.

Frequently asked questions