The template I threw away: rebuilding Ryan Brenizer’s website

Halfway through this project, I deleted the template.

Not because it was broken. It was the template the client had approved, the one that made the budget work, the sensible plan. But every time I looked at the staging site, I saw a generic website wearing Ryan’s photos. So I scrapped it and built every section by hand instead.

The homepage that shipped: hand-built, section by section.

A famous name with a website problem

Ryan Brenizer has photographed over 1,000 weddings since 2006. He invented the Brenizer Method (the bokeh panorama technique that carries his name), American Photo and Rangefinder both named him among the top wedding photographers in the world, and his work has been featured everywhere from Amazon and B&H to Flickr.

And yet, in early 2026, his web presence didn’t reflect any of that.

His business was running on a Squarespace template under a retired duo brand, full of “we” copy for a partnership that no longer existed. Meanwhile ryanbrenizer.com, the domain that ranked strongly for NYC wedding photography from 2006 to 2016, had been deleted years earlier over a hosting problem and left redirecting to a Patreon profile.

Two decades of search equity, parked on a page that sold nothing.

The old site, days before launch: a Squarespace template under the retired duo brand.

The brief: come home to ryanbrenizer.com

Ryan found me through Perplexity (a first for me, and a sign of where search is going) and got in touch in March 2026. The ask: bring the business back to his own name and his own domain, without losing the rankings and backlinks the old sites still held.

He was precise about the positioning, too. His clients are smart, adult NYC couples who mostly hate being photographed, and the site had to signal calm competence instead of bridal clichés. My favorite line from his project questionnaire:

“I imagine people using the site to realize I’m the only professional who won’t turn their wedding into a content-production nightmare.”

The budget was tight for a build of this scope, so we agreed on a framework approach up front: start from a premium Elementor theme, customize heavily, skip the from-scratch work. Ryan even wrote the success criterion into the questionnaire himself:

“The site looks like a custom build despite our customized framework approach.”

Keep that sentence in mind, it ends up mattering.

The sensible plan, and why it didn’t survive

I researched theme directions and recommended Ohio, a portfolio theme that reads like a design studio instead of a wedding template (most photographer themes lean hard into pastel palettes and script fonts, which was the opposite of this brand). Ryan approved it the same day.

Then I started building with it, and I couldn’t make myself like the result.

Here’s how I broke the news when I delivered the homepage, quoted from my own email:

During the development, I actually decided against using the Ohio template I mentioned earlier, as it introduced too much bulk, too many useless templates that weren’t flexible enough for my liking. It looked too much like a generic site using it. So I ended up taking the fully manual approach and building each section of the home page by hand.

Nobody asked me to do that. The template plan was approved and paid for, and dropping it meant more work at the same price. But “it looks custom despite the framework” was the success criterion, and the framework was failing it. At some point the honest move was to stop trying to make the shortcut work.

The homepage still shipped on the timeline I’d promised, two days early actually.

What custom bought us

Building by hand meant every section could come straight from Ryan’s brand guide instead of from a demo file. A few of the decisions:

• “Camera-shy? Good.” is the first thing you read after the hero. It flips his clients’ biggest fear (being photographed) into the reason to hire him. That headline came out of his own brand work, and no template had a slot for it.
• The brand words from his guide (playful, fearless, dependable, surprising) scroll across the page as a quiet marquee, instead of dying in a PDF nobody opens.
• Typography does the brand’s talking: Italiana for the big headings, Cormorant Garamond for the italic accents, Albert Sans for body text. Editorial, calm, text-friendly.
• No illustrated logo. His name, set as an all-caps wordmark, is the logo. Illustrated marks tend to feel commercial and get in the way of the editorial tone.
• Text stays readable over photos everywhere. Robin (Ryan’s partner, who ran the project day to day) called unreadable text over images her biggest red flag, so the hero overlay got tuned down to a light black wash that keeps the type legible without muddying the image.

The whole homepage in one scroll.

Two days after the homepage went up, Robin sent the email that made the whole reversal worth it:

We finally had a chance to take a deeper look at the homepage. First, the color palette and layout are incredible. Ryan says, “It feels so much more like a business” (yay!!). The moving text with adjectives is so smart, and the brag-worthy stats under the mini-bio work well without seeming pretentious. Thank you for designing the template from scratch, it really does flow! And it looks great on mobile, too.

She thanked me for the from-scratch build without knowing it had been a debate at all.

The migration underneath

The pretty part sits on top of the actual job: moving a 20-year-old business between platforms, domains and brands without breaking what Google knows about it. I’ve written before about changing your domain without losing SEO, and this project used the whole playbook:

• A 301 redirect map from every old thebrenizers.com page to its new home, page by page, including pages that no longer exist (the old albums page now points to services, stuff like that). No lazy domain-level forward.
• Every blog post redirected individually, with the dated permalinks (/blog/2019/07/17/post-slug/) flattened to clean ones along the way.
• The Squarespace blog export was a mess: 128 posts, some exported empty, and everything published through their Narrative editor came over with no content or images at all. Those got recovered manually. Ryan and Robin used the migration as a chance to prune the archive down to the 86 posts worth keeping, something I recommend to anyone moving platforms.
• Staging lived on a subdomain set to noindex, lifted only at launch.

My favorite technical moment came from Ryan himself. He noticed that Elementor’s gallery widget renders images as CSS backgrounds instead of real img tags, which makes an entire portfolio invisible to Google Images and AI crawlers. He was right, so I tested FooGallery on one portfolio page, confirmed real img elements with alt text and lazy loading in the source, and rolled it across all five portfolios. A famous photographer personally checking his img tags. My kind of client.

He also ran his own AI audit of the staging site (ChatGPT and Claude, both) and sent me the report. Some of it I’d already done, some I implemented, some I rejected with reasons. That’s the shape of client collaboration in 2026, and I’m here for it.

The rebuilt Wedding Documentary portfolio. Every image here is a real img element that Google can read.

Handing over the keys

A custom site the owner can’t edit is a liability, and frictionless self-management was in the brief from day one (Ryan blogs, Robin manages content). So the last stretch of the project was deliberately about handing over control: a training call covering Elementor’s containers, the testimonial carousel, gallery reordering in FooGallery, and the contact form’s conditional logic (one form, a weddings/other toggle, so corporate inquiries skip the wedding questions).

The signal that it worked came before the site even launched:

We’re at such a great point! I feel confident I can replace photos and trim the blog before needing your final touches.

By the end, Robin was duplicating testimonial rows and swapping page copy in WordPress on her own. That’s the goal: the developer bottleneck is gone, and I’m not it.

The review grid Robin now maintains herself, circular client photos and all.

Launch day

We launched on a Monday morning, my time, which is 3 to 5 am in New York. Lowest possible traffic, quietest possible switch. Redirects went live and got tested page by page, the boring launch checklist ran start to finish, and Search Console and Analytics were handed over the same day.

Five hours later:

“ALEX!!! THIS IS AMAZING!!! Thank you so much for all your beautiful work and dedication to the site. It looks absolutely fantastic and will serve Ryan well!”

On our final call before launch, with both of them on camera, one line stood out:

“You’ve been beyond our imagination.”

And the detail I’ll quietly brag about: I didn’t ask for the footer credit. They requested it. “We want people to be able to know that it was you.”

Same business, same headline words even. Different website.

Too early for numbers, on purpose

The site is days old as I write this, so you won’t find traffic charts here. Search Console needs a few months to tell the real story of a domain migration, and I’d rather report actual numbers later than impressive-sounding ones now. I’ll update this case study once the data is in.

What I can already report: the migration held on launch day, every old URL resolves to its new home, and the portfolio images are now readable by every crawler that matters.

What photographers can take from this

A template is a fine starting point until it starts costing you the thing that makes you distinctive. Most photographers don’t need a from-scratch build, and I say that as someone who sells them. But if your brand has a real point of view (and Ryan’s “clients who hate being photographed” positioning is exactly that), a template will average it out into everyone else’s website.

The test I’d give you: open your homepage and ask whether another photographer could swap in their name and photos and publish it. If yes, your website is a placeholder, whatever it cost.

The about page, before and after. One of these could be anyone’s website.

And if your best-ranking years live on an old domain somewhere, that equity is recoverable. It takes a redirect map and some patience, and it’s a lot cheaper than earning those links twice.

I’ve been building photography websites since 2007, and this is the work I enjoy most: a custom site shaped around one photographer’s actual voice. If your website could be anyone’s, what would it take to make it unmistakably YOURS?

Related reading: the Chris Dei custom website case study (another NYC photographer, another custom build), and WordPress page builders for how Elementor fits into custom work.