Build · Directory
MechanicRank, a Repair Shop Directory Built Like a Pipeline
MechanicRank is a directory where drivers find repair shops. It is a static site built from a staged data pipeline, and a gate at the end refuses to publish if any stage came back short.
- Year 1Website
- Year 2Map Listings
- Year 3Booking Tool
- Year 4Front Desk
- Year 5Payments
- Year 6Reports
Same six pieces.
Built once. Switched on in hours.
The Short Version
- Four stages run in order: ingest, certifications, claims, build.
- An integrity gate stops the build when data is partial, so a bad night never reaches the live site.
- Shops can claim their own listing and fix what is wrong.
- New and changed pages are sent to search engines through IndexNow every day.
| Site type | Static build |
|---|---|
| Pipeline | Ingest, certifications, claims, build |
| Safety | Integrity gate before every build |
| Owner action | Claim a listing |
| Search pings | IndexNow, daily |
| Hosting | Static files at the edge |
- IngestShop recordsDedupe by phone
- CertificationsMatch by idNever by name
- ClaimsOwner editsVerified details
- Integrity gateCounts checkedRefuse if short
- BuildStatic pagesSitemapIndexNow ping
The Problem With Most Shop Directories
A driver with a check engine light wants one thing. A shop near them that is open and good at the job. Most directories make them work for it. Half the listings are closed. The phone numbers are old. The shop pages all say the same sentence with a different city pasted in.
The shop loses too. Its listing is wrong, and it has no way to fix it. A customer calls a dead number and books with someone else.
We wanted a directory where the data was checked before it went live, where a shop could fix its own page, and where every page said something true about that one shop.
What We Built
MechanicRank is a static site. There is no database behind the live pages. Every page is a plain file built ahead of time, which is why it loads fast and cannot fall over under traffic.
The files come out of a pipeline that runs in stages.
- Ingest. Shop records come in and get cleaned. Duplicates collapse on the phone number, because two listings with one phone are almost always one shop.
- Certifications. Shops that hold trade certifications get them attached. Records are matched by id, never by name, because two shops can share a name and one shop can go by three.
- Claims. When an owner claims a listing and fixes a detail, that fix wins over anything the pipeline found on its own.
- Build. The site, the sitemap and the search pings come out the other end.
Drivers never sign in. The shop is the page, and the driver is a visitor. That one choice shapes the whole site.
How It Is Wired
Each stage writes its output to disk and the next stage reads it. That makes every stage easy to rerun on its own. If the certifications step fails, you fix it and run it again. You do not start from the top.
Between the last data stage and the build sits the integrity gate. It compares what came in against what was there last time. If a stage returned far fewer records than before, or a required field went empty across a whole state, the gate stops. The live site stays as it was. Nobody wakes up to a directory with half its shops missing.
After a good build, a daily job sends new and changed pages to search engines through IndexNow. It only sends pages it has not sent before. You can read more about how that works on the search and indexing page.
What Broke and What We Changed
A Short File Looks Like Closed Shops
A data stage can hit a limit partway through and still write what it has. The file looks fine. The build does not know it is short. It builds a site with gaps, and the gaps look like shops that closed. We have watched fetchers in our network record a failed call as an empty result. That is the failure the integrity gate exists for. A short stage stops the build instead of shipping it.
Names Are Not Ids
Matching by shop name is how a badge lands on the wrong shop. Two shops in one metro can share a name, and one shop can go by three. We match every record on a stable id and do not trust names at all.
Pages That Said Nothing
A template sentence with the city swapped in is the kind of page that makes a search engine distrust a whole site. We rewrote the pages so the opening lines come from the shop's own data. Paste one shop's opening under another shop and it stops being true. That is the test.
What the Directory Deliberately Does Not Do
Some choices were about what to leave out.
- It does not invent ratings or reviews. A directory that makes up a star rating is one complaint away from losing every ranking it has. If a shop has no reviews on file, the page says nothing about stars.
- It does not ask drivers to sign up. A driver with a warning light has no time for an account. The page gives them what they need and gets out of the way.
- It does not write straight into a CRM. When a driver sends a request or an owner claims a page, the directory hands off one clean record and stops. A site that knows another system's tables breaks the day that system changes.
- It does not build from a guess. If the gate is unsure, the old site stays up. A stale page for one more day beats a wrong page for anyone.
Each of these makes the site a little less clever. Each one keeps it trusted.
What It Means When You Switch It On
If you own a shop, you get a listing you can claim and correct. The driver who finds you sees your real hours, your real phone and your real certifications. And because the page is built from your record, it says something about your shop and not about every shop.
If you want a directory of your own, the same pipeline shape carries over to any trade. Stage the data, gate the build, let owners claim, and ping search engines when pages change. We wrote down how to do that without stamping the same template on every site in the directory factory.
Questions People Ask
How do I claim my shop on MechanicRank?
Find your shop's page and use the claim option on it. Once you verify you run the shop, your fixes take priority over anything the pipeline found.
Why is my shop's information wrong?
Listing data goes stale as shops move and change numbers. Claiming your listing is the fastest way to fix it, and your corrections win on the next build.
Do drivers need an account to use it?
No. Drivers search and read without signing in. Only shop owners sign in, to claim and fix their listing.
How fast do changes show up?
They go live on the next build. New and changed pages are then sent to search engines through IndexNow the same day.
We sell time
Get Years of Building Switched On in Hours
A thirty minute call. A written price. Nothing built until you say yes.