Why hand-coded sites rank and get cited by AI.

Hand-coded sites rank and get cited by AI because they load faster, ship clean semantic HTML, and give full control over the structured data that search engines and answer engines read. A site built by hand on Astro or Next.js carries none of the template, theme and page-builder weight that slows most websites down, and nothing stands between you and the markup that decides how you are ranked and quoted. This guide explains each reason and how it maps to a real build.

Speed and Core Web Vitals

Faster pages rank better because speed is both a direct Google signal and the thing that keeps visitors on the page. Google measures real-world loading, interactivity and visual stability as Core Web Vitals, and uses them as a ranking factor. A page that loads quickly and stays stable as it loads beats a slow, shifting page covering the same topic.

Hand-coded sites have a structural advantage here. A typical templated site loads a theme, several plugins and a page builder, which add large amounts of CSS and JavaScript to every page whether it is used or not. A hand-coded site ships only the code that page needs, so it is lighter and faster by default, and far easier to keep inside the Core Web Vitals thresholds over time. Speed also compounds: a fast site is cheaper to crawl, so search engines can reach more of it more often. This is the same engineering that underpins the studio's SEO work, where the build itself is the lever.

Clean semantic HTML and why it helps ranking

Semantic HTML helps you rank because it tells a search engine what each part of a page means, not just how it looks. A heading marked as a heading, a list marked as a list, and a navigation block marked as navigation give the crawler a clear map of the page. When the structure is honest, the search engine can understand the topic, the sub-topics and the relationships between them with far less guesswork.

Hand-coded sites tend to ship clean, minimal, correctly nested markup because a person chose every element for its meaning. Page builders, by contrast, often wrap content in deep stacks of generic containers that carry no meaning, which buries the actual content and dilutes the signal. Clean markup is also the foundation of accessibility: the same structure that a screen reader relies on is the structure a crawler relies on, so building it once serves both. A page a machine can parse cleanly is a page it can rank confidently.

Structured data and AI extraction

Structured data gets you cited because it states the facts of a page in a format machines can extract without ambiguity. Schema, written as JSON-LD, labels the parts of a page: this is an article, this is its author, this is the published date, this is a question and its answer, this is a price. Search engines and answer engines can lift those labelled facts and reuse them with confidence, which is the foundation of being quoted rather than skimmed.

This matters more than ever as people ask questions of ChatGPT, Perplexity, Copilot and Google AI Overviews instead of scrolling a results page. Those systems favour sources whose facts are clearly stated and clearly labelled. A hand-coded build lets you place exact, page-specific JSON-LD inline on every page, rather than relying on a one-size plugin. Getting found in answer engines is its own discipline, covered under AI search visibility, and clean structured data is where it starts.

No page-builder bloat

Page builders cost you rankings because they add weight and noise that a hand-coded site never carries. A visual builder trades a small amount of editing convenience for a large amount of code: extra CSS frameworks, JavaScript libraries, render-blocking scripts and nested wrappers that exist only to make the editor work. Every visitor downloads that overhead, and every crawler has to wade through it to reach your content.

The effect shows up in the numbers that matter. Bloated pages are slower, which hurts Core Web Vitals. Deeply nested markup is harder to parse, which weakens the semantic signal. And duplicated template structure shared across thousands of other sites offers nothing distinctive to rank. A fuller comparison of the trade-offs sits in the guide on custom versus website builders. Removing the builder is not a tweak; it removes the cause of several ranking problems at once.

Server-rendered content and why AI crawlers need it

Server-rendered content is essential for AI citation because most answer-engine crawlers read the raw HTML a server returns and do not reliably run JavaScript. A modern browser will execute JavaScript to build a page in front of a human, but many crawlers skip or fail that step. If your words, prices and answers only appear after JavaScript runs, those crawlers often see an empty shell and have nothing to index or quote.

Hand-coded Astro and Next.js sites send the finished HTML from the server, either pre-built at deploy time or rendered per request, so the content is present in the very first response. That single decision makes the difference between a page an answer engine can cite and a page it cannot see. Heavy client-side frameworks that build everything in the browser are the common cause of pages that rank thinly and never get quoted, and server rendering is the fix.

How this maps to a real build

On a real project these reasons are not separate features; they are the natural result of building the site by hand on the right foundation. Choosing Astro or Next.js gives you server-rendered HTML and minimal shipped code. Writing the markup by hand gives you clean semantics and inline schema. Skipping the page builder removes the bloat. None of it is bolted on afterwards, because it is the way the site is constructed.

That is the approach behind every project here: one founder designs and codes the site so the build, the rankings and the AI citations are never at odds. See how it comes together in web design, or read the companion guide on getting cited by ChatGPT. When you are ready, the fastest next step is a fixed-fee quote with honest next steps.