Scanned sites / www.crownautobody.ca / 2026-09-18-0013

www.crownautobody.ca scan from 9/18/2026, 12:13:41 AM

A newer scan exists. See the latest report for www.crownautobody.ca.

Scan 2026-09-18-0013

Scanned 9/18/2026, 12:13:41 AM, finished 9/18/2026, 12:21:28 AM. Found with openstreetmap overpass

Site: https://www.crownautobody.ca/

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

51/ 100Needs work

On September 18, 2026 the Site Spider crawled 131 pages and 483 assets of www.crownautobody.ca, starting from https://www.crownautobody.ca/. It scored 51 out of 100, a result that needs work. 9 of 14 checks found something to fix, led by broken links (65), non-200 responses (65), meta descriptions (49); 5 checks passed. 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 1 info findings. See the security findings ↓

Pages crawled
131
Assets fetched
483
Status
Completed
Checks with issues
9 of 14
  • Title tags22 issues
    22 of 59 pages have title issues. 4 noindex or canonicalized pages excluded.
  • Meta descriptions49 issues
    49 of 59 pages have meta description issues. 4 noindex or canonicalized pages excluded.
  • Headings8 issues
    8 of 59 pages have heading issues. 4 noindex or canonicalized pages excluded.
  • Broken links65 issues
    65 internal links point at 65 broken URLs.
  • Redirects3 issues
    4 redirecting URLs, 0 of them chained.
  • Non-200 responses65 issues
    69 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 59 indexable pages have indexability warnings. 4 pages noindex by design.
  • Image alt textOK
    0 of 554 image references have no alt attribute. 248 use an empty alt (decorative), which is fine.
  • Heavy assets13 issues
    13 assets larger than 500 KB among the 100 heaviest.
  • Orphan pages16 issues
    16 pages have no internal links pointing at them.
  • Sitemap coverage16 issues
    4 sitemaps listing 59 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 16 reachable only via the sitemap.
  • Thin contentOK
    0 of 59 pages have fewer than 200 words. 4 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1076 sites, median 82%, average 80%

www.crownautobody.ca scores 51%, higher than 1% of the 1076 scanned sites. See the full ranking.

028550%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 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%: 1 site36%: 1 site37%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 1 site47%: 0 sites48%: 0 sites49%: 0 sites50%: 3 sites51%: 4 sites52%: 1 site53%: 1 site54%: 2 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 6 sites59%: 3 sites60%: 5 sites61%: 8 sites62%: 12 sites63%: 4 sites64%: 8 sites65%: 9 sites66%: 7 sites67%: 15 sites68%: 27 sites69%: 12 sites70%: 22 sites71%: 21 sites72%: 23 sites73%: 24 sites74%: 30 sites75%: 27 sites76%: 37 sites77%: 36 sites78%: 33 sites79%: 30 sites80%: 41 sites81%: 52 sites82%: 50 sites83%: 45 sites84%: 51 sites85%: 47 sites86%: 45 sites87%: 47 sites88%: 55 sites89%: 38 sites90%: 51 sites91%: 36 sites92%: 26 sites93%: 17 sites94%: 16 sites95%: 8 sites96%: 9 sites97%: 4 sites98%: 2 sites99%: 1 site100%: 12 sites51% 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 website has significant technical issues impacting SEO, including broken links and missing meta elements. Prioritize fixing these for better performance.

  1. 1

    Fix Broken Links

    Why: Eliminating broken links improves user experience and ranking.

    How: Update or remove the 65 internal links that point to broken URLs listed in the crawl report.

    Checks: broken-links

  2. 2

    Address Non-200 Responses

    Why: Resolving non-200 URLs ensures all pages are accessible for users and search engines.

    How: Redirect or correct the 69 URLs that did not return a 2xx response.

    Checks: status-codes

  3. 3

    Revise Title Tags

    Why: Improving title tags enhances click-through rates from search results.

    How: Shorten the titles on 22 affected pages to be under 60 characters.

    Checks: titles

  4. 4

    Update Meta Descriptions

    Why: Optimized meta descriptions improve search visibility and click rates.

    How: Add or revise descriptions for the 49 pages with issues, ensuring they are under 160 characters.

    Checks: meta-descriptions

  5. 5

    Fix Heading Issues

    Why: Correcting heading tags aids in content structure and SEO.

    How: Ensure all pages have a single H1 tag, particularly for the 8 pages currently missing one.

    Checks: headings

  6. 6

    Resolve Orphan Pages

    Why: Linking orphan pages helps with indexing and user navigation.

    How: Create internal links to the 16 orphan pages to ensure they are accessible.

    Checks: orphan-pages

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

This review outlines security vulnerabilities in your website which could lead to exploitation or data leakage. Key issues include the absence of essential response headers and the use of obsolete libraries. Implementing the recommended security headers and updating libraries is crucial.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users may be intercepted when accessing your site without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    No Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows unauthorized script execution, risking data breaches.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without this header, your pages can be embedded in frames, increasing clickjacking risks.

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

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript LibraryMedium

    Why it matters: jQuery 1.9.1 has known vulnerabilities that could be exploited, affecting site security.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-OptionsLow

    Why it matters: Absence of this header can lead to MIME sniffing and potentially dangerous script execution.

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

    Evidence: MIME sniffing protection

  6. 6

    No Referrer PolicyLow

    Why it matters: Without a referrer policy, sensitive URL information may be leaked to other sites.

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

    Evidence: Referrer policy

  7. 7

    Server Banner Discloses VersionLow

    Why it matters: Exposing software versions can help attackers exploit known vulnerabilities.

    Fix: Modify your server configuration to hide version details and add: Server: your-server-name.

    Evidence: Software version disclosure

  8. 8

    No Permissions PolicyInfo

    Why it matters: Lacking this policy can lead to unnecessary access to devices (camera, microphone) by malicious scripts.

    Fix: Add the header: Permissions-Policy: geometries=();

    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://www.crownautobody.ca/ → no strict-transport-security
    • https://www.crownautobody.ca/about-us/ → no strict-transport-security
    • https://www.crownautobody.ca/why-us/ → no strict-transport-security
    • https://www.crownautobody.ca/services/ → no strict-transport-security
    • https://www.crownautobody.ca/process/ → no strict-transport-security
    • https://www.crownautobody.ca/blogs/ → no strict-transport-security
    • https://www.crownautobody.ca/faq/ → no strict-transport-security
    • https://www.crownautobody.ca/mpi-direct-repair/ → no strict-transport-security
    • https://www.crownautobody.ca/car-rental/ → no strict-transport-security
    • https://www.crownautobody.ca/glass-repair/ → no strict-transport-security
    • https://www.crownautobody.ca/towing/ → no strict-transport-security
    • https://www.crownautobody.ca/in-case-of-accident/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 63 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.crownautobody.ca/ → no content-security-policy
    • https://www.crownautobody.ca/about-us/ → no content-security-policy
    • https://www.crownautobody.ca/why-us/ → no content-security-policy
    • https://www.crownautobody.ca/services/ → no content-security-policy
    • https://www.crownautobody.ca/process/ → no content-security-policy
    • https://www.crownautobody.ca/blogs/ → no content-security-policy
    • https://www.crownautobody.ca/faq/ → no content-security-policy
    • https://www.crownautobody.ca/mpi-direct-repair/ → no content-security-policy
    • https://www.crownautobody.ca/car-rental/ → no content-security-policy
    • https://www.crownautobody.ca/glass-repair/ → no content-security-policy
    • https://www.crownautobody.ca/towing/ → no content-security-policy
    • https://www.crownautobody.ca/in-case-of-accident/ → 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://www.crownautobody.ca/ → no x-frame-options
    • https://www.crownautobody.ca/about-us/ → no x-frame-options
    • https://www.crownautobody.ca/why-us/ → no x-frame-options
    • https://www.crownautobody.ca/services/ → no x-frame-options
    • https://www.crownautobody.ca/process/ → no x-frame-options
    • https://www.crownautobody.ca/blogs/ → no x-frame-options
    • https://www.crownautobody.ca/faq/ → no x-frame-options
    • https://www.crownautobody.ca/mpi-direct-repair/ → no x-frame-options
    • https://www.crownautobody.ca/car-rental/ → no x-frame-options
    • https://www.crownautobody.ca/glass-repair/ → no x-frame-options
    • https://www.crownautobody.ca/towing/ → no x-frame-options
    • https://www.crownautobody.ca/in-case-of-accident/ → 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.crownautobody.ca/ → no x-content-type-options
    • https://www.crownautobody.ca/about-us/ → no x-content-type-options
    • https://www.crownautobody.ca/why-us/ → no x-content-type-options
    • https://www.crownautobody.ca/services/ → no x-content-type-options
    • https://www.crownautobody.ca/process/ → no x-content-type-options
    • https://www.crownautobody.ca/blogs/ → no x-content-type-options
    • https://www.crownautobody.ca/faq/ → no x-content-type-options
    • https://www.crownautobody.ca/mpi-direct-repair/ → no x-content-type-options
    • https://www.crownautobody.ca/car-rental/ → no x-content-type-options
    • https://www.crownautobody.ca/glass-repair/ → no x-content-type-options
    • https://www.crownautobody.ca/towing/ → no x-content-type-options
    • https://www.crownautobody.ca/in-case-of-accident/ → 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://www.crownautobody.ca/ → no referrer-policy
    • https://www.crownautobody.ca/about-us/ → no referrer-policy
    • https://www.crownautobody.ca/why-us/ → no referrer-policy
    • https://www.crownautobody.ca/services/ → no referrer-policy
    • https://www.crownautobody.ca/process/ → no referrer-policy
    • https://www.crownautobody.ca/blogs/ → no referrer-policy
    • https://www.crownautobody.ca/faq/ → no referrer-policy
    • https://www.crownautobody.ca/mpi-direct-repair/ → no referrer-policy
    • https://www.crownautobody.ca/car-rental/ → no referrer-policy
    • https://www.crownautobody.ca/glass-repair/ → no referrer-policy
    • https://www.crownautobody.ca/towing/ → no referrer-policy
    • https://www.crownautobody.ca/in-case-of-accident/ → 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://www.crownautobody.ca/ → no permissions-policy
    • https://www.crownautobody.ca/about-us/ → no permissions-policy
    • https://www.crownautobody.ca/why-us/ → no permissions-policy
    • https://www.crownautobody.ca/services/ → no permissions-policy
    • https://www.crownautobody.ca/process/ → no permissions-policy
    • https://www.crownautobody.ca/blogs/ → no permissions-policy
    • https://www.crownautobody.ca/faq/ → no permissions-policy
    • https://www.crownautobody.ca/mpi-direct-repair/ → no permissions-policy
    • https://www.crownautobody.ca/car-rental/ → no permissions-policy
    • https://www.crownautobody.ca/glass-repair/ → no permissions-policy
    • https://www.crownautobody.ca/towing/ → no permissions-policy
    • https://www.crownautobody.ca/in-case-of-accident/ → 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 (614 responses)
    • x-powered-by: PHP/7.4.33 (137 responses)
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 1.9.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.9.1 in https://progisync.progi.com/public/lib_booking_widget/js/jquery-1.9.1.min.js: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • 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)
    • img1.wsimg.com (40 script tags)
6 checks passed, 1 not applicable
  • OKHTTPS

    All 63 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

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

This report was produced by the DIY SEO Hub Site Spider crawling www.crownautobody.ca from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.

www.crownautobody.ca scan 2026-09-18-0013 | DIY SEO Hub