Scanned sites / spokelaw.com

SEO report for spokelaw.com DR 2

The latest Site Spider scan of spokelaw.com, with 1 scan on record. Each scan is at its own address, for example /domain/spokelaw-com/2026-10-02-1401.

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

Latest scan

Scanned 2026-10-02 14:01:55 UTC, finished 2026-10-02 14:30:46 UTC. Found on page 4 of brave web search results

Site: https://spokelaw.com/

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

75/ 100Good

On October 2, 2026 the Site Spider crawled 16 pages and 51 assets of spokelaw.com, starting from https://spokelaw.com/. It scored 75 out of 100, a good result. 7 of 27 checks found something to fix, led by title tags (16), meta descriptions (16), links to other sites (10); 12 checks passed. Most of the points went to title tags (−10), meta descriptions (−8), links to other sites (−4). 8 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: Medium1 medium, 1 low and 1 info findings. See the security findings ↓

Pages crawled
16
Assets fetched
51
Status
Completed
Checks with issues
7 of 27
CoverageComplete crawl

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

  • Title tags16 issues
    16 of 16 pages have title issues.
    −10 points
  • Meta descriptions16 issues
    16 of 16 pages have meta description issues.
    −8 points
  • HeadingsOK
    0 of 16 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites10 issues
    10 destinations answered with an error, 20 could not be determined (timeouts, rate limits or refusals), of 32 destinations checked.
    −4 points
  • 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.
  • Indexability2 issues
    2 of 16 indexable pages have indexability warnings.
    −1.3 points
  • Image alt textOK
    0 of 48 image references have no alt attribute.
  • Heavy assetsOK
    0 assets larger than 500 KB among 51 fetched assets.
  • Orphan pages2 issues
    2 pages have no internal links pointing at them.
    −0.5 points
  • Sitemap coverage2 issues
    5 sitemaps listing 16 URLs: 0 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 16 pages; none is a dead end or buried.
  • Thin content1 issue
    1 of 16 pages have fewer than 200 words.
    −0.5 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 16 page URLs are plain lowercase addresses without parameters.
  • Canonicals2 noted
    2 of 16 pages have a canonical worth checking.
  • Robots directives16 noted
    16 pages carry a robots directive; 0 carry none.
  • Anchor text21 noted
    21 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure16 noted
    16 of 16 pages could use the title, heading and snippet space better.
  • 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 16 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 cookiesOK
    0 cookies set by the site; 16 response headers recorded across 67 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 16 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 Insights5 noted
    Mobile performance 66 on average across 5 pages; 5 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 site sits among all scanned sites

2909 sites, median 80%, average 79%

spokelaw.com scores 75%, higher than 29% of the 2909 scanned sites. See the full ranking.

0761520%: 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%: 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%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 134 sites79%: 112 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 131 sites85%: 106 sites86%: 97 sites87%: 95 sites88%: 82 sites89%: 77 sites90%: 57 sites91%: 61 sites92%: 44 sites93%: 32 sites94%: 25 sites95%: 17 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites75% 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.

The crawl found several issues including missing titles and meta descriptions, indexability warnings, and orphan pages. Prioritizing these fixes will improve your site's SEO significantly.

  1. 1

    Add Title Tags for All Pages

    Why: All pages have title issues, impacting search visibility.

    How: Create unique title tags for each page, ensuring they accurately describe the content.

    Checks: titles

  2. 2

    Implement Meta Descriptions

    Why: All pages lack meta descriptions, which are crucial for CTR.

    How: Write concise and relevant meta descriptions for each page.

    Checks: meta-descriptions

  3. 3

    Resolve Indexability Warnings

    Why: Two pages lack canonical tags, potentially causing duplicate content issues.

    How: Check if the pages are duplicates and set a canonical tag if necessary.

    Checks: indexability

  4. 4

    Link to Orphan Pages

    Why: Orphan pages are not indexed well due to lack of internal links.

    How: Add internal links from other relevant pages to the orphan pages.

    Checks: orphan-pages

  5. 5

    Improve Sitemap Coverage

    Why: Two URLs are only reachable via sitemap and may hinder SEO.

    How: Ensure these URLs have internal links pointing to them.

    Checks: sitemap-coverage

  6. 6

    Enhance Thin Content

    Why: One page has fewer than 200 words, which can affect its ranking.

    How: Add more relevant content to this page to meet word count standards.

    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 security review identified critical issues regarding missing security headers and server version disclosure. Implementing a Content Security Policy and Permissions Policy is essential to mitigate risks associated with script injections and unauthorized feature access. Immediate action is needed to improve the site's security posture.

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

    Missing Content Security PolicyMedium

    Why it matters: Without a CSP header, the site is vulnerable to content injection attacks.

    Fix: Add a Content-Security-Policy header to all responses: `Content-Security-Policy: default-src 'self';`

    Evidence: Content Security Policy

  2. 2

    Server Version DisclosureLow

    Why it matters: Revealing the server version may help attackers exploit known vulnerabilities.

    Fix: Configure the server to hide version information: set the `server_tokens` directive to `off` in your server configuration.

    Evidence: Software version disclosure

  3. 3

    Missing Permissions PolicyInfo

    Why it matters: No Permissions-Policy header means the site may inadvertently allow dangerous features.

    Fix: Add a Permissions-Policy header to all responses: `Permissions-Policy: geolocation=(), microphone=(), camera=();`

    Evidence: Permissions policy

What the checks found

  • FoundContent Security PolicyMedium

    None of the 16 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://spokelaw.com/ → no content-security-policy
    • https://spokelaw.com/services/ → no content-security-policy
    • https://spokelaw.com/people/ → no content-security-policy
    • https://spokelaw.com/contact/ → no content-security-policy
    • https://spokelaw.com/conceptual-blog-post/ → no content-security-policy
    • https://spokelaw.com/nature-blog-post/ → no content-security-policy
    • https://spokelaw.com/illustrative-blog-post/ → no content-security-policy
    • https://spokelaw.com/office-workers-blog-post/ → no content-security-policy
    • https://spokelaw.com/objects-blog-post/ → no content-security-policy
    • https://spokelaw.com/social-casual-blog-post/ → no content-security-policy
    • https://spokelaw.com/work-in-action-blog-post/ → no content-security-policy
    • https://spokelaw.com/customer-in-action-blog-post/ → no content-security-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://spokelaw.com/ → no permissions-policy
    • https://spokelaw.com/services/ → no permissions-policy
    • https://spokelaw.com/people/ → no permissions-policy
    • https://spokelaw.com/contact/ → no permissions-policy
    • https://spokelaw.com/conceptual-blog-post/ → no permissions-policy
    • https://spokelaw.com/nature-blog-post/ → no permissions-policy
    • https://spokelaw.com/illustrative-blog-post/ → no permissions-policy
    • https://spokelaw.com/office-workers-blog-post/ → no permissions-policy
    • https://spokelaw.com/objects-blog-post/ → no permissions-policy
    • https://spokelaw.com/social-casual-blog-post/ → no permissions-policy
    • https://spokelaw.com/work-in-action-blog-post/ → no permissions-policy
    • https://spokelaw.com/customer-in-action-blog-post/ → 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: openresty/1.29.2.3 (67 responses)
  • 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/
10 checks passed, 2 not applicable
  • OKHTTPS

    All 16 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 16 HTML pages.

  • OKClickjacking protection

    x-frame-options is set on all 16 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 16 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 16 HTML pages.

  • OKMixed content

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

  • OKForms over HTTPS

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

  • 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

    The sampled pages load no scripts from other domains.

  • Not applicableCookie flags

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

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

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.

Earlier scans of spokelaw.com

No other scans of this site yet.

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

Own spokelaw.com?