How to Find Public Business Contact Details on a Website
Find public emails, phones, and location hints on a company site: what to check by hand, what AGNURA scans on the tab and same-origin contact pages, and how to use contacts ethically.
You will be able to find public business contact details on a company website, verify them on a live page, and decide whether they are fair to use in outreach.
This is website research, not a people database. You only collect what the site already publishes. Hub context: What Is Website Intelligence for Sales and Outreach?. Broader pre-email flow: How to Research a Prospect’s Website Before Writing an Email.
When this applies
Use this workflow when:
- You have a public company URL (homepage, product page, or contact page)
- You need an email, phone, or location hint the business chose to show
- You will verify every address before you put it in a draft
Do not use this to hunt personal inboxes, scrape private data, or bypass login walls.
Prerequisites
- Desktop Chrome (or Chromium) and a normal
http/httpstab - The company’s public site
- Optional: AGNURA installed (Install AGNURA From the Chrome Web Store)
- Optional later: a saved email template if you want AGNURA’s Send Email path in Gmail (needs a detected email + template; you still review and send)
Direct answer
- Open the homepage or the contact/about page if you already know it.
- Check footer, header, and Contact / About links by hand.
- Prefer
mailto:/tel:links and clear text over guesses. - Optionally run AGNURA on the tab to collect candidates from the page and common same-origin contact/about URLs.
- Open any promising contact URL yourself and confirm the address is real.
- Skip noreply, placeholder, and anything you cannot defend.
- Use contacts only for legitimate, human-reviewed outreach.
Step-by-step
1. Start on the right public page
Open the homepage or the page that represents the business you will email. Avoid chrome:// pages, logged-in dashboards, and gated portals.
Expected result: You can see public footer/nav without signing in.
2. Do a fast human scan
Before any tool, look for:
| Place | What to look for |
|---|---|
| Footer | Email, phone, address, “Contact us” |
| Header / nav | Contact, Support, About, Help |
| Contact form page | mailto: links, visible support addresses |
| About / locations | Phone, store address, regional emails |
Click Contact or About when the label is clear. Many sites hide the real address off the homepage.
Expected result: You either see a contact or know which path to open next.
3. Prefer strong evidence over weak copy
| Stronger | Weaker |
|---|---|
mailto:hello@company.com | Email-looking text inside a marketing sentence |
tel:+1… link | A random digit string in a blog post |
Organization JSON-LD email / telephone | Image of an email (tools often miss this) |
| Clear support@ on a contact page | noreply@ or example.com placeholders |
If the only “email” is glued to footer labels (for example text jammed after the TLD), treat it carefully until you see a clean address on the page.
4. Optional: let AGNURA collect candidates
Keep the company tab focused. Open the AGNURA popup and wait for analysis (or reload for a live run). Product steps: Run Your First Website Analysis.
AGNURA’s contact pass (current product behavior):
| Source | What it can pick up |
|---|---|
| Current tab | JSON-LD organization/local-business fields; mailto: / tel:; email/tel-like form fields; plain text in footer/header/main/contact/about-ish regions; meta description tokens; postal hints from address-like blocks |
| Same-origin fetches | Up to 24 contact/about-style URLs (static list + up to 12 paths discovered from link text/path on the open tab). Each fetch ~2.5s max, credentials: "omit". Pending fetches can stop early once at least one email and one phone are found from those pages |
| Static path examples | /contact, /contact-us, /pages/contact, /about, /pages/about-us, /support, /get-in-touch, and similar |
| Output | Deduped emails and phones (capped for UI, about 20 each); optional address / city / state / country; confidence low / medium / high from how structured vs link/text evidence looks |
Filters drop many weak matches (image-like suffixes, domains such as example.com, and noreply-style locals). Filters are helpful, not perfect.
Expected result: The popup shows zero or more candidate emails/phones. Empty results are normal when contacts are image-only, bot-blocked, or on unusual URLs.
5. Verify on a live page you control
Treat every automated field as a candidate.
- If AGNURA listed an email, open the page where it should appear (footer or contact URL).
- If nothing showed but you know a contact page exists, navigate to that URL and run analysis again. The current tab is always scanned; fetches can miss 404s, 403s, non-HTML, or bot protection.
- Confirm phone digits match what you see.
- Confirm city/country before you localize a pitch.
Expected result: An “allowed contacts” note with only addresses you personally saw.
6. Choose what is fair to use
| OK for many B2B outreach cases | Avoid |
|---|---|
| Published sales@ / hello@ / info@ meant for inquiries | Personal staff emails harvested from unrelated pages |
| Support phone on a contact page | Numbers that fail a visual check |
| Public HQ address the site displays | Invented roles or “I found your private inbox” framing |
| One clear ask after you review the draft | Bulk spam, phishing, or harassment |
AGNURA’s docs warn: do not use the tool to harass, spam, or phish. Follow your own email law and the site’s published contact preferences. AGNURA does not auto-send.
7. Move to outreach only after verification
If you use AGNURA next:
- Send Email needs at least one detected email and a saved template. It opens Gmail compose; you edit and send.
- Generate AI Email (optional) needs AGNURA credits and email template prompt. It uses analysis context. You still review and send.
See How to Personalize an Outreach Email From Website Research.
Common failures and fixes
| Problem | Likely cause | Fix |
|---|---|---|
| No email in the popup | Contact only on an unusual path, image, or widget | Open the real contact page; analyze that tab |
| Email on site, still empty after analysis | Cached snapshot; fetch 404/403; SPA shell without mailto in live DOM | Popup reload; open contact URL directly; check Network for failed contact fetches |
| Phone found, email missing | Site publishes tel only | Use phone ethically or find another public channel; Send Email stays disabled without email |
| Weird false-positive digits or address | Plain-text regex noise | Discard anything you cannot see cleanly on the page |
| Confidence looks high, still wrong | Structured data + links can still be stale | Trust the live page over the label |
Verification checklist
- Contact appears on a live public page you opened
- Address is a business inquiry channel, not a noreply sink
- Phone digits match visible copy or a
tel:link - Location fields match footer/about if you will mention them
- Draft names only verified facts
- You will review before send (no auto-send)
Ethical use (short)
Public does not mean “do anything.” Use published business contacts for relevant, honest outreach. Prefer channels the site offers (contact form, published inbox). Stop if the site asks you not to solicit. Do not use extraction to build harassment lists or phishing targets. Handle any exports under your own data policy.
When to escalate to human judgment
- High-value deal: open contact/about yourself even if the tool looks complete
- Regulated industry or region: check counsel / compliance before cold email
- Only a form, no email: use the form or a different channel; do not invent an address
- Conflicting emails: prefer the contact page over a random footer match
How AGNURA helps this job
| Job | Without AGNURA | With AGNURA |
|---|---|---|
| Find candidates | Manual footer and contact clicks | Current page + same-origin contact/about probes |
| Structure results | Notes | Emails, phones, optional location, confidence |
| Start Gmail draft | Copy/paste | Template + optional AI draft from analysis (you send) |
| Keep proof | Screenshots | Local analysis snapshot / JSON export if you need it |
Compared with common alternatives
| Approach | Fit |
|---|---|
| Manual contact hunt | Highest control; slower |
| Enrichment / people databases | Different job; still verify website claims |
| Generic email finder tools | Often person-level; different risk profile |
| AGNURA on the active tab | Fast public-site candidates beside the page; verification still required |
Limits (product-true)
AGNURA contact extraction does not:
- Crawl the whole domain
- Read every alternate contact URL outside the static + discovered set
- Bypass bot protection or login walls
- Guarantee completeness or freshness
- Add a manual “type any To:” field when no email was detected (v1 Send Email stays disabled)
- Auto-send mail
County is not a separate field. Postal parsing can be incomplete.
Privacy: analysis contact fields stay in the extension’s local analysis path unless you later send context to managed AI for AI email or to your own webhook for Add Lead. See AGNURA Privacy in Plain Language.
Related guides
- What Is Website Intelligence for Sales and Outreach?
- How to Research a Prospect’s Website Before Writing an Email
- Run Your First Website Analysis
- How to Personalize an Outreach Email From Website Research
- How AGNURA Detects Website Platforms and Themes
Soft next step
Pick one known company site, find its contact page by hand, then run AGNURA from the homepage and from /contact (or /pages/contact) and compare what appears. Install when you want that in the popup:
Try AGNURA in Chrome
Draft in Gmail, LinkedIn, WhatsApp, and Reddit. You review every message before send.
Add to Chrome