Scanned sites / wagilbert.com / 2026-09-12-2207

wagilbert.com scan from 2026-09-12 22:07:07 UTC DR 9

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

Scan 2026-09-12-2207

Scanned 2026-09-12 22:07:07 UTC, finished 2026-09-12 23:36:44 UTC. Found on page 5 of brave web search results

Site: https://wagilbert.com/

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

83/ 100Good

On September 12, 2026 the Site Spider crawled 609 pages and 1000 assets of wagilbert.com, starting from https://wagilbert.com/. It scored 83 out of 100, a good result. 8 of 26 checks found something to fix, led by heavy assets (52), sitemap coverage (573), meta descriptions (196); 10 checks passed. Most of the points went to heavy assets (−6), sitemap coverage (−5.7), meta descriptions (−2.6). 8 checks found something the score does not count, listed as noted. 11 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: Medium2 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
609
Assets fetched
1000
Status
Completed
Checks with issues
8 of 26
CoverageJob finished, partial coverage

1,609 of 1,609 discovered URLs were fetched, 2,648 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 111 link destinations on other sites were checked.

  • Title tags133 issues
    133 of 573 pages have title issues. 26 noindex or canonicalized pages excluded.
    −2.2 points
  • Meta descriptions196 issues
    196 of 573 pages have meta description issues. 26 noindex or canonicalized pages excluded.
    −2.6 points
  • Headings3 issues
    3 of 573 pages have heading issues. 26 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites5 issues
    5 destinations answered with an error, 34 could not be determined (timeouts, rate limits or refusals), of 111 destinations checked.
    −0.3 points
  • Redirects10 issues
    11 redirecting URLs, 2 of them chained.
    −0.1 points
  • Non-200 responses11 noted
    11 URLs did not return a 2xx response. 10 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.
  • Indexability25 issues
    25 of 597 indexable pages have indexability warnings. 2 pages noindex by design.
    −0.4 points
  • Image alt textOK
    0 of 5431 image references have no alt attribute. 66 use an empty alt (decorative), which is fine.
  • Heavy assets52 issues
    52 assets larger than 500 KB among 1000 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage573 issues
    1 sitemap listing 0 URLs: 573 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.7 points
  • Internal link counts20 noted
    Internal link counts for 500 pages; 20 worth a look.
  • Thin contentOK
    0 of 573 pages have fewer than 200 words. 26 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format3 noted
    3 of 609 page URLs are harder to read, share or cache than they need to be.
  • Canonicals26 noted
    26 of 599 pages have a canonical worth checking.
  • Robots directives599 noted
    599 pages carry a robots directive; 0 carry none.
  • Anchor text114 noted
    114 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure256 noted
    256 of 573 pages could use the title, heading and snippet space better. 26 noindex or canonicalized pages excluded.
  • Image weight and alt length619 noted
    103 images over 100 KB; 516 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 599 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; 14 response headers recorded across 1609 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 599 pages; 517 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.
  • 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

2347 sites, median 79%, average 78%

wagilbert.com scores 83%, higher than 64% of the 2347 scanned sites. See the full ranking.

0581150%: 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%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 7 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 71 sites73%: 70 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 107 sites79%: 85 sites80%: 107 sites81%: 105 sites82%: 115 sites83%: 102 sites84%: 106 sites85%: 88 sites86%: 71 sites87%: 74 sites88%: 59 sites89%: 66 sites90%: 35 sites91%: 47 sites92%: 38 sites93%: 24 sites94%: 17 sites95%: 12 sites96%: 12 sites97%: 12 sites98%: 5 sites99%: 2 sites100%: 68 sites83% 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. 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 site has several SEO issues that need fixing, including redirects, non-200 responses, title and meta description problems, heading issues, indexability warnings, and sitemap coverage errors. Addressing these will improve site performance and organic visibility.

  1. 1

    Fix Redirects

    Why: Chained redirects can slow down page loading and negatively impact SEO.

    How: Identify and consolidate chained redirects to direct users to the final destination in one step.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: URLs not returning a 2xx response can harm user experience and search indexing.

    How: Update or remove the non-200 status URLs to ensure they return a valid response.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Improper title length can decrease click-through rates in search results.

    How: Revise the titles to be 60 characters or less, ensuring they accurately describe the page.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Missing or duplicate meta descriptions can lead to lower search visibility.

    How: Add unique meta descriptions that summarize each page, making them appealing for search results.

    Checks: meta-descriptions

  5. 5

    Fix Heading Structure

    Why: Multiple H1 tags can confuse search engines and dilute page relevance.

    How: Ensure each page has only one H1 tag and organize content with appropriate H2 and H3 tags.

    Checks: headings

  6. 6

    Update Sitemap Coverage

    Why: Pages not listed in the sitemap reduce their chance of being indexed.

    How: Review and regenerate the sitemap to include all indexable pages, ensuring it is submitted to search engines.

    Checks: sitemap-coverage

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 wagilbert.com lacks key security measures, including HTTP Strict Transport Security and proper content-type options, which can expose it to threats. Additionally, sensitive credentials are present in the code, which could lead to unauthorized access. Immediate remediation is recommended.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, an attacker can intercept the first request when the site is accessed without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Exposed Google API KeyMedium

    Why it matters: A Google API key is publicly accessible without restrictions, increasing the risk of abuse.

    Fix: Restrict the API key in the Google Cloud console to use HTTP referrers that specify your domain.

    Evidence: Keys and secrets in page code

  3. 3

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may execute files as scripts based on their contents, which can lead to exploitation.

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

    Evidence: MIME sniffing protection

  4. 4

    Third-Party Scripts Without Subresource Integrity (SRI)Low

    Why it matters: Using third-party scripts without SRI means a compromise of these external hosts could affect your site.

    Fix: Consider adding SRI to the scripts or implement a Content-Security-Policy that specifies trusted hosts.

    Evidence: Third-party scripts

  5. 5

    Sensitive Path in robots.txtInfo

    Why it matters: The robots.txt file reveals a private directory which could assist potential attackers in probing the site.

    Fix: Implement proper access control for sensitive paths like /wp-admin/ 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://wagilbert.com/ → no strict-transport-security
    • https://wagilbert.com/about/ → no strict-transport-security
    • https://wagilbert.com/about/why-us/ → no strict-transport-security
    • https://wagilbert.com/about/bill-gilbert/ → no strict-transport-security
    • https://wagilbert.com/about/ashley-richards/ → no strict-transport-security
    • https://wagilbert.com/about/beth-bollinger/ → no strict-transport-security
    • https://wagilbert.com/about/michael-bodey/ → no strict-transport-security
    • https://wagilbert.com/awards-and-press/ → no strict-transport-security
    • https://wagilbert.com/testimonials/ → no strict-transport-security
    • https://wagilbert.com/washington-amazon-delivery-truck-accident/ → no strict-transport-security
    • https://wagilbert.com/seattle-washington-amazon-delivery-truck-driver-accident-lawyer/ → no strict-transport-security
    • https://wagilbert.com/spokane-washington-car-accident-lawyer/ → no strict-transport-security
  • 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://wagilbert.com/ → no x-content-type-options
    • https://wagilbert.com/about/ → no x-content-type-options
    • https://wagilbert.com/about/why-us/ → no x-content-type-options
    • https://wagilbert.com/about/bill-gilbert/ → no x-content-type-options
    • https://wagilbert.com/about/ashley-richards/ → no x-content-type-options
    • https://wagilbert.com/about/beth-bollinger/ → no x-content-type-options
    • https://wagilbert.com/about/michael-bodey/ → no x-content-type-options
    • https://wagilbert.com/awards-and-press/ → no x-content-type-options
    • https://wagilbert.com/testimonials/ → no x-content-type-options
    • https://wagilbert.com/washington-amazon-delivery-truck-accident/ → no x-content-type-options
    • https://wagilbert.com/seattle-washington-amazon-delivery-truck-driver-accident-lawyer/ → no x-content-type-options
    • https://wagilbert.com/spokane-washington-car-accident-lawyer/ → no x-content-type-options
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…wU (39 chars) in https://wagilbert.com/washington-unnecessary-surgery-lawyers/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • 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 (24 script tags)
    • www.google.com (1 script tag)
  • 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, 4 not applicable
  • OKHTTPS

    All 599 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKClickjacking protection

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

  • 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

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

  • OKExposed files and listings

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

  • Not applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

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

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

Own wagilbert.com?