Meta Info not Updated for Keep Alive components

[po-trottier]

When a component is wrapped in a keep-alive tag () the Meta Info for the page is not updated after the initial load, as the created hook is not being called.

Repro steps:

1. Create a vue app with a Vue Router
2. Create 2 routes
3. Make 1 of these routes keep-alive
4. Set a different Meta Title for each route
5. Start the app
6. Navigate to the Keep-Alive page. The title will be OK
7. Navigate to the regular page. The title will be OK
8. Go back to the Keep-Alive page. The title will NOT BE OK.

The title should be updated on focus/beforeEachRoute, not on created.

[troxler]

Thanks for the bug report. Could you provide a code example to reproduce the issue?

[po-trottier]

@troxler

There you go:
https://github.com/po-trottier/vue-headful-example

Steps:

1. npm install
2. npm run serve
3. go to the about page
4. come back to the home page (by using the navigation bar)
5. Notice the title is still that of the About page

[troxler]

Thanks for that. It seems that it can be solved using the activated hook. See db4aa5e. I will do some more testing and make a release if it works out well.

[positivethinking639]

@troxler Is this method really useful for SEO? if I right-click on my website and select View Page Source, I see the title, description, keywords don't change. I look doubtful this way is correct

[troxler]

@positivethinking639 Are you referring to keep-alive components? This issue is still open and they are not supported yet. Or are you referring to vue-headful in general? Are you using prerendering or server-side rendering?

[positivethinking639]

@troxler I'm sorry. I just want to make sure. I referring to vue-headful in general. I don't use SSR. I think using vue-headful, it already supports SEO. Because vue-headful exist meta tags. So I think vue-headful had support SEO

[troxler]

@positivethinking639 A quick search on this topic lead me to this site which seems to explain the limitations of JavaScript regarding SEO (I only very quickly skimmed through it though). In short: If you want to be sure that your JavaScript page is indexed properly, you have to use either prerendering or SSR.

[positivethinking639]

So there is no proof if using vue-headful is really useful for SEO?

…

On Sun, Dec 1, 2019 at 1:42 AM troxler ***@***.***> wrote: @positivethinking639 <https://github.com/positivethinking639> A quick search on this topic lead me to this site <https://www.onely.com/blog/ultimate-guide-javascript-seo/> which seems to explain the limitations of JavaScript regarding SEO (I only very quickly skimmed through it though). In short: If you want to be sure that your JavaScript page is indexed properly, you have to use either prerendering or SSR. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#12?email_source=notifications&email_token=ANMKOXBTQVWJPFRR62SWZBDQWKXYBA5CNFSM4INC5Z4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQRH2I#issuecomment-560010217>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANMKOXF7OPCDTFYKK43UCMDQWKXYBANCNFSM4INC5Z4A> .

[po-trottier]

Yes, the plugin indeed helps for SEO. I use it in with Rendertron to serve dynamically rendered content (SSR for Crawlers, and CSR for regular clients) and my pages are index as expected, with proper meta info and all.

[positivethinking639]

So are you saying that if we only use vue-headful for our vue project, isn't that useful for SEO? We have to collaborate it with the SSR package to be useful for SEO. Right?

…

On Sun, Dec 1, 2019 at 6:34 AM P-O ***@***.***> wrote: Yes, the plugin indeed helps for SEO. I use it in with Rendertron to serve dynamically rendered content (SSR for Crawlers, and CSR for regular clients) and my pages are index as expected, with proper meta info and all. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#12?email_source=notifications&email_token=ANMKOXFMSLFDWYSNG7VQBATQWLZ7RA5CNFSM4INC5Z4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQWE7A#issuecomment-560030332>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANMKOXDVC7BJFRBPIJW7VKDQWLZ7RANCNFSM4INC5Z4A> .

[po-trottier]

Yes, web crawlers, in general, don't play nice with SPAs. You can read about it here

[positivethinking639]

Okay thanks. Maybe I will use this docs https://ssr.vuejs.org/ to implement ssr

…

On Sun, Dec 1, 2019 at 7:06 AM P-O ***@***.***> wrote: Yes, web crawlers, in general, don't play nice with SPAs. You can read about it here <https://developers.google.com/search/docs/guides/dynamic-rendering> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#12?email_source=notifications&email_token=ANMKOXEZBQQNTWL5Y7HYHI3QWL5W3A5CNFSM4INC5Z4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQWSPQ#issuecomment-560032062>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANMKOXDL2PJ7LP4U5FYI5C3QWL5W3ANCNFSM4INC5Z4A> .

[troxler]

Fixed in version 2.1.