Scanned sites / www.borhotlaw.com / 2026-09-26-2029

www.borhotlaw.com scan from 2026-09-26 20:29:39 UTC DR 0

A newer scan exists. See the latest report for www.borhotlaw.com.

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

Scan 2026-09-26-2029

Scanned 2026-09-26 20:29:39 UTC, finished 2026-09-27 15:06:32 UTC. Found with openstreetmap overpass

Site: https://www.borhotlaw.com/

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

81/ 100Good

On September 26, 2026 the Site Spider crawled 4 pages and 57 assets of www.borhotlaw.com, starting from https://www.borhotlaw.com/. It scored 81 out of 100, a good result. 8 of 27 checks found something to fix, led by title tags (2), meta descriptions (2), headings (2); 7 checks passed. Most of the points went to title tags (−5), meta descriptions (−4), headings (−3). 12 checks found something the score does not count, listed as noted. 10 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: Medium4 medium, 3 low and 2 info findings. See the security findings ↓

Pages crawled
4
Assets fetched
57
Status
Completed
Checks with issues
8 of 27
CoverageComplete crawl

61 of 66 discovered URLs were fetched, 5 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 7 link destinations on other sites were checked.

  • Title tags2 issues
    2 of 2 pages have title issues. 2 noindex or canonicalized pages excluded.
    −5 points
  • Meta descriptions2 issues
    2 of 2 pages have meta description issues. 2 noindex or canonicalized pages excluded.
    −4 points
  • Headings2 issues
    2 of 2 pages have heading issues. 2 noindex or canonicalized pages excluded.
    −3 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites2 noted
    0 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 7 destinations checked.
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses1 noted
    1 URL did not return a 2xx response. 0 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 2 indexable pages have indexability warnings. 2 pages noindex by design.
  • Image alt text1 issue
    1 of 3 image references have no alt attribute. 2 use an empty alt (decorative), which is fine.
    −2 points
  • Heavy assets1 issue
    1 asset larger than 500 KB among 57 fetched assets.
    −0.6 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −1 points
  • Sitemap coverage1 issue
    2 sitemaps listing 2 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −1.5 points
  • Internal link counts2 noted
    Internal link counts for 4 pages; 2 worth a look.
  • Thin content1 issue
    1 of 2 pages have fewer than 200 words. 2 noindex or canonicalized pages excluded.
    −2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format1 noted
    1 of 4 page URLs are harder to read, share or cache than they need to be.
  • Canonicals2 noted
    2 of 4 pages have a canonical worth checking.
  • Robots directives4 noted
    4 pages carry a robots directive; 0 carry none.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure1 noted
    1 of 2 pages could use the title, heading and snippet space better. 2 noindex or canonicalized pages excluded.
  • Image weight and alt length1 noted
    1 image 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 validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 4 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookies1 noted
    1 cookie set by the site, 1 missing a protective flag; 14 response headers recorded across 61 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 4 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 Insights2 noted
    Mobile performance 61 on average across 2 pages; 2 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2874 sites, median 80%, average 79%

www.borhotlaw.com scores 81%, higher than 52% of the 2874 scanned sites. See the full ranking.

0751500%: 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%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 54 sites70%: 46 sites71%: 80 sites72%: 75 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 131 sites85%: 105 sites86%: 95 sites87%: 96 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 sites81% 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

Written from an earlier version of the analysis (rules v4). The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

There are several key issues to address for your website's SEO, including redirects, title tags, meta descriptions, headings, image alt text, and thin content. Implementing these fixes will improve indexability and user experience.

  1. 1

    Fix Redirects

    Why: Redirects can impact SEO and user experience.

    How: Update the redirect for your sitemap URL to direct it properly.

    Checks: redirects

  2. 2

    Add Title Tags

    Why: Missing or short title tags hurt visibility in search results.

    How: Create unique, descriptive title tags for both pages, ensuring they are over 30 characters.

    Checks: titles

  3. 3

    Implement Meta Descriptions

    Why: Meta descriptions influence click-through rates from search results.

    How: Write compelling meta descriptions for both pages.

    Checks: meta-descriptions

  4. 4

    Correct Headings Structure

    Why: Multiple H1s can confuse search engines and users.

    How: Limit each page to one H1 and use H2s appropriately.

    Checks: headings

  5. 5

    Add Image Alt Text

    Why: Alt text improves accessibility and image SEO.

    How: Provide a descriptive alt attribute for the image missing it.

    Checks: images-alt

  6. 6

    Enhance Thin Content

    Why: Thin content can struggle to rank well in search engines.

    How: Expand the 'Contact Us' page to include more relevant information, aiming for at least 200 words.

    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 has several security issues, primarily related to missing HTTP headers and cookie protection. Implementing recommended security headers will help prevent various attacks, including interception and clickjacking. Addressing these issues will improve the site's overall security posture.

  • 0 high
  • 4 medium
  • 3 low
  • 2 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=31536000; includeSubDomains'.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows loading resources from anywhere, increasing risk of cross-site scripting.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of this header risks clickjacking attacks through frame embedding.

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

    Evidence: Clickjacking protection

  4. 4

    Missing Cookie Flags for wp-login.phpMedium

    Why it matters: Cookies lack proper flags, making them vulnerable to theft or misuse.

    Fix: Set flags like 'HttpOnly', 'Secure', and 'SameSite=Strict' on the cookie.

    Evidence: Cookie flags

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: This allows browsers to infer types, which can lead to unintended execution of scripts.

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

    Evidence: MIME sniffing protection

  6. 6

    Server Banner Reveals Version InformationLow

    Why it matters: Exposing server version can help attackers find specific vulnerabilities.

    Fix: Hide server version by configuring server settings, such as setting 'ServerTokens Prod'.

    Evidence: Software version disclosure

  7. 7

    Use of Third-Party Scripts without SRILow

    Why it matters: Lack of Subresource Integrity means a compromised third-party script can alter behavior.

    Fix: Use Subresource Integrity attributes or implement a Content Security Policy to control script sources.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Without this policy, unused browser features remain accessible, increasing risk.

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

    Evidence: Permissions policy

  9. 9

    Sensitive Paths Revealed in robots.txtInfo

    Why it matters: Publicly listing paths can expose the site to probing and unauthorized access attempts.

    Fix: Consider securing the sensitive path with authentication instead of relying on robots.txt.

    Evidence: Sensitive paths in robots.txt

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://www.borhotlaw.com/ → no strict-transport-security
    • https://www.borhotlaw.com/wp-login.php → no strict-transport-security
    • https://www.borhotlaw.com/wp-login.php?action=lostpassword → no strict-transport-security
    • https://www.borhotlaw.com/contact-us/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 4 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://www.borhotlaw.com/ → no content-security-policy
    • https://www.borhotlaw.com/wp-login.php → no content-security-policy
    • https://www.borhotlaw.com/wp-login.php?action=lostpassword → no content-security-policy
    • https://www.borhotlaw.com/contact-us/ → no content-security-policy
  • FoundClickjacking protectionMedium

    2 of 4 HTML pages send 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://www.borhotlaw.com/ → no x-frame-options
    • https://www.borhotlaw.com/contact-us/ → 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://www.borhotlaw.com/ → no x-content-type-options
    • https://www.borhotlaw.com/wp-login.php → no x-content-type-options
    • https://www.borhotlaw.com/wp-login.php?action=lostpassword → no x-content-type-options
    • https://www.borhotlaw.com/contact-us/ → no x-content-type-options
  • FoundPermissions policyInfo

    2 of 4 HTML pages send 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://www.borhotlaw.com/wp-login.php → no permissions-policy
    • https://www.borhotlaw.com/wp-login.php?action=lostpassword → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: LiteSpeed (61 responses)
    • x-powered-by: PHP/7.4.33 (10 responses)
  • FoundCookie flagsMedium

    1 of 1 cookie are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • wordpress_test_cookie (set by https://www.borhotlaw.com/wp-login.php) lacks HttpOnly, SameSite
  • NoteThird-party scripts

    Scripts run from 1 other domain 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.)

    • www.googletagmanager.com (2 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /wp-admin/
7 checks passed
  • OKHTTPS

    All 4 crawled pages were served over HTTPS.

  • OKReferrer policy

    A referrer policy is set through a <meta name="referrer"> tag.

  • OKMixed content

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

  • OKForms over HTTPS

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

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 www.borhotlaw.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 www.borhotlaw.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.borhotlaw.com?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming www.borhotlaw.com. Removal needs no account and no proof of purchase.