探客时代
Metascraper
Get unified metadata from websites using Open Graph, Microdata, RDFa, Twitt...
README
A library to easily get unified metadata from websites using Open Graph, Microdata, RDFa, Twitter Cards, JSON-LD, HTML, and more.
What is it
metascraper is library to easily scrape metadata from an article on the web using Open Graph metadata, regular HTML metadata, and series of fallbacks.
It follows a few principles:
- Have a high accuracy for online articles by default.
- Make it simple to add new rules or override existing ones.
- Don't restrict rules to CSS selectors or text accessors.
Getting started
Let's extract accurate information from the following website:
First, metrascraper expects you provide the HTML markup behind the target URL.
There are multiple ways to get the HTML markup. In our case, we are going to run a programmatic headless browser to simulate real user navigation, so the data obtained will be close to a real-world example.
- ``` js
- const getHTML = require('html-get')
- /**
- * `browserless` will be passed to `html-get`
- * as driver for getting the rendered HTML.
- */
- const browserless = require('browserless')()
- const getContent = async url => {
- // create a browser context inside the main Chromium process
- const browserContext = browserless.createContext()
- const promise = getHTML(url, { getBrowserless: () => browserContext })
- // close browser resources before return the result
- promise.then(() => browserContext).then(browser => browser.destroyContext())
- return promise
- }
- /**
- * `metascraper` is a collection of tiny packages,
- * so you can just use what you actually need.
- */
- const metascraper = require('metascraper')([
- require('metascraper-author')(),
- require('metascraper-date')(),
- require('metascraper-description')(),
- require('metascraper-image')(),
- require('metascraper-logo')(),
- require('metascraper-clearbit')(),
- require('metascraper-publisher')(),
- require('metascraper-title')(),
- require('metascraper-url')()
- ])
- /**
- * The main logic
- */
- getContent('https://microlink.io')
- .then(metascraper)
- .then(metadata => console.log(metadata))
- .then(browserless.close)
- .then(process.exit)
- ```
The output will be something like:
- ``` json
- {
- "author": "Microlink HQ",
- "date": "2022-07-10T22:53:04.856Z",
- "description": "Enter a URL, receive information. Normalize metadata. Get HTML markup. Take a screenshot. Identify tech stack. Generate a PDF. Automate web scraping. Run Lighthouse",
- "image": "https://cdn.microlink.io/logo/banner.jpeg",
- "logo": "https://cdn.microlink.io/logo/trim.png",
- "publisher": "Microlink",
- "title": "Turns websites into data — Microlink",
- "url": "https://microlink.io/"
- }
- ```
What data it detects
?> Custom metadata detection can be defined using a rule bundle.
Here is an example of the metadata that metascraper can detect:
A audio URL that best represents the article.
A human-readable representation of the author's name.
An ISO 8601 representation of the date the article was published.
The publisher's chosen description of the article.
A video URL that best represents the article.
An image URL that best represents the article.
An ISO 639-1 representation of the url content language.
An image URL that best represents the publisher brand.
A human-readable representation of the publisher's name.
The publisher's chosen title of the article.
The URL of the article.
How it works
metascraper is built out of rules bundles.
It was designed to be easy to adapt. You can compose your own transformation pipeline using existing rules or write your own.
Rules bundles are a collection of HTML selectors around a determinate property. When you load the library, implicitly it is loading core rules.
Each set of rules load a set of selectors in order to get a determinate value.
These rules are sorted with priority: The first rule that resolve the value successfully, stop the rest of rules for get the property. Rules are sorted intentionally from specific to more generic.
Rules work as fallback between them:
- If the first rule fails, then it fallback in the second rule.
- If the second rule fails, time to third rule.
- etc
metascraper do that until finish all the rule or find the first rule that resolves the value.
Importing rules
metascraper exports a constructor that need to be initialized providing a collection of rules to load:
- ``` js
- const metascraper = require('metascraper')([
- require('metascraper-author')(),
- require('metascraper-date')(),
- require('metascraper-description')(),
- require('metascraper-image')(),
- require('metascraper-logo')(),
- require('metascraper-clearbit')(),
- require('metascraper-publisher')(),
- require('metascraper-title')(),
- require('metascraper-url')()
- ])
- ```
Again, the order of rules are loaded are important: Just the first rule that resolve the value will be applied.
Use the first parameter to pass custom options specific per each rules bundle:
- ``` js
- const metascraper = require('metascraper')([
- require('metascraper-clearbit')({
- size: 256,
- format: 'jpg'
- })
- ])
- ```
Rules bundles
?> Can't find the rules bundle that you want? Let's open an issue to create it.
Official
Rules bundles maintained by metascraper maintainers.
Core essential
- metascraper-audio – Get audio property from HTML markup.
- metascraper-author – Get author property from HTML markup.
- metascraper-date – Get date property from HTML markup.
- metascraper-description – Get description property from HTML markup.
- metascraper-feed – Get RSS/Atom feed URL from HTML markup.
- metascraper-image – Get image property from HTML markup.
- metascraper-iframe – Get iframe for embedding content for the supported providers.
- metascraper-lang – Get lang property from HTML markup.
- metascraper-logo – Get logo property from HTML markup.
- metascraper-logo-favicon – Metascraper logo favicon fallback.
- metascraper-media-provider – Get specific video provider url (Facebook/Twitter/Vimeo/etc).
- metascraper-publisher – Get publisher property from HTML markup.
- metascraper-readability – A Mozilla readability connector for metascraper.
- metascraper-title – Get title property from HTML markup.
- metascraper-url – Get url property from HTML markup.
- metascraper-video – Get video property from HTML markup.
Vendor specific
- metascraper-amazon – Metascraper integration with Amazon.
- metascraper-clearbit – Metascraper integration with Clearbit Logo API.
- metascraper-instagram – Metascraper integration for Instagram.
- metascraper-manifest – Metascraper integration for detecting PWA Web app manifests.
- metascraper-soundcloud – Metascraper integration with SoundCloud.
- metascraper-telegram – Metascraper integration with Telegram.
- metascraper-uol – Metascraper integration for uol.com URLs.
- metascraper-spotify – Metascraper integration with Spotify.
- metascraper-youtube – Metascraper integration with YouTube.
Community
Rules bundles maintained by individual users.
- metascraper-address – Get schema.org formatted address.
- metascraper-shopping – Get product information from HTML markup on merchant websites.
See CONTRIBUTING for adding your own module!
API
constructor(rules)
Create a new metascraper instance declaring the rules bundle to be used explicitly.
rules
Type: Array
The collection of rules bundle to be loaded.
metascraper(options)
Call the instance for extracting content based on rules bundle provided at the constructor.
options
url
Type: String
The URL associated with the HTML markup.
It is used for resolve relative links that can be present in the HTML markup.
it can be used as fallback field for different rules as well.
html
Type: String
The HTML markup for extracting the content.
rules
Type: Array
You can pass additional rules to add on execution time.
These rules will be merged with your loaded [rules](#rules) at the beginning.
validateUrl
Default: true
Ensure the URL provided is validated as a WHATWG URL API compliant.
Benchmark
To give you an idea of how accurate metascraper is, here is a comparison of similar libraries:
| Library | [metascraper](https://www.npmjs.com/package/metascraper) | [html-metadata](https://www.npmjs.com/package/html-metadata) | [node-metainspector](https://www.npmjs.com/package/node-metainspector) | [open-graph-scraper](https://www.npmjs.com/package/open-graph-scraper) | [unfluff](https://www.npmjs.com/package/unfluff) |
|:----------|:-----------------------------------------------------------|:---------------------------------------------------------------|:-------------------------------------------------------------------------|:-------------------------------------------------------------------------|:---------------------------------------------------|
| Correct | 95.54% | 74.56% | 61.16% | 66.52% | 70.90% |
| Incorrect | 1.79% | 1.79% | 0.89% | 6.70% | 10.27% |
| Missed | 2.68% | 23.67% | 37.95% | 26.34% | 8.95% |
A big part of the reason for metascraper's higher accuracy is that it relies on a series of fallbacks for each piece of metadata, instead of just looking for the most commonly-used, spec-compliant pieces of metadata, like Open Graph.
metascraper's default settings are targetted specifically at parsing online articles, which is why it's able to be more highly-tuned than the other libraries for that purpose.
If you're interested in the breakdown by individual pieces of metadata, check out the full comparison summary, or dive into the raw result data for each library.
License
Authored and maintained by Microlink with help from contributors.
microlink.io · GitHub microlinkhq · Twitter @microlinkhq
