ドメインを比較
サイト価値、トラフィック、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.
blackberry.net 1
github.com 1
:lane is currently balanced
Both domains perform similarly across the weighted signals in this lane.
Business:
Balanced
Reach:
Balanced
SEO:
github.com
Performance:
blackberry.net
Trust:
Balanced
Business
Balanced
blackberry.net
0
github.com
0
Reach
Balanced
blackberry.net
0
github.com
0
SEO
github.com
blackberry.net
0
github.com
5
Seo gap 7.0
Indexability gap 15
Performance
blackberry.net
blackberry.net
2
github.com
0
Performance gap 85
Trust
Balanced
blackberry.net
0
github.com
0
Next Best Moves
The clearest actions to close the gap and improve this domain fastest.
blackberry.net
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
63 points behind
Why: github.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.
Close the SEO score gap
SEO
7 points to match
Why: github.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
15 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.
github.com
Priority is based on the current gap, likely impact and available audit evidence.
Lift technical performance
Performance
85 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.
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.
SEO Audit Snapshot
A compact technical SEO check so users can compare on-page readiness at a glance.
59/100
Pass 5
Warn 3
Fail 3
IDX 75
ONP 11
PERF 100
TRUST 65
HTTP Status
200
Pass
Indexability
Indexable
Pass
robots.txt
Found
Pass
sitemap.xml
Found
Pass
Canonical URL
Missing
Warn
H1 Count
0
Fail
Title Length
0
Fail
Description Length
0
Fail
HTML lang
Missing
Warn
Viewport Meta
Missing
Warn
Image Alt Coverage
0/0
Pass
66/100
Pass 8
Warn 3
Fail 0
IDX 90
ONP 74
PERF 15
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
70
Pass
Description Length
190
Warn
HTML lang
en
Pass
Viewport Meta
Present
Pass
Image Alt Coverage
17/24
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.
Improve PageSpeed performance
HIGH
Impact 12
Effort L
Confidence 88%
Focus area github.com
A: 0 | B: 12
Why it matters: Low performance can reduce rankings, engagement, and conversion.
Recommended fix: Optimize render-blocking resources, image delivery, caching, and script payload size.
Add a unique title tag
HIGH
Impact 12
Effort S
Confidence 93%
Focus area blackberry.net
A: 12 | B: 0
Why it matters: Missing titles reduce relevance signals and SERP clarity.
Recommended fix: Add one descriptive <title> per page with the primary topic and brand.
Add meta description
HIGH
Impact 10
Effort S
Confidence 91%
Focus area blackberry.net
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 blackberry.net
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.
次の発見ルート
比較したシグナルをもとに、より広いハブページや価値の高いSEO機会セットへ進んでください。