Skip to content
Method
Process

Blueprint. Build. Rank.

Three stages, and the artifacts each one produces. Visible methodology is the point — you should be able to tell what you’re buying before you buy it.

Blueprint

Before anything is designed, we work out what the site has to do and how people will look for it.

This is the stage that gets skipped, and skipping it is what produces the rebuild six months later. Structure decided here is nearly free; structure changed after the design is finished costs a redesign.

A designer and a client lean over a work table covered with printed wireframes and colorful sticky notes, talking through a site's structure on paper
What this stage produces
Keyword and intent map
The queries your customers actually use, grouped by what they’re trying to do — research, compare, or buy.
Entity map
The things your business is about (services, locations, brands) and how they relate. This is what becomes your page structure and your schema.
Sitemap and URL scheme
Every page, its purpose, its target query, and its final URL — agreed before anything is built.
Wireframes
Layout and hierarchy for each page template, in gray. No color, no imagery — so the conversation is about structure rather than taste.
Core Web Vitals budget
A performance ceiling agreed up front. It constrains design decisions rather than being measured after them.

Build

Design and development, against the blueprint — on whichever platform fits your situation.

Next.js, WordPress, or Webflow. We pick based on who needs to edit the site and how often, not on what we prefer building. You own the result either way.

A designer works at two monitors in a warmly lit studio — colorful page layouts taking shape on one screen, the site's code on the other
What this stage produces
Visual design
Applied to the approved wireframes, so layout arguments are already settled and the conversation is about the brand.
Copy
Written against the intent map — to rank and to convert. Included unless you’d rather write it yourself.
Schema graph
Structured data built by hand from the entity map. Not a plugin’s guess at what your business is.
Accessibility pass
Contrast, focus order, keyboard operation, and semantics checked before launch, not after a complaint.
Redirect map
If you have an existing site: every old URL mapped to its new equivalent, built as URLs change rather than reconstructed from memory at the end.

Rank

Launch, verify, and hand over a plan you can actually run.

The site going live is the middle of the process, not the end of it. What happens in the two weeks after launch decides whether the work holds.

A designer turns a laptop toward a delighted business owner, showing her a chart of her site's search traffic climbing
What this stage produces
Launch checklist
Redirects live at launch, staging noindex confirmed gone, sitemap submitted, no 404s from the old URL list.
Analytics and Search Console
GA4 and Google Search Console wired and verified before launch day, so the first day of data is the first day.
Timestamped baseline
Rankings, traffic, and Core Web Vitals recorded at launch. Without this, every later question about whether the site helped is a guess.
Ranking plan
What to publish, in what order, and why — the next six months of content and technical work, prioritized. It’s yours.
The handoff

You leave with the plan, not a dependency.

Every build ships with the ranking plan attached. Run it yourself, hand it to your marketing person, or hand it to the SEO practice next door. All three are fine — the code and the plan are yours either way.