blog.padi.com · pros-blog.padi.com → padi.com

We're not sacrificing traffic. We're consolidating it.

The blog content is moving into padi.com. This overview shows what that decision protects, what changes, and why the pages being retired carry almost none of the value they appear to — using the numbers already in the mapping sheet.

Scope 18,123 URLsWindow Jun 2025 – Jun 2026Source GSC + GA4, per-URL
01

Three sites competing with themselves

Today the content lives across three separate domains. Each holds its own authority, its own backend, and ranks against the others for the same searches — so PADI's own pages split traffic between them instead of compounding it.

padi.com

The core domain. Highest authority, the destination everything should point to.

blog.padi.com

Consumer blog. Strong traffic, but its authority builds the subdomain — not padi.com.

pros-blog.padi.com

Professional blog. Publicly indexed, earning search traffic, on its own separate stack.

1,502 queries
where padi.com and the blogs currently rank against each other — splitting their own authority. The merge ends that self-competition and pools it into one domain.
02

Half the pages. Under one percent of the value.

The concern is: how much traffic do we lose by archiving? The honest answer is in the depth gauge below. The pages marked for retirement are roughly half the URL count — but they sit at the bottom, carrying almost no clicks. And even they are redirected, not deleted.

Keep + migrate
99.4% of clicks
Retire bucket
0.64% of clicks
↓ deeper = lower value, safe to retire

The retire bucket is 9,220 URLs — about 51% of all pages. But over the last 12 months those pages returned only 9,691 clicks and 81,207 sessions.

51%
of URLs
retired
<1%
of clicks
affected

Against 1,514,803 total clicks and 2,465,408 total sessions. We're clearing bulk, not value — and every retired URL is 301-redirected, so residual equity passes through.

03

Every URL gets one of three fates

There is no guessing and no blanket cut. Each row in the mapping sheet is judged on data already captured — traffic, impressions, AI visibility, backlinks, cannibalization — and lands in exactly one of these.

Fate 01

Keep + migrate

Any page with meaningful clicks, impressions, AI visibility, backlinks or rankings moves to padi.com as-is. Nothing lost.

Url_Clicks · Impressions
Referring_Domains · Backlinks
Fate 02

Merge + consolidate

Where two or three pages compete for the same query, they combine into the strongest one and the rest redirect to it. This is where authority is gained.

Cannibalization_Flag
Cannibal_Sibling_URL
Fate 03

Retire + redirect

Only pages with no clicks, no meaningful impressions, no AI visibility and no backlinks. Even these 301-redirect to the closest relevant page.

Decision = Retire
→ closest match / hub

Nothing is deleted into a void

Keep and merge preserve equity by definition. Retire redirects it. So the maximum exposure is the retire bucket's own traffic — the <1% shown above — and even that is caught by a redirect. You can see the exact list any time by filtering the sheet's Decision column to Retire.

04

Pages seen by AI are protected, even with no clicks

A page can send almost no clicks yet still be cited in AI answers or shown in a SERP feature. Retiring on clicks alone would miss that — so the rule reads two separate signals already in the sheet.

Signal A · visibility

Surfaced in AI Overviews & SERP features

Impressions that appear without a click. Several blog pages carry thousands of AI impressions — these stay, regardless of click volume.

AI_Impressions
Signal B · referral

Traffic sent from LLMs to the site

Visits arriving from ChatGPT, Perplexity and Gemini — tracked per page, so an AI-fed page is never mistaken for a dead one.

GA4_AI_Referral_Sessions · GA4_AI_Sources

Any page with either signal becomes a keep-and-re-optimize candidate — never a retire one.