gwuhaolin / koa-seo

koa SEO middleware

koa-seo

SEO middleware for koa base on chrome-render, a substitute for prerender.

Modern web app use technique like react.js vue.js which render html in browser, this lead to search engine can't crawl your page content.

This project want to solve this kind of problem in a general-purpose way, it detect request is from search engine crawler then use headless chrome to render out your modern web page and return to crawler.

Here is koa-seo's architecture diagram:

Use

npm i koa-seo

then use it:

const Koa = require('koa');
const seoMiddleware = require('koa-seo');
const app = new Koa();

app.use(seoMiddleware({
    render: {
        // use `window.isPageReady=1` to notify chrome-render page has ready
        useReady: true,
    }
}));

app.listen(3000);

you can download and run this complete demo

Options

• render options from koa-chrome-render

For more flexible use case see koa-chrome-render.

Friends

• koa-seo dependent on koa-chrome-render chrome-render middleware for koa.
• chrome-render general server render base on chrome.
• chrome-pool Headless chrome tabs manage pool.
• express-middleware-seo SEO middleware for express base on chrome-render

koa-seo's Issues

将ua伪装成crawler怎么判断是否被爬

1.将ua伪装成crawler怎么判断是否被爬？
2.如果开启useReady，不设置window.isPageReady = 1,headless chrome会生成html吗？
多谢楼主帮助。

有考虑出个 express 版本的中间件吗

关于给搜索引擎静态化页面得疑问

这样给客户和搜索引擎不一样得代码页面会被判断为作弊么？

Detecting browser window size

If you have a responsive application that will serve different content depending on the device resolution, then there is no reliable way to fetch a version specific to that device. Without this you will get DOM mismatch error when rendering the page on the client-side.

Opening an issue to start a conversation about possible solutions.

[discuss]about headless-chrome render failed.

I tried some headless-chrome render solution inlcuding koa-seo, and always failed when render "http://www.chenggua.com" or "m.chenggua.com". It is always successful when render "http://vue-prerender.deboy.cn/titleFromRouterDefine". So i guess is there any conflict or other problems?

BTW, phantomjs render "www.chenggua.com" is OK, with some tiny errors about codec.
This issue is raised only for discussion, about headless-chrome render capacity and robust.

LIGHTHOUSE_CHROMIUM_PATH need to be set?

When I try to run demo, there is error:
Error: The environment variable LIGHTHOUSE_CHROMIUM_PATH must be set to executable of a build of Chromium version 54.0 or later.

I suggest to deploy a docker file, so it is easy for other developers to use or contribute.