Scanned sites / runyowa.com / 2026-11-02-1402

runyowa.com scan from 2026-11-02 14:02:13 UTC DR 2

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

Scan 2026-11-02-1402

Scanned 2026-11-02 14:02:13 UTC, finished 2026-11-02 15:47:23 UTC. Found on page 3 of brave web search results

Site: https://runyowa.com/

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

80/ 100Good

On November 2, 2026 the Site Spider crawled 286 pages and 283 assets of runyowa.com, starting from https://runyowa.com/. It scored 80 out of 100, a good result. 11 of 33 checks found something to fix, led by meta descriptions (232), heavy assets (10), title tags (109); 10 checks passed. Most of the points went to meta descriptions (−6.7), heavy assets (−6), title tags (−3.9). 12 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, 4 low and 1 info findings. See the security findings ↓

Pages crawled
286
Assets fetched
283
Status
Completed
Checks with issues
11 of 33
CoverageComplete crawl

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

  • Title tags109 issues
    109 of 257 pages have title issues. 22 noindex or canonicalized pages excluded.
    −3.9 points
  • Meta descriptions232 issues
    232 of 257 pages have meta description issues. 22 noindex or canonicalized pages excluded.
    −6.7 points
  • Headings1 issue
    1 of 257 pages have heading issues. 22 noindex or canonicalized pages excluded.
  • Broken links1 issue
    2 internal links point at 1 broken URL.
    −0.1 points
  • Links to other sites4 issues
    4 destinations answered with an error, 21 could not be determined (timeouts, rate limits or refusals), of 47 destinations checked.
    −0.6 points
  • Redirects3 issues
    4 redirecting URLs, 0 of them chained.
  • Non-200 responses3 issues
    7 URLs did not return a 2xx response. 7 of them are pages, 3 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 257 indexable pages have indexability warnings. 22 pages noindex by design.
  • Image alt textOK
    0 of 1661 image references have no alt attribute. 234 use an empty alt (decorative), which is fine.
  • Heavy assets10 issues
    10 assets larger than 500 KB among 283 fetched assets.
    −6 points
  • Orphan pages17 issues
    17 pages have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage122 issues
    7 sitemaps listing 156 URLs: 103 crawled pages missing, 2 listed URLs broken or redirecting, 17 reachable only via the sitemap.
    −2.6 points
  • Internal link counts31 noted
    Internal link counts for 279 pages; 31 worth a look.
  • Thin content1 issue
    1 of 257 pages have fewer than 200 words. 22 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format6 noted
    6 of 286 page URLs are harder to read, share or cache than they need to be.
  • CanonicalsOK
    0 of 279 pages have a canonical worth checking.
  • Robots directives279 noted
    279 pages carry a robots directive; 0 carry none.
  • Anchor text106 noted
    106 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure24 noted
    24 of 257 pages could use the title, heading and snippet space better. 22 noindex or canonicalized pages excluded.
  • Image weight and alt length27 noted
    27 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies1 noted
    1 URL answered in a way worth looking at.
  • HTML and head validationOK
    All 279 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data278 noted
    279 of 257 indexable pages carry structured data: BreadcrumbList (279), ListItem (279), Organization (279), WebSite (279), WebPage (156). 278 pages with errors a rich result would fail on.
  • Near duplicates6 noted
    6 pages in 3 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 279 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 positions18 noted
    18 of 240 linked pages are linked only from the template, never from another page's content.
  • Pagination5 noted
    9 pages in pagination sequences; 5 with problems.
  • Headers and cookiesOK
    0 cookies set by the site; 13 response headers recorded across 569 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 279 pages; 245 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.
  • Spelling44 noted
    44 words an English dictionary does not know, on 68 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2609 sites, median 80%, average 78%

runyowa.com scores 80%, higher than 50% of the 2609 scanned sites. See the full ranking.

0601190%: 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%: 1 site45%: 5 sites46%: 5 sites47%: 5 sites48%: 5 sites49%: 8 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 10 sites55%: 10 sites56%: 7 sites57%: 15 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 20 sites65%: 31 sites66%: 39 sites67%: 39 sites68%: 37 sites69%: 48 sites70%: 48 sites71%: 74 sites72%: 73 sites73%: 77 sites74%: 76 sites75%: 84 sites76%: 95 sites77%: 106 sites78%: 117 sites79%: 106 sites80%: 119 sites81%: 115 sites82%: 118 sites83%: 117 sites84%: 119 sites85%: 97 sites86%: 87 sites87%: 85 sites88%: 70 sites89%: 71 sites90%: 47 sites91%: 57 sites92%: 40 sites93%: 28 sites94%: 21 sites95%: 14 sites96%: 16 sites97%: 15 sites98%: 7 sites99%: 2 sites100%: 69 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

There are several areas for improvement on your site, primarily around broken links, redirects, meta descriptions, and internal linking. Addressing these will enhance user experience and SEO performance.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and SEO.

    How: Update or remove the internal links pointing to broken URLs.

    Checks: broken-links

  2. 2

    Correct Redirects

    Why: Redirects can slow down site performance and confuse users.

    How: Eliminate unnecessary redirects to improve loading times and user navigation.

    Checks: redirects

  3. 3

    Update Meta Descriptions

    Why: Many pages lack meta descriptions, reducing visibility in search results.

    How: Create and add unique meta descriptions to 119 pages.

    Evidence: 119 pages have no meta description at all.

    119 pages affected

    Checks: meta-descriptions

  4. 4

    Enhance Internal Linking

    Why: Orphan pages are harder to discover and rank.

    How: Add internal links to 17 orphan pages to improve navigation and indexing.

    Checks: orphan-pages

  5. 5

    Address Non-200 Responses

    Why: Seven URLs returned non-200 status codes, affecting accessibility.

    How: Identify and resolve issues with the URLs returning errors.

    Checks: status-codes

  6. 6

    Optimize Heavy Assets

    Why: Large assets can slow down page loading.

    How: Reduce the size of large images and files where applicable.

    Evidence: 1.7 MB of image, loaded by 2 pages, so every visitor to any of them downloads it.

    2 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    Checks: heavy-assets

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 runyowa.com has several security headers missing, making it more vulnerable to certain attacks. Addressing these issues will improve the site's defenses against malicious actions and protect user data.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Lack of HSTS allows interception of requests from users typing the site address without HTTPS.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Absence of CSP means browser restrictions on content loading are not enforced, increasing risk of XSS.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without X-Frame-Options, the site is vulnerable to clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-OptionsLow

    Why it matters: The absence of this header allows browsers to execute files based on content type rather than declared type.

    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 URLs get exposed when users navigate away from the site.

    Fix: Add the header: Referrer-Policy: no-referrer-when-downgrade.

    Evidence: Referrer policy

  6. 6

    Server Version DisclosureLow

    Why it matters: Revealing server details can aid attackers in finding exploits.

    Fix: Remove or modify headers to hide exact versions; for Apache, consider setting ServerTokens Prod.

    Evidence: Software version disclosure

  7. 7

    Mixed ContentLow

    Why it matters: Loading resources over HTTP on HTTPS pages can lead to security issues.

    Fix: Ensure all resources are loaded over HTTPS or use relative URLs.

    Evidence: Mixed content

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Absence of permissions-policy may expose features unnecessarily, increasing potential impacts of malicious scripts.

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

    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://runyowa.com/ → no strict-transport-security
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no strict-transport-security
    • https://runyowa.com/civil-litigation/ → no strict-transport-security
    • https://runyowa.com/automobile-accidents/ → no strict-transport-security
    • https://runyowa.com/wrongful-death/ → no strict-transport-security
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no strict-transport-security
    • https://runyowa.com/administrative-law-and-tribunals/ → no strict-transport-security
    • https://runyowa.com/privacy-breaches/ → no strict-transport-security
    • https://runyowa.com/civil-fraud/ → no strict-transport-security
    • https://runyowa.com/contract-dispute/ → no strict-transport-security
    • https://runyowa.com/insurance-disputes/ → no strict-transport-security
    • https://runyowa.com/professional-discipline/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 279 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://runyowa.com/ → no content-security-policy
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no content-security-policy
    • https://runyowa.com/civil-litigation/ → no content-security-policy
    • https://runyowa.com/automobile-accidents/ → no content-security-policy
    • https://runyowa.com/wrongful-death/ → no content-security-policy
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no content-security-policy
    • https://runyowa.com/administrative-law-and-tribunals/ → no content-security-policy
    • https://runyowa.com/privacy-breaches/ → no content-security-policy
    • https://runyowa.com/civil-fraud/ → no content-security-policy
    • https://runyowa.com/contract-dispute/ → no content-security-policy
    • https://runyowa.com/insurance-disputes/ → no content-security-policy
    • https://runyowa.com/professional-discipline/ → 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://runyowa.com/ → no x-frame-options
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no x-frame-options
    • https://runyowa.com/civil-litigation/ → no x-frame-options
    • https://runyowa.com/automobile-accidents/ → no x-frame-options
    • https://runyowa.com/wrongful-death/ → no x-frame-options
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no x-frame-options
    • https://runyowa.com/administrative-law-and-tribunals/ → no x-frame-options
    • https://runyowa.com/privacy-breaches/ → no x-frame-options
    • https://runyowa.com/civil-fraud/ → no x-frame-options
    • https://runyowa.com/contract-dispute/ → no x-frame-options
    • https://runyowa.com/insurance-disputes/ → no x-frame-options
    • https://runyowa.com/professional-discipline/ → 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://runyowa.com/ → no x-content-type-options
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no x-content-type-options
    • https://runyowa.com/civil-litigation/ → no x-content-type-options
    • https://runyowa.com/automobile-accidents/ → no x-content-type-options
    • https://runyowa.com/wrongful-death/ → no x-content-type-options
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no x-content-type-options
    • https://runyowa.com/administrative-law-and-tribunals/ → no x-content-type-options
    • https://runyowa.com/privacy-breaches/ → no x-content-type-options
    • https://runyowa.com/civil-fraud/ → no x-content-type-options
    • https://runyowa.com/contract-dispute/ → no x-content-type-options
    • https://runyowa.com/insurance-disputes/ → no x-content-type-options
    • https://runyowa.com/professional-discipline/ → 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://runyowa.com/ → no referrer-policy
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no referrer-policy
    • https://runyowa.com/civil-litigation/ → no referrer-policy
    • https://runyowa.com/automobile-accidents/ → no referrer-policy
    • https://runyowa.com/wrongful-death/ → no referrer-policy
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no referrer-policy
    • https://runyowa.com/administrative-law-and-tribunals/ → no referrer-policy
    • https://runyowa.com/privacy-breaches/ → no referrer-policy
    • https://runyowa.com/civil-fraud/ → no referrer-policy
    • https://runyowa.com/contract-dispute/ → no referrer-policy
    • https://runyowa.com/insurance-disputes/ → no referrer-policy
    • https://runyowa.com/professional-discipline/ → 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://runyowa.com/ → no permissions-policy
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no permissions-policy
    • https://runyowa.com/civil-litigation/ → no permissions-policy
    • https://runyowa.com/automobile-accidents/ → no permissions-policy
    • https://runyowa.com/wrongful-death/ → no permissions-policy
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no permissions-policy
    • https://runyowa.com/administrative-law-and-tribunals/ → no permissions-policy
    • https://runyowa.com/privacy-breaches/ → no permissions-policy
    • https://runyowa.com/civil-fraud/ → no permissions-policy
    • https://runyowa.com/contract-dispute/ → no permissions-policy
    • https://runyowa.com/insurance-disputes/ → no permissions-policy
    • https://runyowa.com/professional-discipline/ → 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: Apache (569 responses)
    • x-powered-by: PHP/8.1.34 (293 responses)
  • FoundMixed contentLow

    2 resources on HTTPS pages are loaded over plain HTTP.

    • https://runyowa.com/elementor-landing-page-2209/ loads image http://buinfinitytech.com/law/wp-content/uploads/2023/03/Screenshot-2023-03-16-135326.jpg
    • https://runyowa.com/elementor-landing-page-2209/ loads image http://buinfinitytech.com/law/wp-content/uploads/2023/03/Screenshot-2023-03-16-135326.jpg
  • NoteThird-party scripts

    Scripts run from 2 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.)

    • www.googletagmanager.com (40 script tags)
    • www.google.com (15 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/
5 checks passed, 1 not applicable
  • OKHTTPS

    All 279 crawled pages were served over HTTPS.

  • OKForms over HTTPS

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

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

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

Own runyowa.com?