SEO report

SEO report for geekflare.com

https://geekflare.com/ · checked Sun, 01 Nov 2026 20:23 GMT

✓ 37 Passed! 4 Warnings✗ 5 FailedAI readiness 78%

Fix these first

  1. Title tagcritical

    “Web Scraping API, Search API & Screenshot API | Geekflare”

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

    See the details

  2. Freshness signalsmedium

    No published/updated date found.

    Fix: Show a 'last updated' date and add dateModified to your structured data.

    See the details

  3. HTML sizemedium

    394 kB of HTML – heavy for phones.

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

    See the details

  4. Imagesmedium

    49 image(s).

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

    See the details

  5. 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.

    See the details

  6. Entity clarityhigh

    Identified as: Organization.

    Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

    See the details

  7. Render-blocking resourceshigh

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

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

    See the details

  8. Text-to-code ratiolow

    3% of the HTML is visible text.

    Fix: Trim unused markup, inline scripts and builder bloat.

    See the details

Check the whole website

This report covers one page. The full-site audit crawls up to 250 pages to find broken links, duplicate titles, orphan pages and more.

Run a full-site audit

Monitor this site weekly

We'll re-check it every week and track the score, with a history graph and a list of anything that breaks.

Compare with competitors

See how this page scores against up to two competitors, side by side, and where they beat you.

Compare sites

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 geekflare.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://geekflare.com/sitemap.xml with 100 URLs.

    Declared in robots.txt.

    This page is listed in it.

    Most recent lastmod: 2026-09-30T00:00:00.000Z.

  • ✓

    Canonical URLhigh

    Canonical: https://geekflare.com/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✓

    www / non-wwwmedium

    www.geekflare.com redirects to geekflare.com.

Search snippet & sharing 79%

How the page looks in Google results and when shared.

  • !

    Title tagcritical

    “Web Scraping API, Search API & Screenshot API | Geekflare”

    About 542px of Google's ~580px desktop width.

    Repeated words: api.

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

  • ✓

    Meta descriptionhigh

    141 characters, ~918px 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 93%

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

  • ✓

    Word countmedium

    1,568 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.

  • ✓

    Readabilitymedium

    Flesch reading ease 66 (plain English), about 10 words per sentence.

  • ✓

    Topic focushigh

    5 of 5 title keywords appear in the main content.

  • ✓

    H1 headingcritical

    “Web data, ready for AI.”

  • ✓

    Heading structuremedium

    31 headings for 1568 words.

    Levels are in order.

  • ✗

    Text-to-code ratiolow

    3% of the HTML is visible text.

    Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 78%

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

    6 heading(s) phrased as questions, e.g. “Which APIs does Geekflare offer?”.

  • !

    Entity clarityhigh

    Identified as: Organization.

    No sameAs links to official profiles (Google Business Profile, LinkedIn, Facebook, Companies House…).

    Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  • ✗

    Freshness signalsmedium

    No published/updated date found.

    Fix: Show a 'last updated' date and add dateModified to your structured data.

  • ✓

    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

    2 JSON-LD block(s): SoftwareApplication, Offer, Organization, ImageObject, FAQPage, Question, Answer.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

    Google now shows FAQ rich results only for well-known government and health sites, but the markup still helps machines read your Q&As.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 50%

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

  • ✓

    Server response (TTFB)high

    35 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

    394 kB of HTML – heavy for phones.

    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 3 stylesheet(s) in <head>.

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

  • !

    Scripts & third partiesmedium

    24 script tag(s); files loaded from 1 other domain(s): googletagmanager.com.

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

  • ✗

    Imagesmedium

    49 image(s).

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

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

    1 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.

  • ✓

    Cachinglow

    Cache-Control: s-maxage=31536000

  • i

    HTTP/3low

    Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.

Security 100%

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; preload

  • ✓

    Security headerslow

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

  • ✓

    Server fingerprintlow

    No X-Powered-By header (server: cloudflare).

Mobile & accessibility 83%

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

  • ✓

    Mobile viewportcritical

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

  • ✓

    Image alt textmedium

    All 49 images have alt text.

  • ✓

    Form labelsmedium

    All 2 form fields are labelled.

  • ✗

    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.

Local SEO not scored

This site doesn't look like a local business, so these checks are shown for information and not scored.

  • i

    LocalBusiness markuphigh

    No LocalBusiness structured data.

  • i

    Contact details on pagemedium

    No phone number found.

    No postcode found (fine for service-area businesses).

  • i

    Map & directionslow

    No map or directions link.

This report checks one page. Scores are a guide, not a guarantee of rankings. Check another page · Print or save as PDF

Want these fixed for you? XKey is made by IceWork, a Blackpool web studio. IceWork builds fast websites that pass every check here – a 3-page site with domain and a year's hosting is £350 all in.