What kind of model do you need?
Are you capturing some information about the visual aspects? In which case wire-frames or other story-boarding techniques are good.
You also need may to capture navigation information, which can be done via story-boarding but sometimes a UML state diagram is more succint and easy to reason about.
Then you may also wish to capture the data model associated with each state, and in which case a simple UML class diagram works well.
In an AJAX-based app you also need to document the "invisible" ajax activities, and again UML state diagrams along with classes for the invoked REST services can be helpful.