Scanned sites / www.crownautobody.ca / 2026-09-16-1743
www.crownautobody.ca scan from 9/16/2026, 5:43:33 PM
A newer scan exists. See the latest report for www.crownautobody.ca.
Scan 2026-09-16-1743
Scanned 9/16/2026, 5:43:33 PM, finished 9/16/2026, 5:50:49 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.
On September 16, 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, 4 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 issues13 of 33 pages have title issues. 4 noindex or canonicalized pages excluded.
- Meta descriptions27 issues27 of 33 pages have meta description issues. 4 noindex or canonicalized pages excluded.
- Headings2 issues2 of 33 pages have heading issues. 4 noindex or canonicalized pages excluded.
- Broken links39 issues92 internal links point at 39 broken URLs.
- RedirectsOK0 redirecting URLs, 0 of them chained.
- Non-200 responses39 issues41 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 33 indexable pages have indexability warnings. 4 pages noindex by design.
- Image alt textOK0 of 317 image references have no alt attribute. 144 use an empty alt (decorative), which is fine.
- Heavy assets2 issues2 assets larger than 500 KB among the 100 heaviest.
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage19 issuesNo sitemap found. Tried: https://www.crownautobody.ca/sitemap.xml (500). Add one at /sitemap.xml or list it in robots.txt.
- Thin contentOK0 of 33 pages have fewer than 200 words. 4 noindex or canonicalized pages excluded.
- Duplicate content39 issues1 group of pages with identical HTML.
Where this scan sits among all scanned sites
1053 sites, median 82%, average 80%
www.crownautobody.ca scores 48%, higher than 1% of the 1053 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsThe site has several critical issues affecting SEO, including broken links and status code errors. Addressing these will significantly improve your site's health and visibility. Implementing a sitemap and optimizing title tags and meta descriptions are also essential improvements.
- 1
Fix Broken Links
Why: 92 internal links pointing to broken URLs hinder user experience and SEO.
How: Identify and correct the broken links or remove them. Check links from pages using a reliable tool.
Checks: broken-links
- 2
Resolve Non-200 Status Codes
Why: 41 URLs return errors, impacting user access and search engine crawling.
How: Review and fix the URLs returning status codes like 500. Ensure correct functioning of backend scripts and pages.
Checks: status-codes
- 3
Update Title Tags
Why: 13 pages have title issues that can affect search ranking and visibility.
How: Revise titles to be under 60 characters. Ensure they are descriptive and relevant.
Checks: titles
- 4
Optimize Meta Descriptions
Why: 27 pages lack or have ineffective meta descriptions, affecting click-through rates.
How: Create unique, descriptive meta descriptions (up to 160 characters) for each affected page.
Checks: meta-descriptions
- 5
Add Missing H1 Headings
Why: 2 pages without H1 headings can hinder SEO performance.
How: Ensure each page has a clear H1 heading that reflects the page's content.
Checks: headings
- 6
Create and Upload Sitemap
Why: No sitemap can hinder search engines from indexing the site properly.
How: Create a sitemap.xml and upload it to the root directory, then list it in the robots.txt file.
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 crawlYour website has several security concerns that need addressing, including missing transport security measures and HTTP headers crucial for protecting against various attacks. Implementing these fixes will enhance your site's resilience against potential threats.
- 0 high
- 3 medium
- 4 low
- 1 info
- 1
Missing HSTS HeaderMedium
Why it matters: Without enforcing HSTS, users can be intercepted when entering the site without HTTPS.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload to all responses.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security PolicyMedium
Why it matters: Lack of a CSP allows scripts and resources to load from any source, increasing risk of XSS attacks.
Fix: Add the header: Content-Security-Policy: default-src 'self'; to all HTML pages.
Evidence: Content Security Policy
- 3
Missing X-Frame-Options HeaderMedium
Why it matters: Absence of this header risks clickjacking attacks by allowing your site to be framed by malicious sites.
Fix: Add the header: X-Frame-Options: DENY to all HTML pages.
Evidence: Clickjacking protection
- 4
Missing X-Content-Type-Options HeaderLow
Why it matters: Without this header, browsers may incorrectly execute files based on their content type.
Fix: Add the header: X-Content-Type-Options: nosniff to all HTML pages.
Evidence: MIME sniffing protection
- 5
Missing Referrer PolicyLow
Why it matters: Not using a referrer policy may expose sensitive URL information when users navigate away from your site.
Fix: Add the header: Referrer-Policy: no-referrer to all HTML pages.
Evidence: Referrer policy
- 6
Exposing Server and Framework VersionsLow
Why it matters: Revealing your server version provides attackers with valuable information to exploit vulnerabilities.
Fix: Remove the headers: server and x-powered-by from HTTP responses.
Evidence: Software version disclosure
- 7
Third-Party Scripts Without Subresource IntegrityLow
Why it matters: Running scripts from third-party sources without integrity checks may introduce security vulnerabilities.
Fix: Implement a Content-Security-Policy that restricts loads to trusted domains, or use Subresource Integrity for external scripts.
Evidence: Third-party scripts
- 8
Missing Permissions PolicyInfo
Why it matters: Lacking a permissions policy may grant features like camera and geolocation to untrusted scripts.
Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(self) to all HTML pages.
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.