SEO report for xsssql.com
https://xsssql.com/ · checked Wed, 11 Nov 2026 06:33 GMT
Fix these first
- XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- Canonical URLhigh
No canonical tag.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- Server response (TTFB)high
2143 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.
- HTTP → HTTPS redirecthigh
http:// does not redirect to https://.
Fix: 301-redirect all http:// requests to https://.
- H1 headingcritical
“新一代 分布式智能 漏洞扫描平台”
Fix: Use one H1 that states the page topic with its main keyword.
- www / non-wwwmedium
Both www.xsssql.com and xsssql.com load without redirecting – Google may see duplicate sites.
Fix: Pick one version (with or without www) and 301-redirect the other to it.
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 xsssql.com…
Indexing & crawling 60%
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
No robots.txt found (HTTP 404) – crawlers may read everything.
Googlebot is allowed to crawl this page.
Fix: Add a robots.txt that allows crawling and lists your sitemap.
- ✗
XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- ✗
Canonical URLhigh
No canonical tag.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- ✓
Redirectshigh
Loads directly with no redirects.
- ✗
www / non-wwwmedium
Both www.xsssql.com and xsssql.com load without redirecting – Google may see duplicate sites.
Fix: Pick one version (with or without www) and 301-redirect the other to it.
Search snippet & sharing 83%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“TestSecScan — 分布式智能漏洞扫描平台”
About 272px of Google's ~580px desktop width.
- ✓
Meta descriptionhigh
86 characters, ~660px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 42%
Is there enough clear, useful text that matches what the page targets?
- !
Word countmedium
215 words of main content (menus and footer excluded).
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
Not enough paragraph text to score readability.
- !
Topic focushigh
1 of 2 title keywords appear in the main content (missing: 分布式智能漏洞扫描平台).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
- !
H1 headingcritical
“新一代 分布式智能 漏洞扫描平台”
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- ✗
Heading structuremedium
27 headings for 215 words – a lot for the amount of text.
1 skipped level(s), e.g. H2 → H4.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- !
Text-to-code ratiolow
9% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 38%
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
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✗
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
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✗
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 privacy; missing about and contact.
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 0%
Machine-readable facts for rich results and AI.
- ✗
JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
Links 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
12 internal and 1 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 11 internal link(s).
No broken links found.
1 link(s) point to a redirect – link to the final address instead.
Performance 60%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✗
Server response (TTFB)high
2143 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.
- ✓
HTML sizemedium
29 kB of HTML.
- ✓
Compressionmedium
Compressed with gzip.
- !
Render-blocking resourceshigh
1 blocking script(s) and 1 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✓
Scripts & third partiesmedium
1 script tag(s); files loaded from 0 other domain(s).
- !
Imagesmedium
2 image(s).
2 without width/height – can cause layout shift (CLS).
The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.
0 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-cache
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 50%
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: 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 2 images have alt text.
- ✓
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.