Live page review
Open a page, click StrictSEO, and see metadata, headings, answer clarity, schema, links, images, trust signals, and fix guidance without setting up a project first.
Chrome extension beta · Private early access
StrictSEO Chrome ExtensionFind SEO & AEO issues as you browse.
Open a page, click StrictSEO, and review its metadata, headings, links, schema, answer clarity, and trust signals. Keep browsing to spot patterns across pages. Use StrictSEO Browser when you need saved crawls, Search Console opportunities, fix tracking, Lighthouse, or accessibility evidence.
Work-in-progress Chrome extension. The beta software is free and shared by private email after an access request is complete.
Working beta capabilities
- 72 page checks
- 50-page extension sessions
- 500-page bounded crawl
- Search Console outcomes
- Lighthouse + axe-core
Software overview
One toolkit for finding, fixing, and verifying SEO and AEO issues.
StrictSEO is built for the messy middle of real SEO work: you are already looking at a page, something feels weak, and you need evidence precise enough for a writer, developer, consultant, or client to act on.
The Chrome extension gives immediate rendered-page feedback while you browse. StrictSEO Browser adds local crawls, server evidence, Search Console opportunities, fix tracking, Lighthouse, and axe-core when the decision needs more proof.
Exact fix evidence
Find the affected selector, nearby text, sanitized DOM excerpt, inventory position, and relationship context behind a finding so the issue is easier to reproduce and repair.
Local site investigation
Use StrictSEO Browser for bounded crawls, HTTP responses, redirects, robots and sitemap evidence, internal-link architecture, Lighthouse, and accessibility checks.
Traceable outcomes
Save actions, verify implementation with newer scans, and compare later Search Console clicks, impressions, CTR, and position without pretending correlation is causation.
Where is the manual?
The complete operating manual is now a permanent top-nav item.
It covers the Chrome extension, public analyzer, StrictSEO Browser, exact DOM evidence, local crawls, Search Console workflows, fix tracking, exports, Lighthouse, axe-core, privacy boundaries, and troubleshooting.
Two workflows, one engine
Start on the page. Crawl the site only when you need to.
The extension reports what the rendered page exposes. The local browser adds saved crawl, server, Search Console, Lighthouse, and accessibility evidence. Both use the same issue names and fix guides.
Working beta
Chrome extension
Review pages while you browse
Click StrictSEO on the page you are viewing. The side panel refreshes during same-site navigation and builds a temporary multi-page review without asking you to configure a project.
Best forWriters, editors, consultants, and quick client reviews
- 72 rendered-page SEO and AEO checks
- Up to 50 reviewed pages per temporary session
- Live findings, filters, fix guides, and exports
Working beta
StrictSEO Browser
Investigate the site more deeply
Launch the local browser when the work needs a saved crawl, server evidence, Search Console opportunities, fix tracking, Lighthouse reports, or automated accessibility checks.
Best forTechnical audits, template diagnosis, and broader site reviews
- Up to 100 browsed pages and a 25–500 page bounded crawl
- HTTP, redirect, robots.txt, sitemap, depth, and inlink evidence
- Read-only Search Console evidence, fix plans, and later-period outcomes
- Lighthouse, axe-core, Readability, and complete report downloads
Why the shared engine matters
A title issue, AEO opportunity, or schema warning means the same thing in the website analyzer, extension, local browser, saved export, and StrictSEO repair guide.
Why an extension
SEO issues are easiest to fix when you are already on the page.
A crawler or enterprise suite is useful later, but a lot of everyday SEO work starts with one page: a draft, a landing page, a client URL, or a competitor example.
StrictSEO puts the first check in the browser so solo SEOs can inspect the page, decide what matters, and export a clear report without opening a heavy platform.
Audit the page you are already viewing
Click the extension on an HTTP or HTTPS page and send a bounded page snapshot into the StrictSEO analyzer.
Run a broad rendered-page audit
Evaluate 72 deterministic checks across technical, content, AEO, trust, links, images, schema, international, social, mobile, security, and local performance evidence.
Build a site view while you browse
Compare reviewed pages for recurring issues, duplicate metadata, canonical collisions, and captured internal-link gaps without a background crawler.
Private early access
Request the Chrome extension build for your workflow.
Direct downloads are not published. Tell StrictSEO which site, product, operating environment, and SEO workflow you need to evaluate. Once the required request information is complete, StrictSEO emails the free private beta software package and checksum without creating a product account.
Local app beta · Source fallback
Move from page review to technical site investigation.
StrictSEO Browser adds the evidence and history that an active-tab extension cannot provide: a saved bounded crawl, HTTP responses, redirect paths, robots.txt and sitemap discovery, broken internal destinations, read-only Search Console opportunities, accessibility checks, and downloadable Lighthouse reports.
Use it to identify which page to improve, save the action and baseline, verify the technical repair, then compare a later Search Console period to see whether traffic evidence moved.
After receiving and extracting the free versioned source package:
npm install --prefix local-browsernpm --prefix local-browser startThe source package requires Node.js 22+ and Chrome or Chromium. A no-terminal macOS app build exists for local evaluation, but public distribution still requires Developer ID signing, notarization, release hosting, and automatic-update design.
Working feature set
See what each tool can observe.
Both interfaces run the same page checks. Switch to the local browser when the decision needs saved history, Search Console evidence, an HTTP response, internal crawl paths, Lighthouse, or axe-core.
| Capability | Chrome extension | Local browser | Value |
|---|---|---|---|
| Rendered-page SEO and AEO analysis | 72 deterministic checks | The same 72-check engine | Review metadata, indexability, headings, content clarity, trust signals, links, images, schema, social previews, mobile behavior, security, and locally exposed performance evidence. |
| AEO and answer clarity | Included | Included | Find missing direct answers, unclear openings, weak question coverage, limited reader aids, and evidence or attribution gaps without pretending these checks guarantee citations. |
| Browsed-site patterns | Up to 50 pages | Up to 100 pages | Expose repeated template issues, duplicate titles, descriptions and H1s, canonical collisions, language coverage, and captured internal-link gaps as you navigate. |
| Bounded same-origin crawl | Not included | 25–500 pages | Discover site-wide technical weaknesses with explicit limits, configurable depth, robots.txt rules, sitemap seeds, crawl paths, and affected URL lists. |
| Server and discovery evidence | Rendered page only | Included | Check response status, headers, redirect chains, robots rules, XML sitemaps, inlinks, orphan candidates, broken internal destinations, and response timing. |
| Lighthouse and accessibility | Local page heuristics | Lighthouse + axe-core | Add controlled performance, accessibility, SEO, and best-practice lab evidence while keeping it separate from field Core Web Vitals and ranking claims. |
| Search opportunities and outcomes | Not included | Search Console sync or CSV | Prioritize pages from first-party clicks, impressions, CTR, and position; save an action and compare a later period without presenting correlation as causation. |
| Local project and fix verification | Temporary browser session | Saved on this device | Compare bounded crawls, track planned and fixed work, verify technical checks on a newer scan, and keep search outcomes separate from implementation proof. |
| Actionable deliverables | JSON, CSV, Markdown, copy | JSON, CSV, Markdown + Lighthouse HTML/JSON | Keep the observed evidence, priority, next action, affected pages, and a permanent StrictSEO repair guide together when work is handed to a client or teammate. |
From signal to fix
Each finding keeps the evidence and next action together.
Save the observed value, affected pages, fix instructions, and verification step in the same report you hand to an editor, developer, client, or teammate.
- 01
See the evidence
Each finding starts with what StrictSEO actually observed on the rendered page, in the browsed session, or during the explicit local crawl.
- 02
Separate fixes from reviews
Confirmed problems, judgment calls, and passed checks stay distinct so a heuristic is not presented as a guaranteed ranking factor.
- 03
Know the next action
Every actionable finding includes a concrete recommendation and affected-page context instead of stopping at a warning label.
- 04
Verify the implementation
Rerun the page or crawl after the change. StrictSEO separates checks that now pass from URLs or checks that were not re-evaluated.
- 05
Measure the later outcome
Sync a later Search Console period to compare clicks, impressions, CTR, and position while keeping demand, competition, and seasonality in view.
Built-in explanations
See why a check fired, how to operate the tool, and how to verify the fix.
The operating manual teaches every control and workflow. The SEO and AEO audit guide shows which evidence to collect first. The issue library explains each signal, repair, and follow-up test.
A practical improvement loop
Find the weakness. Fix it. Verify it. Measure what changed.
Start on the page, expand to the site only when necessary, and keep the evidence, recommendation, implementation note, verification, and later outcome in one local project.
- 1
Spot the obvious blockers
Check metadata, headings, image alt coverage, links, and schema before you spend time on deeper research.
- 2
Prioritize what to fix
Use the report's fix, review, passed, and context labels to decide what deserves action now.
- 3
Record and verify the fix
Add work to the local fix plan, record what changed, then use a newer page scan or crawl to verify the implementation.
- 4
Measure whether it helped
Use read-only Search Console evidence or CSV imports to compare a cleanly later period and keep the result traceable without claiming false causation.
Privacy and safety boundary
The beta is useful because it is narrow.
The extension uses user-initiated active-tab access and temporary Chrome session storage. StrictSEO Browser keeps project evidence locally; its optional Search Console connection requests read-only access and never includes Google credentials in reports or StrictSEO.com requests.
Important limit: visible page text can still contain sensitive information. Use the beta only on pages where local browser processing is acceptable.
Read the permission reviewData boundary
Local audits and first-party search evidence cover the workflow. Web-scale indexes still need external data.
StrictSEO can inspect rendered pages, crawled site evidence, local lab tests, and first-party Search Console clicks, impressions, CTR, and average position. Licensed search volume, scheduled location-based rankings, backlinks, competitor traffic, and AI mentions require separate data sources.
Keyword and SERP datasets
Search volume, keyword difficulty, ranking history, SERP features, and query gaps require licensed or first-party search data integrations.
PlannedBacklink and competitor indexes
External backlinks, referring domains, link intersect, organic competitor traffic, and market estimates require a web-scale crawl index.
PlannedRank and AI visibility tracking
Scheduled rankings, AI mentions, citations, prompt coverage, alerts, and trends require persistent projects and regularly refreshed external observations.
PlannedLaunch FAQ
What the Chrome extension does now.
How do I access the StrictSEO beta?
The public analyzer remains available on StrictSEO.com. The Chrome extension and StrictSEO Browser are free private beta software: submit the required contact form details, and once the request is complete StrictSEO replies by email with the appropriate versioned package and checksum. Direct download links are not published on the site.
What is the difference between the extension and StrictSEO Browser?
The Chrome extension is the fast workflow: click it on a page, keep browsing that site, and collect live page findings and cross-page patterns. StrictSEO Browser is the deeper local app: it uses the same analysis engine and adds saved crawls, response and sitemap evidence, Search Console opportunities and later-period outcomes, axe-core checks, and Lighthouse lab reports. The source package requires Node.js 22+ and Chrome or Chromium; the macOS app removes the Node and terminal setup.
Who should use the beta?
The beta is for solo SEO consultants, small in-house teams, publishers, and small agencies that need fast page-level checks without opening a heavyweight enterprise platform.
Does the extension upload my page content?
The current audited build has no snapshot upload API. After you select StrictSEO, it reviews the active page locally, refreshes suggestions during same-site navigation, and keeps downloadable page reports only in temporary Chrome session storage.
What are the limits of the beta?
The extension analyzes pages you deliberately visit and does not run a hidden crawl. StrictSEO Browser can start an explicit bounded crawl, run Lighthouse, and use first-party Search Console clicks, impressions, CTR, and average position. It still does not supply licensed search volume, location-based rank tracking, external backlink indexes, competitor traffic estimates, field Core Web Vitals, or guaranteed search-engine and AI-answer visibility.
Request a private, versioned StrictSEO build for your site and operating environment.