Use Google Search Console's URL Inspection tool to check whether a page on your app website is indexed. Read the saved Google index result first. A successful live test answers a different question: whether the current page appears eligible for indexing. Google's URL Inspection guide explains the two views.
I make AppFound, a NaguBuilds project. I'm building it for founders investigating AI app recommendations, and it is currently prelaunch. Keep Google indexing results in a separate section of your research notes. It can help you investigate a missing website page; it does not establish that an AI assistant recommends the app.
Inspect the exact page you care about
Choose a product page or article, not just the domain. Copy its full public URL and open the matching property in Search Console. Inspect that URL using the search bar at the top.
Keep the URL unchanged in your notes. Switching between a homepage, an app page and an article can make two reports look contradictory when they describe different pages. If opening the address redirects you elsewhere, record both addresses before deciding which page you meant to check.
You need access to the site's Search Console property. A public search result is not a substitute for seeing the report for a property you manage.
Read the index result before testing the live page
Google's single-page troubleshooting guide explains how to read the verdict and expand the indexing details.
If the report says the URL is on Google, it has been indexed, but that does not guarantee appearance for a particular search. If it says the URL is not on Google, expand the page-indexing section and save the reported reason.
Check the crawl information and the canonical URL Google selected. The canonical is the version Google chose when it identified similar pages. Compare it with the address you intended to publish before treating a different URL as an error.
Record the result as it appears. "Not indexed" describes a state; the reason beneath it determines what to investigate. Avoid turning every such report into a generic instruction to rewrite the article or submit it again.
Use the live test to inspect a change
Run the live test when you need to check the page Google can access now, especially after a fix. Keep that result beside the saved index result, with its own date.
The live test does not prove that Google has indexed the page, and it cannot predict Google's selected canonical. Those limits are documented in the URL Inspection reference.
For a hypothetical app page, you might see an older index report describing a problem and a new live test that succeeds. Your note should say that the current test passed while the saved index result still shows the earlier state. Do not combine them into "now indexed" without evidence of that change.
Copy this page-inspection record
- Full URL and Search Console property:
- Page task, such as product information or setup instructions:
- Date I checked the saved index result:
- Exact index verdict and reported reason:
- Last crawl date shown, or unavailable:
- Google-selected canonical shown, or unavailable:
- Date and outcome of any separate live test:
- What changed on the page, if anything:
- One next action supported by the report:
- Date to look again, without assuming a deadline:
Fill the record from the report you can see and label unavailable fields. If you cannot access the report, resolve that access gap before drawing a conclusion about the page.
Treat search shortcuts and requests carefully
A site: search can be a quick public check, but its results are not a complete inventory. Google says an indexed URL is not guaranteed to appear in that query. Use its site-operator guidance before treating a missing result as proof of non-indexing.
After adding or fixing a page, you can request indexing when you have the required Search Console access. Google says a request does not guarantee inclusion, and repeating it for the same URL does not make crawling faster. Its recrawl guidance explains the available routes.
Keep your request date with the record. When you return, compare the new report with the saved one and check whether the reported problem has changed.
If your next question is whether an AI assistant recommends the app, use the separate AI recommendation audit worksheet. You can also visit AppFound's prelaunch page and waitlist; its visible report is an example, not a live audit of your app.