I have included a Vimeo video on the following page using the Free FV player:
The settings of the video are:
– Hide this video from vimeo.com
– Video can be embedded Anywhere
– No one can comment
– People cannot download the video
– People cannot add the video to collections.
I have also activated the video sitemap and schema features but the video deson’t appear in the sitemap and no schema is generated.
Is this normal? Do I need to have the paying version of the plugin for this to work?
I just did some more tests. I bought a pro license of FV player, then integrated to FV player with Vimeo as described here:
I removed the video from the post and from the list of FV Player videos in the admin panel, then readded it.
Yet, the video still doesn’t appear in the video sitemap:
Furthermore the schema object doesn’t appear to be created either:
Both features (video sitemap and schema markup) are activated in the settings:
I also did another test where I made the video visible to anyone, including on the vimeo.com homepage. Yet, the sitemap stays empty and the schema markup isn’t generated it seems.
Do neither of these features work? In that case, the (pro) plugin isn’t really of much use to me…
thank you for your detaled notes. The issue is that the video sitemap has to link to the actual video file (video:content_loc) or there has to be a link to the player playing the video (video:player_loc) which in fact could be the Vimeo video link. However that wouldn’t be helping with the site SEO I think.
What we can do is to link to the iframe embed link of the player for each video. Are all your videos publicly accessible, or do you have a membership section too?
The videos are set to “Hide from Vimeo homepage”. Otherwise they are accessible I think:
Up to a few days ago I used the following manually created video sitemap:
But my site was losing visitors since July 2018, but I didn’t know why.
Then a few days ago I noticed that my videos weren’t indexed anymore in Google, and after some investigation, it appeared that Vimeo retired their flash video player, which is referenced in the old manual sitemap like this:
I have now created a new manual sitemap using the following player_loc tag:
I’m not 100% if this will work, however.
What I can tell is that I have lost more than 50% of my traffic, probably because the old manual video sitemap wasn’t valid anymore with the flash player in there.
So what I’d like to do is to have a plugin that automatically generates the right video sitemap (and schema) so I don’t have to maintain this stuff manually.
That’s why I’m looking into your FV Player.
there are two possible URLs FV Player Pro could be using for video:player_loc for Vimeo. Let’s take https://foliovision.com/player/demos/vimeo-integration as an example.
The first way would be to use the FV Player iframe embed links, so for first 2 players on that page it would be:
There is a chance that it could work with the FV Player Video Link feature too:
Advantage of that approach is that it actually gives you the full website, so you can see the video in context.
Are all your videos publicly accessible, or do you have a membership section too? I’m asking as we need to figure out if we can just enable this for all players, or if we have to somehow also sense if the post is restricted for members-only.
Google seems to even recommend that it should be given access to members-only content based on reverse IP lookup – that sounds like a way to really get the members-only videos indexed, but it’s also fairly complex.
adding a checkbox which switched the video sitemap into the mode of operation suitable for your needs is not a problem, however we need to figure it out so that it’s not just another setting out there and it’s really beneficial to a lot of users.
We cannot let FV Player users reveal their private videos to the whole world that way. WordPress has some self-destructing checkboxes in it, such as “Discourage search engines from indexing this site”, but we try to not be like WordPress when it comes to serious stuff like this.
OK. Could you give me a time frame for a resolution of this problem.
Another thing I’ve alluded to previously:
I have now set up a test page with both a private and a public Vimeo video:
When I look at the video sitemap, neither the private nor the public video are included there:
Furthermore, neither the private nor the public video seems to create schema markup:
I would expect for at least the public video to appear in the sitemap and schema markup.
Any idea what is going on?
Thanks for your note.
Google’s demands on information required to index videos are somewhat unreasonable (Google have tightened them up due to spammers submitting huge sitemaps with video promised but no videos there). Each video has to be downloaded and stored by Google individually. If it’s done wrong, all of a site’s videos will be viewable directly on Google and on a specific URL, making it possible for a hacker to guess a site’s video addresses and download and pirate all the content.
After some tests, we’ve determined membership protected pages and their videos are fairly safe as Google won’t be able to index them at all.
What needs to be done to keep other spiders out of a site’s videos is reverse DNS lookup when Google comes calling, i.e. Google’s spiders will be allowed to view and download these files but others won’t. This is fairly challenging and cannot be done at the player level. It would require some custom configuration of both the web server and the cache plugin not to delay page load times substantially.
As membership videos are protected, I can see this as a less important security issues as we first apprehended. We will make advanced site map indexing available sometime in April (we have a very heavy workload). If you’d like to accelerate this work to next week with a development contribution of $100, we’d be happy to oblige you. You would be the first to get the feature and have our personal troubleshooting on your site until it’s working right for you. Of course the commercial value of this much work is more like $500 but as it will make the player better in the long run and your site is an informational one not particularly commercial, I’m able to make you this special offer for accelerated development.
Thanks for being part of Foliovision!
Making the web work for you, Alec
PS. As Martin noted, the issue with the video sitemap no longer working has to do with changes which Vimeo made to their default video formats which made it impossible for Google to determine if the videos are really there.
- This reply was modified 1 year, 4 months ago by Alec Kinnear.
I am willing to pay the $100 to contribute to the development of the sitemap feature, as this could really save me a lot of time and hassle over the long run.
Just a few points/questions before we proceed:
* Would the <video:title> and <video:description> tags be pulled from the corresponding title and description fields of the Vimeo video?
* Would the schema.org structured data tags also be populated with the same info from Vimeo?
I would also need an invoice for this for my accounting, I guess this won’t be a problem?
I have played a bit more with the Video player this weekend:
For comparison, I have also created a test page for the ARVE player that I currently use, but which has no Sitemap support:
I have identified several problems with the FV player, and written them down at the bottom of the FV player test page. Those problems would have to be adressed in addition to supporting Vimeo videos in the sitemap.
Let me know what you think.
are all your FV Player videos stored in database? I mean if you can see all of them in the wp-admin -> FV Player screen.
The thing is that we can improve the sitemap functionality for Vimeo for these, but having to support the old shortcodes make it really tricky.
I see the video sitemap improvements you have on mind on https://www.enjoy-swimming.com/test-page-foliovision.html – the video names, descriptions and duplicate <url> entries when there are multiple videos.
We could improve that too.
FV Player Schema.org implementation works with contentURL property which is basically the same as video:content_loc. So it requires an actual video file. But we could use the embed URL for the embedUrl property instead. You are right that is just uses the post title and description for these schema.org fields too a you explained on https://www.enjoy-swimming.com/test-page-foliovision.html
I would handle that as a separate issue.
All the videos you see on https://www.enjoy-swimming.com/test-page-foliovision.html are in the wp-admin -> FV Player screen, indeed.
Re shortcode functionality: As long as the schema/sitemap attributes such as name, description, video length etc. get pulled from the corresponding Vimeo video, the ability to override these values in WordPress via shortcode is not critical.
It can make sense when for example I use a Youtube video I don’t own and want to override the title/description for SEO purposes in my schema/sitemap attributes, but I don’t have that many Youtube videos I use so it isn’t that important.
It’s just that ARVE does this and in some cases such as above it can be interesting.
I have about 65 Vimeo videos on my site and only 5-10 Youtube videos, so the Vimeo sitemap/schema functionality is most important to me.
Re contentURL/embedURL: I use the following tag in my manually created video sitemap (https://www.enjoy-swimming.com/video-sitemap.manual.xml):
That’s the tag that I was given by Vimeo and my videos are now slowly getting indexed by Google, so I guess that would be the URL you need to use?
I don’t know if you can get direct access to the video file from Vimeo, and in a way this makes sense because they have different resolutions for different screen sizes AFAIK.
the issue with using https://player.vimeo.com/video/178502339 kind of URLs is that a lot of websites restrict that one from working – they only allow their videos to be accessed from specific domain.
Having all the videos in database makes this easier. But I’m still checking how to harmonize your requirements with what we need for some other websites. We can’t just forget about the websites who use the old shortcodes and no db.
we have worked on this:
1) If there are multiple videos in single post, these video:video tags are wrapped in the single url tag properly.
2) It uses the video title properly.
3) It uses the post meta description for the description field and if there are multiple videos it grabs a sentence from the previous paragraph (if there is any). This is a bit experimental, but it worked fine on our website.
Ideally there would be a SEO description field for each video. We actually did something similar for a Netflix style website recently – the field is called Synopsis and it would suit this purpose perfectly.
4) If the video can’t be linked to as it’s not a simple video file, it uses the player embed code. That way even Vimeo or YouTube videos get on the sitemap with the player_loc pointing to your website.
You can get the new version which we are currently testing here: https://github.com/foliovision/fv-wordpress-flowplayer/archive/11030502-sitemap-embed-codes.zip
You will have to first deactivate and delete the current FV Player plugin you are using. WordPress will warn you that you might loose settings and data, but it’s not the case with our plugin, no settings now videos will be lost. Or you can just replace the plugin files via FTP.
Then just make sure you are not using the “Disable Embed Button” setting, as without enabled embedding it can’t show these Vimeo and YouTube video in the sitemap using player_loc tag.
Sorry for the late reply, I have been very busy over the last few days.
I have taken a two hours this evening to install and test the updated plugin, and there are indeed a few great improvements in there!
As you have written, the title tag can now be controlled via the shortcode editor. Great! I was also able to include the Vimeo and Youtube videos in the sitemap by reactivating the embed button.
The video description tag controllable is usable, although it would be ideal to also be able to specify the description via the shortcode editor…
I also had a look at the schema.org structured data generated but I saw that that functionality hasn’t evolved yet. I guess this will be one of the next steps?
I have updated my test page with my findings at the bottom of the page:
thank you for your feedback, I’m including the relevant part of that HTML file here:
1) video:description – Ideally, description could be set via a text box in the shortcode editor (or taken from Vimeo)
2) video:publication_date – publication date is the publication date of the post and not of the videos.
3) video:duration – it would be useful to include the duration of a video in the sitemap
4) Sitemap modification date – if an item is modified in the shortcode editor in the FV Player video list page, the sitemap isn’t updated. One has to not forget to rebuild the pages on which the videos appear to have the sitemap be updated
5) All the improvements should be done for Schema.org too