What the evidence supports
- All five fetched mobile-app homepages had meta descriptions and four exposed a canonical tag in the fetched response.
- Two exposed Organization schema; one exposed Product, SoftwareApplication, MobileApplication or WebApplication schema on the homepage.
- Two named at least one tracked AI crawler in robots.txt, while one served a valid llms.txt file.
What the mobile app sample showed
Presence checks were regex-based against the fetched public response. A missing observation can mean absent markup, client rendering, bot blocking or a response variant, so raw records and hashes are published.
| Observed signal | Count | Practical interpretation |
|---|---|---|
| Meta description | 5 of 5 | Each sampled site provided basic search-result messaging. |
| Canonical | 4 of 5 | The unresolved site needs rendered inspection before a definitive issue claim. |
| Organization schema | 2 of 5 | Brand identity markup was present in a minority of fetched homepages. |
| Product or app schema | 1 of 5 | Homepage absence does not rule out app markup on a dedicated product page. |
| Valid llms.txt | 1 of 5 | Adoption was limited and should not replace crawlable product documentation. |
A better mobile app search program
Create install-decision pages
Answer device, compatibility, price, privacy, outcomes and alternative questions on crawlable web URLs.
Connect web and store facts
Keep product name, screenshots, platform support, pricing and release details consistent.
Prove the outcome
Publish transparent tests, user research or product data instead of unsupported best-app claims.
Methodology
- Selected five recognizable public sites in each of five industries before fetching results.
- Requested the public homepage, robots.txt and llms.txt with a disclosed RadiusRankResearchBot user agent and a 12-second timeout.
- Recorded final URL, status, title, meta description, canonical, JSON-LD type presence, robots signals, explicit AI crawler agents and valid llms.txt presence.
- Kept blocked, rate-limited and failed fetches in the raw dataset. No failed record was imputed as a missing on-page feature.
Limitations
- The study did not inspect Apple App Store or Google Play listing fields, rankings or reviews.
- The sample contains five named sites and is not statistically representative.
- Regex presence checks do not score accuracy, completeness, content quality, rankings or commercial results.
- A public response can vary by location, user agent, cookies, JavaScript and edge configuration.
Questions
Does this benchmark identify the best mobile app website?
No. It records a narrow set of public technical signals. It does not test rankings, usability, content quality, conversion or business performance.
Why keep blocked sites in the sample?
Removing them after collection would bias the result. They remain as failed observations and are excluded from successful-homepage feature denominators.
Sources and data
- RadiusRank 25-site AI readiness sample: Raw public fetch records, response hashes, methodology and five-industry summary.
- Google Organization structured data: Official guidance for organization identity and administrative details.
- Google Software app structured data: Official software application markup guidance and eligibility details.
Found a changed price, product limit or source? Email team@radiusrank.com with the official URL. We preserve the snapshot date instead of silently rewriting historical data.