Scanned sites / www.crownautobody.ca / 2026-10-18-1557

www.crownautobody.ca scan from 10/18/2026, 3:57:35 PM DR 17

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

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

Scan 2026-10-18-1557

Scanned 10/18/2026, 3:57:35 PM, finished 10/18/2026, 4:03:42 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.

53/ 100Needs work

On October 18, 2026 the Site Spider crawled 131 pages and 390 assets of www.crownautobody.ca, starting from https://www.crownautobody.ca/. It scored 53 out of 100, a result that needs work. 9 of 34 checks found something to fix, led by broken links (65), non-200 responses (65), meta descriptions (50); 12 checks passed. Most of the points went to broken links (−20), non-200 responses (−10), meta descriptions (−6.3). 13 checks found something the score does not count, listed as noted. 3 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: Medium4 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
131
Assets fetched
390
Status
Completed
Checks with issues
9 of 34
CoverageComplete crawl

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

  • Title tags22 issues
    22 of 59 pages have title issues. 4 noindex or canonicalized pages excluded.
    −3.5 points
  • Meta descriptions50 issues
    50 of 59 pages have meta description issues. 4 noindex or canonicalized pages excluded.
    −6.3 points
  • Headings8 issues
    8 of 59 pages have heading issues. 4 noindex or canonicalized pages excluded.
    −0.8 points
  • Broken links65 issues
    65 internal links point at 65 broken URLs.
    −20 points
  • Links to other sites66 noted
    0 destinations answered with an error, 4 could not be determined (timeouts, rate limits or refusals), of 16 destinations checked.
  • Redirects3 issues
    4 redirecting URLs, 0 of them chained.
    −0.2 points
  • Non-200 responses65 issues
    69 URLs did not return a 2xx response. 68 of them are pages, 65 with an error status; the rest are assets or redirects.
    −10 points
  • 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 assets7 issues
    7 assets larger than 500 KB among 390 fetched assets.
    −4.2 points
  • Orphan pages16 issues
    16 pages have no internal links pointing at them.
    −1 points
  • Sitemap coverage16 issues
    4 sitemaps listing 59 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 16 reachable only via the sitemap.
    −1.5 points
  • Internal link counts4 noted
    Internal link counts for 63 pages; 4 worth a look.
  • 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.
  • URL format6 noted
    6 of 131 page URLs are harder to read, share or cache than they need to be.
  • Canonicals4 noted
    4 of 63 pages have a canonical worth checking.
  • Robots directives63 noted
    63 pages carry a robots directive; 0 carry none.
  • Anchor text30 noted
    30 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure42 noted
    42 of 59 pages could use the title, heading and snippet space better. 4 noindex or canonicalized pages excluded.
  • Image weight and alt length18 noted
    18 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.
  • HTML and head validationOK
    All 63 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    63 of 59 indexable pages carry structured data: WebSite (63), BreadcrumbList (62), ListItem (62), CreativeWork (60), WebPage (59). 0 pages with errors a rich result would fail on.
  • Near duplicates5 noted
    5 pages in 2 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 63 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 positions9 noted
    9 of 43 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    14 pages in pagination sequences; 0 with problems.
  • Headers and cookiesOK
    0 cookies set by the site; 12 response headers recorded across 521 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 63 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 61 on average across 5 pages; 5 below Google's good thresholds.
  • Spelling23 noted
    23 words an English dictionary does not know, on 15 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2280 sites, median 79%, average 78%

www.crownautobody.ca scores 53%, higher than 3% of the 2280 scanned sites. See the full ranking.

0571130%: 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%: 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%: 1 site28%: 0 sites29%: 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%: 6 sites47%: 4 sites48%: 4 sites49%: 5 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 13 sites58%: 16 sites59%: 6 sites60%: 16 sites61%: 12 sites62%: 21 sites63%: 25 sites64%: 22 sites65%: 36 sites66%: 34 sites67%: 34 sites68%: 35 sites69%: 45 sites70%: 40 sites71%: 66 sites72%: 75 sites73%: 69 sites74%: 65 sites75%: 73 sites76%: 87 sites77%: 91 sites78%: 111 sites79%: 88 sites80%: 104 sites81%: 113 sites82%: 110 sites83%: 91 sites84%: 109 sites85%: 78 sites86%: 68 sites87%: 68 sites88%: 60 sites89%: 59 sites90%: 33 sites91%: 45 sites92%: 31 sites93%: 21 sites94%: 14 sites95%: 9 sites96%: 8 sites97%: 9 sites98%: 4 sites99%: 0 sites100%: 70 sites53% 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 v5). 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.

Your website has several issues that need addressing, including broken links, redirects, and missing meta descriptions. Focusing on these will significantly improve your site’s usability and SEO performance.

  1. 1

    Fix Broken Links

    Why: Broken links negatively affect user experience and SEO.

    How: Update or remove the links leading to broken URLs, like `https://www.crownautobody.ca/2025/03/[email protected]`.

    Checks: broken-links

  2. 2

    Address Non-200 Responses

    Why: Non-200 responses indicate issues that may deter users and search engines.

    How: Resolve these URLs to return proper status codes, particularly `https://www.crownautobody.ca/author/admin/`.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: Proper titles help search visibility and user engagement.

    How: Revise titles exceeding 60 characters to be concise.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Meta descriptions are crucial for attracting clicks from search results.

    How: Create and optimize meta descriptions for pages missing them.

    Checks: meta-descriptions

  5. 5

    Fix Heading Issues

    Why: Proper headings improve content structure and SEO.

    How: Ensure each page has a singular H1 and appropriate H2s.

    Checks: headings

  6. 6

    Reduce Heavy Assets

    Why: Large assets slow page loads and affect user experience.

    How: Optimize or remove large files like CSS and images over 500 KB.

    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 lacks several important security headers, which can expose it to risks like clickjacking and man-in-the-middle attacks. Additionally, it uses an outdated version of a JavaScript library that has known vulnerabilities. Immediate implementation of security headers and library updates is recommended.

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

    Lack of HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be subjected to man-in-the-middle attacks when accessing the site via HTTP.

    Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains; preload' to your server configuration.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without a CSP, the site is vulnerable to cross-site scripting (XSS) and data injection attacks.

    Fix: Add the header 'Content-Security-Policy: default-src 'self';' to your server configuration.

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options, the site can be embedded in another site, leading to clickjacking risks.

    Fix: Add the header 'X-Frame-Options: DENY' to your server configuration.

    Evidence: Clickjacking protection

  4. 4

    Outdated JavaScript LibraryMedium

    Why it matters: Using jQuery 1.9.1 exposes the site to known vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or later to address these vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without X-Content-Type-Options, browsers could incorrectly interpret files, leading to potential security risks.

    Fix: Add the header 'X-Content-Type-Options: nosniff' to your server configuration.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Lack of a referrer policy can expose full URLs of visited pages, leaking user privacy.

    Fix: Add the header 'Referrer-Policy: no-referrer' to your server configuration.

    Evidence: Referrer policy

  7. 7

    Server Version DisclosureLow

    Why it matters: Revealing server version information can provide attackers with insights into potential vulnerabilities.

    Fix: Remove or modify server banners. Adjust server configuration to hide 'Server' and 'X-Powered-By' headers.

    Evidence: Software version disclosure

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: A Permissions Policy can limit browser API features, reducing the risk from potential vulnerabilities.

    Fix: Add the header 'Permissions-Policy: none' to your server configuration.

    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 (521 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

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

Sites scoring near www.crownautobody.ca

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

Own www.crownautobody.ca?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming www.crownautobody.ca. Removal needs no account and no proof of purchase.