Scanned sites / rapidlawn.ca / 2026-10-01-1356
rapidlawn.ca scan from 10/1/2026, 1:56:53 PM
Scan 2026-10-01-1356
Scanned 10/1/2026, 1:56:53 PM, finished 10/1/2026, 9:45:00 PM. Found on page 4 of brave web search results
Site: https://rapidlawn.ca/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On October 1, 2026 the Site Spider crawled 655 pages and 1000 assets of rapidlawn.ca, starting from https://rapidlawn.ca/. It scored 89 out of 100, a good result. 10 of 16 checks found something to fix, led by heavy assets (6), sitemap coverage (318), title tags (101); 5 checks passed. Most of the points went to heavy assets (−3.6), sitemap coverage (−3), title tags (−1.6). 1 check found something the score does not count, listed as noted. 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
- 655
- Assets fetched
- 1000
- Status
- Completed
- Checks with issues
- 10 of 16
1,655 of 1,655 discovered URLs were fetched, 1,258 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 148 link destinations on other sites were checked.
- Title tags101 issues101 of 113 pages have title issues. 522 noindex or canonicalized pages excluded.−1.6 points
- Meta descriptions96 issues96 of 113 pages have meta description issues. 522 noindex or canonicalized pages excluded.−1.2 points
- Headings83 issues83 of 113 pages have heading issues. 522 noindex or canonicalized pages excluded.−0.8 points
- Broken links1 issue3 internal links point at 1 broken URL.
- Links to other sites7 issues7 destinations answered with an error, 45 could not be determined (timeouts, rate limits or refusals), of 148 destinations checked.−0.4 points
- Redirects19 issues20 redirecting URLs, 0 of them chained.−0.1 points
- Non-200 responses1 issue21 URLs did not return a 2xx response. 20 of them are pages, 1 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability37 issues37 of 154 indexable pages have indexability warnings. 481 pages noindex by design.−0.6 points
- Image alt textOK0 of 0 image references have no alt attribute.
- Heavy assets6 issues6 assets larger than 500 KB among 1000 fetched assets.−3.6 points
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage318 issuesNo sitemap found. Tried: https://rapidlawn.ca/sitemap.xml (301). Add one at /sitemap.xml or list it in robots.txt.−3 points
- Internal link countsOKInternal link counts for 500 pages.
- Thin contentOK0 of 113 pages have fewer than 200 words. 522 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1694 sites, median 80%, average 79%
rapidlawn.ca scores 89%, higher than 86% of the 1694 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 good health but requires attention to broken links, redirects, title and meta description issues, indexing, and a sitemap. Prioritizing fixes will enhance SEO performance.
- 1
Fix Broken Links
Why: Resolving broken links improves user experience and site authority.
How: Redirect or remove links to the broken URL: https://rapidlawn.ca/service-item/skid-steer/
Checks: broken-links
- 2
Add a Sitemap
Why: A sitemap helps search engines index your pages accurately.
How: Create a sitemap and ensure it's accessible at /sitemap.xml.
Checks: sitemap-coverage
- 3
Resolve Redirect Issues
Why: Minimizing redirects improves page load speeds and user experience.
How: Eliminate unnecessary redirects. Ensure URLs resolve directly to their final destination.
Checks: redirects
- 4
Address Title Tag Issues
Why: Effective title tags enhance click-through rates and relevance.
How: Shorten or rewrite title tags longer than 60 characters for affected pages.
Checks: titles
- 5
Enhance Meta Descriptions
Why: Unique meta descriptions improve clickability and search visibility.
How: Provide unique meta descriptions for pages that share the same description.
Checks: meta-descriptions
- 6
Fix Heading Issues
Why: Proper heading structure aids user navigation and SEO.
How: Ensure each page contains only one H1 tag.
Checks: headings
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 crawlThe site has multiple security headers missing, which increases the risk of interception and attacks. Addressing these issues, such as implementing HTTP Strict Transport Security, will improve user safety. Additionally, an exposed Google API key needs to be restricted more effectively.
- 0 high
- 4 medium
- 3 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors may be intercepted during their first connection when they use HTTP.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: The absence of CSP can allow unauthorized scripts and styles, increasing XSS risk.
Fix: Add a CSP header: Content-Security-Policy: default-src 'self'; script-src 'self' https://maps.googleapis.com https://cdn.callrail.com.
Evidence: Content Security Policy
- 3
Missing X-Frame-OptionsMedium
Why it matters: Without X-Frame-Options, the site is vulnerable to clickjacking attacks.
Fix: Add the header: X-Frame-Options: DENY.
Evidence: Clickjacking protection
- 4
Leaked Google API KeyMedium
Why it matters: An exposed API key could allow unauthorized access if not properly restricted.
Fix: Restrict the key usage in Google Cloud console based on HTTP referrer.
Evidence: Keys and secrets in page code
- 5
Missing X-Content-Type-OptionsLow
Why it matters: Without this header, browsers may incorrectly execute files based on their content.
Fix: Add the header: X-Content-Type-Options: nosniff.
Evidence: MIME sniffing protection
- 6
Missing Referrer PolicyLow
Why it matters: Not using a Referrer-Policy can expose full URLs to other sites.
Fix: Add the header: Referrer-Policy: no-referrer-when-downgrade.
Evidence: Referrer policy
- 7
Third-party Scripts without Subresource IntegrityLow
Why it matters: Relying on external scripts without integrity checks can lead to altered script execution.
Fix: Consider implementing Content-Security-Policy that includes trusted sources, or use Subresource Integrity where applicable.
Evidence: Third-party scripts
- 8
Missing Permissions PolicyInfo
Why it matters: Without this policy, potentially unsafe features may be accessible to injected scripts.
Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(), camera=().
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://rapidlawn.ca/ → no strict-transport-security
- https://rapidlawn.ca/general-landscaping/ → no strict-transport-security
- https://rapidlawn.ca/landscape-design/ → no strict-transport-security
- https://rapidlawn.ca/irrigation/ → no strict-transport-security
- https://rapidlawn.ca/sod-turf-installation/ → no strict-transport-security
- https://rapidlawn.ca/artificial-turf/ → no strict-transport-security
- https://rapidlawn.ca/pathway-install/ → no strict-transport-security
- https://rapidlawn.ca/patio-install/ → no strict-transport-security
- https://rapidlawn.ca/paving-stone-install/ → no strict-transport-security
- https://rapidlawn.ca/stone-installation/ → no strict-transport-security
- https://rapidlawn.ca/retaining-wall-installation/ → no strict-transport-security
- https://rapidlawn.ca/mulch-installation/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 635 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://rapidlawn.ca/ → no content-security-policy
- https://rapidlawn.ca/general-landscaping/ → no content-security-policy
- https://rapidlawn.ca/landscape-design/ → no content-security-policy
- https://rapidlawn.ca/irrigation/ → no content-security-policy
- https://rapidlawn.ca/sod-turf-installation/ → no content-security-policy
- https://rapidlawn.ca/artificial-turf/ → no content-security-policy
- https://rapidlawn.ca/pathway-install/ → no content-security-policy
- https://rapidlawn.ca/patio-install/ → no content-security-policy
- https://rapidlawn.ca/paving-stone-install/ → no content-security-policy
- https://rapidlawn.ca/stone-installation/ → no content-security-policy
- https://rapidlawn.ca/retaining-wall-installation/ → no content-security-policy
- https://rapidlawn.ca/mulch-installation/ → 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://rapidlawn.ca/ → no x-frame-options
- https://rapidlawn.ca/general-landscaping/ → no x-frame-options
- https://rapidlawn.ca/landscape-design/ → no x-frame-options
- https://rapidlawn.ca/irrigation/ → no x-frame-options
- https://rapidlawn.ca/sod-turf-installation/ → no x-frame-options
- https://rapidlawn.ca/artificial-turf/ → no x-frame-options
- https://rapidlawn.ca/pathway-install/ → no x-frame-options
- https://rapidlawn.ca/patio-install/ → no x-frame-options
- https://rapidlawn.ca/paving-stone-install/ → no x-frame-options
- https://rapidlawn.ca/stone-installation/ → no x-frame-options
- https://rapidlawn.ca/retaining-wall-installation/ → no x-frame-options
- https://rapidlawn.ca/mulch-installation/ → 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://rapidlawn.ca/ → no x-content-type-options
- https://rapidlawn.ca/general-landscaping/ → no x-content-type-options
- https://rapidlawn.ca/landscape-design/ → no x-content-type-options
- https://rapidlawn.ca/irrigation/ → no x-content-type-options
- https://rapidlawn.ca/sod-turf-installation/ → no x-content-type-options
- https://rapidlawn.ca/artificial-turf/ → no x-content-type-options
- https://rapidlawn.ca/pathway-install/ → no x-content-type-options
- https://rapidlawn.ca/patio-install/ → no x-content-type-options
- https://rapidlawn.ca/paving-stone-install/ → no x-content-type-options
- https://rapidlawn.ca/stone-installation/ → no x-content-type-options
- https://rapidlawn.ca/retaining-wall-installation/ → no x-content-type-options
- https://rapidlawn.ca/mulch-installation/ → 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://rapidlawn.ca/ → no referrer-policy
- https://rapidlawn.ca/general-landscaping/ → no referrer-policy
- https://rapidlawn.ca/landscape-design/ → no referrer-policy
- https://rapidlawn.ca/irrigation/ → no referrer-policy
- https://rapidlawn.ca/sod-turf-installation/ → no referrer-policy
- https://rapidlawn.ca/artificial-turf/ → no referrer-policy
- https://rapidlawn.ca/pathway-install/ → no referrer-policy
- https://rapidlawn.ca/patio-install/ → no referrer-policy
- https://rapidlawn.ca/paving-stone-install/ → no referrer-policy
- https://rapidlawn.ca/stone-installation/ → no referrer-policy
- https://rapidlawn.ca/retaining-wall-installation/ → no referrer-policy
- https://rapidlawn.ca/mulch-installation/ → 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://rapidlawn.ca/ → no permissions-policy
- https://rapidlawn.ca/general-landscaping/ → no permissions-policy
- https://rapidlawn.ca/landscape-design/ → no permissions-policy
- https://rapidlawn.ca/irrigation/ → no permissions-policy
- https://rapidlawn.ca/sod-turf-installation/ → no permissions-policy
- https://rapidlawn.ca/artificial-turf/ → no permissions-policy
- https://rapidlawn.ca/pathway-install/ → no permissions-policy
- https://rapidlawn.ca/patio-install/ → no permissions-policy
- https://rapidlawn.ca/paving-stone-install/ → no permissions-policy
- https://rapidlawn.ca/stone-installation/ → no permissions-policy
- https://rapidlawn.ca/retaining-wall-installation/ → no permissions-policy
- https://rapidlawn.ca/mulch-installation/ → 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…zk (39 chars) in https://rapidlawn.ca/forestry-mulching-brush-cutting-and-land-clearing-services/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
- 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.)
- maps.googleapis.com (3 script tags)
- cdn.callrail.com (19 script tags)
7 checks passed, 1 not applicable
- OKHTTPS
All 635 crawled pages were served over HTTPS.
- OKSoftware version disclosure
The Server header names a product without a version, and there is no X-Powered-By header.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
25 forms found, all on HTTPS pages posting to HTTPS addresses.
- OKVulnerable JavaScript libraries
1 library version 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.
- 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 rapidlawn.ca
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- www.eyesinthevillage.ca89/100 · rank 194 · 64 pages
- shortysplumbing.ca89/100 · rank 194 · 74 pages
- winstoncashatt.com89/100 · rank 194 · 132 pages
- www.boisemountaineyecare.com89/100 · rank 194 · 41 pages
- dentrixdentalcare.com89/100 · rank 194 · 259 pages
- eyesharvesthills.com89/100 · rank 194 · 42 pages
This report was produced by the DIY SEO Hub Site Spider crawling rapidlawn.ca from its pages as published, the way a search engine does. It shows summary figures only.
Own rapidlawn.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 rapidlawn.ca. Removal needs no account and no proof of purchase.