Mobile-first indexing

The phone version is the version on file

Most sites are one site that rearranges itself by screen size. That part is fine. The trouble starts when the phone layout does not just rearrange things but drops them: a service table, a paragraph of detail, a block of questions, the list of towns in the footer.

If it is missing from the phone version, it is effectively missing, because that is the copy the search engine keeps. Content tucked inside a tab or an accordion still counts, since it is there in the page. Content deleted from the small-screen layout does not.

Say a plumbing company lists fourteen towns it serves in a footer that is switched off on phones. On a laptop the site states plainly where it works. On file, it says nothing of the sort.

The same goes for the parts nobody looks at. Images, headings, and structured data need to be present in the phone version too, not only in the wide one.

The idea behind it is not a fashion. Search engines once built their record of a site from the wide layout, then the searching moved to phones and the record moved with it. The mechanic has been steady since: one crawl, small-screen layout, that is the copy on file.

Why this lands harder on a local business

People search for a locksmith or a tree crew where the problem is, which means outdoors, one-handed, in a hurry. So the version of your site a search engine reads is also the version most of your customers see. Those used to be two separate arguments. They are now the same argument.

There is a second half that has nothing to do with crawlers. A page can be stored perfectly and still be miserable to use one-handed: a phone number printed as plain text instead of something you can press, buttons packed so close that a thumb catches the wrong one, a services list set in type that needs pinching to read. Search engines read the first problem. Customers feel the second.

The durable answer is one site that serves the same content at every width and is drawn for the small screen first, which is how we approach custom web design.

It shows up in the small pieces too. A one-tap review-request tool we built for a New Jersey glass and mirror shop only works because it assumes the customer is holding a phone, not sitting at a desk.

What it does not mean

It does not mean desktop visitors stopped counting. They still hire people. It means the phone layout is the one being read and stored.

It does not mean you need a separate mobile address, the sort that starts with an m. That leaves two sites to keep in step, and one of them always drifts.

It does not mean the wide layout can be an afterthought either. It means the two have to say the same thing. Whichever one gets drawn first, the content is not allowed to differ.

It does not mean short pages win. A long page a phone can comfortably read beats a short page that had the details cut out of it.

And it has nothing to do with apps. An app is a separate thing you ask someone to install. This is about the website you already have.