Technical SEO · Supporting checklist

Mobile SEO Checklist

A mobile SEO checklist is a technical review of the content, search signals and usable journeys your site delivers on a phone. Start with representative pages, compare important mobile content with desktop, and test navigation, layouts and forms. Finish by repeating the repaired journey on an actual phone and keeping performance findings in their own measured workflow.

Free to useNo account neededSaved in your browser
Desktop and phone page layouts showing matching content, with a magnifying glass over the phone’s touch button.
Compare mobile content and check how navigation, buttons and page features work on a phone.
Your working checklist

Work through the checklist

Click a square to mark a task as Pass. Click again to undo. Use the result menu for a problem, a blocker or a task that does not apply. You do not need to enter notes.

14 checks

Check Mobile Content and Search Signals

Mobile content parity means keeping the useful page information and intended search signals available in the mobile version. The layout can differ while the substance remains equivalent.

Choose mobile templates and real visitor journeys

Cover the pages and actions that matter on a phone.

Use this for: The representative public pages selected for this review.

Choose an important URL from each relevant template: homepage, service, article, category and product. Include a long page, a deep landing page and a page with a form or filter. For each one, name the main information and action a visitor should find.

Open the same URLs on desktop and in a narrow browser viewport, then plan a real-phone check. Note the tested browser and device when useful. A desktop window made narrow is a layout check, not proof that an actual phone browser behaves the same way.

Example

Hypothetical example: A repair business checks its service page, a pricing article and a booking form instead of assuming that a good homepage covers all three.

  1. Select examples from the important templates.
  2. Name the information and action expected on each.
  3. Keep the same URL set for desktop, emulation and phone tests.
More help and optional notesHigh · SEO lead and site owner
PassThe sample covers the important templates and visitor actions.
FailOnly the homepage or a convenient screen size is tested.

If it fails: Add the missing template or journey before generalizing.

Retest: Refresh the sample after a redesign or a new page type.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Identify responsive, dynamic or separate mobile pages

Apply the right checks to the way the site is built.

Use this for: The representative public pages selected for this review.

Open one URL on desktop and phone and compare the final addresses. Ask the developer whether the site uses responsive CSS on the same HTML, different HTML at the same URL, or separate mobile URLs. A changed layout alone does not establish which architecture is in use.

Keep a same-content desktop/mobile pair for separate URLs. For dynamic serving, ask the developer to test both response variants and the caching behavior so the wrong version is not reused. You do not need a separate mobile domain simply to support mobile-first indexing.

Example

Hypothetical example: A catalog stays on the same product URL but receives a shorter mobile response. The team audits the response content as well as the CSS.

  1. Compare final addresses on both devices.
  2. Confirm the delivery method with the developer.
  3. Identify the page pairs or response variants to test.
More help and optional notesMedium · SEO lead and developer
PassThe architecture and relevant response variants are known.
FailThe audit assumes responsive delivery from appearance alone.

If it fails: Confirm the actual delivery method before changing canonicals or redirects.

Retest: Check the same sample after template or cache changes.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Compare important mobile content with desktop

Keep the useful answer available in the mobile version.

Use this for: The representative public pages selected for this review.

Compare the main heading, service or product details, explanatory text and meaningful images on the paired views. On long pages, search the rendered document for a distinctive sentence from each important section. Record a missing section as a specific content gap rather than a general mobile score.

Accordions can organize a smaller screen; the crucial distinction is whether the content is available in the rendered page or fetched only after a tap. Preserve the useful substance and headings while allowing the visual layout to differ.

Example

Hypothetical example: A desktop product page explains compatibility and returns, but the mobile template omits both. The fix restores those answers in accessible mobile sections.

  1. List the essential sections in the desktop view.
  2. Find their equivalents in the mobile rendered content.
  3. Restore missing substance without forcing an identical layout.
More help and optional notesHigh · SEO lead and developer
PassThe mobile page contains equivalent useful main content and meaningful headings.
FailImportant details disappear from the mobile response or render.

If it fails: Restore the missing content in the mobile template.

Retest: Compare the corrected page and another page using that template.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check the mobile rendering Google can retrieve

Separate what a visitor sees from what the testing tool retrieves.

Use this for: The representative public pages selected for this review.

For an important public URL, use Search Console URL Inspection when available. Distinguish the stored indexed-page information from a live test. In the live result, inspect the rendered HTML and screenshot for the main heading, key details and navigation, then check reported resource failures.

Compare this with a fresh browser load. If public CSS, scripts or images are blocked, give the exact resource to the developer. Keep private routes and security controls protected. A successful live test shows that test result; it does not guarantee indexing.

Example

Hypothetical example: A phone displays a product description after a tap, but the live test HTML lacks it. The team investigates interaction-dependent loading before requesting another review.

  1. Run a live inspection of the public sample.
  2. Compare rendered HTML and screenshot with the expected content.
  3. Investigate specific missing content or resource errors.
More help and optional notesHigh · SEO lead and developer
PassThe tested mobile render exposes the expected public content without unresolved blocking errors.
FailEssential content is missing or an important public dependency cannot be retrieved.

If it fails: Repair the relevant content delivery or public-resource restriction.

Retest: Repeat the live test after deployment and keep indexing conclusions separate.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Compare titles, descriptions, directives and structured data

Prevent a mobile template from changing the intended search signals.

Use this for: The representative public pages selected for this review.

Ask the developer or use an approved crawler to compare the page title, meta description, robots directives, canonical and relevant structured data for desktop and mobile responses. Check the actual response or rendered head rather than a CMS setting alone.

For a responsive single URL, the same page should not gain an accidental mobile-only noindex. On separate mobile URLs, use the architecture-specific relationship check below instead of forcing every URL to self-canonicalize. Verify that structured data still describes content visitors can find. Keep titles and meta descriptions equivalent in meaning across mobile and desktop versions.

Example

Hypothetical example: A mobile template inherits a noindex setting from development while desktop is indexable. The team fixes the mobile response before evaluating search traffic.

  1. Compare the actual head and applicable response directives.
  2. Identify unintended device-specific differences.
  3. Confirm structured data matches the visible page.
More help and optional notesHigh · SEO lead and developer
PassThe paired responses preserve the intended metadata, directives and accurate structured data.
FailMobile delivery introduces an unintended indexing restriction or conflicting signal.

If it fails: Correct the mobile template and any cached response containing the old signal.

Retest: Inspect both response variants after the fix.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Test equivalent destinations on a separate mobile site

Avoid sending every phone visitor to a generic page.

Use this for: Sites with separate mobile URLs.

If the site uses separate mobile URLs, open a deep desktop page on a phone and confirm that any redirect reaches its equivalent mobile content. Check that both versions load the intended page instead of an error or the mobile homepage.

Have the developer verify the paired canonical/alternate relationship: the mobile page points to the corresponding desktop canonical, and the desktop page identifies its mobile alternate. On multilingual separate-URL sites, check that language alternates connect the appropriate mobile versions. Skip this item for a single responsive URL.

Example

Hypothetical example: A desktop service-detail URL redirects to the mobile homepage. The fix maps it to the matching service page and preserves its identity.

  1. Open several deep desktop URLs on a phone.
  2. Confirm each has the correct mobile equivalent.
  3. Validate the paired canonical/alternate and applicable language annotations.
More help and optional notesHigh · SEO lead and developer
PassSeparate mobile routes preserve equivalent content and correct page-pair signals.
FailUnrelated pages collapse to one mobile destination or pair annotations conflict.

If it fails: Repair the one-to-one mappings and relevant annotations.

Retest: Retest direct visits, redirects and page heads for each corrected pair.

Not applicable: The site uses one responsive URL per page.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Test Mobile Layouts and Complete Journeys

Mobile usability checks cover reading, navigation and actions under real phone conditions. A page that looks good in a screenshot can still fail when the keyboard opens or a menu is tapped.

Check width, orientation and page overflow

Keep the main page readable within a phone screen.

Use this for: The representative public pages selected for this review.

In browser device mode, try a narrow phone width, a wider phone width and landscape. Scroll from top to bottom and look for clipped headings, images that push the page sideways, and fixed bars that cover content. Inspect the viewport setting if the whole page appears shrunk.

Ask the developer for a device-width viewport and flexible layout where needed. Keep necessary two-dimensional content, such as a wide comparison table, in a clearly scrollable local container rather than making the entire page scroll sideways.

Example

Hypothetical example: A pricing table forces the service heading offscreen. The repair confines sideways scrolling to the table and leaves the rest of the page within the viewport.

  1. Test narrow, wide and landscape layouts.
  2. Find the element causing clipping or page-wide overflow.
  3. Recheck after the layout or viewport correction.
More help and optional notesHigh · SEO lead and developer
PassOrdinary content fits the viewport and any necessary wide component remains usable.
FailThe page is shrunk, clipped or requires page-wide sideways scrolling to read ordinary text.

If it fails: Correct the viewport or overflowing component without hiding important content.

Retest: Repeat the same widths and orientation changes.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check readable text and text enlargement

Let visitors read without losing controls or content.

Use this for: The representative public pages selected for this review.

Read the introduction, body copy, captions and form labels on a phone. Increase text size or browser zoom and check whether text overlaps, buttons lose their labels or content becomes inaccessible. Include a page with long headings and an error message.

Ask the developer to retain zoom and use flexible containers. Test text enlargement up to 200% as a focused accessibility check; a single font-size number does not prove readability or full accessibility compliance.

Example

Hypothetical example: Enlarging text hides the final line of a service description inside a fixed-height card. Removing the fixed height preserves the full answer.

  1. Read important text at the default size.
  2. Increase text size or zoom and revisit the controls.
  3. Fix clipping, overlap and disabled zoom.
More help and optional notesMedium · SEO lead and developer
PassText remains readable and enlargement does not remove necessary content or functionality.
FailEnlargement hides labels, clips answers or prevents the main action.

If it fails: Use flexible sizing and preserve user zoom.

Retest: Recheck the affected templates with enlarged text.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Test touch targets and sticky controls

Make the intended action easy to select.

Use this for: The representative public pages selected for this review.

On a phone, tap the menu, close buttons, pagination, filter controls and main action. Watch for accidental neighboring taps and controls covered by a sticky header, cookie banner or chat widget. Test the real clickable area, not only the visible icon.

If a target is small, ask for a larger hit area or more separation. WCAG 2.2 AA uses a 24 by 24 CSS-pixel minimum with defined exceptions, including spacing; many important controls benefit from more generous sizing. This is an accessibility check, not a search-ranking threshold.

Example

Hypothetical example: A tiny close icon is next to a promotion link. Expanding its clickable area and adding separation makes the intended dismissal reliable.

  1. Tap important and closely spaced controls.
  2. Check their hit areas and any overlapping fixed elements.
  3. Increase size or spacing where taps are unreliable.
More help and optional notesMedium · SEO lead and developer
PassThe tested controls can be selected reliably without nearby or overlapping targets interfering.
FailSmall, crowded or covered targets prevent reliable selection.

If it fails: Adjust target size, spacing or fixed-element placement.

Retest: Repeat the same taps on the phone after the change.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Follow mobile menus and deep-page links

Keep important destinations reachable on touch devices.

Use this for: The representative public pages selected for this review.

Open the mobile menu, follow a category or service link, visit a deeper page and return. Check that navigation does not require hover and that menu controls open, close and leave the page usable. Test pagination or category links where a long list extends beyond the first screen.

Ask the developer to confirm that destination links use real anchors with usable href values. A working menu animation alone does not establish crawlable links. Do not remove important navigation solely to make the header smaller.

Example

Hypothetical example: A desktop submenu opens on hover, but no tap exposes its service links on a phone. The team adds an operable disclosure and retains real destination anchors.

  1. Navigate from the mobile menu to a deep destination.
  2. Test closing, returning and later listing pages.
  3. Verify real destination links in the rendered markup.
More help and optional notesHigh · SEO lead and developer
PassImportant destinations remain reachable through operable mobile navigation and real links.
FailHover-only controls, dead menus or missing anchors block the route.

If it fails: Repair the control behavior and destination anchors.

Retest: Repeat the complete navigation journey from a fresh load.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Try the main form with the on-screen keyboard

Catch mobile failures that a static screenshot misses.

Use this for: Pages with forms or interactive search.

Open the contact, quote or search form on a phone. Tap each field and check its visible label, keyboard type, validation message and next control. Confirm that the keyboard and sticky bars do not cover the active field or the button needed to continue.

Use a safe test environment or an approved test submission for a form that creates a real booking, order or message. Preserve entered information when fixing validation errors. A small-screen appearance check does not establish that the full transaction works.

Example

Hypothetical example: A quote form looks correct until the keyboard opens and covers the Continue button. The layout is adjusted before testing the approved submission path.

  1. Open the keyboard for each important field.
  2. Check labels, errors and the next action.
  3. Use an approved test path to verify completion where applicable.
More help and optional notesHigh · Site owner and developer
PassThe tested mobile form remains understandable and operable through its approved test path.
FailKeyboard overlap, missing labels or inaccessible errors block completion.

If it fails: Repair the affected field or keyboard-aware layout and validation behavior.

Retest: Repeat the same test with the error state as well as valid input.

Not applicable: The selected pages have no forms or search controls.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check promotions and consent overlays on arrival

Keep the page answer accessible when a visitor arrives.

Use this for: Pages with consent dialogs, promotions, chat overlays or app prompts.

Open a public landing page in a fresh browsing session and check what appears before and after scrolling. Test closing a newsletter offer, chat panel or app promotion. Verify that the page remains readable and scrollable after dismissal.

Replace unnecessary full-screen promotions with a less obstructive presentation. Keep legally required consent or age-verification behavior intact and have the responsible team review it; do not remove required controls merely to improve a mobile test.

Example

Hypothetical example: A welcome offer covers the service details and its close button sits outside the phone screen. A smaller dismissible panel fixes access to the answer.

  1. Check the first visit and triggered overlay states.
  2. Test dismissal and restored page scrolling.
  3. Repair discretionary obstruction while preserving required controls.
More help and optional notesHigh · SEO lead and developer
PassVisitors can reach the main content and operate the relevant dialogs.
FailA discretionary overlay hides the answer or leaves the page unusable after dismissal.

If it fails: Reduce or repair the obstructive presentation.

Retest: Retest a fresh visit and the trigger that originally caused the problem.

Not applicable: No overlays appear in the tested journey.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Verify the repaired journey on an actual phone

Confirm the practical result beyond desktop emulation.

Use this for: The representative public pages selected for this review.

Repeat the priority journey on a real phone after the fixes: open the landing page, read the answer, use the menu and operate the approved form or product interaction. Where practical, cover the browser families your audience uses, such as Safari on iPhone and Chrome on Android.

Check portrait and landscape, back navigation and a fresh visit. If you only have emulation available, keep that limitation clear and leave the real-device check unfinished rather than marking it passed.

Example

Hypothetical example: Emulation passes, but the iPhone keyboard hides a form error. The actual-device retest catches the remaining issue before the audit is closed.

  1. Open the repaired public pages on an actual phone.
  2. Repeat the full journey and relevant orientations.
  3. Retain any unavailable device check as untested.
More help and optional notesHigh · Site owner and QA reviewer
PassThe repaired priority journey works on the actual device/browser combinations tested.
FailA real-device failure remains or emulation is presented as a physical-device test.

If it fails: Fix the reproducible device issue or arrange the missing test.

Retest: Repeat the original journey after each relevant repair.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Prioritize parity failures before cosmetic refinements

Turn the mobile review into a short repair plan.

Use this for: The representative public pages selected for this review.

Group repeated findings by template. Put missing main content, unintended noindex, wrong destinations and blocked main actions ahead of cosmetic spacing changes. Give each fix a concrete URL and an expected result so the responsible person knows what to retest.

Route slow loading or poor responsiveness to the Core Web Vitals and page-speed checklists. Mobile layout, field performance and indexing are related checks with different evidence. Optional notes can help you return to a finding, but you can use the checklist without writing a report.

Example

Hypothetical example: One shared menu defect affects twelve service pages. The team fixes that component once, then retests several services and the original failing phone journey.

  1. Group findings by the shared component or template.
  2. Assign the most consequential content or journey failure first.
  3. Retest representative pages after the shared fix.
More help and optional notesHigh · SEO lead and site owner
PassEach actionable mobile failure has a clear next fix and repeatable check.
FailThe review ends with a score and no identifiable repair.

If it fails: Convert the largest unresolved failure into a specific task and owner.

Retest: Revisit the same pages after the repair.

Not applicable: No pages or features in the stated scope require this check.

Optional: the URL or template, what you found and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Reset this checklist?

This removes saved statuses, evidence and result dates for the checks on this page. Other checklists keep their records. Export a CSV first if you need a copy.

A useful result, every time

Check a task. Choose a result.

This is a manual SEO workflow. It helps you decide what to investigate and keep a usable record. It does not crawl your website or verify your answers automatically.

  1. Choose your scope. Pick the relevant task group and representative pages you are authorized to inspect.
  2. Run the stated check. Follow the steps, then choose your result. Click the square for Pass, or use the result menu for another status. You do not need to type anything.
  3. Assign the next action. Fix a problem when you can, or ask the right person for help. Optional notes can remind you what to do next. Check the result again after a fix.

What your progress means

Review progress counts passes and failures against applicable checks. Failed work still counts as reviewed. Blocked and untested checks remain unfinished. This is not an SEO score.

Untested
You have not checked this yet.
Pass
You checked it and it works as described.
Fail
You checked it and found something to fix.
Blocked
You need access, information or someone’s help.
Not applicable
This task does not apply to your website.

Export CSV downloads the checks currently shown and any optional notes. Print expands the instructions for that view. Saved results stay in this browser; there is no account sync.

Apply the workflow

What Should You Do After the Mobile Checks?

Use the findings to repair a specific template or journey, then choose the relevant deeper workflow for rendering or performance problems.

What Should a Mobile-First Parity Report Include?

A mobile-first parity report pairs each important template with the content and action expected on a phone. Keep the device or test type alongside the result so a browser simulation is not mistaken for a physical-device check.

This hypothetical table is a format you can copy into your own working notes. Export CSV on this page saves checklist results and optional notes; it does not inspect your website automatically.

Hypothetical mobile findings and the next repair.
SampleMobile findingNext actionRetest
Service detailPricing answer absent from mobile content.Restore the section in the shared template.Compare rendered content and the actual phone view.
Product categorySubmenu requires hover.Add an operable touch disclosure with real links.Reach the category from the mobile menu.
Quote formKeyboard covers the validation message.Repair error positioning and scrolling.Repeat the approved form test on the affected phone.

Which Tools Should You Use for a Mobile SEO Audit?

Use browser device mode for responsive layout checks, Search Console URL Inspection for relevant rendering and indexing information, and an actual phone for touch, keyboard and browser behavior. Use PageSpeed Insights for performance diagnostics and available field data.

Google retired the Mobile-Friendly Test and Search Console Mobile Usability report in December 2023. Do not make either retired tool a required step in your current audit.

Can You Put Mobile Content Inside Accordions?

You can put mobile content inside usable accordions when the content remains available to visitors and the rendered page. Check whether a tap merely reveals existing content or starts the only request that fetches it.

For important search content, avoid depending on a click, swipe or typed query to load the answer. A compact layout and missing content are different situations.

Is Responsive Design Enough for Mobile SEO?

Responsive design helps a layout adapt to screen width, but it does not establish content parity, correct directives, working navigation or a usable form. Test those conditions on representative pages.

A good mobile experience does not guarantee indexing or higher rankings. Keep rendering, indexing and performance conclusions tied to their own checks.

Which Checklist Should You Use for a Related Mobile Issue?

Follow the workflow that owns the failure, then repeat the mobile journey after the repair.

Continue With a Focused Technical Review

Use the workflow that matches the discovery, rendering or delivery issue you are investigating.

A clear process, with honest limits.

Follow the steps, choose the result that matches what you found, and check again after changes. Notes are optional. A completed check does not guarantee indexing, traffic or rankings. How the checklists work.