Run Your First Website Analysis

Your task is to run website analysis on the page you are viewing and read the results without treating them as verified company data.

AGNURA AI Assistant analyzes the active tab. Open a public website, open the popup, and AGNURA collects public signals from that page and related same-origin requests. No AGNURA credits is required for this step.

If AGNURA is not installed yet, use Install AGNURA From the Chrome Web Store. For the full action map, use AGNURA Feature Reference by App and Action.

Prerequisites

• Chrome with AGNURA installed and enabled
• A normal http or https page in the active tab (a public prospect site is ideal)
• Network access for sitemap and related probes (offline you may still see on-page signals)

You do not need AGNURA sign-in and credits for analysis. Sign in when you want AI email or channel drafts later (Sign In and Use AGNURA AI Credits).

Direct answer

1. Open the prospect website in Chrome.
2. Click the AGNURA icon.
3. Wait for the popup to finish analysis (or show a clear error).
4. Read platform, contacts, and other rows.
5. Use the header reload control when you need a fresh live run instead of the cached snapshot.

Exact steps

1. Pick a good tab

Use a normal website URL, for example a company homepage or product page.

Avoid these for a first test:

• chrome:// pages
• The Chrome Web Store listing page
• Many PDF-only or special viewer pages where injection is limited

Make sure that tab is focused. AGNURA follows the active tab, not a background tab.

2. Open the popup

1. Click the AGNURA toolbar icon (pin it if it is hidden under Extensions).
2. The popup starts analysis for that tab automatically on open.

You should see loading, then results. Current builds should show a Failed: line instead of spinning forever if something breaks (there is a popup-side timeout).

3. Read the main result areas

Exact labels can vary slightly by build, but a first run usually includes:

Area	What it means	How to read it
Platform / stack hint	Best-guess CMS or commerce platform	Note the confidence score (0 to 100). Higher means more matching signals, not proof.
Page title / description	From the open document	Useful context for outreach; still verify on the page.
Contacts	Emails, phones, and related fields when found	Heuristic. Check the live site before you email anyone.
Social / chat / marketing clues	Public widgets and links	Presence clues, not a full tech audit.
Pages / sitemap count	Estimate from /sitemap.xml walking when available	Caps apply on large sites. “Not detected” is common when sitemaps live elsewhere.
Last fetched / cache hints	When this snapshot was built	See cache section below.

Under the platform icon, SEO Analysis opens a separate on-page report. That is the next setup guide after this one. Analysis itself does not use managed AI.

4. Optional exports

When results are ready you can:

• Copy JSON or Download JSON for the analysis snapshot
• Continue to templates / Open in Gmail only if contacts and templates allow it
• Open SEO Analysis for the current-page audit

Treat exported emails and phones as sensitive business data under your own policy.

Cache, reload, and confidence

One-hour analysis cache

For http(s) pages, AGNURA may store the merged result in chrome.storage.local for about one hour for the same normalized URL (origin + path + query; hash ignored; trailing slash normalized).

Situation	What happens
Reopen popup on the same URL within an hour	Popup can show Cache: yes and reuse the snapshot (no full live refetch)
Different path or query on the same site	New analysis path
After about one hour	Live analysis again
Header reload	Clears that tab’s analysis cache and the origin sitemap snapshot, then runs a full live analysis

Use reload when the page changed, contacts look stale, or you need a fresh page text excerpt for later AI email.

Confidence labels

Platform confidence is a heuristic score. Hybrid sites can look like two stacks at once. “Unknown” is a valid outcome.

Contact rows can miss emails behind images, widgets, or uncommon URL patterns. They can also include false positives. Always verify on the page before outreach.

What success looks like

Check	Expected
Tab	Public http(s) site focused
Popup	Opens and finishes with results or a clear Failed line
Platform row	Name and/or confidence you can interpret
Manual check	You spot-checked at least one contact or claim on the live page
Reload	Header reload produces a new Last fetched time when you need live data

Limits and non-goals

Website analysis does not:

• Crawl your full site like a desktop crawler product
• Guarantee accurate contacts, platform labels, or company facts
• Use managed AI by itself
• Replace Apollo enrichment APIs (Apollo capture is a separate visible-row scrape on Apollo.io)
• Work the same on every blocked or unusual page type

Sitemap counts only walk /sitemap.xml (and nested files discovered from there) with safety caps. Alternate paths such as /wp-sitemap.xml are not probed as a substitute index in the current product.

Common problems

Problem	What to try
Empty or generic results	Confirm the tab is http(s), not chrome://; hard-refresh the page; popup reload
Injection failed	Switch to a normal website; reload the extension on chrome://extensions
Missing email	Open the contact/about page in the tab and analyze again; verify the address is visible in HTML text
Stale data after a site change	Use popup reload (clears the one-hour snapshot)
Sitemap “Failed to fetch” offline	Expected on a live run without network; open once online to seed cache
Endless spinner (older builds)	Update AGNURA; current builds should time out with a Failed line

Related guides

• Install AGNURA From the Chrome Web Store
• Sign In and Use AGNURA AI Credits
• What Is AGNURA?
• AGNURA Feature Reference by App and Action
• AGNURA Privacy in Plain Language

Soft next step

Run analysis on one real prospect homepage, verify one contact on the page, then open SEO Analysis from the platform area when you want the current-page SEO report.

Add to Chrome