This is a common question that the answer, for some, causes angst. Stated in the words of one user, "whaddya mean I can't align the view on one sheet with the view on another sheet exactly??!!??"
With other software people are accustomed to orienting their work with a notion of a Cartesian coordinate system (X,Y,Z) even for a sheet. With Revit the sheet is a bit nebulous. This is just a view that a title block family is placed in automatically when you create it AND can also host other views, a special version of a regular view. There isn't a coordinate system in this view, there is, but it isn't obvious to us. The title block family provides this reference for us but if it were to be deleted you'd be lost with no way to determine where you really were looking relative to another sheet.
Technically Revit just uses the outer boundary lines of a title block family to define the scope of the view to print. I'm referring to the rectangle boundary lines you find in the title block templates provided by the installation. It really doesn't matter where you put the views on the "sheet", well....not to Revit.
What is the objection? People want a floor plan on one sheet to sit directly above the floor plan on the next or subsequent sheets so that it doesn't "walk" back and forth or shift its location as you flip from page to page. Revit's "attitude" on this has been..."close enough is good enough". This is the characterization that drives some people crazy. I too was a bit perturbed years ago. I guess I've mellowed some since.
Here's my take on it. In a set of many sheets the portion of the set that will benefit from such precision is probably a relatively small number. Plans of the same scale certainly ought to be positioned on sheets so you see the project from the same "viewpoint" for each. As soon as you start showing partial, enlarged or other plans the relevance of the alignment between sheets is lost or at least less relevant.
That might seem an excuse to not bother to provide the ability to align them? I suppose at some point it might have been a factor in the decision to devote time to it from a software developer's perspective. In the scheme of things they probably thought that a roof tool would bring more value or importance than aligning views between sheets, so it dropped somewhat in the "To Do List". I imagine somewhere, in some office, they are wrestling with this sort of "can we do this or can we do that" argument every day.
What are your options then?
A view placed on a sheet is very much like a piece of paper on your desk. You can slide the paper around your desk (assuming it isn't cluttered) but there really is no point of reference between the paper and the desk. On the real desk eventually the paper will fall to the ground if you push too far. In Revit there is no real edge except for those lines in the title block family, outside of those Revit stops trying to print your work.
Two sheet views are a lot like two separate desks with their own paper and no real relationship between the two at all.
If you want these views to "stack" on these sheets you need to provide some point of reference and that reference can be the title block family itself. Some users will draw a detail line from a fixed point on their title block (in the sheet view) to a location on the sheet where they'd like their plan view to "sit". This line is then copied to clipboard and then Paste Aligned/Current view in the next sheet view. This gives you the same point for reference. Unfortunately the model visible in the plan's view port will not snap "through the view port" to this line so you are back to "close enough is good enough". If you zoom in you can get it so close that it won't be noticeable unless you export to dwg and then externally reference those files together, which does happen now and then.
Another technique is to provide a set of lines in the title block family itself that can be turned of by using a yes/no parameter associated with the Visible parameter for the line(s). Imagine the detail grid of the NCS/UDS (National Cad Standard / Uniform Document System). You can also store a "cross hair" somewhere or in several locations for this purpose. Think a little outside the proverbial box and you can get much more satisfying though not precise results.
Remember that "close enough is good enough" happens all the time...our tolerance for it just changes depending what the activity is.