SEO report

SEO report for calendly.com

https://calendly.com/ · checked Sun, 01 Nov 2026 16:06 GMT

✓ 31 Passed! 9 Warnings✗ 7 FailedAI readiness 75%

Fix these first

  1. Title tagcritical

    “Meeting Scheduling Software and AI Meeting Tools | Calendly”

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

    See the details

  2. H1 headingcritical

    2 H1 headings – one clear H1 is best practice.

    Fix: Use one H1 that states the page topic with its main keyword.

    See the details

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

    See the details

  4. Freshness signalsmedium

    No published/updated date found.

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

    See the details

  5. HTML sizemedium

    855 kB of HTML – heavy for phones.

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

    See the details

  6. Imagesmedium

    82 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

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

  8. Meta descriptionhigh

    159 characters, ~1011px of ~990px.

    Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

    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 calendly.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://calendly.com/marketing-site/sitemap.xml with 1,073 URLs.

    Declared in robots.txt.

    This page is listed in it.

    Most recent lastmod: 2026-10-30T20:21:01.666Z.

  • ✓

    Canonical URLhigh

    Canonical: https://calendly.com

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✓

    www / non-wwwmedium

    www.calendly.com redirects to calendly.com.

  • ✓

    hreflangmedium

    6 hreflang link(s).

    All language codes are valid.

Search snippet & sharing 67%

How the page looks in Google results and when shared.

Content quality 70%

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

  • ✓

    Word countmedium

    1,320 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 57 (fairly easy), about 10 words per sentence.

  • ✓

    Topic focushigh

    3 of 4 title keywords appear in the main content (missing: software).

  • !

    H1 headingcritical

    2 H1 headings – one clear H1 is best practice.

    Fix: Use one H1 that states the page topic with its main keyword.

  • !

    Heading structuremedium

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

    Levels are in order.

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

  • ✗

    Text-to-code ratiolow

    1% of the HTML is visible text.

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

AI search readiness 75%

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.

    Training-only crawlers blocked: CCBot. That's a licensing choice – these companies document them as separate from their search crawlers.

  • ✓

    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.

  • ✓

    Entity clarityhigh

    Identified as: Organization.

    5 official profile link(s) (sameAs).

  • ✗

    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

    1 JSON-LD block(s): Organization, ImageObject, WebSite.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 46%

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

  • ✓

    Server response (TTFB)high

    152 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

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

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

  • !

    Scripts & third partiesmedium

    14 script tag(s); files loaded from 2 other domain(s): googletagmanager.com, cdn.calendlycms.com.

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

  • ✗

    Imagesmedium

    82 image(s).

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

    63 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: no-store, no-cache, must-revalidate, max-age=0, s-maxage=0

    Fix: Set Cache-Control so browsers and CDNs can reuse the page.

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

  • ✗

    Security headerslow

    Present: nosniff.

    Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  • ✓

    Server fingerprintlow

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

Mobile & accessibility 80%

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

  • ✓

    Mobile viewportcritical

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

  • ✓

    Image alt textmedium

    All 82 images have alt text.

  • ✗

    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.