HaGorer 2 (Towing & Recovery)

Towing and roadside recovery is a service people look for at the worst moment of their day: in a car that will not start, on the hard shoulder, one-handed. The search is almost always local and situational - the name of a service plus the name of an area - and every one of those pairs carries a different intent and needs a different answer. A single-page site can answer one such pair. It cannot answer twenty, because it does not contain twenty headings, twenty addresses or twenty pages Google can rank separately. That was the problem here: a structure in which every service and every service area has a page and a body of its own, without the site becoming twenty-two variants of one piece of text - and one that loads fast on a weak mobile connection, because that is the condition it will actually be read in.

The site is built in HTML and CSS alone, with no content management system and no plugins: 22 static pages served as files. That is what produces the load time in the field, and it is also what reduces the attack surface - there is no admin panel to get into and no plugin that needs updating every month. The structure is the real work. Every service and every service area has its own page with its own H1, and each page carries Schema.org markup telling Google this is a local business with a service, a service area and a telephone number rather than a page of text. Accessibility was built in rather than bolted on: heading hierarchy, alternative text, full keyboard navigation and contrast to the Israeli standard IS 5568, with no third-party accessibility widget. And the site is installable on a phone as a PWA, so someone who calls a tow truck once can leave it on their home screen and reach it next time without searching again.