Sounds like you have a lot of unused indexes, yes. But you need to consider how long it is since the DMVs were reset (usually the last time SQL Server was restarted). If you have so many 0s because you rebooted the server this morning, don't go dropping any indexes based on that. Conversely, it's not only indexes with no reads that may be inefficient - you may also want to consider dropping indexes with fewer reads than updates. It's not an exact science, so test before you do anything in live, and make sure you have a backout plan in case you see any unintended effects.