Live data from Hacker News

Used vue.js with laravel and my site is not SEO friendly anymore

news.ycombinator.com

11–18 of 18 posts

Re: Used vue.js with laravel and my site is not SEO friendly anymore

#11
post #8

I think that google now uses a headless browser. Unless your page loads in too much time, nothing should change on the SEO side if you have the same content at the same place.

That is not true. As far as I know, google does execute js but does not wait for ajax calls.

source please!

Re: Used vue.js with laravel and my site is not SEO friendly anymore

#14
post #8

I think that google now uses a headless browser. Unless your page loads in too much time, nothing should change on the SEO side if you have the same content at the same place.

That is not true. As far as I know, google does execute js but does not wait for ajax calls.

In google webmaster I saw the error when ran "fetch as google". It had issues with Ajax calls.

Re: Used vue.js with laravel and my site is not SEO friendly anymore

#15

I think that google now uses a headless browser. Unless your page loads in too much time, nothing should change on the SEO side if you have the same content at the same place.

From what I've heard they do, but not for all of it. The bulk of the crawling is still done without it, and some subset of pages (probably based on some detection of "this site requires JS") is crawled with the more expensive, JS-enabled crawler too.

Re: Used vue.js with laravel and my site is not SEO friendly anymore

#16
With all these discussion, my question to this group is that should I stick with vue.js ? I was using data tables and developer advocated vue.js being much better and flexible, which I agree but then these SEO challenges. If I am on laravel framework, what options do I have to implement pagination and filter conditions in SEO friendly manner. I have seen some sites using Ajax but they change the url by incrementing a variable in the url.

Re: Used vue.js with laravel and my site is not SEO friendly anymore

#18

SPA and SEO are not compatible. SPA is good for apps, backends, admins ...

A SPA supporting deep linking and an access model that provides unauthenticated access to public content should, in principle, be able to be made indistinguishable from a set of classic webpages with the public portion of the app content, from an SEO perspective, at least if one takes the JS rendering ability of the search bot(s) of concern into account.
Post reply on HN