Overview

This is the site you’re on right now. I built it to give people a clear place to see who I am, what I do, and how I think — and to prove that I can structure and write a site with SEO in mind, not just make something look nice.

The current version is also an upgrade point. After building multiple new project pages and reusable content blocks, I’ve tightened the system so I can publish new work faster without losing quality.

Objective

• Give people a clear place to see who I am, what I do, and how I think.
• Prove I can plan a clean site structure that makes sense to users and Google.
• Show I understand positioning — who the site is for and why it exists.
• Demonstrate strong on-page fundamentals: titles, headings, internal links, metadata, and tracking.
• Build a reusable case study system so every future project page stays consistent and easy to ship.

What’s new in the upgrade

• A consistent “rounded card” component system across the Work page and case studies.
• Clearer portfolio presentation so visitors can skim projects fast and click into proof.
• Better page hierarchy and internal linking between Home → Work → case studies → Contact.
• Stronger copy that explains what I built (structure, UX, SEO, performance) in plain English.

SEO & site structure

I treated myself like a client and built the site around how people actually browse: one clear promise, a simple path to proof, and a direct route to get in touch.

• One clear main heading per page that explains who I help and what I do.
• Simple flow: hero → what I do → featured projects → about → contact.
• Headings used with intent (H1 for the main idea, H2/H3 for sections and sub-points).
• Copy written around real search intent (SEO, structure, web help) without stuffing keywords.
• Internal links from the homepage into key case studies, and back towards Work / Contact.

The goal is for the structure to make sense to a human first, and also be easy for Google to understand.

Technical setup

This version is built on Squarespace for speed, but I still treated it like a proper SEO build — and I’ve been upgrading it as my work has expanded.

• Custom page titles and meta descriptions on key pages.
• Checked and adjusted heading hierarchy instead of letting the template decide.
• Clean, readable URLs where the platform allows it.
• Basic performance + mobile checks so it loads fast and reads well on a phone.
• Analytics connected so I can see what people click and where they drop off.

For client projects, I’m increasingly shipping fully custom coded builds as well. That gives me tighter control over markup, schema, and performance so I can take technical SEO further than a builder allows.