Skip to content

Ad Personam — Marketing & Wedding Agency

WordPress → Next.js: 100 Accessibility, Best Practices and SEO

Next.jsSupabaseTechnical SEOStudio Dashboard

Project overview

A Sydney agency selling social content to businesses and wedding content to couples. Rebuilt off WordPress onto Next.js and Supabase from the owner's own design, with a separate weddings side, case studies and testimonials published from a studio dashboard she runs, and every public page static and CDN-cached — mobile Performance 97–100 on the live domain.

The challenge

Ad Personam sell two things to two audiences who want the opposite of each other: social media and content marketing to businesses, and wedding content creation to couples. The existing site treated them as one, opening with no H1 and a 1.7 MB hero image, and the domain carried nothing to build on — a Domain Rating of 0, no organic keywords, no traffic, and 95 referring domains of pure spam accumulated in a single month.

What we did

  • Rebuilt on Next.js and Supabase from the owner's own design specification — her type, her warm neutrals and a single brass accent, with every contrast ratio measured and the brass kept off body text where it would fail
  • The two audiences separated by page rather than by visitor state: the weddings side has its own pages, packages and ground colour, so no page varies by cookie, every public route stays static and CDN-cacheable, and a crawler sees exactly what a person sees
  • Service pages aimed at the searches each audience actually makes — social media management in Sydney for businesses, wedding content creation for couples — each with its own H1, canonical, description and JSON-LD
  • A studio dashboard where she publishes case studies, journal posts, clients and testimonials herself, guarded twice: a session check at the edge and an admin-profile check in the layout, because being signed in is not the same as being an admin
  • An enquiry flow that saves every lead to the database before it emails, with a honeypot that Chrome autofill can no longer trip — so a real enquiry is never silently dropped as a bot
  • Positions taken deliberately and documented — no thin per-suburb landing pages from a DR 0 domain, no Review or AggregateRating schema for a business with no reviews yet, and a disavow filed for the 95 spam referring domains rather than treated as a crisis
  • A clean cutover: domain moved to the new build with the old hosts 301-redirected, business email set up on her own domain, Search Console verified and the sitemap submitted

The results

97–100
Mobile Performance on the live domain (was 73)
100
Accessibility, Best Practices and SEO (were 89, 100 and 85)
1.6–2.6s
Mobile LCP on home, service and work pages
0
Cumulative Layout Shift on every page tested

Services delivered

Web DevelopmentTechnical SEOBacklink AuditDomain & Email Migration

Interested in similar services? View all services →

Summary

A two-audience business does not need two websites, and it does not need one website that changes shape for each visitor. Giving each audience its own pages on one domain keeps every link and every crawl building the same authority, and keeps every page static and fast. The restraint matters as much as the build: on a domain with no history, the pages that were not created and the schema that was not fabricated protect the ones that were.

Want results like these?

Let's talk about your project. Free 30-minute consultation, no commitment.

Start a project