Google reads your mobile site first
Google finished moving to mobile-first indexing. Its crawler now uses a smartphone user agent for nearly every site. Whatever your mobile pages show is what Google ranks.
That has practical consequences for law firm sites:
- Practice area copy, attorney bios and FAQs must be present on mobile, not trimmed for space.
- Structured data, titles, meta descriptions and alt text must match between desktop and mobile.
- Content in accordions or tabs is fine, as long as it loads in the page without a tap.
- Images and videos need the same quality and markup on both versions.
A mobile site that hides content to look clean can quietly lose rankings. Good law firm SEO starts with that parity.
The first screen decides
On a phone, the first screen is small and the visitor is often stressed. In our reviews of law firm sites, the strongest mobile homepages answer three questions before any scrolling:
- What do you handle? A plain headline: "Car accident lawyers in Tampa", not a slogan.
- Are you near me? City or region, visible without a tap.
- How do I reach you now? A large call button and a short path to a form.
Skip autoplay video, rotating sliders and full-screen pop-ups. They push the answers down and slow the page. A short line on hours or response time helps, if it is accurate.
Tap-to-call that actually connects
Many legal clients would rather call than type. Make that easy.
- Use a real tel: link (a phone link the browser can dial), not a number inside an image.
- Place a call button in the header, and consider a sticky call bar at the bottom of the screen.
- If you use call tracking, swap numbers with a script that keeps the link working and the format readable.
- Decide what happens after hours. A live answering service, a text option or a clear callback promise beats voicemail.
- Keep the number consistent with your Google Business Profile, so local search signals stay clean.
Label the button with an action, such as "Call now" or "Call for a free review" if that offer is real. A bare icon is easy to miss and unclear to screen readers. Check that the button is large enough to hit with a thumb while walking, and that it is not crowded by a chat bubble.
Test the button on an actual phone. Broken links in sticky bars are one of the most common mobile defects we see.
Forms people finish on a phone
Every extra field costs completions. On mobile the cost is higher, because typing is slow.
- Ask for name, phone or email, and a short description. Collect the rest at intake.
- Use the right input types (tel, email) so the correct keyboard appears.
- Add autocomplete attributes so phones can fill name and contact details.
- Use visible labels. Placeholder text disappears as soon as someone types.
- Show errors next to the field, in plain words, without clearing what was entered.
- Avoid puzzle CAPTCHAs. Use invisible spam checks instead.
Think about what happens after the tap on Submit. Show a clear confirmation on the same page, state when someone will respond and offer the phone number again. A silent form leaves a nervous visitor wondering if it worked, and many will submit twice or give up.
Add a short notice that submitting the form does not create an attorney-client relationship, and ask visitors not to share confidential details yet. Under rules protecting prospective clients, what someone sends you can still carry duties.
Speed on a real 4G connection
Your office Wi-Fi is not your client's connection. Someone searching from a hospital parking lot may be on a weak cellular signal.
Google's Core Web Vitals set the bar: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint within 200 milliseconds and Cumulative Layout Shift under 0.1. INP replaced First Input Delay in March 2024. Google judges these at the 75th percentile of real visits, so a fast test on your own phone is not proof.
Common mobile slowdowns on law firm sites:
- Oversized hero photos and background video.
- Chat widgets and review carousels that load heavy scripts on every page.
- Several web fonts in multiple weights.
- Tracking tags that block rendering.
Third-party scripts deserve a hard look. Every widget, pixel and embed competes with your content for the same limited bandwidth and processor time. Remove anything no one has used in a year, delay the rest until after the page is interactive, and recheck INP after each change.
Test with throttled 4G in Chrome DevTools or PageSpeed Insights. Our guide on improving website speed walks through fixes, and the background on Google's page experience signals explains how they fit into ranking.
Responsive beats a separate mobile site
Google recommends responsive design: one URL and one set of HTML that adapts to screen width. Separate mobile subdomains create duplicate content, redirect errors and parity gaps.
A responsive build should hold up from a 320-pixel screen to a wide desktop:
- Include a viewport meta tag and never force horizontal scrolling.
- Set body text around 16 pixels, and inputs at 16 pixels or larger so iPhones do not zoom on focus.
- Keep line length readable and paragraphs short on narrow screens.
- Make tables scroll inside their own container or restack them as lists.
If you are planning a rebuild, our notes on law firm website design cover structure and conversion paths.
Accessibility on a small screen
WCAG 2.2, published in October 2023, added criteria that matter most on phones. Aim for level AA:
- Target size (2.5.8). Tap targets at least 24 by 24 CSS pixels, or spaced so they do not overlap. Bigger is better for call buttons.
- Focus not obscured (2.4.11). Sticky headers and call bars must not hide the element a keyboard or switch user is on.
- Dragging movements (2.5.7). Any swipe-only control, like a testimonial slider, needs a tap alternative.
- Redundant entry (3.3.7). Do not make people retype information they already gave in the same process.
Also check how your site behaves with a phone's built-in tools. Turn on the screen reader, enlarge system text and switch to dark mode. Buttons should announce their purpose, text should grow without overlapping and contrast should hold.
Older criteria still apply: content must reflow at 320 CSS pixels, work in both orientations and meet 4.5:1 text contrast. Screen reader users on iOS and Android need real labels on buttons and form fields. Accessibility claims against websites are common in the US, so this is risk management as well as good service.
A ten-minute phone check
Before your next redesign meeting, pick up your own phone and do this:
- Search for your main practice area and city, and open your site from the results.
- Time how long until the headline and call button appear.
- Tap the call button. Does it dial the right number?
- Fill out the form with one thumb. Count the fields and note any zooming.
- Rotate the phone, then increase the system text size. Does anything break?
- Open an attorney bio and a practice page. Is the content the same as on desktop?
Anything that fails here is likely costing you calls already.




