Architecture
The Infrastructure Architecture
You know what's wrong. Now you need the blueprint to fix it—designed precisely, documented clearly, ready for whoever builds it. I design the full infrastructure for your site or business and leave you with a complete specification you can hand to any developer, any team, or build from yourself.
What I look at
Site architecture
URL structure, internal linking, page hierarchy, how authority flows through the site.
Schema entity graph
Person, Organisation, Service, FAQPage, Article — fully specified and ready to implement.
AEO content architecture
Answer-first structure, FAQ blocks, keyword mapping scoped per page and article.
Discoverability layer
robots.txt, llms.txt, sitemap structure, AI crawler access, canonical strategy.
Technical specification
A complete handoff document your developer can work from directly.
Content strategy
Pillar structure, topic clusters, internal linking plan, publish order.
What you leave with
A complete infrastructure design
Site structure, schema graph, AEO architecture, content plan. Everything specified before a line of code is written.
Schema markup ready to implement
Every type specified for every page, with field values, @id references, and copy-paste JSON-LD blocks.
A developer handoff document
Your team or any developer can implement from it directly. No interpretation needed.
No dependency on me to build it
Design is mine, implementation is yours. You own the blueprint outright.
Questions
What is an infrastructure architecture?
An infrastructure architecture is a complete design specification for how your site or business should be built — site structure, schema markup, AEO content layout, discoverability signals, and technical requirements. It's the blueprint that comes after the diagnosis and before the build.
Who is this for?
Founders and operators who've had the Infrastructure Audit and know what needs fixing — but have a developer or team who can implement it themselves. You need the design, not the build.
What's the difference between this and the audit?
The audit finds the problem. The architecture designs the solution. You leave the audit knowing what's wrong. You leave the architecture knowing exactly how to fix it, specified in enough detail to hand to a developer.
What's the difference between this and the full build?
In the architecture engagement, I design — you or your team build. In the full build, I design and oversee implementation end to end. The architecture is the right choice if you have capable people to execute.
Do I need the audit first?
Usually yes. The audit confirms the scope and makes the architecture more precise. If you already have a clear picture of what needs fixing, we can scope from there.
What does the handoff document look like?
A structured document covering every page, every schema type, every content block — with specifications, copy-paste JSON-LD, keyword targets, FAQ questions, and implementation notes. Formatted for a developer, readable by a non-technical founder.