HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
thomasdavis
seoserver
JavaScript2013–2013
thomasdavis / seoserver

seoserver

SEO Server is a command line tool that runs a server that allows GoogleBot, as well as other crawlers, to crawl Javascript heavy websites.

2Distinct people
3Mentions
0Explicit recommenders
219GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

SEO Server is a command line tool that runs a server that allows GoogleBot, as well as other crawlers, to crawl Javascript heavy websites.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2013-05-23 17:27:30 UTC to 2013-10-07 13:05:10 UTC. Weeks start Monday, UTC.

012013-05-20 00:00:00 UTC to 2013-05-27 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 202013-05-27 00:00:00 UTC to 2013-06-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-03 00:00:00 UTC to 2013-06-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-10 00:00:00 UTC to 2013-06-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-17 00:00:00 UTC to 2013-06-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-24 00:00:00 UTC to 2013-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-01 00:00:00 UTC to 2013-07-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-08 00:00:00 UTC to 2013-07-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-15 00:00:00 UTC to 2013-07-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-22 00:00:00 UTC to 2013-07-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-29 00:00:00 UTC to 2013-08-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 292013-08-05 00:00:00 UTC to 2013-08-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-08-12 00:00:00 UTC to 2013-08-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-08-19 00:00:00 UTC to 2013-08-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-08-26 00:00:00 UTC to 2013-09-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-02 00:00:00 UTC to 2013-09-09 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2013-09-09 00:00:00 UTC to 2013-09-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-16 00:00:00 UTC to 2013-09-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-23 00:00:00 UTC to 2013-09-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-30 00:00:00 UTC to 2013-10-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-10-07 00:00:00 UTC to 2013-10-14 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 7

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 202013-05-20 00:00:00 UTC2013-05-27 00:00:00 UTC101
May 272013-05-27 00:00:00 UTC2013-06-03 00:00:00 UTC000
Jun 32013-06-03 00:00:00 UTC2013-06-10 00:00:00 UTC000
Jun 102013-06-10 00:00:00 UTC2013-06-17 00:00:00 UTC000
Jun 172013-06-17 00:00:00 UTC2013-06-24 00:00:00 UTC000
Jun 242013-06-24 00:00:00 UTC2013-07-01 00:00:00 UTC000
Jul 12013-07-01 00:00:00 UTC2013-07-08 00:00:00 UTC000
Jul 82013-07-08 00:00:00 UTC2013-07-15 00:00:00 UTC000
Jul 152013-07-15 00:00:00 UTC2013-07-22 00:00:00 UTC000
Jul 222013-07-22 00:00:00 UTC2013-07-29 00:00:00 UTC000
Jul 292013-07-29 00:00:00 UTC2013-08-05 00:00:00 UTC000
Aug 52013-08-05 00:00:00 UTC2013-08-12 00:00:00 UTC000
Aug 122013-08-12 00:00:00 UTC2013-08-19 00:00:00 UTC000
Aug 192013-08-19 00:00:00 UTC2013-08-26 00:00:00 UTC000
Aug 262013-08-26 00:00:00 UTC2013-09-02 00:00:00 UTC000
Sep 22013-09-02 00:00:00 UTC2013-09-09 00:00:00 UTC101
Sep 92013-09-09 00:00:00 UTC2013-09-16 00:00:00 UTC000
Sep 162013-09-16 00:00:00 UTC2013-09-23 00:00:00 UTC000
Sep 232013-09-23 00:00:00 UTC2013-09-30 00:00:00 UTC000
Sep 302013-09-30 00:00:00 UTC2013-10-07 00:00:00 UTC000
Oct 72013-10-07 00:00:00 UTC2013-10-14 00:00:00 UTC101

What Hacker News says

3 sources
This may be the case for pure single page apps, but any real world application will have some pages you want to load faster and have easily indexed by search engines. At https://starthq.com we started out as a single page app with a RESTful API using Angular, but with time it has become apparent that there are certain public pages that need to have the HTML generated server side. Now we have a hybrid solution, where some parts of the page are generated on the server and others, namely the parts that are different for anonymous and logged in users, on the client. We've experimented with the likes of https://github.com/apiengine/seoserver but the truth of the matter is it's actually easier to generate the HTML server side than using Angular.
In Lessons Learned: A Year with a Large AngularJS Project

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.