SEO report for www.cryptohopper.com

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to cryptohopper.com…

Indexing & crawling 100%

Can search engines reach, read and index this page?

• ✓

  Status codecritical

  The page returned HTTP 200.

• ✓

  Indexablecritical

  No noindex instruction – the page can appear in search.

• ✓

  robots.txthigh

  robots.txt found.

  Googlebot is allowed to crawl this page.

• ✓

  XML sitemaphigh

  Sitemap found at https://www.cryptohopper.com/sitemap.xml with over 621 URLs (we read the first 1 MB).

  Declared in robots.txt.

  This page is listed in it.

  Most recent lastmod: 2026-07-06.

• ✓

  Canonical URLhigh

  Canonical: https://www.cryptohopper.com/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  1 redirect before the page loaded.

  https://cryptohopper.com/ → https://www.cryptohopper.com/

  A single redirect to your preferred address is normal; just make sure your own links use the final address.

• ✓

  www / non-wwwmedium

  cryptohopper.com redirects to www.cryptohopper.com.

• ✓

  hreflangmedium

  15 hreflang link(s).

  All language codes are valid.

Search snippet & sharing 79%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “Cryptohopper | The Best Crypto Trading Bot for Automated Trading”

  About 595px of Google's ~580px desktop width – it will probably be cut off.

  Repeated words: trading.

  Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• ✓

  Meta descriptionhigh

  154 characters, ~950px of ~990px.

  Good length.

  Google sometimes rewrites descriptions to match the search; a good one is still used most often.

• ✓

  Open Graph & social cardsmedium

  Open Graph title and image set.

  Twitter/X card: summary_large_image.

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✓

  Languagelow

  lang="en"

Content quality 69%

Is there enough clear, useful text that matches what the page targets?

• ✗

  Word countmedium

  20 words of main content (inside <main>).

  Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

  Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.

  Count words and keywords with the free word counter

  Read the guide: how to write SEO content

• i

  Readabilitymedium

  Not enough paragraph text to score readability.

• ✓

  Topic focushigh

  4 of 5 title keywords appear in the main content (missing: best).

• ✓

  H1 headingcritical

  “The world’s most customizable crypto trading bot”

• ✗

  Heading structuremedium

  44 headings for 20 words – a lot for the amount of text.

  1 skipped level(s), e.g. H2 → H4.

  Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  Read the guide: the on-page SEO checklist

• ✓

  Text-to-code ratiolow

  49% of the HTML is visible text.

AI search readiness 88%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

• ✓

  AI crawler accesshigh

  Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

• ✓

  Snippet controlshigh

  No snippet restrictions – search and AI answers can quote this page.

• ✓

  llms.txtlow

  /llms.txt found.

• ✗

  Question-led contentmedium

  No headings phrased as questions.

  Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  Read the guide: how to write SEO content

• ✓

  Entity clarityhigh

  Identified as: Organization, Person.

  7 official profile link(s) (sameAs).

• ✓

  Freshness signalsmedium

  The page shows when it was published or last updated.

• ✓

  Trust pages (E-E-A-T)medium

  Links found to all three: about, contact and privacy.

Structured data 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  5 JSON-LD block(s): Organization, ImageObject, Person, PostalAddress, Place, ContactPoint, WebSite, SearchAction, Service, OfferCatalog, Offer, WebPage.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 88%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  86 internal and 57 external links.

• !

  Anchor text qualitymedium

  Same text used for different pages: “read more”.

  4 vague link(s) like “click here” or “read more”.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

Performance 46%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

• ✓

  Server response (TTFB)high

  43 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

• ✗

  HTML sizemedium

  980 kB of HTML – heavy for phones (we only analysed the first 1 MB).

  Fix: Remove inline bloat, base64 images and unused markup.

• i

  Compressionmedium

  Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.

• !

  Render-blocking resourceshigh

  1 blocking script(s) and 0 stylesheet(s) in <head>.

  Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  Read the guide: Core Web Vitals

• ✗

  Scripts & third partiesmedium

  42 script tag(s); files loaded from 1 other domain(s): cdn.sanity.io.

  Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  104 image(s).

  11 without width/height – can cause layout shift (CLS).

  1 image(s) after the first three aren't lazy-loaded.

  10 use WebP/AVIF or responsive srcset.

  Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

  Read the guide: image SEO

• ✓

  Cachinglow

  Cache-Control: public, s-maxage=600, stale-while-revalidate=3600

• ✓

  HTTP/3low

  Server advertises HTTP/3 (faster on mobile networks).

Security 92%

Visitor safety signals that browsers and Google check.

• ✓

  HTTPScritical

  Secure HTTPS with no mixed content.

• ✓

  HTTP → HTTPS redirecthigh

  http:// redirects to https://.

• ✓

  HSTSmedium

  HSTS: max-age=31536000; includeSubDomains

• ✓

  Security headerslow

  Present: CSP, nosniff, Referrer-Policy, Permissions-Policy, clickjacking protection.

• ✗

  Server fingerprintlow

  X-Powered-By reveals “Next.js”.

  Fix: Remove X-Powered-By so attackers can't see your software versions.

Mobile & accessibility 80%

Usable on phones and by everyone – Google indexes the mobile version.

• ✓

  Mobile viewportcritical

  viewport: width=device-width, initial-scale=1

• ✓

  Image alt textmedium

  All 104 images have alt text.

• ✓

  Link nameslow

  Every link has a readable name.

• ✗

  Tap-to-contactmedium

  No tel: or mailto: links.

  Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.

  Read the guide: mobile-friendly websites

Local SEO 33%

Signals that help you appear in Google Maps and 'near me' searches.

• ✗

  LocalBusiness markuphigh

  No LocalBusiness structured data.

  Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Contact details on pagemedium

  A UK phone number is shown.

  A UK postcode is shown.

• ✗

  Map & directionslow

  No map or directions link.

  Fix: Add a Google Maps directions link so customers can find you.

  Read the guide: the local SEO checklist