Scanned sites / www.crownautobody.ca / 2026-09-17-1259

www.crownautobody.ca scan from 9/17/2026, 12:59:01 PM

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

Scan 2026-09-17-1259

Scanned 9/17/2026, 12:59:01 PM, finished 9/17/2026, 1:05:22 PM. 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.

48/ 100Poor

On September 17, 2026 the Site Spider crawled 76 pages and 331 assets of www.crownautobody.ca, starting from https://www.crownautobody.ca/. It scored 48 out of 100, a poor result. 8 of 14 checks found something to fix, led by broken links (39), non-200 responses (39), duplicate content (39); 6 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: Medium3 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
76
Assets fetched
331
Status
Completed
Checks with issues
8 of 14
  • Title tags13 issues
    13 of 33 pages have title issues. 4 noindex or canonicalized pages excluded.
  • Meta descriptions27 issues
    27 of 33 pages have meta description issues. 4 noindex or canonicalized pages excluded.
  • Headings2 issues
    2 of 33 pages have heading issues. 4 noindex or canonicalized pages excluded.
  • Broken links39 issues
    92 internal links point at 39 broken URLs.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responses39 issues
    41 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 33 indexable pages have indexability warnings. 4 pages noindex by design.
  • Image alt textOK
    0 of 317 image references have no alt attribute. 144 use an empty alt (decorative), which is fine.
  • Heavy assets2 issues
    2 assets larger than 500 KB among the 100 heaviest.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage19 issues
    No sitemap found. Tried: https://www.crownautobody.ca/sitemap.xml (500). Add one at /sitemap.xml or list it in robots.txt.
  • Thin contentOK
    0 of 33 pages have fewer than 200 words. 4 noindex or canonicalized pages excluded.
  • Duplicate content39 issues
    1 group of pages with identical HTML.

Where this scan sits among all scanned sites

1064 sites, median 82%, average 80%

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

027540%: 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%: 1 site46%: 1 site47%: 0 sites48%: 1 site49%: 0 sites50%: 3 sites51%: 3 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%: 20 sites71%: 20 sites72%: 23 sites73%: 24 sites74%: 31 sites75%: 26 sites76%: 38 sites77%: 36 sites78%: 32 sites79%: 30 sites80%: 41 sites81%: 52 sites82%: 47 sites83%: 44 sites84%: 51 sites85%: 47 sites86%: 45 sites87%: 46 sites88%: 54 sites89%: 38 sites90%: 51 sites91%: 36 sites92%: 24 sites93%: 17 sites94%: 15 sites95%: 8 sites96%: 9 sites97%: 5 sites98%: 2 sites99%: 1 site100%: 12 sites48% 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

Significant improvements are needed on your website, including fixing broken links, addressing missing title tags and meta descriptions, and creating a sitemap. Prioritize these fixes for better SEO performance.

  1. 1

    Fix Broken Links

    Why: 92 internal links point to broken URLs, affecting user experience and SEO.

    How: Identify and update or remove links pointing to broken URLs listed in the findings.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: 41 URLs are returning non-200 responses, harming page accessibility.

    How: Investigate and fix or remove URLs that return 500 status codes.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: 13 pages have title issues, which can lead to poor search visibility.

    How: Edit titles to ensure each is between 30-60 characters for clarity and relevance.

    Checks: titles

  4. 4

    Add Missing Meta Descriptions

    Why: 27 pages have meta description issues, impacting click-through rates.

    How: Create concise meta descriptions (150-160 characters) for the pages identified without them.

    Checks: meta-descriptions

  5. 5

    Implement a Sitemap

    Why: No sitemap is found, making it difficult for search engines to crawl your site efficiently.

    How: Create a sitemap and list it in your robots.txt file or upload it to /sitemap.xml.

    Checks: sitemap-coverage

  6. 6

    Fix Duplicate Content

    Why: Identical content could confuse search engines and dilute your page authority.

    How: Revise the duplicate pages to ensure unique content or use canonical tags.

    Checks: duplicate-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

Your website is missing several important security headers that protect visitors and enhance security. Implementing these headers will help defend against common attacks and improve user privacy.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted when 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 Policy (CSP)Medium

    Why it matters: Absence of a CSP means scripts and resources can load from any location, increasing risk of cross-site scripting (XSS).

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, pages can be embedded in a malicious iframe, posing clickjacking risks.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may incorrectly interpret file types, leading to potential execution of malicious scripts.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-Policy HeaderLow

    Why it matters: Not setting a referrer policy can expose sensitive information in URLs when users navigate away from your site.

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

    Evidence: Referrer policy

  6. 6

    Server Version DisclosureLow

    Why it matters: Revealing server information allows attackers to exploit known vulnerabilities.

    Fix: Remove or change the X-Powered-By header. Consider hiding server details.

    Evidence: Software version disclosure

  7. 7

    Missing Permissions-Policy HeaderInfo

    Why it matters: This header limits browser features, improving security by restricting capabilities of injected scripts.

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

    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 37 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 (407 responses)
    • x-powered-by: PHP/7.4.33 (78 responses)
  • 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 (37 script tags)
    • img1.wsimg.com (37 script tags)
6 checks passed, 2 not applicable
  • OKHTTPS

    All 37 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

  • Not applicableSensitive paths in robots.txt

    No robots.txt was fetched.

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-17-1259 | DIY SEO Hub