StrictSEORequest free access

Text-only user manual

Install the StrictSEO Chrome extension beta.

Use these step-by-step instructions to request the free private beta, verify the supplied SemVer package, load it in Chrome, choose production or localhost, and run your first on-page SEO and AEO report.

Work in progressVersion 0.8.0 is an early, unpacked beta for evaluation, not a stable Chrome Web Store release. The interface, permissions, report fields, and installation steps may change.
Request free private accessRead the full operating manual

Before starting

Know which setup you are testing.

Production mode opens reports on https://strictseo.com. Local testing mode opens http://localhost:3114 and requires npm run dev to be running from this site folder.

Chrome 116 or newerExtracted extension folderDeveloper mode enabledHTTP or HTTPS page to analyzePort 3114 only for detailed local reports

Install summary

The short version.

Request free access, verify the supplied versioned package, extract it, enable Developer mode, load the extracted folder, pin StrictSEO, then select it on a page to open the live-review side panel.

  1. 1Request and verify the free beta package
  2. 2Extract the folder
  3. 3Open Chrome extensions
  4. 4Load the unpacked extension
  5. 5Choose production or local testing
  6. 6Start live review
01

Request and verify the free beta package

Submit the required early-access details. After StrictSEO checks the request for completeness, the free private beta software and its matching SHA-256 checksum are sent by email.

  1. Confirm the package filename contains the SemVer release named in the reply.
  2. Run the supplied SHA-256 check and test the package before extracting it.
  3. Do not repost the private email link or try to load the package file directly in Chrome.
02

Extract the folder

Unzip the file and locate the extracted StrictSEO-Chrome-Extension-VERSION folder that contains manifest.json.

  1. Chrome needs the extracted folder, not an individual file.
  2. The folder should include manifest.json, background.js, bridge.js, options.html, options.js, options.css, SECURITY.md, README.md, and icons.
  3. Move the folder somewhere stable before loading it, because Chrome references that local folder.
03

Open Chrome extensions

Open Chrome and type chrome://extensions into the address bar.

  1. This browser page must be entered in the address bar.
  2. Turn on Developer mode in the upper-right area of the Extensions page.
  3. After Developer mode is enabled, Chrome shows the Load unpacked button.
04

Load the unpacked extension

Choose Load unpacked and select the extracted strictseo-analyzer folder.

  1. Select the folder that contains manifest.json.
  2. Chrome should add StrictSEO Page Analyzer and automatically open its welcome page.
  3. Follow the welcome page to find StrictSEO in Chrome’s puzzle-piece Extensions menu and pin the green S.
  4. If Chrome reports that the manifest is missing, you selected the wrong folder level or the package was not fully extracted.
05

Choose production or local testing

Open the StrictSEO extension details, then Extension options, and choose where reports should open.

  1. Production opens reports at https://strictseo.com and does not need a local server.
  2. Local testing opens http://localhost:3114 and requires the StrictSEO dev server to be running.
  3. The selected report target is the only preference saved by the extension.
06

Start live review

Open an HTTP or HTTPS page and select the StrictSEO toolbar icon. Keep the side panel open while navigating within that website.

  1. Suggestions refresh after same-site navigation.
  2. Crossing to another website pauses review until you select StrictSEO again.
  3. Search, filter, rescan, and download the session’s suggestions as JSON, CSV, or Markdown before closing Chrome.

Report target

Pick one mode.

The extension does not accept arbitrary report destinations. It can open only the production analyzer or the fixed local development origin.

Production

Choose this when you want the installed extension to open reports on https://strictseo.com. This is the default and does not need the local dev server.

Local testing

Choose this when testing workspace changes. Run npm run dev from strictseo-com and confirm the site is available on http://localhost:3114.

Troubleshooting

Fix the common setup problems.

This beta has no Chrome Web Store auto-update path. Keep the extracted folder available and reload the extension manually after replacing it with a newer version.

Chrome says the manifest is missing

Select the extracted folder containing manifest.json, not the supplied package, not an individual file, and not a parent folder above the extracted extension.

Localhost refused to connect

Run npm run dev from the StrictSEO site folder and confirm the terminal shows port 3114. Use Production mode if you do not need local testing.

The extension shows an error

Use an ordinary HTTP or HTTPS page. Chrome internal pages, the Chrome Web Store, local files, and protected documents may block extension scripts.

The panel did not refresh

Reload the page and select the StrictSEO toolbar icon again. If you crossed to another website, Chrome requires that new click before review can continue.

Privacy reminder

Use the beta only where local page reading is acceptable.

The audited build has no snapshot upload API, analytics, or remote-code path. It reads bounded visible metadata, headings, paragraphs, links, images, and JSON-LD after you activate live review.

Avoid confidential pages if even temporary processing inside Chrome is inappropriate. No software can honestly be guaranteed risk-free.

Read the full permission and privacy review