ドメインを比較
サイト価値、トラフィック、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.
perl.org 1
slate.com 3
slate.com leads in :lane
slate.com wins this lane with stronger combined signals than :other.
Business:
slate.com
Reach:
slate.com
SEO:
slate.com
Performance:
Balanced
Trust:
perl.org
Business
slate.com
perl.org
0
slate.com
5
Value gap $21,307,056
Income gap $59
Reach
slate.com
perl.org
0
slate.com
3
Visitors gap 1,865
Pageviews gap 6,527
SEO
slate.com
perl.org
0
slate.com
5
Seo gap 3.0
Indexability gap 10
Performance
Balanced
perl.org
0
slate.com
0
Trust
perl.org
perl.org
2
slate.com
1
Trust gap 29
Ssl gap 1 SSL
Next Best Moves
The clearest actions to close the gap and improve this domain fastest.
perl.org
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 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
11 points behind
Why: slate.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.
Improve internal linking depth
Architecture
168 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.
slate.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.
Raise trust and safety confidence
Trust
29 points behind
Why: perl.org looks weaker on trust-oriented checks such as HTTPS, SSL quality or safety signals.
Do next: Strengthen HTTPS, certificate quality and surface clearer trust signals across the site.
SEO Audit Snapshot
A compact technical SEO check so users can compare on-page readiness at a glance.
81/100
Pass 9
Warn 2
Fail 0
IDX 90
ONP 67
PERF 100
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
44
Pass
Description Length
118
Pass
HTML lang
en
Pass
Viewport Meta
Present
Pass
Image Alt Coverage
13/17
Warn
84/100
Pass 9
Warn 2
Fail 0
IDX 100
ONP 78
PERF 100
TRUST 36
HTTP Status
200
Pass
Indexability
Indexable
Pass
robots.txt
Found
Pass
sitemap.xml
Found
Pass
Canonical URL
Present
Pass
H1 Count
4
Warn
Title Length
61
Pass
Description Length
147
Pass
HTML lang
en
Pass
Viewport Meta
Present
Pass
Image Alt Coverage
24/25
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 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.
Publish XML sitemap
MEDIUM
Impact 7
Effort S
Confidence 84%
Focus area perl.org
A: 7 | B: 0
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 perl.org
A: 6 | B: 0
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.
Reduce to a single primary H1
MEDIUM
Impact 5
Effort S
Confidence 82%
Focus area slate.com
A: 0 | B: 5
Why it matters: Multiple H1 tags can blur content hierarchy.
Recommended fix: Keep one main H1 and move secondary section titles to H2/H3.
次の発見ルート
比較したシグナルをもとに、より広いハブページや価値の高いSEO機会セットへ進んでください。
関連ハブ