ds_

I understand it's due to connect being bought by sencha. The FAQ states it's more like connect, with some express goodies moved to the middleware level.

And I don't think even that really belongs in this list.

I have to agree with RyanZAG, log4j seems a strange inclusion in this list.

Wouldn't the secrets file be added to gitignore?

I wouldn't say SEO is a major hurdle, there is prerender.io (http://prerender.io/getting-started#ruby) and countless other services which help (I made one).

It's the Great Rift http://en.wikipedia.org/wiki/Great_Rift_(astronomy)

Indeed, it would make a nice wallpaper.

You can see it in areas with little light pollution (although not quite like this image), otherwise most of the stars are too faint.

Yes, it's the plane of our galaxy. If you click show constellations and objects, you can see where we are in the spiral, bottom left.

What's broken about it?

Or martini? I liked the look of martini but have not delved deep enough to make an informed decision. Might pick Go for my next side project...

A service that allows single page ajax applications to be indexed with minimal effort http://crawlspa.com

The documentation isn't great but it isn't terrible either. I hope people thinking of giving angular a try aren't put off by the constant over-dramatisation.

Me personally? Or 'one'? :)

I think it's like others have said, there is a difference between giving up completely and changing direction/priorities.

Yes, but they simulate multiple pages by fetching new data via ajax requests and modifying the DOM with javascript.

It already is: http://foundation.zurb.com/docs/applications.html

To the foundation team, "makes us to do so much quicker" should probably be "enables us to do so much quicker".

I can appreciate that. Is there anything that would alleviate your concerns? It is something that should only affect crawlers and I'd expect most new users of the service to have zero Google presence (so better than nothing/worth a try?).

I can't see a better way of handling the integration.

Yep, I thought brombone had an interesting pricing model :) I wonder if they managed to get any signups.

Cool, ill be interested in seeing what you start charging after the beta :) Good luck with it, its reassuring that im not the only one to have thought this to be a good idea.

The crawler is a bit hands on. Crawlspa refreshes the cache in the background after each request. For sites with frequently updated content, having to recrawl may become a headache.

It doesnt crawl (although I will offer this soon) but it doesnt require entering any domains or sitemaps like the other options (easier to configure). You just submit your top level domain and let google do the crawling.

I'm using crawlspa for crawlspa, you can see how google has indexed the homepage:

https://www.google.com/#q=crawlspa+ajax

from

http://crawlspa.com?_escaped_fragment_=

Apologies, I wanted to validate the idea before I invested much more. I will surely improve the design moving forwards.

Thanks, that's great.

And yes, I have considered it. Actually, I've had that suggested before - a number of developers have said they would have liked it for their last client.

Understood - so I should clearly state that crawlers can't usually see AJAX content and that this will allow them to see and index it, leading to more search engine traffic. I was cautious of spelling out the obvious, I didn't want to insult anyone's intelligence :D

> developers who would like a quick solution for seo until they have time to address it in more detail later"

Makes sense. I'd hope that the price is low enough that they decide it's not worth ever having their own setup.

> 3.99 is a weird number for me. Just throws me off. I'd raise it to 4.99

Thanks, advice taken. To any late-comers, please contact me by email if you're interested in a subscription at the previous price :)

2 is just a generalization of 1 and 3. To expand on 4, currently I display how many crawler requests were made and the average response time. If I were to further invest, I'd split these metrics by path requested and have it available over any time interval.

Do you have any ideas on what other pain points I could solve with this idea?

It shouldn't, because the crawler should only see your server (your server stands in front of crawlspa as a proxy). If you don't have access to your server config and redirect in the code, then it's possible.

Thanks, will try to make it clearer.

I think the value proposition is this:

1) You can configure it in minutes, whereas it may take a competent developer several hours to set this up on your own servers (possibly $100s in wages = several years subscription).

2) One less worry.

3) If your servers are bogged down, google still gets served the pages quickly (point 2).

4) Bonus metrics.

Updated, thanks.