Scanned sites / avexai.io / 2026-10-04-1135

avexai.io scan from 10/4/2026, 11:35:39 AM

Scan 2026-10-04-1135

Scanned 10/4/2026, 11:35:39 AM, finished 10/4/2026, 11:41:15 AM

Site: https://avexai.io/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

80/ 100Good

On October 4, 2026 the Site Spider crawled 50 pages and 206 assets of avexai.io, starting from https://avexai.io/. It scored 80 out of 100, a good result. 12 of 16 checks found something to fix, led by meta descriptions (42), title tags (29), links to other sites (4); 3 checks passed. Most of the points went to meta descriptions (−7.3), title tags (−6.3), links to other sites (−1.6). 1 check found something the score does not count, listed as noted. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: Medium3 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
50
Assets fetched
206
Status
Completed
Checks with issues
12 of 16
CoverageComplete crawl

256 of 256 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 75 link destinations on other sites were checked.

  • Title tags29 issues
    29 of 46 pages have title issues.
    −6.3 points
  • Meta descriptions42 issues
    42 of 46 pages have meta description issues.
    −7.3 points
  • Headings2 issues
    2 of 46 pages have heading issues.
    −0.3 points
  • Broken links2 issues
    2 internal links point at 2 broken URLs.
    −0.9 points
  • Links to other sites4 issues
    4 destinations answered with an error, 20 could not be determined (timeouts, rate limits or refusals), of 75 destinations checked.
    −1.6 points
  • Redirects2 issues
    2 redirecting URLs, 0 of them chained.
    −0.2 points
  • Non-200 responses2 issues
    4 URLs did not return a 2xx response. 4 of them are pages, 2 with an error status; the rest are assets or redirects.
    −0.4 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability5 issues
    5 of 46 indexable pages have indexability warnings.
    −1.1 points
  • Image alt textOK
    0 of 207 image references have no alt attribute. 98 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 206 fetched assets.
  • Orphan pages2 issues
    2 pages have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage6 issues
    7 sitemaps listing 42 URLs: 4 crawled pages missing, 0 listed URLs broken or redirecting, 2 reachable only via the sitemap.
    −0.8 points
  • Internal link countsOK
    Internal link counts for 46 pages.
  • Thin content5 issues
    5 of 46 pages have fewer than 200 words.
    −0.9 points
  • Duplicate content2 issues
    1 group of pages with identical HTML.
    −0.3 points

Where this scan sits among all scanned sites

2060 sites, median 79%, average 78%

avexai.io scores 80%, higher than 50% of the 2060 scanned sites. See the full ranking.

0521040%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 1 site28%: 0 sites29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 1 site36%: 2 sites37%: 2 sites38%: 3 sites39%: 1 site40%: 2 sites41%: 1 site42%: 0 sites43%: 1 site44%: 1 site45%: 4 sites46%: 5 sites47%: 4 sites48%: 3 sites49%: 3 sites50%: 5 sites51%: 5 sites52%: 8 sites53%: 5 sites54%: 7 sites55%: 8 sites56%: 5 sites57%: 10 sites58%: 14 sites59%: 6 sites60%: 10 sites61%: 11 sites62%: 18 sites63%: 19 sites64%: 18 sites65%: 34 sites66%: 27 sites67%: 40 sites68%: 33 sites69%: 26 sites70%: 39 sites71%: 53 sites72%: 66 sites73%: 54 sites74%: 58 sites75%: 76 sites76%: 81 sites77%: 78 sites78%: 97 sites79%: 86 sites80%: 104 sites81%: 97 sites82%: 103 sites83%: 96 sites84%: 84 sites85%: 69 sites86%: 73 sites87%: 67 sites88%: 67 sites89%: 49 sites90%: 37 sites91%: 41 sites92%: 25 sites93%: 18 sites94%: 16 sites95%: 8 sites96%: 6 sites97%: 8 sites98%: 1 site99%: 2 sites100%: 56 sites80% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

The site has several critical issues needing attention, such as broken links and numerous title and meta description problems. Addressing these will improve SEO effectiveness and site usability.

  1. 1

    Fix Broken Links

    Why: Two broken internal links harm user experience and SEO.

    How: Update or remove links to the broken URLs.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: Four URLs returning non-200 responses can hinder search engine indexing.

    How: Check and fix errors, ensuring all URLs return 200 statuses.

    Checks: status-codes

  3. 3

    Address Title Tag Issues

    Why: 29 pages have title problems, which can negatively impact click-through rates.

    How: Revise titles to be under 60 characters for all affected URLs.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: 42 pages lack effective meta descriptions affecting search visibility.

    How: Write unique meta descriptions under 160 characters for each affected page.

    Checks: meta-descriptions

  5. 5

    Fix Heading Issues

    Why: Two pages have heading issues, which can confuse SEO and users.

    How: Ensure each page has a single H1 and properly structured headings.

    Checks: headings

  6. 6

    Ensure Page Indexability

    Why: Five pages flagged for indexability can impact search rankings.

    How: Check for canonical tags and implement them where needed.

    Evidence: 5 pages flagged: No canonical.

    5 pages affected

    Depends on: Confirm the pages really share a cause before changing them together.

    Checks: indexability

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

The website avexai.io lacks several important security headers, exposing it to potential attacks like man-in-the-middle and clickjacking. Urgent measures should be taken to implement HTTP Strict Transport Security, Content Security Policy, and X-Frame-Options. Additional headers for MIME sniffing and referrer policies are also needed.

  • 0 high
  • 3 medium
  • 3 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, a user can be intercepted on their first request when accessing via HTTP.

    Fix: Add 'Strict-Transport-Security' header with a value of 'max-age=63072000; includeSubDomains'.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows for potential injection of malicious scripts and content.

    Fix: Implement 'Content-Security-Policy' header with a value that specifies trusted sources (e.g., 'default-src 'self';').

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Not using X-Frame-Options lets others embed pages in frames, risking clickjacking attacks.

    Fix: Add 'X-Frame-Options' header with a value of 'DENY' or 'SAMEORIGIN'.

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-OptionsLow

    Why it matters: The absence of this header increases the risk of MIME sniffing attacks.

    Fix: Add 'X-Content-Type-Options' header with a value of 'nosniff'.

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-PolicyLow

    Why it matters: Not having a referrer policy can leak sensitive URL data to external sites.

    Fix: Implement 'Referrer-Policy' header with a value of 'no-referrer' or 'same-origin'.

    Evidence: Referrer policy

  6. 6

    Server Information LeakageLow

    Why it matters: Revealing framework information via 'X-Powered-By' can assist attackers in targeting vulnerabilities.

    Fix: Remove or set 'X-Powered-By' to a value that does not disclose the framework version.

    Evidence: Software version disclosure

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Without this header, untrusted scripts can utilize sensitive browser features.

    Fix: Add 'Permissions-Policy' header with a value that restricts unused features (e.g., 'geolocation=()').

    Evidence: Permissions policy

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://avexai.io/ → no strict-transport-security
    • https://avexai.io/blog/ → no strict-transport-security
    • https://avexai.io/tools/cgt-calculator → no strict-transport-security
    • https://avexai.io/contact → no strict-transport-security
    • https://avexai.io/gdpr → no strict-transport-security
    • https://avexai.io/privacy-policy → no strict-transport-security
    • https://avexai.io/terms → no strict-transport-security
    • https://avexai.io/blog/hargreaves-lansdown-portfolio-tracker/ → no strict-transport-security
    • https://avexai.io/blog/category/wealth-intelligence/uk-brokers/ → no strict-transport-security
    • https://avexai.io/blog/category/us-brokers/ → no strict-transport-security
    • https://avexai.io/blog/category/uk-tax-reporting/ → no strict-transport-security
    • https://avexai.io/blog/category/portfolio-analytics/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 46 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.

    • https://avexai.io/ → no content-security-policy
    • https://avexai.io/blog/ → no content-security-policy
    • https://avexai.io/tools/cgt-calculator → no content-security-policy
    • https://avexai.io/contact → no content-security-policy
    • https://avexai.io/gdpr → no content-security-policy
    • https://avexai.io/privacy-policy → no content-security-policy
    • https://avexai.io/terms → no content-security-policy
    • https://avexai.io/blog/hargreaves-lansdown-portfolio-tracker/ → no content-security-policy
    • https://avexai.io/blog/category/wealth-intelligence/uk-brokers/ → no content-security-policy
    • https://avexai.io/blog/category/us-brokers/ → no content-security-policy
    • https://avexai.io/blog/category/uk-tax-reporting/ → no content-security-policy
    • https://avexai.io/blog/category/portfolio-analytics/ → no content-security-policy
  • FoundClickjacking protectionMedium

    No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://avexai.io/ → no x-frame-options
    • https://avexai.io/blog/ → no x-frame-options
    • https://avexai.io/tools/cgt-calculator → no x-frame-options
    • https://avexai.io/contact → no x-frame-options
    • https://avexai.io/gdpr → no x-frame-options
    • https://avexai.io/privacy-policy → no x-frame-options
    • https://avexai.io/terms → no x-frame-options
    • https://avexai.io/blog/hargreaves-lansdown-portfolio-tracker/ → no x-frame-options
    • https://avexai.io/blog/category/wealth-intelligence/uk-brokers/ → no x-frame-options
    • https://avexai.io/blog/category/us-brokers/ → no x-frame-options
    • https://avexai.io/blog/category/uk-tax-reporting/ → no x-frame-options
    • https://avexai.io/blog/category/portfolio-analytics/ → no x-frame-options
  • FoundMIME sniffing protectionLow

    No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://avexai.io/ → no x-content-type-options
    • https://avexai.io/blog/ → no x-content-type-options
    • https://avexai.io/tools/cgt-calculator → no x-content-type-options
    • https://avexai.io/contact → no x-content-type-options
    • https://avexai.io/gdpr → no x-content-type-options
    • https://avexai.io/privacy-policy → no x-content-type-options
    • https://avexai.io/terms → no x-content-type-options
    • https://avexai.io/blog/hargreaves-lansdown-portfolio-tracker/ → no x-content-type-options
    • https://avexai.io/blog/category/wealth-intelligence/uk-brokers/ → no x-content-type-options
    • https://avexai.io/blog/category/us-brokers/ → no x-content-type-options
    • https://avexai.io/blog/category/uk-tax-reporting/ → no x-content-type-options
    • https://avexai.io/blog/category/portfolio-analytics/ → no x-content-type-options
  • FoundReferrer policyLow

    No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://avexai.io/ → no referrer-policy
    • https://avexai.io/blog/ → no referrer-policy
    • https://avexai.io/tools/cgt-calculator → no referrer-policy
    • https://avexai.io/contact → no referrer-policy
    • https://avexai.io/gdpr → no referrer-policy
    • https://avexai.io/privacy-policy → no referrer-policy
    • https://avexai.io/terms → no referrer-policy
    • https://avexai.io/blog/hargreaves-lansdown-portfolio-tracker/ → no referrer-policy
    • https://avexai.io/blog/category/wealth-intelligence/uk-brokers/ → no referrer-policy
    • https://avexai.io/blog/category/us-brokers/ → no referrer-policy
    • https://avexai.io/blog/category/uk-tax-reporting/ → no referrer-policy
    • https://avexai.io/blog/category/portfolio-analytics/ → no referrer-policy
  • FoundPermissions policyInfo

    No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.

    • https://avexai.io/ → no permissions-policy
    • https://avexai.io/blog/ → no permissions-policy
    • https://avexai.io/tools/cgt-calculator → no permissions-policy
    • https://avexai.io/contact → no permissions-policy
    • https://avexai.io/gdpr → no permissions-policy
    • https://avexai.io/privacy-policy → no permissions-policy
    • https://avexai.io/terms → no permissions-policy
    • https://avexai.io/blog/hargreaves-lansdown-portfolio-tracker/ → no permissions-policy
    • https://avexai.io/blog/category/wealth-intelligence/uk-brokers/ → no permissions-policy
    • https://avexai.io/blog/category/us-brokers/ → no permissions-policy
    • https://avexai.io/blog/category/uk-tax-reporting/ → no permissions-policy
    • https://avexai.io/blog/category/portfolio-analytics/ → no permissions-policy
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (256 responses)
    • x-powered-by: Next.js (6 responses)
7 checks passed, 2 not applicable
  • OKHTTPS

    All 46 crawled pages were served over HTTPS.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKThird-party scripts

    Scripts from 1 other domain all carry Subresource Integrity hashes.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Sites scoring near avexai.io

Their neighbours in the SEO rank table, which orders every scanned site by health score.

This report was produced by the DIY SEO Hub Site Spider crawling avexai.io from its pages as published, the way a search engine does. It shows summary figures only.

Own avexai.io?

avexai.io scan 2026-10-04-1135 | DIY SEO Hub