As with Forms, an essential part of the Pages we build are the informational labels displayed. At MS we tend to call them in short UI strings. For the majority of pages these labels, including their (textual) content, are inherited from the table fields they are bounded to. However some parts of a Page will not inherit their textual content, but are, let me call it, self containing. Some examples:
To be sure that all of the UI strings related to a Page can be translated, you have to take care that all these self containing labels have their CaptionML property populated with at least an ENU value.
Don't populate the Name property but the Caption for these controls.
Standard tools like MakeCap or make-ml to help you create (missing) caption, or a translation tool, will do this for table fields, but not for page controls.
So ... be sure to populate CaptionML for these controls!
There is no standard tool to do this. If you search for "translation" on my blog you will find some posts that give some tips on this.