In using the Microsoft Graph API to retrieve site page data, it becomes a bottleneck for content management in not being able to retrieve the underlying text data for a webPart. One can retrieve the webPart Type, ID, and Instance ID, but not the underlying data intuitively. Example: if a navigable link is placed as text it is retrievable, however if it is placed in a webPart it is not. If this information is made more accessible by the graph API, documentation & page anomalies (Discovery of End-Points, Siloed Pages, incorrect navigation, etc.) of complex sites can be extracted without burdening content creators with logging information.