3?F
GEMRUSH

Technical SEO

Can AI crawlers reach, read and trust your site?

Is anything technically blocking AI engines?

Checks passing

2/7

Site-wide audit

Critical blockers

2

Costing visibility now

Schema coverage

39%↑ 6%

Of key templates

AI bots allowed

2/4

GPTBot and PerplexityBot restricted

Things hurting your visibility
CriticalHigh impact340 pages

GPTBot and PerplexityBot partially blocked

Your robots file blocks two AI crawlers from the product section - the exact pages you want quoted.

Fix · Allow GPTBot, PerplexityBot, ClaudeBot and Google-Extended on public content paths.

CriticalHigh impact1 pages

Organization and SoftwareApplication schema missing

Engines cannot confirm who you are, so they lean on directories that can.

Fix · Add sitewide SoftwareApplication schema with sameAs links to authoritative profiles.

WarningHigh impact63 pages

Client-rendered product content

Some content only appears after JavaScript runs, and most AI crawlers do not wait.

Fix · Server-render the main content of crawlable templates.

WarningMedium impact22 pages

Slow mobile page load on hubs

Hub pages take 4.8s on mobile; slow pages get crawled less often.

Fix · Compress hero imagery and defer non-critical scripts to reach sub-2.5s LCP.

WarningMedium impact47 pages

Duplicate feature pages

Near-identical feature pages split your authority across duplicates.

Fix · Consolidate duplicates and canonicalise to a single feature page.

HealthyLow impact

XML sitemap and canonicals

Sitemaps are current and canonicals are consistent - healthy.

Fix · No action needed.

HealthyLow impact

HTTPS and security headers

All pages serve over HTTPS with valid certificates.

Fix · No action needed.