ドメインを比較
サイト価値、トラフィック、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.
dns.google 2
who.int 2
:lane is currently balanced
Both domains perform similarly across the weighted signals in this lane.
Business:
dns.google
Reach:
who.int
SEO:
who.int
Performance:
dns.google
Trust:
Balanced
Business
dns.google
dns.google
5
who.int
0
Value gap $816,537
Income gap $4,010
Reach
who.int
dns.google
0
who.int
3
Visitors gap 27,645
Pageviews gap 96,758
SEO
who.int
dns.google
0
who.int
5
Seo gap 21
Indexability gap 25
Performance
dns.google
dns.google
3
who.int
0
Performance gap 15
Mobile speed gap 46
Trust
Balanced
dns.google
0
who.int
0
Next Best Moves
The clearest actions to close the gap and improve this domain fastest.
dns.google
Priority is based on the current gap, likely impact and available audit evidence.
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.
Strengthen on-page relevance
On-page
53 points behind
Why: who.int 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.
Close the SEO score gap
SEO
21 points to match
Why: who.int 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
25 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.
who.int
Priority is based on the current gap, likely impact and available audit evidence.
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
15 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.
SEO Audit Snapshot
A compact technical SEO check so users can compare on-page readiness at a glance.
63/100
Pass 5
Warn 4
Fail 2
IDX 65
ONP 40
PERF 90
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
17
Warn
Description Length
0
Fail
HTML lang
en
Pass
Viewport Meta
Present
Pass
Image Alt Coverage
0/0
Pass
84/100
Pass 10
Warn 1
Fail 0
IDX 90
ONP 93
PERF 75
TRUST 65
HTTP Status
200
Pass
Indexability
Indexable
Pass
robots.txt
Found
Pass
sitemap.xml
Missing
Warn
Canonical URL
Present
Pass
H1 Count
1
Pass
Title Length
31
Pass
Description Length
97
Pass
HTML lang
en
Pass
Viewport Meta
Present
Pass
Image Alt Coverage
0/25
Pass
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 meta description
HIGH
Impact 10
Effort S
Confidence 91%
Focus area dns.google
A: 10 | B: 0
Why it matters: Missing descriptions reduce control of SERP snippets.
Recommended fix: Add a compelling meta description with clear value proposition and intent match.
Add one H1 heading
HIGH
Impact 10
Effort S
Confidence 90%
Focus area dns.google
A: 10 | B: 0
Why it matters: Missing H1 weakens topical hierarchy for users and crawlers.
Recommended fix: Add exactly one descriptive H1 aligned with page intent.
Improve Largest Contentful Paint
MEDIUM
Impact 7
Effort L
Confidence 86%
Focus area who.int
A: 0 | B: 7
Why it matters: High LCP harms perceived load speed and Core Web Vitals.
Recommended fix: Prioritize above-the-fold assets, compress hero media, and optimize server response.
Add robots.txt
MEDIUM
Impact 7
Effort S
Confidence 85%
Focus area dns.google
A: 7 | B: 0
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.
次の発見ルート
比較したシグナルをもとに、より広いハブページや価値の高いSEO機会セットへ進んでください。
関連ハブ