Someone searches “print shop near me”. Google Maps shows three listings, not ten websites. The tap that follows lands on a phone, and the page has about a second to prove it is the same business as the listing.
The listing already has a name, a phone number, a category, and a pin. The page confirms those three. A redesign that changes the phone, or hides it inside a picture, leaves Maps with two businesses where there is one.
I check the markup before I touch the layout.
Put the phone in a real link
The Maps session is on a phone. The number has to be the same one as the listing, and it has to be tappable.
<a href="tel:+541100000000">11 0000-0000</a> Use the E.164 form in href, with the country code and no spaces. Show the local format as the visible text, the way people dial it. Put that link at the top of the page, in the header, not only in the footer.
A number drawn inside the hero image, or set as a background, cannot be tapped. A WhatsApp button that uses a third number, one that appears nowhere else, splits the business in two.
Write the name, the address, and the phone as text
Maps compares the listing with the words on the page. Those words have to be in the HTML.
<address> North Print <br> KM 50, Pilar, Buenos Aires <br> <a href="tel:+541100000000">11 0000-0000</a> </address> The same string belongs in the footer and on the contact page. A service-area business, one that visits the customer, states the area it actually covers. A pin in the middle of town, chosen because it looks central, points Maps at a place where nobody is served.
LocalBusiness structured data helps when it repeats that same name, address, and phone. It does not replace the visible text. If the schema says one number and the page says another, the contradiction is now machine-readable.
Make the title the trade and the place
The document title and the h1 should say what the customer typed and where.
<title>Print shop in Pilar | North Print</title> <h1>Print shop in Pilar</h1> “Integral solutions” could belong to any city. Maps has nothing to line up with the listing category. One service, one URL: /business-cards/ can say business cards, and the home page can say the trade and the area. A single scrolling page that mentions six trades in one h1 gives the listing nothing specific to confirm.
The business name stays the name on the sign and on the invoice. Adding the city to the name belongs in the title, and in the name itself only when it is already part of the brand.
Keep the first screen light
The visit is already on a cellular connection. The largest element on that first screen is what the phone has to paint.
- Give the hero image a width and a height, so the layout does not jump when it arrives.
- Serve a modern format, and a size close to what the phone actually displays.
- Leave carousels and autoplay video off the first screen. The phone number is the thing that has to be there.
A WordPress theme packed with plugins can miss this even when the design looks fine on a desktop. Each plugin that injects a font, a slider, or a chat bubble on every page delays the number the person came to tap.
If the client will edit the site, the text has to stay text
On a WordPress site the owner will change a photo and, sometimes, the phone. The editable field for the phone has to output an <a href="tel:">, not a new hero image with the number baked in.
A page builder is fine when the service name, the area, and the phone remain real text widgets. The moment those three live only inside an image widget, the listing and the page drift apart the first time someone updates the design.
The order
Category on the listing first: the trade people type. Then the same name, address, and phone on the listing and in the HTML, with the pin where the business actually works. Then recent photos of the work. Then the page, which confirms the listing instead of trying to replace it.
The map side of that order — why three listings show up, and why a farther one can rank first when Google understands what it sells — is the piece I wrote as How local SEO works.
