SEO report for modelcontextprotocol.com.cn
https://modelcontextprotocol.com.cn/docs/2026-07-28/getting-started/intro · checked Wed, 11 Nov 2026 21:05 GMT
Fix these first
- 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.
- HTTP → HTTPS redirecthigh
http:// does not redirect to https://.
Fix: 301-redirect all http:// requests to https://.
- Title tagcritical
“什么是模型上下文协议 (MCP)? - Model Context Protocol - MCP 模型上下文协议”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- Open Graph & social cardsmedium
Open Graph title or image missing.
Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.
- Word countmedium
125 words of main content (inside <main>).
Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.
- 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.
- 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.
- Scripts & third partiesmedium
134 script tag(s); files loaded from 3 other domain(s): pagead2.googlesyndication.com, cdn.jsdelivr.net.cn, mintcdn.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
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.com.cn…
Indexing & crawling 94%
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.com.cn/sitemap.xml with 147 URLs.
Not declared in robots.txt.
This page is listed in it.
Most recent lastmod: 2026-08-29.
Fix: Add a 'Sitemap:' line to robots.txt, list every indexable page and include accurate lastmod dates.
- ✓
Canonical URLhigh
Canonical: https://modelcontextprotocol.com.cn/docs/2026-07-28/getting-started/intro
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://modelcontextprotocol.com.cn/ → https://modelcontextprotocol.com.cn/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.com.cn isn't in use (HTTP 525).
Search snippet & sharing 38%
How the page looks in Google results and when shared.
- !
Title tagcritical
“什么是模型上下文协议 (MCP)? - Model Context Protocol - MCP 模型上下文协议”
About 557px of Google's ~580px desktop width.
Repeated words: mcp.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- ✗
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.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="zh-hans"
Content quality 58%
Is there enough clear, useful text that matches what the page targets?
- ✗
Word countmedium
125 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.
- i
Readabilitymedium
Reading-ease scores only work for English; this page is lang="zh-hans".
- !
Topic focushigh
3 of 6 title keywords appear in the main content (missing: model, context, protocol).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
- ✓
H1 headingcritical
“什么是模型上下文协议 (MCP)?”
- !
Heading structuremedium
17 headings for 125 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 66%
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.
- !
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 75%
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.
Block 1: no schema.org @context
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- ✓
Required propertiesmedium
Key types include Google's required properties.
Recommended but missing: Article.datePublished, Article.author.
Links 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
21 internal and 8 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
1 link(s) point to a redirect – link to the final address instead.
Performance 75%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
220 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
264 kB of HTML.
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with br.
- ✓
Render-blocking resourceshigh
0 blocking script(s) and 2 stylesheet(s) in <head>.
- ✗
Scripts & third partiesmedium
134 script tag(s); files loaded from 3 other domain(s): pagead2.googlesyndication.com, cdn.jsdelivr.net.cn, 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: max-age=86400, public
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 58%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✗
HTTP → HTTPS redirecthigh
http:// does not redirect to https://.
Fix: 301-redirect all http:// requests to https://.
- ✗
HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- ✓
Security headerslow
Present: CSP, nosniff, Referrer-Policy, clickjacking protection.
- ✓
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).
- ✓
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.
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.