How was drivnhub.com built, and how can I check it?

Why show how my own site is built?

Because Drivn is new, and I'd rather show you work you can check than ask you to take my word for it. Client case studies will go up as projects finish, with real before-and-after numbers. Until then, this site is the clearest example of how I build, and everything below can be verified in a few minutes without asking me anything.

How is it built for speed?

The site is written in code rather than assembled in a drag-and-drop builder, so each page only loads what it actually uses. Most pages are pre-built ahead of time, so the server hands over a finished page instead of building it on every visit. Images are served in modern formats at the right size for each screen, and the styling is inlined so nothing blocks the first paint.

You can test it yourself on PageSpeed Insights. My guide on reading a PageSpeed report explains what the numbers mean.

How is it structured for Google and AI tools?

Every page carries structured data (schema) describing what it is, in a format search engines and AI tools read directly. Across the site that includes:

• Organization and ProfessionalService: who Drivn is, what it offers and where.
• Service: one for each service page.
• FAQPage: on every page with common questions.
• Article: on every guide, with the author and dates.
• HowTo: the project process on the home page.
• BreadcrumbList, WebPage, AboutPage, ContactPage and CollectionPage: how the pages fit together.

Paste any page into Google's Rich Results Test or the Schema Markup Validator to see exactly what's there.

Can AI tools actually read it?

Yes, on purpose. The site's robots.txt explicitly allows the crawlers behind the main AI tools, including OAI-SearchBot and GPTBot (OpenAI), PerplexityBot, ClaudeBot, Google-Extended and Applebot-Extended, alongside the normal search engine crawlers. Plenty of sites block some of these by accident and never know.

There's also an llms.txt file, a plain-text summary of the business and its key pages for tools that read it, and a longer llms-full.txt. Both are generated from the same content as the pages themselves, so they can never say something the site doesn't. My guide on what llms.txt is explains why it's a low-cost extra rather than a ranking trick.

How do new pages get found quickly?

The sitemap lists every page with the real date it last changed, not the date of the last deploy, so search engines can trust it. New and updated pages are also sent to search engines that support IndexNow, such as Bing, after every deploy, and Google Search Console is connected so I can see what's indexed.

What can't this site show you yet?

Client results. Speed, structure and crawlability are the foundations, but the proof that matters most is enquiries for real businesses, and I won't invent those. They'll appear here as projects launch and have time to show real numbers.

In the meantime, run your own site through the free SEO audit to see how it compares, or get a tailored quote for a site built the same way.