Diagnosing a 76% traffic collapse for Wedded Wonderland
A full-spectrum audit covering technical SEO, Core Web Vitals, topical authority gaps, and a
3-month remediation roadmap for a luxury wedding media platform.
Websiteweddedwonderland.com
AuditorTabitha Shalini
Audit dateApril 17, 2026
Tech stackNuxt.js (SSR)
ToolsAhrefs · Screaming Frog · PageSpeed Insights
Overview
The problem at a glance
Three compounding failures behind a 76% traffic loss
Wedded Wonderland once commanded 14,000 monthly organic visits and 1,558 top-3 keyword
positions. By April 2026 those had collapsed to 6,231 visits and 263 positions — a suppression driven by three
compounding failures: a critical Nuxt.js rendering bug hiding SEO directives from Google, a mobile performance
score of 47/100 blocking ranking recovery, and 83% of pages too thin to satisfy Google's Helpful Content
system.
Monthly traffic
6,231
↓ 76% from peak 14,003
Mobile PageSpeed
47/100
Core Web Vitals: FAILED
Top-3 positions
263
↓ from 1,558 in Sep 2021
Mar 2026 CTR
2.9%
247K impressions → 7K clicks
Traffic analysis · May 2021 – Apr 2026
60-month Ahrefs traffic data
Three phases of collapse and partial recovery
The Ahrefs data tells a precise story across 60 months. A healthy baseline gives way to a
catastrophic fall aligned with Google's 2023 Helpful Content updates, then a partial recovery in late 2025 —
proof the domain retains authority and that the right intervention will work.
Technical SEO · Screaming Frog crawl of 2,776 pages
20+ issue types · 4 that matter most
A Nuxt.js rendering failure operating across 78% of pages
The crawl returned a consistent pattern: a Nuxt.js rendering failure is misplacing SEO
directives on the majority of pages, meaning Google is operating on the site essentially blind while also
receiving contradictory signals from duplicate heading structures.
● Critical
Meta tags & canonicals outside <head>
78%
505 pages. Title tags, canonical tags, and robots directives are rendered outside
<head> — Google may ignore all of them. Root cause: Nuxt.js SSR hydration timing. Fix: enforce
useSeoMeta() at page component level.
● Critical
Canonicals missing sitewide
91%
589 pages have no canonical tag at all. Without canonical signals, Google resolves
preferred URLs independently — risking ranking fragmentation across parameter variants and paginated paths.
● Critical
Duplicate H1 tags across almost all pages
89%
573 pages share identical H1 text. Combined with 74% of pages having multiple H1
elements, Google cannot differentiate what any page is about. A CMS template-level issue requiring developer
intervention.
● Critical
Broken internal links (4xx errors)
65 URLs
65 internal links resolve to client errors. Dead-end crawl paths wasting crawl budget,
leaking PageRank, and degrading user experience. Each requires a 301 redirect or anchor correction.
● High
Low content pages
83%
535 pages under 200 words. The dominant signal triggering Google's Helpful Content
suppression. Requires triage: expand pages ranking 4–20, consolidate duplicates, remove orphaned thin content.
● High
Page titles & meta descriptions oversized
81%
526 titles exceed 561px and 449 meta descriptions exceed 155 characters — both
truncated in SERPs. Contributing directly to the 2.9% CTR against 247K monthly impressions.
Core Web Vitals · PageSpeed Insights · Apr 17, 2026
Mobile & desktop assessment
Both mobile and desktop failed assessment
Mobile is the primary concern: a 6.1s field LCP from a 47/100 score is a direct ranking
suppressor. The root cause is 659 KB of unused JavaScript blocking the main thread for 4.4 seconds. Desktop
fares better in lab conditions but fails in real-user field data due to the same JS payload.
📱 Mobile
47
FAILED
Core Web Vitals assessment
LCP (field)6.1s
LCP (lab)9.1s
FCP (field)5.8s
INP110ms
CLS0.13
TTFB0.4s ✓
🖥 Desktop
70
FAILED
Core Web Vitals assessment
LCP (field)3.0s
LCP (lab)0.4s ✓
FCP (field)2.7s
INP83ms ✓
CLS0.03 ✓
JS exec time2.6s
Primary performance diagnostics
CriticalReduce unused JavaScript — 659
KiB
CriticalInefficient cache lifetimes —
469 KiB
CriticalLegacy JavaScript — 112
KiB
High1,011 images missing size attributes (CLS)
Competitive landscape · Ahrefs data
Authority gap analysis
An authority gap — but a bridgeable one
The most instructive comparison is not The Knot or Brides.com — it's insideweddings.com. A
smaller operation at DR 70 is generating 5× Wedded Wonderland's traffic despite lower keyword overlap. The gap
is content architecture and topical depth, not domain authority.
Domain
DR
Monthly traffic
Traffic scale
theknot.com
91
3.2M
brides.com
85
922K
weddingwire.com
90
721K
zola.com
88
629K
insideweddings.com
70
33K
weddedwonderland.com
59
6.2K
Semantic SEO · Content architecture
Topical authority recommendations
From flat blog to semantic content network
Wedded Wonderland's 99% informational traffic and near-zero commercial/transactional visits
reflect an absence of topical depth. The site exists as a collection of articles rather than a structured
knowledge hub. The recommended architecture establishes five pillar pages as authority anchors, with cluster
and micro-cluster pages feeding back into them.
Pillar
Luxury Wedding Venues by RegionComplete Luxury Planning GuideWedding Dress by Designer
Cluster
Italy VenuesAustralia VenuesBudget PlanningVera Wang GuideGivenchy Bridal
Micro
Best Amalfi Coast venues 2026Sydney waterfront venues12-month wedding checklistVera Wang mermaid gowns
247K impressions at 2.9% CTR = 7,274 clicks. Fixing truncated titles and duplicate meta
descriptions could realistically lift CTR to 5–6% — doubling traffic with zero new content.
970
Keywords ranking 4–10
970 keywords one content depth update away from page 1. Adding depth, fixing heading
structure, and adding internal links from pillar pages is the fastest ranking path.
Oct
Seasonal window deadline
Organic impressions spiked to 261K in November 2025 — peak engagement season. Fixes must
land by October 2026 to capture this surge instead of wasting it at low CTR.
4–6w
AI Overview eligibility
FAQPage schema + answer-first content structure unlocks Google AI Overview inclusion. None
of the current pages qualify. Systematic FAQ implementation could lift impressions within weeks.
Remediation roadmap
3-month action plan
Prioritised fixes across three monthly sprints
Month 1
Fix foundations
P1Fix <head> tag
placement for title, canonical & robots across all Nuxt page templatesDev
P1Resolve all 65 broken
internal links with 301 redirects or corrected anchorsSEO
P1Identify and remove/defer
659 KiB of unused JavaScript via DevTools Coverage auditDev
P1Implement
self-referencing canonicals on all 589 pages currently missing themDev +
SEO
P1Rewrite unique H1 tags
for all 573 pages with duplicates, aligned to primary keywordContent
P2Full content audit:
categorise all pages into Expand / Consolidate / RemoveSEO
P2Implement Article +
BreadcrumbList schema sitewide via Nuxt SEO moduleDev
Month 2
Performance & content
P2Migrate images to WebP
via @nuxt/image; add width/height to all 1,011 unsized imagesDev
P2Configure browser cache
1-year TTL for static assets; set LCP image fetchpriority="high"DevOps
P2Rewrite all 162 duplicate
page titles + 152 duplicate meta descriptionsSEO
P2Expand top 30 thin pages
currently ranking positions 4–20 (fastest traffic wins)Content
P2Publish Pillar 1: Luxury
Wedding Venues by Region + Pillar 2: Luxury Planning GuideContent
P2Add FAQPage schema to 15+
planning guides for AI Overview eligibilitySEO
P3Full Screaming Frog
rescan to verify all critical issues resolved; resubmit sitemap to GSCSEO
Methodology
How this audit was conducted
Four independent data sources, cross-referenced
The audit triangulated four independent data sources to ensure findings were consistent
across toolsets rather than artefacts of any single platform. The Nuxt.js rendering diagnosis emerged
specifically from cross-referencing Screaming Frog's rendered HTML output against PageSpeed's Lighthouse data
— neither alone would have pinpointed the <head> displacement as a framework-level issue.