Mobile Friendly Test
Check a URL for mobile-friendly viewport support and preview its screenshot.
Mobile Friendly Checker for Viewport and Screenshot Review
Mobile Friendly Test checks a submitted URL for a basic mobile-readiness signal and shows a mobile screenshot preview. You enter a website URL, select Start Test, and the result displays either This Website is Mobile Friendly or This Website is Not Mobile Friendly. The result area also includes a More details link and a screenshot rendered in a mobile-style frame.
This tool is designed for a quick first pass, not a complete mobile SEO audit. In the verified project code, the status is based on whether the page exposes a viewport value in the document head. That means the result is most useful for catching an obvious missing mobile viewport setup and for visually reviewing how the submitted page appears in a phone-sized preview. It should not be treated as a full replacement for manual testing, browser developer tools, accessibility review, Core Web Vitals analysis, or search-console diagnostics.
Use it when you want a fast page-level check before deeper review. If the main question is how the same page behaves across many screen widths, the Responsive Website Checker is the better next step because it lets you select desktop, tablet, mobile, and television viewport sizes after loading the URL.
How to Use Mobile Friendly Test
- Paste a public page URL into the Enter URL field.
- Use a complete URL format like the visible example https://www.example.com.
- Select Start Test.
- Review the result table to see whether the page is marked mobile friendly or not mobile friendly.
- Open More details when you want to continue the review in the external mobile-friendly testing path.
- Look at the mobile screenshot preview to spot obvious layout or rendering problems.
The tool needs a reachable URL. If a page is blocked, offline, protected by login, or unavailable to the screenshot driver, the visual preview may not represent what normal visitors see. For a basic reachability check before running visual tests, use Ping Website to confirm that the domain responds.
What the Result Can and Cannot Prove
The visible status answers a narrow question: does the inspected page expose the mobile signal the tool checks for? A positive result is helpful because a viewport tag is a common requirement for mobile layout behavior. A negative result is also useful because missing viewport configuration can make mobile browsers render a page as if it were a wide desktop canvas.
| Result element | What it tells you | What it does not guarantee |
|---|---|---|
| Mobile Friendly or Not Mobile Friendly | Whether the inspected page passes the tool's viewport-based check. | It does not prove every element is readable, fast, accessible, or tap-friendly. |
| More details | A path to continue testing outside the Gouho result table. | It does not change the submitted page or fix mobile issues automatically. |
| Mobile screenshot | A visual preview of the loaded page in a mobile-style frame. | It does not test every device, orientation, interaction, or logged-in state. |
For layout work, combine the status with visual inspection. A page can include a viewport tag and still have overflow, small text, crowded buttons, fixed-width images, or menus that do not work well on touch screens. The screenshot gives you a fast way to notice those problems before a full device test.
Practical Use Cases for Mobile Page Checks
- Launch review: check important landing pages before publishing a campaign or sending traffic from mobile ads.
- Template updates: test one representative page after a theme, header, menu, or CSS change.
- Client reporting: capture a simple status and screenshot when explaining why a page needs responsive cleanup.
- SEO maintenance: confirm the page has a basic mobile setup before moving to deeper indexing or performance work.
- Bug triage: compare a reported mobile issue with a fresh screenshot from the current live URL.
If the screenshot looks wrong but the page is marked mobile friendly, treat that as a design problem rather than a contradiction. The status and visual preview answer related but different questions. The status checks the page setup; the screenshot helps you judge what a visitor may see.
Tips for Better Mobile Review
Test the exact URL that users visit, not only the home page. Product pages, article pages, tool pages, forms, and checkout paths can use different templates. A home page can pass a basic mobile check while an internal page still has a fixed-width table, a large embedded element, or a missing viewport caused by a separate layout.
When the mobile screenshot is available, look for horizontal scrolling, content cut off at the sides, text that appears too small, buttons placed too close together, cookie banners covering the main action, and images that overflow the screen. These are practical issues that a simple yes-or-no result may not fully describe.
If the page uses redirects, test the final public URL. If the submitted URL redirects from HTTP to HTTPS, from non-www to www, or through a tracking path, the screenshot and external detail link may reflect the final loaded page. To inspect that chain separately, use the HTTP Header Checker before repeating the mobile test.
Who Should Use Mobile-Friendly Checks
Website owners can use it to confirm that important pages are not missing a basic mobile setup. Developers can use it after editing page templates or CSS that affects the document head. SEO specialists can use it as a quick screening step before more detailed mobile usability work. Content teams can use the screenshot to catch publishing mistakes that make a new page look broken on phones.
The best way to use the result is as an early warning signal. If the status is not mobile friendly, inspect the page source and template. If the status is mobile friendly but the preview still looks poor, continue with responsive layout testing and browser-based debugging.
How This Differs From a Full Responsive Preview
A mobile-friendly status check and a responsive preview are related, but they are not the same task. This page answers whether the submitted page has a basic mobile setup signal and gives you one phone-style screenshot. A responsive preview asks a broader layout question by changing the available screen size repeatedly. Use the status result when you need a fast yes-or-no screening point, and move to a responsive preview when the visual layout needs closer inspection across several breakpoints.
This distinction helps avoid overreading the result. A page can be marked mobile friendly and still need design improvements. A page can also fail a simple mobile check because of a missing viewport value even if parts of the design appear usable. The safest review process is to use the result as the first filter, then inspect the screenshot and any important templates manually.