am-potato.com.cn
Potato官网 - Potato中文版下载 | 朋友圈分享动态，自由畅聊社交平台
1 failed · 8 warnings · 20 passed
Audited Wed, 22 Jul 2026 06:15:55 GMT · https://am-potato.com.cn/
Meta & Head
21.5/25
Title, description, canonical, social tags — what search engines read first.
Meta descriptionhigh impactlow effort
Meta description is "Potato官网下载平台提供丰富的社交功能，包含朋友圈动态分享、兴趣社区、免费视频通话。打造自由、有趣的社交体验，支持全平台设备下载使用。" (69 characters)
Search engines truncate descriptions past roughly 160 characters, and very short ones waste the snippet space that persuades searchers to pick your listing over the next one. Rewrite it to 70–160 characters: state what the page offers, work the primary keyword in naturally (matching words get bolded in results), and end with a benefit or call to action. Don't cram in keywords — the description influences clicks, not rankings, so write it for humans.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:image
Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:image tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.
7 passing checks
- Title tag<title> is "Potato官网 - Potato中文版下载 | 朋友圈分享动态，自由畅聊社交平台" (41 characters)
- Canonical URLCanonical href is "https://am-potato.com.cn/index.html"
- Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingNo restrictive robots meta tag
Content & Structure
17.2/25
Headings, copy depth, images, structured data, internal linking.
Structured data (JSON-LD)medium impactmedium effort
1 JSON-LD block(s) present but none usable — block 1: Unexpected non-whitespace character after JSON at position 405 (line 1 column 406)
This page ships JSON-LD blocks, but they're malformed or missing an @type, so search engines discard them entirely — you get zero rich-result benefit from work that's already been done. Fix the JSON syntax (trailing commas and unescaped quotes are the usual culprits) and give every block a valid schema.org @type, e.g. {"@context": "https://schema.org", "@type": "Article", ...}. Validate with Google's Rich Results Test before deploying — a block that parses locally can still fail Google's stricter requirements for required properties.
Word counthigh impactlow effort
404 words of visible text
With only a few hundred words, this page gives search engines little to index and often loses to more thorough competitors targeting the same query. Expand it toward 600+ words of genuinely useful material: answer the questions visitors arrive with, and add examples, specifics, an FAQ section, or step-by-step detail. Don't pad with fluff or repeat keywords to hit a number — length should be a byproduct of covering the topic properly, never the goal itself.
Heading hierarchylow impactlow effort
Heading level jumps from h2 ("为什么选择 Potato") to h4 ("隐私保护")
Headings form the page's outline; when levels jump (h2 straight to h4), search engines and screen readers get a broken table of contents and the relationship between sections turns ambiguous. Fix the jump by stepping down one level at a time — promote the deeper heading, or add the missing intermediate level. The usual cause is choosing heading tags for their default font size; set sizes in CSS instead and let the tags reflect actual document structure.
Internal linkinglow impactlow effort
2 internal, 0 external links
Only a couple of internal links means crawlers see this page as loosely connected to the rest of your site, and less of its authority flows onward. Add contextual links to your most important related pages — in-body links with descriptive anchor text carry the most weight.
4 passing checks
- Single H1 heading1 h1 found: "Potato社交版_Potato中文版下载"
- Image alt text1 of 1 images have alt text
- HTML lang attribute<html lang="zh-CN">
- JavaScript-dependent contentvisible text ~1449 chars in the initial HTML
Technical
22.2/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
robots.txt present and permissivemedium impactlow effort
no robots.txt found
Without a robots.txt, crawlers assume everything is allowed — not fatal, but you lose the ability to keep them out of low-value areas (internal search results, carts, admin paths) and the standard place to advertise your sitemap. Create a plain-text robots.txt at the site root with at least a "User-agent: *" line and "Sitemap: https://www.example.com/sitemap.xml". Don't use it to hide sensitive URLs, though — the file is public, and disallowing a page doesn't remove it from the index; use noindex or authentication for that.
XML sitemap availablemedium impactlow effort
no sitemap.xml found
Without an XML sitemap, search engines discover pages only by following links, so new, deep, or weakly linked pages get found slowly or not at all. Generate one at /sitemap.xml — most frameworks and CMSs have a generator built in or as a plugin — listing every canonical, indexable URL, then add "Sitemap: https://www.example.com/sitemap.xml" to robots.txt and submit it in Google Search Console. Keep it clean: listing redirected, noindexed, or 404 URLs erodes crawler trust in the whole file.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
9 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- Fast time to first byte740 ms
- Reasonable HTML size24.0 KB
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.