7,500 ドメイン分析済み · 20 カテゴリー · 無料・即時

ドメインを比較

サイト価値、トラフィック、SEO、ホスティング指標を並べて比較します。

ランキングを見る
Use this domain comparison to benchmark value, traffic, SEO quality, technical health and trust signals side by side.

Executive Summary

A fast head-to-head view of which domain leads in the areas that matter most.

duckdns.org 3 telegram.org 1
duckdns.org leads in :lane
duckdns.org wins this lane with stronger combined signals than :other.
Business: duckdns.org Reach: duckdns.org SEO: duckdns.org Performance: telegram.org Trust: Balanced
Business
duckdns.org
duckdns.org
5
telegram.org
0
Value gap $17,900,781
Income gap $493
Reach
duckdns.org
duckdns.org
3
telegram.org
0
Visitors gap 15,654
Pageviews gap 54,789
SEO
duckdns.org
duckdns.org
5
telegram.org
0
Seo gap 4.0
Indexability gap 10
Performance
telegram.org
duckdns.org
0
telegram.org
2
Performance gap 10
Trust
Balanced
duckdns.org
0
telegram.org
0

Next Best Moves

The clearest actions to close the gap and improve this domain fastest.

duckdns.org
Priority is based on the current gap, likely impact and available audit evidence.
3 priorities
Resolve safety risk signals
Trust Gain about 24 priority points
Why: Negative safety classification can severely reduce trust and traffic.
Do next: Scan and clean malware/phishing indicators, harden CMS/plugins, and request re-evaluation.
Lift technical performance
Performance 10 points behind
Why: Speed or rendering signals lag behind the competing domain and may hold back SEO quality.
Do next: Improve Core Web Vitals, image delivery and frontend payload before the next refresh.
Improve internal linking depth
Architecture 44 internal links behind
Why: The competing domain exposes more internal links from the homepage and looks easier to crawl.
Do next: Expose more important pages through clearer internal links and navigation paths.
telegram.org
Priority is based on the current gap, likely impact and available audit evidence.
4 priorities
Resolve safety risk signals
Trust Gain about 24 priority points
Why: Negative safety classification can severely reduce trust and traffic.
Do next: Scan and clean malware/phishing indicators, harden CMS/plugins, and request re-evaluation.
Close the SEO score gap
SEO 4 points to match
Why: duckdns.org trails the competing domain on overall SEO score and needs the fastest high-impact fixes first.
Do next: Prioritize the highest-severity audit fixes and refresh the crawl after each batch.
Improve indexability signals
Indexability 10 points behind
Why: :domain is behind on crawlability or indexability checks that directly affect discoverability.
Do next: Fix robots, sitemap, canonical and index directives so the homepage is cleanly discoverable.
Strengthen on-page relevance
On-page 8 points behind
Why: duckdns.org has weaker title, description, headings or content-depth signals than the competing domain.
Do next: Tighten title/description quality, heading structure and homepage content depth.
指標 duckdns.org 勝者 telegram.org
推定価値 $557,053,205 duckdns.org $539,152,425
日次訪問者数 165,348 duckdns.org 149,694
日次ページビュー 578,718 duckdns.org 523,929
日次収益 $5,208 duckdns.org $4,715
SEO Score 67 duckdns.org 63
Indexability 75 duckdns.org 65
OnPage 44 duckdns.org 36
パフォーマンス 90 telegram.org 100
Trust 65 — 65
Coverage 90 duckdns.org 81
Confidence 93 duckdns.org 84
SEO Freshness (h) 145 duckdns.org 181
Country Canada — Netherlands
TLD org — org
カテゴリー — — —
レジストラ Gandi SAS — GoDaddy.com, LLC
Internal Links 15 telegram.org 59
Structured Data Blocks 0 — 0
PageSpeed Mobile 77 duckdns.org —
PageSpeed Desktop 96 duckdns.org —
PageRank 4 telegram.org 6
Trancoランク #153 duckdns.org #169
SSLグレード A — A
セキュリティ状態 — — —

SEO Audit Snapshot

A compact technical SEO check so users can compare on-page readiness at a glance.

duckdns.org
67/100
Pass 5 Warn 6 Fail 0 IDX 75 ONP 44 PERF 90 TRUST 65
HTTP Status
200 Pass
Indexability
Indexable Pass
robots.txt
Missing Warn
sitemap.xml
Found Pass
Canonical URL
Missing Warn
H1 Count
1 Pass
Title Length
8 Warn
Description Length
46 Warn
HTML lang
Missing Warn
Viewport Meta
Present Pass
Image Alt Coverage
3/3 Warn
telegram.org
63/100
Pass 3 Warn 7 Fail 1 IDX 65 ONP 36 PERF 100 TRUST 65
HTTP Status
200 Pass
Indexability
Indexable Pass
robots.txt
Missing Warn
sitemap.xml
Missing Warn
Canonical URL
Missing Warn
H1 Count
0 Fail
Title Length
18 Warn
Description Length
23 Warn
HTML lang
Missing Warn
Viewport Meta
Present Pass
Image Alt Coverage
11/11 Warn

Top Levers Across Both Domains

Shared high-impact improvements pulled from the latest recommendations and audits.

Resolve safety risk signals
CRITICAL Impact 24 Effort L Confidence 94% Focus area Both
A: 24 | B: 24
Why it matters: Negative safety classification can severely reduce trust and traffic.
Recommended fix: Scan and clean malware/phishing indicators, harden CMS/plugins, and request re-evaluation.
Add one H1 heading
HIGH Impact 10 Effort S Confidence 90% Focus area telegram.org
A: 0 | B: 10
Why it matters: Missing H1 weakens topical hierarchy for users and crawlers.
Recommended fix: Add exactly one descriptive H1 aligned with page intent.
Improve image ALT coverage
HIGH Impact 8 Effort M Confidence 84% Focus area Both
A: 8 | B: 8
Why it matters: Missing ALT text reduces accessibility and image search context.
Recommended fix: Add concise descriptive ALT text for informative images and empty ALT for decorative assets.
Add robots.txt
MEDIUM Impact 7 Effort S Confidence 85% Focus area Both
A: 7 | B: 7
Why it matters: robots.txt helps crawlers understand allowed paths and improves crawl clarity.
Recommended fix: Create /robots.txt with allowed sections and a sitemap reference.
Publish XML sitemap
MEDIUM Impact 7 Effort S Confidence 84% Focus area telegram.org
A: 0 | B: 7
Why it matters: A sitemap improves URL discovery and recrawl efficiency.
Recommended fix: Generate /sitemap.xml, include canonical URLs, and keep it auto-updated.

次の発見ルート

比較したシグナルをもとに、より広いハブページや価値の高いSEO機会セットへ進んでください。

メタハブ →