Search our knowledge base, browse topics, or send us a message — we'll get back to you within 24 hours.
Send us your question or issue and we'll reply with a detailed solution within 24 hours, Monday–Friday.
Send a MessageMost questions are answered here. Browse by category — installation, features, troubleshooting, privacy, and export.
Go to FAQsFound something broken? Tell us exactly what happened and we'll fix it in the next release — usually within a week.
Report BugClick any category to jump to the relevant FAQ section.
How to install from the Chrome Web Store, enable the extension, and load it as an unpacked developer extension.
How to analyze any URL, use the dashboard, understand your E-E-A-T score, and navigate the full report.
How the E-E-A-T score is calculated, what each dimension means, and how to interpret the weighted scoring model.
How to export as CSV, JSON, PDF, and how to send a full report summary to your email address.
Fixing a stuck audit, CORS errors, the extension not loading, or the dashboard not showing results.
What data we collect (none), why each Chrome permission is required, and how your analyses are stored locally.
Once the extension is live on the Chrome Web Store, click Add to Chrome on the listing page, then confirm by clicking Add extension in the popup. The extension icon will appear in your Chrome toolbar.
If you don't see it, click the puzzle piece icon (Extensions) in the toolbar and pin EEAT Analyzer to keep it visible.
1. Download and unzip the extension files.
2. Go to chrome://extensions in Chrome.
3. Enable Developer mode (toggle in the top-right corner).
4. Click Load unpacked and select the unzipped folder.
The extension will be loaded and the icon will appear in your toolbar. Click Reload after making any changes.
Yes — any Chromium-based browser supports Chrome extensions. EEAT Analyzer is tested on Chrome and should work on Microsoft Edge, Brave, Vivaldi, and Arc. We officially support and test only Chrome; other browsers may have minor differences.
Current tab: Navigate to any page in Chrome and click the EEAT Analyzer icon in the toolbar. Click Analyze in the popup to start a full audit of that page.
Any URL: Open the extension popup and paste any public URL into the Analyze any URL field. Press Enter or click Go → to audit it without visiting the page.
From the Dashboard: Open the Dashboard, paste a URL in the large search bar at the top, and click Analyze Now.
It works on every public website — WordPress, Shopify, Webflow, Next.js, Nuxt, SvelteKit, plain HTML, news sites, portfolios, SaaS landing pages, and more. There are no platform restrictions whatsoever.
Click the extension icon in the toolbar to open the popup, then click the Dashboard button. The dashboard opens in a new Chrome tab showing all your saved analyses, score cards, filters, and the URL analyzer.
The overall score uses a weighted formula: E-E-A-T 35% + Technical 20% + Content 20% + Meta Tags 15% + Social 10%. Each dimension is scored 0–100 individually, then combined. The weights reflect the relative importance Google assigns to each signal.
E-E-A-T itself is broken into four sub-dimensions: Experience (25pts), Expertise (25pts), Authoritativeness (28pts), and Trust (25pts).
E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) is Google's quality framework used by Search Quality Raters to assess content. The "Experience" dimension was added in 2022, rewarding content that demonstrates real first-hand knowledge.
It accounts for 35% of the score because it is the broadest and most complex signal — covering author credentials, schema markup, citations, HTTPS, trust pages, and more.
The most common reasons are missing structured data (Article + Person schema account for 11 points), no author bio section, or missing Open Graph tags. Check the Issues & Fixes tab — every issue is listed with its exact point value and a step-by-step fix.
E-E-A-T signals like author credentials and first-hand experience language are also significant. A great page with no author byline or schema markup will score lower than expected.
On any analysis report page, click the Export button in the top-right corner, then select Export as CSV. The CSV includes your overall scores, every issue found, the SEO impact of each issue, and the numbered fix instructions.
In the Dashboard, there is an Email Full Report bar. Enter your email address and click Send Report. This opens your default email client (Gmail, Outlook, etc.) pre-filled with a summary of all your analyses — scores, issue counts, and URLs. You then send it from your own email account.
Note: Email delivery in v1.0 uses your local mail client. A direct server-side delivery feature is planned for v1.1.
This usually means the background service worker timed out or the site blocks external requests. Try these steps:
1. Navigate directly to the page in Chrome first, then click Analyze from the extension popup. This uses the live DOM instead of fetching externally.
2. Reload the extension: go to chrome://extensions, find EEAT Analyzer, and click the reload circular arrow icon.
3. Some pages (behind login, Cloudflare protection, or heavy SPAs) cannot be analyzed via URL fetch. Navigate to the page directly and use the popup's Analyze button instead.
This is typically caused by a stale extension context. Go to chrome://extensions, find EEAT Analyzer, and click the reload icon. Then try opening the dashboard again.
If the issue persists, disable and re-enable the extension. All your saved analysis data is stored in chrome.storage.local and will not be lost when reloading or re-enabling.
Partial results appear when the HTML fetch succeeded but was incomplete, or when the page uses heavy client-side rendering (React, Vue, Angular SPA) that produces minimal HTML at fetch time. In these cases:
Navigate to the page directly in Chrome, wait for it to fully load, then click Analyze from the popup. This analyzes the live, fully rendered DOM rather than the raw HTML fetch.
No. We have no server-side component that receives any data. All SEO analysis runs entirely within your browser's extension context. Analysis results are stored only in Chrome's local chrome.storage.local — on your device, accessible only to you.
The <all_urls> permission is required so the background service worker can fetch HTML from any URL you explicitly request. Without it, the extension could only analyze one specific domain.
This permission is only used when you actively request an analysis. It is never used passively while you browse.
Open the Dashboard, then click the Clear All button in the top-right corner. This permanently removes all stored analysis results from chrome.storage.local. You can also delete individual analyses by clicking the ✕ button on any analysis card.
Try these before sending us a message — they resolve 90% of reported problems.
Go to chrome://extensions, find EEAT Analyzer, and click the circular reload arrow. This resets the background service worker and clears any stale state.
For pages behind login or heavy JavaScript frameworks, go to the page in Chrome and wait for it to fully load. Then click Analyze from the popup — this uses the live DOM rather than a URL fetch.
Fixes: Partial results, SPA pagesEnsure the URL starts with https:// or http://. Paste the full URL including the path. URLs behind authentication, VPN, or on localhost cannot be fetched externally.
EEAT Analyzer requires Chrome 100 or later (Manifest V3 support). Go to chrome://settings/help to check and update. The extension uses modern Chrome APIs not available in older versions.
Couldn't find your answer above? Our team responds to every message within 24 hours, Monday to Friday. Please include as much detail as possible so we can help you quickly.