npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@mahmudul-hasan/seo-scan

v0.1.3

Published

Professional-grade SEO site audit CLI — crawl and audit any website from the terminal

Readme

seo-audit CLI

npm license

Terminal tool for SEO site auditing. Crawls a site, runs eight analyzers on every page, and prints a colour-coded dashboard with the top issues.

Requirements: Node.js 18+

Installation

npm install -g @mahmudul-hasan/seo-scan

Commands


seo-audit run

seo-audit run https://example.com

| Flag | Default | Description | |---|---|---| | --max-pages <n> | 100 | Maximum pages to crawl | | --depth <n> | 3 | Maximum crawl depth from root | | --concurrency <n> | 5 | Concurrent page fetches | | --timeout <ms> | 10000 | Per-request timeout in milliseconds | | --render-js | off | Use Puppeteer for JS-rendered pages | | --format <fmt> | json | json, html, or markdown | | --output <path> | ./reports/audit-YYYY-MM-DD.<ext> | Output file path | | --analyzers <list> | all | Comma-separated subset of analyzers to run | | --no-robots | — | Ignore robots.txt disallow rules | | --config <path> | auto-detected | Path to config file | | --open | off | Open HTML report in browser after saving |

# Save as HTML and open in browser
seo-audit run https://example.com --format html --open

# Limit scope, output to a specific path
seo-audit run https://example.com --max-pages 50 --output ./reports/audit.json

# Run only on-page and technical checks
seo-audit run https://example.com --analyzers onpage,technical

# Audit a JS-heavy site
seo-audit run https://example.com --render-js

seo-audit report

Convert a saved JSON report to HTML or Markdown.

seo-audit report ./reports/audit.json --format html --open

| Flag | Default | Description | |---|---|---| | --format <fmt> | html | json, html, or markdown | | --output <path> | same name, new extension | Output file path | | --open | off | Open HTML report in browser after saving |


seo-audit schedule

Runs an audit immediately, then prints the cron/CI snippet needed to automate future runs.

seo-audit schedule https://example.com --cron "0 6 * * *"

| Flag | Default | Description | |---|---|---| | --cron <expression> | 0 6 * * * | Cron expression | | --format <fmt> | json | Report format | | --output-dir <path> | ./reports | Directory for saved reports | | --max-pages <n> | 50 | Max pages per scheduled audit |


Config file

Create seo-audit.config.ts (or .js / .mjs) in your project root. CLI flags always take priority.

// seo-audit.config.ts
import { defineConfig } from 'seo-auditor';

export default defineConfig({
  url: 'https://example.com',
  maxPages: 150,
  crawlDepth: 4,
  concurrency: 8,
  ignorePatterns: ['**/admin/**', '**/login'],
  analyzers: ['onpage', 'technical', 'performance', 'images'],
});

Specify a custom path with --config ./path/to/config.ts.


CI / CD

GitHub Actions

name: SEO Audit
on:
  push:
    branches: [main]

jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm install -g @mahmudul-hasan/seo-scan
      - run: seo-audit run ${{ vars.SITE_URL }} --format json --output ./audit.json
      - uses: actions/upload-artifact@v4
        with:
          name: seo-report
          path: ./audit.json

Score-gated check

To fail a build on a low score, use the seo-auditor library directly:

// seo-check.mjs
import { Auditor } from 'seo-auditor';

const report = await new Auditor({ url: process.env.SITE_URL, maxPages: 50 }).run();

if (report.siteScore < 70) {
  console.error(`Score ${report.siteScore}/100 is below threshold`);
  process.exit(1);
}

Exit codes

| Code | Meaning | |---|---| | 0 | Audit completed | | 1 | Fatal error (invalid URL, config error) |

A low score does not produce a non-zero exit on its own.


Troubleshooting

Crawl finds very few pages — Increase --depth. If the site requires JavaScript to render links, add --render-js (requires npm install puppeteer).

Pages being skipped — Check robots.txt (use --no-robots to bypass). The server may be returning 4xx/5xx, or requests may be timing out (increase --timeout).

Config file fails to load — Switch from .ts to .js or .mjs if you see an import error.


License

MIT