Blog / May 10, 2026 / Founder essay

Why a single page Awwwards site is the wrong move for SaaS lead generation.

By Joseph W. Anady. The studio site you are reading was a single page Awwwards style build for most of 2026. We tore it apart and rebuilt as a multi page property. The reasons are technical, commercial, and surprisingly simple.

The single page site looked great. Google could not figure out what we ranked for. ChatGPT and Perplexity barely cited us. Conversion was fine but search demand was not converting because we were not visible for the queries that mattered.

For most of 2026 thataiguy.org was a single page hand coded site. The kind of site that wins design awards. Heavy hero animation, scroll choreography, eight major sections strung together with anchor links. It was a portfolio piece in itself.

It also was not earning what it should from search. Search Console showed the kind of pattern that is easy to misread. Plenty of impressions for the brand. A few impressions for "that ai guy" plus various long tail queries. But virtually nothing for the eight big query categories the studio actually serves: tax firm AI, real estate AI, medical AI, insurance AI, hospitality AI, e commerce AI, construction AI, combat sports AI. Plus pricing tiers, plus AI capabilities, plus the 14 tier engine optimization framework. That is at least 28 distinct query categories the single page property was trying to rank one URL for.

Why a single page is not enough.

Google does rank single page sites. It indexes them. It surfaces them for branded queries. What it does not do well is route specific intent queries to a specific section of a 7000 word page. When someone searches for "AI for tax firms" Google wants to serve a page about AI for tax firms. A single page covering eight industries plus six AI capabilities plus 14 SEO tiers does not match the intent cleanly enough to win against a competitor with a dedicated page.

Answer engines have an even harder time. ChatGPT, Perplexity, Claude, and Google AI Overviews extract concise answers. A 7000 word page with eight sections of related but distinct content is hard to extract from. The engines might cite the page for a generic query like "AI consulting" but they will rarely cite it for "best AI workflow automation for insurance agency". The engineering studio that has a dedicated page for each industry plus capability gets cited; the studio with one giant page does not.

What we changed.

The rebuild created roughly 70 new URLs. Eight industry pages. Six AI capability pages. Six pricing tier pages plus three monthly retainer pages. Four pillar pages. Fifteen engine optimization tier pages. Four comparison pages. A handful of standalone pages: infrastructure, process, FAQ, the Joseph Anady bio, MEGAMIND, case studies, and a blog.

Each new page targets one or two query intents. Each page carries full schema for its content type. Each page has its own AEO surface: an answer capsule near the top, a FAQPage block, speakable schema. Each page has its own breadcrumb plus a clear internal link path back to the home page and to related sections. The home page itself shrank from 7000 words to roughly 2000, with each former section becoming a teaser plus a link to the deep page.

What we kept.

The home page kept its visual identity. The hand coded approach stayed. The dark mode design system, the Fraunces serif, the mint plus amber accents, the orb backgrounds. The home page still loads with a custom cursor and an intro animation; it still feels like an Awwwards entry. It just does its job differently. Where before the home page tried to be the only page, now it routes visitors to the page that matches their intent.

The schema graph stayed consistent. The Organization, Person, and WebSite entities have stable IDs across every page. New pages reference those IDs rather than redefining them. This keeps the entity graph clean and lets answer engines understand that the studio behind the new pricing pages is the same studio behind the new AI capability pages.

The pattern is replicable.

If you are a small business with a beautiful one page site that is not earning what it should, the same pattern applies. The fix is not "rebuild on Webflow" or "switch to WordPress". The fix is to recognize that one page can only carry one or two intents cleanly, and to break out the rest of your service catalog into pages that match the queries your customers actually run.

A solo coach with eight workshop topics needs eight pages plus a home page. A clinic with six providers and three specialties needs nine plus pages. A tax firm with five seasonal services needs five plus pages. The math is the same. Every distinct query intent earns a page. The home page becomes the front door, not the only room in the house.

What changes next.

We will publish a follow up in 30 days with the actual measurement: search impressions per query category before and after, AI engine citations spotted, conversion rate change. Honest results, posted publicly. The whole rebuild was done in one afternoon by one engineer using the studio's own tooling and a well structured plan. Anyone reading this can do the same.

If you want help running the same play on your own site, the audit is free and the rebuild quotes are visible on the pricing page. If you would rather do it yourself, the 14 tier engine optimization framework is documented at engine optimization. We are not gatekeeping the work; we ship it faster.

One page for one intent. The home page is the front door, not the only room. If your service catalog has more than three distinct intents, more than three pages should serve them.