Displaying 1 to 3 from 3 results

rendora - dynamic server-side rendering using headless Chrome to effortlessly solve the SEO problem for modern javascript websites

  •    Go

Rendora can be seen as a reverse HTTP proxy server sitting between your backend server (e.g. Node.js/Express.js, Python/Django, etc...) and potentially your frontend proxy server (e.g. nginx, traefik, apache, etc...) or even directly to the outside world that does actually nothing but transporting requests and responses as they are except when it detects whitelisted requests according to the config. In that case, Rendora instructs a headless Chrome instance to request and render the corresponding page and then return the server-side rendered page back to the client (i.e. the frontend proxy server or the outside world). This simple functionality makes Rendora a powerful dynamic renderer without actually changing anything in both frontend and backend code. Dynamic rendering means that the server provides server-side rendered HTML to web crawlers such as GoogleBot and BingBot and at the same time provides the typical initial HTML to normal users in order to be rendered at the client side. Dynamic rendering is meant to improve SEO for websites written in modern javascript frameworks like React, Vue, Angular, etc...

riplink - Find dead links on the web.

  •    Go

riplink finds dead links on the web. It's useful for double-checking web pages for incorrect, or dead web links. Inspired by Wikimedia and the Internet Archive fixing broken links on Wikipedia.

href-counter - Counts internal vs. external hrefs within a page to rate on SEO.

  •    Go

A Golang example application which counts internal vs. external hrefs within a page to rate SEO. The golang.org/x/net/html package is used to iterate through all the HTML tokens in the web-page. It provides a working example of parsing HTML piece-by-piece.