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

react-seo-analyzer

v2.0.1

Published

A React SEO Analyzer package with visual overlay, 20+ checks, and SEO scoring.

Readme

react-seo-analyzer

npm version npm downloads bundle size license

🔍 A zero-dependency SEO linter for React apps — with a live visual overlay, 20+ checks, and an SEO score — all only in development mode.


✨ Why react-seo-analyzer?

Most React SEO tools require server-side rendering or manual auditing. react-seo-analyzer runs right inside your browser during development — giving you instant, inline feedback as you build.

| Feature | react-seo-analyzer | Lighthouse | Other libs | |---|---|---|---| | Dev-mode overlay | ✅ | ❌ | ❌ | | SEO score | ✅ | ✅ | ❌ | | 20+ checks | ✅ | ✅ | ⚠️ partial | | Zero config | ✅ | ❌ | ⚠️ | | Zero dependencies | ✅ | ❌ | ❌ | | Auto-disabled in prod | ✅ | N/A | ❌ |


🚀 Installation

npm install react-seo-analyzer
# or
yarn add react-seo-analyzer

🔧 Usage

Drop <SEOAnalyzer /> anywhere in your app. It renders nothing in production.

import SEOAnalyzer from 'react-seo-analyzer';

function App() {
  return (
    <>
      <SEOAnalyzer />
      {/* your app */}
    </>
  );
}

A floating panel will appear in the bottom-right corner showing your SEO score and all issues, grouped by category. Click the badge to collapse it.


⚙️ Props

| Prop | Type | Default | Description | |---|---|---|---| | devOnly | boolean | true | Only run in NODE_ENV !== 'production' | | overlay | boolean | true | Show the floating UI panel | | console | boolean | true | Also log issues to the browser console | | disableRules | string[] | [] | Rule IDs to skip (see list below) | | onIssues | function | — | Callback (issues, score) => void |

Examples

// Disable the overlay, use console output only
<SEOAnalyzer overlay={false} />

// Disable specific rules
<SEOAnalyzer disableRules={['missingStructuredData', 'missingTwitterCard']} />

// Use a callback for custom reporting
<SEOAnalyzer onIssues={(issues, score) => myReporter.send({ issues, score })} />

📋 Checks

🔴 Errors (–15 pts each)

| Rule ID | Description | |---|---| | missingTitle | No <title> tag found | | missingDescription | No meta description | | missingH1 | No <h1> on the page | | imagesWithoutAlt | Images missing alt attribute | | missingViewport | No viewport meta tag | | robotsNoIndex | Page is set to noindex |

🟡 Warnings (–5 pts each)

| Rule ID | Description | |---|---| | titleLength | Title outside 30–60 character range | | descriptionLength | Description outside 50–160 character range | | multipleH1 | More than one <h1> tag | | missingCanonical | No canonical link tag | | missingLang | No lang attribute on <html> | | missingOgTitle | No og:title Open Graph tag | | missingOgDescription | No og:description Open Graph tag | | missingOgImage | No og:image Open Graph tag | | externalLinksNoRel | External links missing rel="noopener noreferrer" | | headingHierarchy | Heading levels are skipped |

🔵 Info (–1 pt each)

| Rule ID | Description | |---|---| | missingOgUrl | No og:url tag | | missingTwitterCard | No twitter:card tag | | missingTwitterTitle | No twitter:title tag | | missingStructuredData | No JSON-LD structured data | | missingFavicon | No favicon link tag |


📊 Scoring

Your SEO score starts at 100 and points are deducted per issue:

Errors   → –15 pts each
Warnings → –5 pts each
Info     → –1 pt each

| Score | Status | |---|---| | 80–100 | 🟢 Good | | 50–79 | 🟡 Needs work | | 0–49 | 🔴 Critical |


🤝 Contributing

Contributions are welcome!

  • Fork the repo
  • Create a feature branch
  • Run tests: npm test
  • Submit a PR

Have a rule idea? Open an issue.


📄 License

MIT © Artak Harutyunyan