Scanned sites / www.cuppers.ca / 2026-09-12-1631
www.cuppers.ca scan from 2026-09-12 16:31:53 UTC DR 31
A newer scan exists. See the latest report for www.cuppers.ca.
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-09-12-1631
Scanned 2026-09-12 16:31:53 UTC, finished 2026-09-12 16:36:25 UTC
Site: https://www.cuppers.ca/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 12, 2026 the Site Spider crawled 1 page and 3 assets of www.cuppers.ca, starting from https://www.cuppers.ca/. It scored 100 out of 100, an excellent result. All 12 checks passed: nothing needs fixing. 1 check found something the score does not count, listed as noted. 25 checks were not run because the crawl fetched nothing for them.
Security review: Info1 info finding. See the security findings ↓
- Pages crawled
- 1
- Assets fetched
- 3
- Status
- Completed
- Checks with issues
- 0 of 12
4 of 4 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript.
- Title tagsNot checkedNot checked: the crawl fetched nothing this check can look at.
- Meta descriptionsNot checkedNot checked: the crawl fetched nothing this check can look at.
- HeadingsNot checkedNot checked: the crawl fetched nothing this check can look at.
- Broken linksNot checkedNot checked: the crawl fetched nothing this check can look at.
- Links to other sitesNot checkedNot checked: the crawl fetched nothing this check can look at.
- RedirectsNot checkedNot checked: the crawl fetched nothing this check can look at.
- Non-200 responsesNot checkedNot checked: the crawl fetched nothing this check can look at.
- Rate limitedNot checkedNot checked: the crawl fetched nothing this check can look at.
- IndexabilityNot checkedNot checked: the crawl fetched nothing this check can look at.
- Image alt textNot checkedNot checked: the crawl fetched nothing this check can look at.
- Heavy assetsOK0 assets larger than 500 KB among 3 fetched assets.
- Orphan pagesNot checkedNot checked: the crawl fetched nothing this check can look at.
- Sitemap coverageNot checkedNot checked: the crawl fetched nothing this check can look at.
- Internal link countsOKInternal link counts for 0 pages; none is a dead end or buried.
- Thin contentNot checkedNot checked: the crawl fetched nothing this check can look at.
- Duplicate contentNot checkedNot checked: the crawl fetched nothing this check can look at.
- URL formatOKAll 1 page URL are plain lowercase addresses without parameters.
- CanonicalsOK0 of 0 pages have a canonical worth checking.
- Robots directivesOKNo page carries a robots directive; all 0 pages are open to search engines.
- Anchor textOKEvery internal link has descriptive, followed anchor text.
- Title and heading structureOK0 of 0 pages could use the title, heading and snippet space better.
- Image weight and alt lengthOKNo image is over 100 KB or carries alt text over 100 characters.
- Response anomaliesOKNo redirect loops, header redirects or pages served as something other than HTML.
- HTML and head validationNot checkedNot checked: the crawl fetched no HTML pages.
- hreflangNot checkedNot checked: the crawl fetched no HTML pages.
- Structured dataNot checkedNot checked: the crawl fetched no HTML pages.
- Near duplicatesNot checkedNot checked: the crawl fetched no HTML pages.
- Soft 404sNot checkedNot checked: the crawl fetched no HTML pages.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positionsNot checkedNot checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
- PaginationNot checkedNot checked: the crawl fetched no HTML pages.
- Headers and cookiesOK0 cookies set by the site; 7 response headers recorded across 4 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKNo page answered 200, so there is no link equity to share.
- JavaScript renderingNot checkedNot 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 Insights1 notedMobile performance 42 on average across 1 page; 1 below Google's good thresholds.
- SpellingNot checkedNot checked: the crawl fetched no HTML pages.
Where this scan sits among all scanned sites
2873 sites, median 80%, average 79%
www.cuppers.ca scores 100%, higher than 95% of the 2873 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 findingsWritten from an earlier version of the analysis. 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 site has a health score of 90/100, which is excellent. However, it has non-200 responses and lacks a sitemap. Prioritizing these fixes will improve accessibility and SEO performance.
- 1
Fix Non-200 Responses
Why: Three URLs returned non-200 responses, impacting accessibility and SEO.
How: Investigate server settings or permissions for the URLs to return a 200 status. Ensure your main page is publicly accessible.
Checks: status-codes
- 2
Create a Sitemap
Why: No sitemap found could limit search engines' ability to index your site effectively.
How: Create a sitemap.xml file listing your URLs and upload it to the root directory. Add the sitemap URL to robots.txt.
Checks: sitemap-coverage
- 3
Check Permissions for Sitemap URLs
Why: Sitemap URLs returned a 403 status, preventing access.
How: Adjust permissions on the server to allow access to sitemap-related files.
Checks: status-codes
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 robots.txt file lists a sensitive path that may expose private areas of the site. To enhance security, restrict access to sensitive locations properly.
- 0 high
- 0 medium
- 0 low
- 1 info
- 1
Sensitive path exposed in robots.txtInfo
Why it matters: The robots.txt file includes a disallowed path (/wp-admin/) that should be protected. This aids attackers in locating sensitive directories.
Fix: Implement access controls on sensitive directories to prevent unauthorized access, rather than relying on robots.txt to conceal them.
Evidence: Sensitive paths in robots.txt
What the checks found
- NoteSensitive paths in robots.txt
robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.
- Disallow: /wp-admin/
4 checks passed, 11 not applicable
- OKSoftware version disclosure
The Server header names a product without a version, and there is no X-Powered-By header.
- 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.
- OKThird-party scripts
The sampled pages load no scripts from other domains.
- Not applicableHTTPS
No HTML page was fetched, so transport security could not be judged.
- Not applicableHTTP Strict Transport Security
No page was served over HTTPS, so this header does not apply yet.
- Not applicableContent Security Policy
No HTML page was fetched.
- Not applicableClickjacking protection
No HTML page was fetched.
- Not applicableMIME sniffing protection
No HTML page was fetched.
- Not applicableReferrer policy
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicablePermissions policy
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicableCookie flags
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicableMixed content
No page was served over HTTPS, so mixed content does not apply yet.
- Not applicableForms over HTTPS
No forms were found on the sampled pages.
- Not applicableVulnerable JavaScript libraries
No recognisable library versions were found in the sampled scripts.
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.cuppers.ca
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- www.woodyandersonford.comDR 31100/100 · rank 1 · 1 page
- www.specim.comDR 56100/100 · rank 1 · 1 page
- www.tacenterprises.netDR 13100/100 · rank 1 · 1 page
- devmarket.lolDR 0100/100 · rank 1 · 2 pages
- www.greenenergygroup.esDR 299/100 · rank 151 · 80 pages
- glamroom.caDR 699/100 · rank 151 · 4,999 pages
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.cuppers.ca from its pages as published, the way a search engine does. It shows summary figures only.
Own www.cuppers.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.cuppers.ca. Removal needs no account and no proof of purchase.