ドメインを比較
サイト価値、トラフィック、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.
gitlab.com 1
who.int 3
who.int leads in :lane
who.int wins this lane with stronger combined signals than :other.
Business:
who.int
Reach:
who.int
SEO:
gitlab.com
Performance:
who.int
Trust:
Balanced
Business
who.int
gitlab.com
0
who.int
5
Value gap $96,998
Income gap $820
Reach
who.int
gitlab.com
0
who.int
3
Visitors gap 26,039
Pageviews gap 91,137
SEO
gitlab.com
gitlab.com
5
who.int
0
Seo gap 6.0
Indexability gap 10
Performance
who.int
gitlab.com
0
who.int
2
Mobile speed gap 11
Desktop speed gap 21
Trust
Balanced
gitlab.com
0
who.int
0
Next Best Moves
The clearest actions to close the gap and improve this domain fastest.
gitlab.com
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.
Improve internal linking depth
Architecture
76 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.
Expand structured data coverage
Structured data
2 schema blocks behind
Why: who.int uses more structured data blocks, which can improve machine understanding and rich result coverage.
Do next: Add clean schema markup for the brand, organization and key page entities.
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.
Close the SEO score gap
SEO
6 points to match
Why: gitlab.com 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
7 points behind
Why: gitlab.com 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.
SEO Audit Snapshot
A compact technical SEO check so users can compare on-page readiness at a glance.
90/100
Pass 11
Warn 0
Fail 0
IDX 100
ONP 100
PERF 75
TRUST 65
HTTP Status
200
Pass
Indexability
Indexable
Pass
robots.txt
Found
Pass
sitemap.xml
Found
Pass
Canonical URL
Present
Pass
H1 Count
1
Pass
Title Length
60
Pass
Description Length
160
Pass
HTML lang
en-US
Pass
Viewport Meta
Present
Pass
Image Alt Coverage
0/39
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.
Improve PageSpeed performance
HIGH
Impact 12
Effort L
Confidence 88%
Focus area gitlab.com
A: 12 | B: 6
Why it matters: Low performance can reduce rankings, engagement, and conversion.
Recommended fix: Optimize render-blocking resources, image delivery, caching, and script payload size.
Improve Largest Contentful Paint
MEDIUM
Impact 7
Effort L
Confidence 86%
Focus area Both
A: 7 | 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.
Publish XML sitemap
MEDIUM
Impact 7
Effort S
Confidence 84%
Focus area who.int
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.
Increase homepage content depth
MEDIUM
Impact 6
Effort M
Confidence 79%
Focus area who.int
A: 0 | B: 6
Why it matters: Thin content limits topical coverage and relevance context.
Recommended fix: Expand helpful unique copy that answers key user questions and links to deeper pages.
次の発見ルート
比較したシグナルをもとに、より広いハブページや価値の高いSEO機会セットへ進んでください。
関連ハブ