StrictSEORequest free access

Free browser-only SEO tool

On-Page SEO & AEO Analyzer

Read the page you are viewing with the StrictSEO extension, or analyze pasted HTML. Get direct findings without uploading page content, creating an account, or accepting a made-up SEO score.

Runs locallyNo accountFix guides includedJSON + CSV export

Best experience

Analyze the page you are viewing.

Request the free private StrictSEO beta, install it, open a public page, and select the extension icon. Its live-review panel stays beside the page, refreshes during same-site navigation, and saves suggestions for JSON, CSV, or Markdown export.

Work in progressThis unpacked Chrome extension is an early beta for testing. Its interface, permissions, and behavior may change before a stable release.
Request free Chrome extension access Read the full installation and privacy guideOpen the step-by-step installation guide
  1. 1Extract the package sent by email.
  2. 2Open chrome://extensions and enable Developer mode.
  3. 3Choose Load unpacked, then select the unzipped folder.
  4. 4For localhost, open Extension options and select Local testing.
  5. 5Select StrictSEO, keep the side panel open, and browse the site.

No page snapshot is uploaded or stored by StrictSEO.

No extension?

Paste or upload HTML.

Work in progressThe StrictSEO Chrome extension is an unpacked beta intended for local evaluation. Expect changes before a stable release, and avoid sensitive pages unless local processing is acceptable.

Local extension installation

Install the audited Chrome extension in six steps.

StrictSEO Page Analyzer · Work-in-progress betaVersion 0.8.0 · Manifest V3Request free private accessComplete requests receive the free beta package and matching SHA-256 checksum by private email.Open step-by-step installation guide
  1. 01

    Request access and extract

    Submit the required early-access information. After StrictSEO checks the request for completeness, the free private beta software and checksum are sent by email. Save both, verify the checksum, then extract the package. Chrome loads the extracted extension folder, not the package file.

  2. 02

    Open Chrome extensions

    Enter chrome://extensions in Chrome’s address bar. This is a browser page, so it must be typed or pasted into the address bar rather than opened as a normal website link.

  3. 03

    Enable Developer mode

    Turn on Developer mode in the upper-right corner of the Extensions page. This reveals the controls for installing an unpacked local extension.

  4. 04

    Load the extracted folder

    Choose Load unpacked and select the extracted folder that contains manifest.json. StrictSEO opens a welcome page explaining how to pin the green S and run your first analysis.

  5. 05

    Choose the report target

    The production analyzer is selected by default. To test the local StrictSEO site, open the extension’s Details page, choose Extension options, and select Local testing.

  6. 06

    Start live review

    Pin the green S from Chrome’s puzzle-piece Extensions menu. Open an HTTP or HTTPS page and select StrictSEO. Keep the side panel open while navigating within that website.

Default

Use the production analyzer

Choose Production in Extension options. Reports open at https://strictseo.com. No local server is required.

Development

Test your local StrictSEO build

Run npm run dev from the StrictSEO site folder, confirm port 3114 is ready, then choose Local testing in Extension options.

Required integrity check

Verify the private versioned package.

Every supplied release includes a SHA-256 checksum. Confirm the filename, version, full digest, and archive integrity before installation.

macOS or Linux

shasum -a 256 -c supplied-checksum-file.sha256

Windows PowerShell

Get-FileHash supplied-package-file -Algorithm SHA256For PowerShell, compare the complete result with the supplied checksum or release manifest.

Permission and privacy review

What the extension can—and cannot—access.

Security review completed July 13, 2026 for version 0.8.0. No audit can promise zero risk, but this build has a narrow, testable data flow and no network-upload path.

activeTabTemporary access to the page you deliberately analyze after clicking the extension icon. It is not permanent access to every website.
scriptingRuns the packaged snapshot function in that active tab. No downloaded or remotely hosted code is executed.
storageKeeps the production/local preference, current snapshot, and up to 50 page-level suggestion reports in temporary Chrome session storage.
sidePanelKeeps page findings visible beside the website while you navigate and review suggestions.
StrictSEO + localhostAllows the one-time bridge to deliver the snapshot only to strictseo.com or the fixed localhost:3114 development address.
User activates reviewRendered-page snapshotLocal suggestionsSide panelJSON, CSV, or Markdown

What is read

Sanitized page URL, metadata, headings, bounded paragraph text, links, image and schema evidence, semantic landmarks, responsive-layout observations, and aggregate Resource Timing values exposed by the page.

What is not read

Form values, passwords, cookies, browsing history, browser storage, keystrokes, screenshots, network traffic, files, contacts, location, microphone, or camera.

How exposure is reduced

Incognito use is disabled. Credentials, URL fragments, sensitive query values, email and telephone destinations, and non-HTTP URL payloads are redacted. One-time snapshots expire after two minutes.

Important limitation

Visible page text can itself contain personal or confidential information. The current build keeps that snapshot inside Chrome and does not upload it, but avoid sensitive pages unless local processing is acceptable.

Permission behavior follows Chrome’s documentation for activeTab, session storage, and Manifest V3.

Update the local extension

Request or receive the newer SemVer release, verify it, and unzip it into a fresh versioned folder. Open chrome://extensions and choose Reload after selecting the new folder. Confirm the displayed version matches the supplied release manifest.

Remove it completely

Open chrome://extensions, choose Remove on the StrictSEO extension card, confirm removal, and delete the extracted folder and supplied package from your computer.

What it checks

Observable signals, clearly separated from judgment.

The report covers elements available in the rendered page snapshot. Every result shows the observed evidence, a next action, and a direct link to a detailed StrictSEO repair guide.

01

Technical page signals

Title, description, canonical, robots directives, language, viewport, hreflang, HTTPS, Open Graph fields, headings, links, images, and JSON-LD syntax.

02

Evidence and repair guidance

A prioritized action list, search and social previews, link and heading evidence, readable JSON-LD blocks, and direct issue-library links with fix and verification steps.

03

Honest limitations

No rank estimate, traffic forecast, keyword score, backlink claim, or promise that a search engine will select a particular snippet or rich result.

Need more context?

Learn the controls, then choose the next evidence layer.

The operating manual explains every analyzer view, exact-location evidence, export, crawl, Lighthouse, and troubleshooting workflow. The SEO and AEO audit guide separates page checks, crawl and server checks, and external search data.

Read the analyzer manual

Local by design

Your page snapshot stays in the browser.

The extension uses temporary Chrome session storage only long enough to pass the active page snapshot into this report. Delivery requires a one-time token and a trusted analyzer origin. The snapshot is removed after delivery and rejected after two minutes.

Sensitive URL values are redacted before analysis. Downloaded reports are created by your browser and saved only when you choose a download button.

Tool FAQ

What the browser-only analyzer can do.

Can the analyzer read a webpage from its URL?

The private early-access StrictSEO browser extension reads the active tab and sends a temporary page snapshot directly to the analyzer in your browser. The website does not crawl arbitrary URLs or upload the snapshot to a server.

Does StrictSEO store the page being analyzed?

StrictSEO does not receive or persist the snapshot. The extension keeps one snapshot in Chrome session memory behind a one-time token, removes it after delivery, and rejects it after two minutes. Chrome also clears session storage when the extension or browser session ends.

Is the StrictSEO extension safe to install?

Version 0.8.0 uses active-tab access, packaged code, temporary session storage, fixed report origins, and redacted URL values. It has no page-snapshot upload API or remote-code path. No extension is risk-free, so avoid private pages when local processing of visible text would be inappropriate.

What can this tool check?

It checks rendered metadata, indexability directives, headings, content and answer extraction, author and source signals, links, images, JSON-LD, hreflang, social previews, mobile layout, HTTPS, DOM size, and locally exposed performance evidence. During navigation it also compares reviewed pages for repeated issues, duplicate metadata, canonical collisions, and captured internal-link gaps.

What can this tool not verify?

This rendered-page analyzer cannot prove server response codes, HTTP headers, robots.txt behavior, field Core Web Vitals, rankings, backlinks, search volume, traffic, AI mentions, or search-engine selection. The separate source-run StrictSEO Browser now provides bounded crawl evidence and local Lighthouse lab reports, but those still do not replace field or search-platform data.

Where can I learn how to fix a finding?

Every finding links to the StrictSEO issue library. Each reference explains the observed signal, why it may matter, a repair workflow, and how to verify the result without implying a ranking guarantee.