Scanned sites / www.gcoc.ca / 2026-09-16-2148
www.gcoc.ca scan from 9/16/2026, 9:48:50 PM
A newer scan exists. See the latest report for www.gcoc.ca.
Scan 2026-09-16-2148
Scanned 9/16/2026, 9:48:50 PM, finished 9/16/2026, 10:10:56 PM. Found with openstreetmap overpass
Site: https://www.gcoc.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 160 pages and 450 assets of www.gcoc.ca, starting from https://www.gcoc.ca/. It scored 89 out of 100, a good result. 6 of 14 checks found something to fix, led by meta descriptions (158), title tags (6), heavy assets (4); 8 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, 2 low and 1 info findings. See the security findings ↓
- Pages crawled
- 160
- Assets fetched
- 450
- Status
- Completed
- Checks with issues
- 6 of 14
- Title tags6 issues6 of 159 pages have title issues.
- Meta descriptions158 issues158 of 159 pages have meta description issues.
- Headings1 issue1 of 159 pages have heading issues.
- Broken linksOK0 internal links point at 0 broken URLs.
- RedirectsOK1 redirecting URL, 0 of them chained.
- Non-200 responsesOK2 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 159 indexable pages have indexability warnings.
- Image alt textOK0 of 1427 image references have no alt attribute. 1231 use an empty alt (decorative), which is fine.
- Heavy assets4 issues4 assets larger than 500 KB among the 100 heaviest.
- Orphan pages1 issue1 page have no internal links pointing at them.
- Sitemap coverage2 issues1 sitemap listing 160 URLs: 0 crawled pages missing, 1 listed URL broken or redirecting, 1 reachable only via the sitemap.
- Thin contentOK0 of 159 pages have fewer than 200 words.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1053 sites, median 82%, average 80%
www.gcoc.ca scores 89%, higher than 80% 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 findingsYour site has a good health score, but there are several areas for improvement, especially with meta descriptions and title tags. Focus on correcting these for better SEO performance.
- 1
Fix Redirects
Why: One URL redirects incorrectly, potentially affecting user experience.
How: Update any links to point directly to the correct final URL.
Checks: redirects
- 2
Resolve Non-200 Responses
Why: Two URLs are not returning a 2xx response, causing errors for users.
How: Check for the correct status for https://www.gcoc.ca/services/air-conditioning/ and fix the 404 for the asset URL.
Checks: status-codes
- 3
Improve Title Tags
Why: Six title tags are problematic; optimizing these can enhance click-through rates.
How: Revise titles to ensure they are under 60 characters and unique for each page.
Checks: titles
- 4
Update Meta Descriptions
Why: 158 pages lack meta descriptions, potentially impacting search visibility.
How: Create unique, engaging meta descriptions for all pages that are under 160 characters.
Checks: meta-descriptions
- 5
Add H1 Headings
Why: One page is missing an H1 tag, which is critical for SEO.
How: Add a relevant H1 heading to the page at https://www.gcoc.ca/locations/.
Checks: headings
- 6
Optimize Heavy Assets
Why: Having large assets can slow down your website's loading time.
How: Consider compressing or replacing heavy SVG files larger than 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 crawlYour website has several security issues that need immediate attention, especially concerning response headers and exposed keys. Implementing the recommended headers and securing your API key will enhance protection against various web vulnerabilities.
- 0 high
- 4 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, attackers could intercept initial requests if users type the website's address without HTTPS.
Fix: Set the Strict-Transport-Security header to 'max-age=63072000; includeSubDomains'.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Without CSP, there are no restrictions on where your site can load scripts, styles, or frames from, risking XSS attacks.
Fix: Add a Content-Security-Policy header with a restrictive policy, e.g., 'default-src 'self'; script-src 'self';'.
Evidence: Content Security Policy
- 3
Missing X-Frame-OptionsMedium
Why it matters: Not having this header means your site can be embedded in frames, making it vulnerable to clickjacking.
Fix: Set the X-Frame-Options header to 'DENY'. Alternatively, use CSP with 'frame-ancestors 'none';'.
Evidence: Clickjacking protection
- 4
Exposed Google API KeyMedium
Why it matters: The Google API key in your code may allow unauthorized use if not restricted correctly.
Fix: Restrict the API key in the Google Cloud Console based on HTTP referrers to limit its exposure.
Evidence: Keys and secrets in page code
- 5
Missing X-Content-Type-OptionsLow
Why it matters: Without this header, browsers may incorrectly execute files as scripts based on their contents instead of their declared types.
Fix: Add the X-Content-Type-Options header and set it to 'nosniff'.
Evidence: MIME sniffing protection
- 6
Missing Referrer PolicyLow
Why it matters: Without a referrer policy, sensitive information in URLs may be leaked to third-party sites.
Fix: Add a Referrer-Policy header, e.g., 'no-referrer'.
Evidence: Referrer policy
- 7
Missing Permissions PolicyInfo
Why it matters: Lacking this header means unnecessary browser features remain active, which may be exploited by injected scripts.
Fix: Include a Permissions-Policy header, e.g., 'geolocation=(self)'.
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.gcoc.ca/ → no strict-transport-security
- https://www.gcoc.ca/about-us/ → no strict-transport-security
- https://www.gcoc.ca/fleet/ → no strict-transport-security
- https://www.gcoc.ca/faq/ → no strict-transport-security
- https://www.gcoc.ca/contact-us/ → no strict-transport-security
- https://www.gcoc.ca/oil-change/ → no strict-transport-security
- https://www.gcoc.ca/services/ → no strict-transport-security
- https://www.gcoc.ca/services/tire-services/ → no strict-transport-security
- https://www.gcoc.ca/services/transmission-fluid-service/ → no strict-transport-security
- https://www.gcoc.ca/services/radiator-fluid-service/ → no strict-transport-security
- https://www.gcoc.ca/services/differential-fluid-service/ → no strict-transport-security
- https://www.gcoc.ca/services/air-filter-replacements/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 159 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.gcoc.ca/ → no content-security-policy
- https://www.gcoc.ca/about-us/ → no content-security-policy
- https://www.gcoc.ca/fleet/ → no content-security-policy
- https://www.gcoc.ca/faq/ → no content-security-policy
- https://www.gcoc.ca/contact-us/ → no content-security-policy
- https://www.gcoc.ca/oil-change/ → no content-security-policy
- https://www.gcoc.ca/services/ → no content-security-policy
- https://www.gcoc.ca/services/tire-services/ → no content-security-policy
- https://www.gcoc.ca/services/transmission-fluid-service/ → no content-security-policy
- https://www.gcoc.ca/services/radiator-fluid-service/ → no content-security-policy
- https://www.gcoc.ca/services/differential-fluid-service/ → no content-security-policy
- https://www.gcoc.ca/services/air-filter-replacements/ → 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.gcoc.ca/ → no x-frame-options
- https://www.gcoc.ca/about-us/ → no x-frame-options
- https://www.gcoc.ca/fleet/ → no x-frame-options
- https://www.gcoc.ca/faq/ → no x-frame-options
- https://www.gcoc.ca/contact-us/ → no x-frame-options
- https://www.gcoc.ca/oil-change/ → no x-frame-options
- https://www.gcoc.ca/services/ → no x-frame-options
- https://www.gcoc.ca/services/tire-services/ → no x-frame-options
- https://www.gcoc.ca/services/transmission-fluid-service/ → no x-frame-options
- https://www.gcoc.ca/services/radiator-fluid-service/ → no x-frame-options
- https://www.gcoc.ca/services/differential-fluid-service/ → no x-frame-options
- https://www.gcoc.ca/services/air-filter-replacements/ → 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.gcoc.ca/ → no x-content-type-options
- https://www.gcoc.ca/about-us/ → no x-content-type-options
- https://www.gcoc.ca/fleet/ → no x-content-type-options
- https://www.gcoc.ca/faq/ → no x-content-type-options
- https://www.gcoc.ca/contact-us/ → no x-content-type-options
- https://www.gcoc.ca/oil-change/ → no x-content-type-options
- https://www.gcoc.ca/services/ → no x-content-type-options
- https://www.gcoc.ca/services/tire-services/ → no x-content-type-options
- https://www.gcoc.ca/services/transmission-fluid-service/ → no x-content-type-options
- https://www.gcoc.ca/services/radiator-fluid-service/ → no x-content-type-options
- https://www.gcoc.ca/services/differential-fluid-service/ → no x-content-type-options
- https://www.gcoc.ca/services/air-filter-replacements/ → 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.gcoc.ca/ → no referrer-policy
- https://www.gcoc.ca/about-us/ → no referrer-policy
- https://www.gcoc.ca/fleet/ → no referrer-policy
- https://www.gcoc.ca/faq/ → no referrer-policy
- https://www.gcoc.ca/contact-us/ → no referrer-policy
- https://www.gcoc.ca/oil-change/ → no referrer-policy
- https://www.gcoc.ca/services/ → no referrer-policy
- https://www.gcoc.ca/services/tire-services/ → no referrer-policy
- https://www.gcoc.ca/services/transmission-fluid-service/ → no referrer-policy
- https://www.gcoc.ca/services/radiator-fluid-service/ → no referrer-policy
- https://www.gcoc.ca/services/differential-fluid-service/ → no referrer-policy
- https://www.gcoc.ca/services/air-filter-replacements/ → 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.gcoc.ca/ → no permissions-policy
- https://www.gcoc.ca/about-us/ → no permissions-policy
- https://www.gcoc.ca/fleet/ → no permissions-policy
- https://www.gcoc.ca/faq/ → no permissions-policy
- https://www.gcoc.ca/contact-us/ → no permissions-policy
- https://www.gcoc.ca/oil-change/ → no permissions-policy
- https://www.gcoc.ca/services/ → no permissions-policy
- https://www.gcoc.ca/services/tire-services/ → no permissions-policy
- https://www.gcoc.ca/services/transmission-fluid-service/ → no permissions-policy
- https://www.gcoc.ca/services/radiator-fluid-service/ → no permissions-policy
- https://www.gcoc.ca/services/differential-fluid-service/ → no permissions-policy
- https://www.gcoc.ca/services/air-filter-replacements/ → no permissions-policy
- FoundKeys and secrets in page codeMedium
1 credential-like value found in code served to every visitor: Google API key.
- Google API key AIzaSy…jU (39 chars) in https://www.gcoc.ca/locations/alberta/red-deer/6730-taylor-dr/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
- NoteSoftware version disclosure
Responses name the framework in an X-Powered-By header but hide the version.
- server: cloudflare (610 responses)
- x-powered-by: WP Engine (161 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 (40 script tags)
- www.google.com (24 script tags)
6 checks passed, 1 not applicable
- OKHTTPS
All 159 crawled pages were served over HTTPS.
- OKCookie flags
All 1 cookie carry Secure, HttpOnly and SameSite flags.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
128 forms found, all on HTTPS pages posting to HTTPS addresses.
- OKVulnerable JavaScript libraries
2 library versions recognised, none with known vulnerabilities.
- OKExposed files and listings
None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.
- 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.gcoc.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.