We Audited 52 El Paso Business Websites. Here Is What the Scan Found.

We scanned 52 El Paso business websites with DeepAudit, the browser-based auditor we built and use on client work.

Where they came from, since a benchmark is worthless if you cannot see how the sample was drawn: we queried the OpenStreetMap Overpass API for businesses within a 16-kilometer radius of the El Paso city center that publish a website, dropped national chains and aggregators, deduplicated the domains, and scanned the surviving homepages. That produced 60 candidates, of which 52 returned a complete audit. Restaurants, clinics, contractors, retailers, service businesses across the borderland.

This is a purposive sample, not a census of El Paso and not a random one. It describes these 52 sites. Every percentage below counts hard failures only, so the number of sites with room to improve in each category is higher than what you see here.

The median score was 68 out of 100. Twenty-seven of the 52 scored below 70. None reached 90.

The median was less interesting than the repetition. The same few findings appeared across most of the sample.

Every audited page triggered an accessibility failure

All 52 of them, and the accessibility category averaged 45 out of 100, the lowest of any category.

Missing or inadequate focus indicators showed up on 40 sites. A visible focus state is what tells a keyboard user which link, button, or field is currently active. Without it, someone navigating with the Tab key cannot tell what will happen when they press Enter.

Link-label problems showed up on 36. In those cases the purpose of a link is not clearly available from its text or its programmatic context, which makes it harder for someone using a screen reader, or tabbing through a list of links, to work out where each one goes.

These are not cosmetic warnings. They decide whether a visitor can identify controls and move through the page at all. An automated scan is also not a complete accessibility audit. It tells you where manual keyboard and screen-reader testing should start.

Only 4 of the 52 declared a Spanish version

El Paso's language profile makes this worth measuring rather than assuming. Census estimates put 65.9 percent of residents age five and older speaking a language other than English at home.

Here is what we can actually say from the scan: 4 of the 52 sites published hreflang annotations declaring an alternate language version. The other 48 declared none.

Here is what we cannot say. The scan did not check whether a Spanish version existed at a separate URL without annotations, whether the translation was complete, whether the navigation and forms stayed in Spanish, or whether anyone at the business could answer a Spanish-language inquiry. Those are the questions that actually matter, and this scan did not ask them.

hreflang helps Google understand how alternate-language pages relate to each other and which one to show. Google can often identify a page's language from its visible content without it, so a missing tag is not a hole that traffic pours out of. It is one annotation on a bilingual setup that has to exist first.

A real bilingual audit would check for separate crawlable URLs per language, translated titles, headings, navigation, forms, and confirmation messages, reciprocal hreflang, correct canonicals, a crawlable language switcher that does not force a redirect based on location, and a business actually staffed to answer in Spanish. A tag cannot compensate for a half-translated site.

That deserves its own study. We have not run it yet.

llms.txt was absent on two thirds, and that is not an AI-visibility score

Thirty-five of the 52 sites had no llms.txt file.

We are reporting that as file presence and nothing more. llms.txt is a proposed convention, not an established protocol like robots.txt, and there is no documented guarantee that ChatGPT, Claude, or Perplexity use it when recommending a local business. Our later work found most of these files are generated automatically by a platform or plugin rather than written by the business.

This scan measured whether a file existed. It did not ask a single AI assistant to recommend an El Paso restaurant, so it cannot tell you who those assistants name.

The questions worth asking are whether the site publishes its services, location, people, and contact details in crawlable HTML, and whether those facts agree with its external profiles.

The rest of the findings

• No JSON-LD structured data on 30 of 52. Organization or LocalBusiness markup makes your name, address, hours, and service area explicit rather than inferred from the page. It should describe what a visitor can already verify, and it does not replace a complete Google Business Profile.
• Main heading failed on 28 of 52. Missing, empty, or otherwise failing the heading rule. Worth splitting into those subcategories before acting, because they do not mean the same thing.
• Under 300 words on 30 of 52. That is the scanner's threshold and a reason to read the page, not proof it cannot rank. A short contact page can be complete. A long service page can still fail to answer the question.
• No HSTS header on 27 of 52. That is a browser-security finding, not a content or ranking one, and it belongs in the security section rather than beside the SEO checks.

Some of these are one-line changes. Others need content, translation, or template work the business may not control.

What this sample tells us, and what it does not

The same categories kept recurring across 52 sites: accessibility, structured data, headings, content length, and security headers.

Fixing them produces a clearer, more usable website. It does not tell you who will rank first in El Paso, who an AI assistant will name, or who can successfully serve customers in Juárez. Google says local results turn mainly on relevance, distance, and prominence. Your website is one input. Your Business Profile, reviews, categories, location, language quality, and what happens after an inquiry arrives are others, and this scan looked at none of them.

The scan tells you where to investigate. You still have to decide what the evidence means.

Check your own site

Run the free audit on your own site. No signup, no credit card, and the report is yours to keep. Then open the important pages and verify the findings, because an automated tool can show you a pattern and not much more. It certainly cannot tell you whether your Spanish translation is trustworthy or your customer journey works.

If you would rather we read it with you, book a free 15-minute teardown and we will walk through what it found, live, no pitch.