Seo meta data broken
See original GitHub issueVersion
Reproduction link
https://github.com/nuxt/nuxt.js/issues/3957#issuecomment-424345190
Steps to reproduce
See this issue.
What is expected ?
No errors
What is actually happening?
Errors
Additional comments?
Can be prevented by disabling seo (seo: false
)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:10
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Google shows the wrong meta description for my site - Yoast
The meta description tag is missing or broken ... If your WordPress theme doesn't follow best practices, or if you're using plugins that...
Read more >Moz Pro Site Crawl Managing Metadata Issues - Help Hub
These issues concern meta information, such as page titles and descriptions. Meta issues impact how search engines process your pages and display them...
Read more >Things that hurt your SEO rankings and how to fix them, part 2
Accessibility and indexation, broken links and bad redirects, not maximizing Google Search Console, and missing / poor meta tags can hurt ...
Read more >Yoast meta data not loading - WordPress.org
Hi. When I go to the edit screen the yoast meta data (title description etc) is not loading in the post editor section...
Read more >Meta Tags for SEO: A Simple Guide for Beginners
Using the wrong attributes in the meta robots tag can have a catastrophic impact on your site's presence in the search results. Your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is not a bug with
nuxt-i18n
but withvue-meta
. I’ll let this open for visibility. Downgrading to1.5.3
should fix the problem as well.Resolved with
vue-meta@1.5.5