-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google indexing errors #87
Comments
Hi! Humm, it's an interesting conundrum, though the newer report errors are a bit confusing (e.g., the "Video not found on host service" would imply that it sees a video but that video is not index-able or crawl-able, ala usually a private video on YouTube). The "prominent video" error I see from time to time, though that's because of placement and size rules. That said, I suspect I can solve for this. Let me run a couple tests this week, see if I can't make a couple tweaks. 👍 |
Hey @justinribeiro just wanted to check in a see if this is something that you've been able to look into? |
@katiedeangelis Likely same issue as here paulirish/lite-youtube-embed#105 |
Yes, it absolutely is the same issue! |
How frustrating. On the plus side, it appears it may be solvable. Fingers crossed! |
Would it be possible to have an option which autoloads the iframe from lite-youtube on load when Google bot visits the page? I am doing several tests to find out if the videos can really be indexed with lite-youtube but so far the results are inconclusive. |
Hey, I’m a huge fan of this project, which saves a ton of loading time on my site when it comes to embeds. However, I noticed that the script created an indexing problem that Google Search Console pointed out:
Essentially, it is no longer tagging these videos as videos.
I don’t know if there is an easy solution to this, but it appears that the use of this script is creating unintentional side effects that are proving potentially damaging from an SEO standpoint. Any thoughts on a potential common ground here?
The text was updated successfully, but these errors were encountered: