SEO report for www.vectra.ai
https://www.vectra.ai/ · checked Sun, 01 Nov 2026 20:25 GMT
Fix these first
- LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- 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.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- Scripts & third partiesmedium
31 script tag(s); files loaded from 8 other domain(s): cdn.prod.website-files.com, ajax.googleapis.com, cdn.usefathom.com, cdn.jsdelivr.net, d3e54v103j8qbb.cloudfront.net, js.hs-scripts.com….
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- Imagesmedium
73 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- Form labelsmedium
1 of 1 form field(s) have no label.
Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).
- Meta descriptionhigh
188 characters, ~1163px of ~990px.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- Render-blocking resourceshigh
1 blocking script(s) and 2 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
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 vectra.ai…
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://www.vectra.ai/sitemap.xml with 1,806 URLs.
Declared in robots.txt.
This page is listed in it.
Most recent lastmod: 2026-10-30T16:33:38.812Z.
- ✓
Canonical URLhigh
Canonical: https://www.vectra.ai
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://vectra.ai/ → https://www.vectra.ai/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
vectra.ai redirects to www.vectra.ai.
- ✓
hreflangmedium
6 hreflang link(s).
All language codes are valid.
No x-default (recommended for a language picker or fallback page).
Search snippet & sharing 88%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“AI-Native Security & Observability Platform | Vectra AI”
About 479px of Google's ~580px desktop width.
- !
Meta descriptionhigh
188 characters, ~1163px of ~990px.
Long – Google will probably truncate it.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
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="en"
Content quality 90%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
921 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.
- !
Readabilitymedium
Flesch reading ease 47 (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
“AI-native Security and Observability”
- ✓
Heading structuremedium
16 headings for 921 words.
Levels are in order.
- !
Text-to-code ratiolow
5% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 75%
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: Corporation, Person.
11 official profile link(s) (sameAs).
- ✗
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 all three: about, contact and privacy.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
2 JSON-LD block(s): WebSite, SearchAction, WebPage, Corporation, ImageObject, PostalAddress, Person, CreativeWork.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 88%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
220 internal and 30 external links.
- !
Anchor text qualitymedium
Same text used for different pages: “learn more”, “read more”.
6 vague link(s) like “click here” or “read more”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
3 link(s) point to a redirect – link to the final address instead.
Performance 53%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
576 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
257 kB of HTML.
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with gzip.
- !
Render-blocking resourceshigh
1 blocking script(s) and 2 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
31 script tag(s); files loaded from 8 other domain(s): cdn.prod.website-files.com, ajax.googleapis.com, cdn.usefathom.com, cdn.jsdelivr.net, d3e54v103j8qbb.cloudfront.net, js.hs-scripts.com….
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
73 image(s).
73 without width/height – can cause layout shift (CLS).
37 image(s) after the first three aren't lazy-loaded.
The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.
28 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
No Cache-Control header.
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
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=31536000; includeSubDomains
- ✗
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 83%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✓
Image alt textmedium
All 73 images have alt text.
- ✗
Form labelsmedium
1 of 1 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
One-tap contact: email.
Local SEO 50%
Signals that help you appear in Google Maps and 'near me' searches.
- ✗
LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- ✓
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
An email link is shown.
- ✓
Map & directionslow
Links to or embeds a map.