SEO
· 14 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.Cross-tab audit — SEO, performance, crawlability, mobile, structured data
FContent DepthAction36 words, Fairly EasyFIX
Thin content
Reading level
Grade 7
Text-to-HTML Ratio
0 KB / 11 KB
Search engines need substantive text content to understand and rank a page.
Page has near-zero content — Google may treat it as soft 404 or low-quality.
Source: Google Search Central
Very low ratio suggests heavy framework overhead or boilerplate.
Informational: ratio of visible text bytes to total HTML bytes. Very low ratios suggest excessive markup overhead.
CCanonical URLActionIssues foundREVIEW
Search engines cannot follow this canonical, effectively orphaning this page.
Canonical URL returns a non-200 status — Google can't follow the canonical to confirm the relationship.
Source: Google Search Central
Either the canonical has 'www.' and the final URL doesn't, or vice versa. Search engines may index both forms as duplicates. Pick one and use it consistently in the canonical AND the redirect target.
Canonical has 'www.' and final URL doesn't (or vice versa). Search engines may index both forms as duplicates.
Learn more ▾ ▴
Pick one form -- with or without www -- and use it consistently in the canonical AND the redirect target. Both forms can resolve, but unless one redirects to the other AND the canonical agrees, search engines may treat them as duplicate-content variants.
Source: Google Search Central
CSitemap FreshnessActionNo sitemap.xml foundREVIEW
CSitemap × Robots ConsistencyActionSitemap or robots.txt missing -- consistency check skippedREVIEW
A+Meta TagsTitle optimizedPASS
"Nu11Cyber — 网络安全研究团队"
Consider differentiating — the title is for search results, the H1 is for the page.
Title and H1 match exactly — internally consistent but misses an opportunity to optimize each for its audience (Title for SERP CTR, H1 for on-page).
Learn more ▾ ▴
Title and H1 don't have to be identical — and often shouldn't be. The Title competes for SERP click-through (lead with keyword + value prop), while the H1 confirms to the visitor they're on the right page (more conversational is fine). Differentiating gains both surfaces.
Source: Google Search Central / on-page SEO
A+Title Style DepthTitle style is clean -- consistent separator, no stale year, no keyword stuffingPASS
A+Internal Links6 internal, 1 externalPASS
Link Distribution
Anchor Text Quality
Most Linked Internal Pages
| # | URL | Links |
|---|---|---|
| 1 | /contact.html | 1 |
| 2 | #root | 1 |
| 3 | /privacy.html | 1 |
| 4 | /terms.html | 1 |
| 5 | /cookie-policy.html | 1 |
| 6 | /accessibility.html | 1 |
Top External Domains
| Domain | Links |
|---|---|
| www.dmca.com | 1 |
A+Image SEO3 images, 3 descriptive filenamesPASS
See Accessibility tab for detailed alt text quality analysis.
A+Hreflang URL QualityNo hreflang tags on the pagePASS
A+Hreflang CompletenessNo hreflang tags on this page -- check is N/A (single-language site or unannotated)PASS
A+Sitemap HygieneNo sitemap to evaluate -- depth check is N/APASS
A+Markup QualityNo markup-quality issues detectedPASS
A+Schema Markup Audit1 schema types detectedPASS
Rich result eligibility
Organization knowledge panel
Detected schema types
Organization json-ld → Organization knowledge panel2/2 required · 2/4 recommended
Required fields (Google)
- name — Required for the knowledge panel
- url — Required for entity matching
Recommended fields
- logo — Strongly recommended — appears in the knowledge panel header
- sameAs — Add sameAs URLs for social profiles Connects the entity across the web
- contactPoint — Add ContactPoint with telephone and contactType Enables direct contact from the knowledge panel
- description — Used as the panel summary
Adding these recommended fields improves chances of getting Organization knowledge panel in search results.
Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).
Source: Google Search Central
Hreflang0 hreflang tagsINFO
No hreflang tags detected.
Hreflang tags are only needed for multilingual or multi-regional sites.