Mobile UX Agent

It applies rules to stored crawl data, including captured viewport-like markup, headings, image and link counts, alt-text records, page text length, fetch duration, and selected words or markup patterns related to responsive images, navigation, tables, overlays, and forms. Many results are prompts for inspection, not rendered findings.

No. It does not open a mobile viewport, calculate CSS layout, measure element boxes, tap controls, scroll, use a mobile network profile, submit forms, or inspect interactive states. Complete those checks in browsers and representative devices.

No. Google primarily uses a site's mobile version for indexing and ranking, but this checker does not determine indexing behavior or ranking impact. Keep important content and metadata available on mobile, then use Search Console and real performance and usability evidence.

Yes. An initial guest scan is available without an account. A free account includes 5 scans per month; Pro and Agency plans include unlimited scans. Scan time varies with crawl size and website response.

No. The current rules only search captured text for a few inline-style or adjacent-link patterns; they do not measure rendered target boxes or spacing. WCAG 2.2 target-size checks include dimensions, spacing, and exceptions that require rendered inspection.

No. It has no device-segment analytics, funnel data, user research, experiments, or revenue evidence. Use it to assemble follow-up questions, then prioritize verified friction with mobile analytics, observation, accessibility testing, and task-based usability tests.