I wrote the rent-a-car booking themes that thousands of rental companies run their websites on — so when your fleet pages don't rank, I'm reading your code, not guessing at it.
WordPress themes sold. Over 5,000 of them are car rental themes — autoRoyal and the rest.
Rental businesses running on code I wrote. The fleet loop, the availability logic, the booking flow.
I've seen the inside of more rental booking sites than any agency you'll ever talk to.
Every car gets a template with the same policy text, the same insurance block, the same pickup copy — and 40 words of actual difference. Google picks one and ignores the rest.
Availability loaded by script after a date is chosen, vehicles behind a POST request, prices that only exist client-side. If a crawler can't reach the fleet without picking a date first, the fleet isn't indexed.
Transmission, seats, fuel, sort order, pickup point — combined, they mint endless near-duplicate URLs with no canonical and no crawl rules. Your budget gets spent on parameter soup instead of your real pages.
Rental has some of the richest structured-data support available — vehicle attributes, price, location, hours, ratings — and most sites ship none of it. That's free eligibility left on the table.
Three airports and two downtown desks, all represented by a single "Contact" page. There's nothing for a "car rental near [airport]" query to rank, and nothing to attach a Maps listing to.
Your site can answer all three — the data is sitting in your fleet already. But there's no page. The filter shows a result on screen and leaves nothing behind: no URL Google can index, nothing to link to, nothing to rank.
CipAuto is a used car dealer I built from scratch. Different business, identical mechanics: inventory, makes, models, prices.
Every one a real URL in the sitemap — generated from the same data that on most sites never becomes anything but a filter setting.
cipauto.md/vanzari-auto-bmw-3-series-in-chisinauThat page exists because people search for it. Yours doesn't.
(The site is in Romanian. You don't need to read it to see the structure.)
I build the location pages your city and airport queries need — one per pickup point, each with its own hours, fleet subset, directions and schema, not a spun copy of the last one.
Operators with several desks usually have listings that fight each other — duplicate profiles, wrong categories, pins landing in the terminal parking lot. I sort the profiles out and wire each one to the matching page on your site.
SEO for minibus hire behaves differently: fewer searches, much higher intent, and queries built around seat count and occasion rather than car model. The page structure has to match how people actually search.
This is the part agencies write up and hand back to you. I open the theme and fix it: crawlable fleet listings, canonical rules for filters, parameters brought under control, Core Web Vitals on pages carrying a booking widget.
That's it — no form marathon, no call. I open the site, crawl it, read the theme where I can see it, and write back within 48 hours with what's broken and what it's likely costing you.
If the first pass says there's real work, I do the deep version: crawl analysis, booking-flow render test, schema audit, location and query mapping. You get a prioritised plan with effort next to each item.
I make the changes on staging, you review, we ship. Fleet templates, schema, filter rules, location pages, whatever the plan called for — the same person who found it fixes it.
A tourist rental operation on Crete, competing for the searches every visitor makes before they land. Built and maintained on WordPress.
Car leasing in a market where search behaviour is completely different from tourist rental — longer consideration, higher value per contract.
A used car dealer, and the example from the section above — the one where the make and model pages actually exist.
That's how most of this goes. I don't come in to replace anyone. I work in the code, next to whoever is already there.
You send the URL, I tell you what I see. If your site is fine, I'll say that and you've lost nothing.
Scope decides the number: how many locations, how broken the booking layer is, how much of the fleet template has to be rebuilt.
Nothing recurring. When the project's done it's done — you come back when there's a next piece of work, or you don't.
Yes for the diagnosis, and usually for the fix. Crawlability, duplicate fleet templates, filter URLs, schema and location architecture are platform-independent problems — I've seen all of them on custom builds and on the big rental SaaS platforms. Where I can't touch the code myself, I write the change precisely enough that your developer or vendor can apply it without a translation round.
They'll find the issues and send them to whoever built your site. I find them and fix them. And I'm used to working next to an existing team — that's exactly how Next Car and Clevr went. If your agency is doing good work, I'd rather work alongside them than replace them.
Indexing fixes tend to show first — getting a previously uncrawlable fleet indexed can register within weeks. Location pages and Maps work follow a slower curve, and competitive city terms are a multi-month effort. I'll tell you which bucket your situation is in during the first look, rather than promising a date I can't control. TO FILL: replace with your own observed timelines if you have GSC data to back them
No. Single-location operators are often the cleanest wins, because the whole site can point at one geography instead of splitting authority across branches. The work is smaller and so is the bill — the audit scope scales with the site.
Not much. Rental themes solve the same problems in the same handful of ways, so a fleet loop or an availability query written by someone else is still familiar territory. Having built one from scratch means I know where the shortcuts usually are, whoever took them.
Yes, that's a good share of my work. I stay behind your brand, work in your repo and your process, and talk to your client only if you want me to. TO FILL: link to your agency/partner page if you keep one
Three fields. No call, no discovery process, no drip sequence. Within 48 hours you get a written note on what I found in your booking flow, your fleet pages and your location setup — and whether it's worth paying anyone to fix.
Replies come from me, not an assistant. TO FILL: your email address, if you want it visible