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 🙏

© 2024 – Pkg Stats / Ryan Hefner

seo_checks

v0.0.9

Published

A little helper for checking SEO

Downloads

18

Readme

Seo Checks

What is this project about?

This is a small project that helps you to perform seo checks, it is a light weight, flexible and extendible npm package can help you check from file / string / readable stream and export the result to stdout / file / writable stream.

How to use it?

  • You need npm before you start
  • npm install seo_checks

How to run the test?

  • simply run npm test

If you got

const spawn = require('child_process').spawn;
^^^^^
SyntaxError: Use of const in strict mode.

Please run:

nvm install stable

Usage

With provided example file:

<html>
    <head>
        <title>This is a test HTML page</title>
        <meta name="descriptions" value="desc" />
        <meta name="keywords" value="good,html" />
    </head>
    <body>
        <h1>Test HTML</h1>
        <strong>Test HTML</strong>
        <a href="." rel="random link">A link</a>
        <img src="."/>
    </body>
</html>

And use this in your code:

Recommended:

const checks = require('seo_checks');

checks.start().fromFile(__dirname + '/test.html').then(function(seoCheck) {
    return seoCheck.checkImg().checkLink().checkHead().checkStrong().checkH1().toFile(outputFile);
})

Or you can choose in this way:

const checks = require('seo_checks');

checks.checkHtmlFile(__dirname + '/test.html', ['checkImg']).then(function(exports) {
  exports.toFile('test.txt');
});

And you will have a file test.txt:

There are 1 <img> tag without alt attribute

How to add more rules?

  • Currently, pre-defined rules are:
    • checkImg: Detect if any <img /> tag without alt attribute.
    • checkLink: Detect if any <a /> tag without rel attribute.
    • checkHead:
      • Detect if header doesn’t have <title> tag.
      • Detect if header doesn’t have <meta name=“descriptions” ... /> tag.
      • Detect if header doesn’t have <meta name=“keywords” ... /> tag.
    • checkStrong: Detect if there’re more than a certain number of <strong> tag in HTML(default is 15).
    • checkH1: Detect if a HTML have more than 1 <h1> tag.
  • To add more rules, please refer to https://github.com/cuuboy/seo_checks/blob/master/lib/predefined_rules.js and use existing query functions or add / improve more query function at https://github.com/cuuboy/seo_checks/blob/master/lib/tag_queries.js

How will exports look like?

For example:

There are 1 <img> tag without alt attribute
There are 1 <a> tag without rel attribute
<title> is missing
<meta> with name="descriptions" is missing
<meta> with name="keywords" is missing
This document has more than 15 <strong> tag
This document has more than 1 <h1> tag