Live data from Hacker News

Meteor 0.3.9 adds search engine optimization

meteor.com

41–46 of 46 posts

Re: Meteor 0.3.9 adds search engine optimization

#41
post #7

Wait, they added SEO before database authentication? So very logical.

Other core devs are working furiously on auth (getting pretty close). This feature was just releasable first.

Sounds good, despite my first post Meteor is the most interesting framework out there atm IMO.

Re: Meteor 0.3.9 adds search engine optimization

#42
So after year of developing this product, they finally realized that each page should have an unique URL.

It's called lack of vision.

ps. ajax content does not rank in Google SERPs at all, it's a typical band aid solution, so websites made with meteor will have some serious issues with monetization and stuff

Re: Meteor 0.3.9 adds search engine optimization

#43
post #11
post #9

Their technique for generating the HTML representation of deep-link into a Meteor app is to run the entire client app in a headless browser and serialize the generated DOM?! This is an area of vital importance to public, JS-based RIAs, and needs some real innovation. Why even bother delivering this half-baked solution? The processing cost makes it untenable for all but the tiniest of URL-spaces.

Seems like this would be a very easy way to DoS a Meteor app, if it's really spawning a PhantomJS process for each request.

If this content is mostly for spiders, I don't see why you couldn't cache the resulting HTML for 1 hour or so and only regenerate new pages.

Re: Meteor 0.3.9 adds search engine optimization

#44
post #36
post #30

Earlier quoted context omitted.

Above, you know, actual meteors :) Elegant proof if any were needed that so-called SEO is merely tricks for polluting search indexes. As bad as spammers.

Search engines are all about what people are looking for on the web. It's quite possible that more people are currently interested in Meteor the framework than meteors the objects, in which case I wouldn't call this result "pollution." If you really want the Wikipedia page for meteors, nothing's stopping you from going straight there.

I very much doubt that, with the Perseid shower due this weekend.

Re: Meteor 0.3.9 adds search engine optimization

#45
post #18

Who really needs this for their web app? Nearly 99% of heavy web apps require a login, so Google is out of the picture anyway. Anyone who is building a content site with DOM-manipulating Javascript doing all the work have completely lost their way. Seriously, just render your templates on the server and deliver them to the client. Why does the world want app-ify everything?

I have a site with lots of statistics, tables, charts and similar stuff. As you can understand, fetching all that data from the database to render the analytical charts is fairly expensive. My solution is to first render the page template and send it back to the client as quickly as possible with all statistics widgets empty. Then the page makes a few ajax calls to fetch the data from the server to render the pie and bar charts widgets.

It works very well for a human visitor. The page loads extremely quickly and the widgets rendered using javascript and ajax are below the fold anyway so it doesn't matter that they are visible 500 ms later than the initial page load. Unfortunately it is crap for Googlebot which never runs the ajax calls and never "sees" my pretty graphs which leads it to think I have a much more boring site than what it really is.

So that is my need to "app-ify" my site and my, as of yet unfulfilled, need for a framework that is able to provide Googlebot with an accurate view of my appified site.

Re: Meteor 0.3.9 adds search engine optimization

#46
post #9

Their technique for generating the HTML representation of deep-link into a Meteor app is to run the entire client app in a headless browser and serialize the generated DOM?! This is an area of vital importance to public, JS-based RIAs, and needs some real innovation. Why even bother delivering this half-baked solution? The processing cost makes it untenable for all but the tiniest of URL-spaces.

agree. this is a horrible solution. sigh...
Post reply on HN