Interventions With Love
Redesign Autopsy

Executive summary

The Elementor rebuild appears to be a visual redesign that was not accompanied by an SEO migration. The previous Squarespace site was not perfectly optimized — it had no image alt text and a long meta description — but it carried a functional SEO baseline: structured data, social-share metadata, on-page NAP, an analytics tag, and real customer content. Almost none of that has been ported.

If the new build is pushed to www.interventionswithlove.com in its current state, the practical consequences are:

1. Search Console will see a fresh site with no descriptions, no schema, and no rich-result eligibility — Google has to relearn the brand from scratch.
2. Local-pack signal collapses: the on-page address (Cincinnati, Ohio), the phone numbers, and the LocalBusiness schema are all gone.
3. Social shares (Facebook, Instagram, LinkedIn) will render as plain links with no preview image or description.
4. Google may flag the homepage as low-quality due to the visible Lorem Ipsum testimonial section.
5. All Google Analytics history goes dark on day one — the GA4 property tag is not installed.

The headline regression

Track A — What was kept, lost, and added

Track B — Per-element comparison

Track C — Performance posture

Schema regression — what's actually missing

The Squarespace site shipped two JSON-LD blocks. The new Elementor build emits neither. For reference, here is what the live site currently outputs and the new build does not:

<script type="application/ld+json">
{
  "url":"https://www.interventionswithlove.com",
  "name":"Interventions With Love ",
  "image":"//images.squarespace-cdn.com/.../76B4A461-01DF-4257-A2A9-F1C080A46AAB.PNG",
  "@context":"http://schema.org",
  "@type":"WebSite"
}
</script>

<script type="application/ld+json">
{
  "address":"Cincinnati, Ohio \nUSA",
  "image":"https://static1.squarespace.com/.../76B4A461-01DF-4257-A2A9-F1C080A46AAB.PNG",
  "openingHours":"Mo 08:00-17:00, Mo 19:00-23:00, Tu 08:00-17:00, Tu 19:00-23:00, ...",
  "@context":"http://schema.org",
  "@type":"LocalBusiness"
}
</script>

The Elementor build emits zero JSON-LD. Without it, the site is invisible to rich-result surfaces — local pack, knowledge panels, AI overviews, and the structured-data feeds that increasingly determine which practices get cited.

Content audit

Findings summary

Bottom line

The redesign appears to have been treated as a visual project rather than a migration project — and on the visual axis, it falls short as well. On every measurable SEO axis (schema, social metadata, on-page entities, analytics, content depth) the rebuild has stripped the site back below where the Squarespace version stood, and in two places (the staging canonical and the Lorem Ipsum testimonials) it has introduced new issues that would actively harm rankings if launched.

The harder truth is about the design itself. The Elementor build reads as a competent but generic page-builder template: centered serif headlines stacked over thin body copy, a "proud member of" badge strip, and rounded card panels arranged symmetrically. It is not bad — but it does not look like a practice that families turn to in the worst week of their lives. It does not project the dignity, calm, or specialist authority that Gianna's clinical work earns. The original Squarespace site was plainer, but at least it felt like a working professional's site rather than a stock layout.

The harder question is whether Elementor's template-builder vocabulary can ever produce work that feels as considered as the practice itself. That is a different conversation — and one the third option below is built to answer.

Why the third option is better

The design system behind the new site

The recommended build is not a one-off page. It ships with a complete design system — a set of named, reusable tokens for color, typography, spacing, shadow, and motion — implemented as CSS custom properties in src/styles/theme.css. Every page on the site, and every future page Gianna or her team adds, draws from the same vocabulary.

What's in the system

Why the system matters more than any single page

A page-builder site like the Elementor build looks coherent on the day it ships and degrades from there. Every future edit — a new service page, a seasonal banner, a press hit, a downloadable PDF — is a fresh design decision. Some of those decisions will be Gianna's; some will be a contractor's; some will be made under deadline. Without a system, drift is inevitable, and the site becomes visually noisier with every addition.

The custom build inverts that. The hardest design work is done once, encoded in tokens, and then every subsequent page composes from the same vocabulary:

What changed under the hood

EmDash CMS — why not WordPress

EmDash is an Astro-native CMS where the schema is defined in code and the content lives in a real database (Cloudflare D1) with media in object storage (Cloudflare R2). Gianna and her team get a clean admin UI for editing — every page, every blog post, every service description. But unlike WordPress, the schema isn't something a stray plugin can mutate: it's checked into git alongside the code.

Cloudflare — speed and security at the edge

Every request to interventionswithlove.com is served from the Cloudflare edge location nearest the visitor — Cincinnati, Pittsburgh, anywhere a family is sitting at 11pm trying to figure out what to do. The response is generated by a Worker in <50ms typical, then cached at the edge for repeat visitors. There is no origin server to slow down, get hacked, or fall over.

SEO — what we shipped

The new build doesn't treat SEO as an after-launch concern. Every element the Squarespace site had — and every element the Elementor build is missing — is in place from the first deploy.

Future-oriented by design

Every choice in the stack is reversible — and every choice favors open standards over proprietary builders. This matters because the web of three years from now will not look like the web of today. Search is fragmenting; AI agents are becoming primary readers; performance budgets are tightening; privacy regulation is expanding. The site needs to be able to evolve with all of that.