Sounds like you are technically not "linking" the pages (to open in Chrome, Firefox, etc.). Google suspects you of ["bundling" someone else's content][1]: > We don’t allow apps whose primary purpose is to drive affiliate traffic to a website or **provide a webview of a website without permission** from the website owner or administrator. <br> The overall [Stack Exchange *Terms of Service* states][2]: > Other than as expressly set forth in this Agreement, Subscriber **may not copy, modify, publish, transmit,** upload, participate in the transfer or sale of, reproduce (except as provided in this Agreement), create derivative works based on, distribute, perform, **display**, or in any way exploit, any of the Content, software, materials, or Services **in whole or in part**. The *Terms of Service* makes allowances for the API, but does not mention WebViews or iframes<sup>‡</sup>. But [**iFrames have never been allowed** for Stack Exchange content][3] and WebViews are considered worse, by content owners -- hence why both Google [and Apple][4] closely scrutinize apps that use them. You can [contact](https://stackapps.com/contact) Stack Exchange and attempt to get clarification. (Please comment below, if they respond.) But, until then, just display the key info, from API calls in your app, and per [the API terms of service][5]. Then, in the display, you might include a hyperlink that opens in a standard browser. <br><br> ---------- <sup>‡ (It also doesn't permit browsers; so Google is in big, big trouble? (^_^) )</sup> [1]: https://play.google.com/about/ip-deception-spam/spam/webviews-affiliate/ [2]: https://stackexchange.com/legal/terms-of-service#2NetworkContent [3]: https://meta.stackexchange.com/questions/103405/should-stack-exchange-be-using-the-x-frame-options-header [4]: https://meta.stackexchange.com/a/235030/148310 [5]: https://stackexchange.com/legal/api-terms-of-use