The deliverable should be a working site. UX can and should create any necessary working documents, but what is 'signed off on' as a deliverable should be the site itself.
Wireframes, prototypes, content plans, interaction specifications, technical specs, etc are all key elements, but no one type of documentation deliverable can possibly adequately address all of those requirements.
I'd suggest reading up on Lean UX:
The basic premise of Lean UX is Agile methodologies with the ultimate goal of delivering more working user experiences and less paper based documentation.
"I'm looking for an effective way to communicate this to the stakeholders"
Axure, wireframes, etc... can't communicate the full spectrum of details that are needed to fully understand the UX to stakeholders. It's fine to show them these things along the way, but realize that they can't communicate the full spectrum of variables.
For a specific answer, what we've done in the past:
- wireframes for site flow/architecture
- component library for UI interaction specifications
- PSD files for design documentation
- content indexes to map all the necessary content to the above.
The problem is that I've never seen all of those mesh in the end when it comes to actually building the site. So, I tend to see those as popular solutions, but not necessarily efficient solution.