Scanned sites / veemanlaw.com / 2026-11-01-1556

veemanlaw.com scan from 2026-11-01 15:56:23 UTC DR 11

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-11-01-1556

Scanned 2026-11-01 15:56:23 UTC, finished 2026-11-01 16:23:42 UTC. Found on page 3 of brave web search results

Site: https://veemanlaw.com/

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

84/ 100Good

On November 1, 2026 the Site Spider crawled 15 pages and 53 assets of veemanlaw.com, starting from https://veemanlaw.com/. It scored 84 out of 100, a good result. 6 of 33 checks found something to fix, led by meta descriptions (14), thin content (6), title tags (3); 21 checks passed. Most of the points went to meta descriptions (−8), thin content (−3.4), title tags (−2.1). 6 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. 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
15
Assets fetched
53
Status
Completed
Checks with issues
6 of 33
CoverageComplete crawl

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

  • Title tags3 issues
    3 of 14 pages have title issues.
    −2.1 points
  • Meta descriptions14 issues
    14 of 14 pages have meta description issues.
    −8 points
  • Headings1 issue
    1 of 14 pages have heading issues.
    −0.4 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites28 noted
    0 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 12 destinations checked.
  • Redirects1 issue
    2 redirecting URLs, 0 of them chained.
    −0.3 points
  • Non-200 responses2 noted
    2 URLs did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 14 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 42 image references have no alt attribute.
  • Heavy assets3 issues
    3 assets larger than 500 KB among 53 fetched assets.
    −1.8 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverageOK
    2 sitemaps listing 14 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
  • Internal link countsOK
    Internal link counts for 14 pages; none is a dead end or buried.
  • Thin content6 issues
    6 of 14 pages have fewer than 200 words.
    −3.4 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 15 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 14 pages have a canonical worth checking.
  • Robots directives14 noted
    14 pages carry a robots directive; 0 carry none.
  • Anchor text2 noted
    2 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structureOK
    0 of 14 pages could use the title, heading and snippet space better.
  • Image weight and alt length7 noted
    7 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 14 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    14 of 14 indexable pages carry structured data: BreadcrumbList (14), ListItem (14), WebSite (14), Organization (14), WebPage (14). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 14 pages with enough text to compare.
  • Soft 404sOK
    None of 14 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positions6 noted
    6 of 14 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 15 response headers recorded across 68 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 14 pages; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • SpellingOK
    No unfamiliar lower-case words on 14 pages (English pages only).

Where this scan sits among all scanned sites

2488 sites, median 80%, average 78%

veemanlaw.com scores 84%, higher than 68% of the 2488 scanned sites. See the full ranking.

0591180%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 5 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 8 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 28 sites64%: 21 sites65%: 31 sites66%: 36 sites67%: 36 sites68%: 36 sites69%: 49 sites70%: 48 sites71%: 73 sites72%: 72 sites73%: 73 sites74%: 72 sites75%: 75 sites76%: 88 sites77%: 99 sites78%: 112 sites79%: 97 sites80%: 118 sites81%: 111 sites82%: 112 sites83%: 112 sites84%: 115 sites85%: 94 sites86%: 77 sites87%: 84 sites88%: 60 sites89%: 70 sites90%: 45 sites91%: 52 sites92%: 40 sites93%: 27 sites94%: 21 sites95%: 13 sites96%: 14 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites84% 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

Your site has several SEO issues needing attention, especially with meta descriptions, titles, and thin content. Addressing these will improve your site's visibility and user engagement.

  1. 1

    Add Meta Descriptions

    Why: 14 pages lack meta descriptions, impacting click-through rates.

    How: Write concise, relevant meta descriptions (155-160 characters) for all pages.

    Checks: meta-descriptions

  2. 2

    Fix Title Tag Issues

    Why: 3 pages have lengthy title tags, which could be cut off in search results.

    How: Revise titles to stay under 60 characters. Ensure they accurately reflect page content.

    Checks: titles

  3. 3

    Add H1 Tags

    Why: One page is missing an H1, crucial for SEO and user experience.

    How: Add a clear H1 tag that reflects the content of the affected page.

    Checks: headings

  4. 4

    Reduce Heavy Assets

    Why: Large files can slow page load speeds, affecting user experience.

    How: Optimize or compress images and scripts over 500 KB to improve loading times.

    Checks: heavy-assets

  5. 5

    Increase Content Length

    Why: 6 pages have thin content, which may reduce their effectiveness in search rankings.

    How: Expand content on these pages to 200+ words, providing valuable information.

    Checks: thin-content

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 veemanlaw.com lacks essential security headers, exposing it to potential attacks such as interception, clickjacking, and unauthorized script execution. Implementing the suggested headers will help improve security posture significantly.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users accessing the site without https:// can be intercepted.

    Fix: Add the header: Strict-Transport-Security: max-age=63072000; includeSubDomains; preload

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows unrestricted loading of scripts and resources, increasing risk of XSS attacks.

    Fix: Add the header: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, the site risks clickjacking attacks, allowing other sites to embed it.

    Fix: Add the header: X-Frame-Options: DENY

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-OptionsLow

    Why it matters: Absence of this header may lead browsers to execute files as scripts based on content.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Without a referrer policy, sensitive URL information is exposed to third-party sites.

    Fix: Add the header: Referrer-Policy: no-referrer

    Evidence: Referrer policy

  6. 6

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from other domains without Subresource Integrity may introduce vulnerabilities if those domains are compromised.

    Fix: Consider implementing a CSP that restricts sources of scripts or using Subresource Integrity where applicable.

    Evidence: Third-party scripts

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: The absence of this policy allows unintentional access to sensitive features by injected scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(), camera=(), microphone=()

    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://veemanlaw.com/ → no strict-transport-security
    • https://veemanlaw.com/contact/ → no strict-transport-security
    • https://veemanlaw.com/our-team/ → no strict-transport-security
    • https://veemanlaw.com/client-portal/ → no strict-transport-security
    • https://veemanlaw.com/practice-area/ → no strict-transport-security
    • https://veemanlaw.com/practice-area/immigration-law/ → no strict-transport-security
    • https://veemanlaw.com/fee-structures-and-estimates/ → no strict-transport-security
    • https://veemanlaw.com/privacy-policy/ → no strict-transport-security
    • https://veemanlaw.com/disclaimer/ → no strict-transport-security
    • https://veemanlaw.com/our-team/chris-veeman/ → no strict-transport-security
    • https://veemanlaw.com/our-team/linda-liu/ → no strict-transport-security
    • https://veemanlaw.com/our-team/emily-berday/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 14 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://veemanlaw.com/ → no content-security-policy
    • https://veemanlaw.com/contact/ → no content-security-policy
    • https://veemanlaw.com/our-team/ → no content-security-policy
    • https://veemanlaw.com/client-portal/ → no content-security-policy
    • https://veemanlaw.com/practice-area/ → no content-security-policy
    • https://veemanlaw.com/practice-area/immigration-law/ → no content-security-policy
    • https://veemanlaw.com/fee-structures-and-estimates/ → no content-security-policy
    • https://veemanlaw.com/privacy-policy/ → no content-security-policy
    • https://veemanlaw.com/disclaimer/ → no content-security-policy
    • https://veemanlaw.com/our-team/chris-veeman/ → no content-security-policy
    • https://veemanlaw.com/our-team/linda-liu/ → no content-security-policy
    • https://veemanlaw.com/our-team/emily-berday/ → 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://veemanlaw.com/ → no x-frame-options
    • https://veemanlaw.com/contact/ → no x-frame-options
    • https://veemanlaw.com/our-team/ → no x-frame-options
    • https://veemanlaw.com/client-portal/ → no x-frame-options
    • https://veemanlaw.com/practice-area/ → no x-frame-options
    • https://veemanlaw.com/practice-area/immigration-law/ → no x-frame-options
    • https://veemanlaw.com/fee-structures-and-estimates/ → no x-frame-options
    • https://veemanlaw.com/privacy-policy/ → no x-frame-options
    • https://veemanlaw.com/disclaimer/ → no x-frame-options
    • https://veemanlaw.com/our-team/chris-veeman/ → no x-frame-options
    • https://veemanlaw.com/our-team/linda-liu/ → no x-frame-options
    • https://veemanlaw.com/our-team/emily-berday/ → 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://veemanlaw.com/ → no x-content-type-options
    • https://veemanlaw.com/contact/ → no x-content-type-options
    • https://veemanlaw.com/our-team/ → no x-content-type-options
    • https://veemanlaw.com/client-portal/ → no x-content-type-options
    • https://veemanlaw.com/practice-area/ → no x-content-type-options
    • https://veemanlaw.com/practice-area/immigration-law/ → no x-content-type-options
    • https://veemanlaw.com/fee-structures-and-estimates/ → no x-content-type-options
    • https://veemanlaw.com/privacy-policy/ → no x-content-type-options
    • https://veemanlaw.com/disclaimer/ → no x-content-type-options
    • https://veemanlaw.com/our-team/chris-veeman/ → no x-content-type-options
    • https://veemanlaw.com/our-team/linda-liu/ → no x-content-type-options
    • https://veemanlaw.com/our-team/emily-berday/ → 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://veemanlaw.com/ → no referrer-policy
    • https://veemanlaw.com/contact/ → no referrer-policy
    • https://veemanlaw.com/our-team/ → no referrer-policy
    • https://veemanlaw.com/client-portal/ → no referrer-policy
    • https://veemanlaw.com/practice-area/ → no referrer-policy
    • https://veemanlaw.com/practice-area/immigration-law/ → no referrer-policy
    • https://veemanlaw.com/fee-structures-and-estimates/ → no referrer-policy
    • https://veemanlaw.com/privacy-policy/ → no referrer-policy
    • https://veemanlaw.com/disclaimer/ → no referrer-policy
    • https://veemanlaw.com/our-team/chris-veeman/ → no referrer-policy
    • https://veemanlaw.com/our-team/linda-liu/ → no referrer-policy
    • https://veemanlaw.com/our-team/emily-berday/ → 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://veemanlaw.com/ → no permissions-policy
    • https://veemanlaw.com/contact/ → no permissions-policy
    • https://veemanlaw.com/our-team/ → no permissions-policy
    • https://veemanlaw.com/client-portal/ → no permissions-policy
    • https://veemanlaw.com/practice-area/ → no permissions-policy
    • https://veemanlaw.com/practice-area/immigration-law/ → no permissions-policy
    • https://veemanlaw.com/fee-structures-and-estimates/ → no permissions-policy
    • https://veemanlaw.com/privacy-policy/ → no permissions-policy
    • https://veemanlaw.com/disclaimer/ → no permissions-policy
    • https://veemanlaw.com/our-team/chris-veeman/ → no permissions-policy
    • https://veemanlaw.com/our-team/linda-liu/ → no permissions-policy
    • https://veemanlaw.com/our-team/emily-berday/ → no permissions-policy
  • NoteThird-party scripts

    Scripts run from 3 other domains without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)

    • cloud04.titletapsites.com (14 script tags)
    • www.googletagmanager.com (14 script tags)
    • translate.google.com (13 script tags)
8 checks passed, 1 not applicable
  • OKHTTPS

    All 14 crawled pages were served over HTTPS.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKMixed content

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

  • OKForms over HTTPS

    14 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

    1 library version 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.

  • 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.

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 veemanlaw.com

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

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

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

Own veemanlaw.com?