F
F
Finsh2017-03-14 11:39:06
Angular
Finsh, 2017-03-14 11:39:06

Dynamic parts of the site + SEO?

Good afternoon, ladies and gentlemen.
Interested in the following question.
Given:
A very loaded store, links pumped over several years in search engines. A year ago, the store migrated to Laravel 5.2. The store client is generated by serverside. The store is very worried about their established positions in search engines.
Tasks:
1. Save the link mass
2. It is necessary to implement several very dynamic points (on different pages) on the client. We made similar points in the admin part of the store on jquey. We experienced a lot of tears of suffering and pain. Actually the question is, what is the best way to do it? In addition to painful jquery, we consider 3 more options:
1) The Angular2 team has some skills with this tool and is also planning to cut products on it in the near future.
2) React here no one has competencies, as well as plans.
3) Vue. As far as I know, this is the most integrated solution with Laravel, with a small entry threshold.
The technology should allow you to generate html on the server side so that there are no seo drawdowns, it should also not cause a lot of pain in maintenance and allow you to collect not very many bicycles and crutches.
I would be very grateful to everyone for your opinion on this issue, and also if you throw me links and recipes in which similar problems were solved.
P.S. I know out of the box laravel 5.3. vue.js is also coming, but unfortunately we have laravel 5.2

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
Andrey Khokhlov, 2017-03-14
@Finsh

I would:
- Leave page generation as is, on the server.
- Implemented separate functional blocks using Vue
For example, on the product page, the title, description, photo - is given immediately in HTML from the server.
And the add to cart button is already a Vue component.
The same goes for the components: shopping cart, personal account, shopping cart widget in the header, filter in the catalog, and so on.
Why Vue?
Because in the minimum version, you just connected it and it works, you can make 1 component, see how and what without any workflow settings.
Otherwise, you will need to essentially make a new site:
- A full-fledged API
- A full-fledged SPA
- Another backend to implement SSR ( vuejs.org/v2/guide/ssr.html)
Is it worth it?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question