While there has already been an issue filed on this in the repository, it's also an issue that's gone unnoticed and unaddressed by the Unity devs for months and directly impacts the usability of NavMeshLinks. If you want to get, say, the area of an NavMeshLink, you're basically up a creek without a paddle. As far as I can tell from looking at the code, it seems Unity's navigation system currently doesn't take in NavMeshLink data as manually-created off mesh link data. So, if you're planning on using NavMeshLink data in your code, don't use them until this bug is fixed, use the old OffMeshLink script instead. It's more of a pain, however. I love the new Nav Mesh Components, and it pains me to have to highlight this problem, but it's a big oversight that really needs to be addressed.