SEO report

SEO report for modelcontextprotocol.io

https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro · checked Wed, 11 Nov 2026 15:49 GMT

✓ 30 Passed! 12 Warnings✗ 6 FailedAI readiness 72%

Fix these first

  1. Meta descriptionhigh

    No meta description – Google will pick text from the page.

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

    See the details

  2. Title tagcritical

    “What is the Model Context Protocol (MCP)? - Model Context Protocol”

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

    See the details

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

    Links found to about; missing contact and privacy.

    Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

    See the details

  4. Form labelsmedium

    1 of 3 form field(s) have no label.

    Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

    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. Open Graph & social cardsmedium

    Open Graph title and image set.

    Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.

    See the details

  8. Word countmedium

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

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

    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 modelcontextprotocol.io…

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://modelcontextprotocol.io/sitemap.xml with 359 URLs.

    Declared in robots.txt.

    This page is listed in it.

    Most recent lastmod: 2026-11-11T15:17:37.895Z.

  • ✓

    Canonical URLhigh

    Canonical: https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    1 redirect before the page loaded.

    https://modelcontextprotocol.io/ → https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro

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

  • ✓

    www / non-wwwmedium

    www.modelcontextprotocol.io isn't in use (HTTP 530).

Search snippet & sharing 46%

How the page looks in Google results and when shared.

Content quality 73%

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

  • !

    Word countmedium

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

  • !

    Readabilitymedium

    Flesch reading ease 45 (fairly difficult), about 14 words per sentence.

    Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

  • ✓

    Topic focushigh

    4 of 4 title keywords appear in the main content.

  • ✓

    H1 headingcritical

    “What is the Model Context Protocol (MCP)?”

  • !

    Heading structuremedium

    20 headings for 392 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

    2% of the HTML is visible text.

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

AI search readiness 72%

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

    2 heading(s) phrased as questions, e.g. “​ What can MCP enable?”.

    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.

    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

    The page shows when it was published or last updated.

  • ✗

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

    Links found to about; missing contact and privacy.

    Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

Structured data 100%

Machine-readable facts for rich results and AI.

  • ✓

    JSON-LD present & validhigh

    1 JSON-LD block(s): Organization, ImageObject, WebSite, WebPage, BreadcrumbList, ListItem, Article, TechArticle.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

    Recommended but missing: Article.datePublished, Article.author.

  • ✓

    Breadcrumbslow

    BreadcrumbList markup present.

Performance 77%

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

  • ✓

    Server response (TTFB)high

    52 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

    160 kB of HTML.

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

  • ✓

    Compressionmedium

    Compressed with br.

  • ✓

    Render-blocking resourceshigh

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

  • !

    Scripts & third partiesmedium

    17 script tag(s); files loaded from 1 other domain(s): mintcdn.com.

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

  • !

    Imagesmedium

    3 image(s).

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

    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, proxy-revalidate, max-age=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=63072000

  • ✗

    Security headerslow

    Present: CSP, clickjacking protection.

    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 58%

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

  • ✓

    Mobile viewportcritical

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

  • !

    Image alt textmedium

    1 of 3 images have no alt attribute.

    Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).

  • ✗

    Form labelsmedium

    1 of 3 form field(s) have no label.

    Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

  • ✗

    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.