Scanned sites / rapidlawn.ca / 2026-10-01-1356

rapidlawn.ca scan from 2026-10-01 13:56:53 UTC DR 8

A newer scan exists. See the latest report for rapidlawn.ca.

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

Scan 2026-10-01-1356

Scanned 2026-10-01 13:56:53 UTC, finished 2026-10-01 21:45:00 UTC. 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.

89/ 100Good

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 27 checks found something to fix, led by heavy assets (6), sitemap coverage (318), title tags (101); 10 checks passed. Most of the points went to heavy assets (−3.6), sitemap coverage (−3), title tags (−1.6). 7 checks found something the score does not count, listed as noted. 10 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
655
Assets fetched
1000
Status
Completed
Checks with issues
10 of 27
CoverageJob finished, partial coverage

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 issues
    101 of 113 pages have title issues. 522 noindex or canonicalized pages excluded.
    −1.6 points
  • Meta descriptions96 issues
    96 of 113 pages have meta description issues. 522 noindex or canonicalized pages excluded.
    −1.2 points
  • Headings83 issues
    83 of 113 pages have heading issues. 522 noindex or canonicalized pages excluded.
    −0.8 points
  • Broken links1 issue
    3 internal links point at 1 broken URL.
  • Links to other sites6 issues
    6 destinations answered with an error, 44 could not be determined (timeouts, rate limits or refusals), of 148 destinations checked.
    −0.4 points
  • Redirects19 issues
    20 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses1 issue
    21 URLs did not return a 2xx response. 20 of them are pages, 1 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability37 issues
    37 of 154 indexable pages have indexability warnings. 481 pages noindex by design.
    −0.6 points
  • Image alt textOK
    0 of 0 image references have no alt attribute.
  • Heavy assets6 issues
    6 assets larger than 500 KB among 1000 fetched assets.
    −3.6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage318 issues
    No sitemap found. Tried: https://rapidlawn.ca/sitemap.xml (301). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link counts440 noted
    Internal link counts for 500 pages; 440 worth a look.
  • Thin contentOK
    0 of 113 pages have fewer than 200 words. 522 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format446 noted
    446 of 655 page URLs are harder to read, share or cache than they need to be.
  • Canonicals522 noted
    522 of 635 pages have a canonical worth checking.
  • Robots directives635 noted
    635 pages carry a robots directive; 0 carry none.
  • Anchor text4 noted
    4 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure89 noted
    89 of 113 pages could use the title, heading and snippet space better. 522 noindex or canonicalized pages excluded.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 635 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 14 response headers recorded across 1655 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 635 pages; 527 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 62 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2909 sites, median 80%, average 79%

rapidlawn.ca scores 89%, higher than 82% of the 2909 scanned sites. See the full ranking.

0761520%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 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%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 134 sites79%: 112 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 131 sites85%: 106 sites86%: 97 sites87%: 95 sites88%: 82 sites89%: 77 sites90%: 57 sites91%: 61 sites92%: 44 sites93%: 32 sites94%: 25 sites95%: 17 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites89% 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 v4). 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.

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

    Evidence: One URL: no sitemap found.

    1 page affected

    Checks: sitemap-coverage

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

    Evidence: 24 pages share the meta description "Rapid Lawn Landscape Solutions Ltd. is your best Regina lan…", which usually means one template writes it for all of them.

    24 pages affected

    Depends on: If these pages really are the same content, the duplicate meta description is a symptom: canonicalise them to one URL instead.

    Checks: meta-descriptions

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

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

Own rapidlawn.ca?