Scanned sites / www.pranayogastudio.ca / 2026-10-19-0802
www.pranayogastudio.ca scan from 2026-10-19 08:02:34 UTC DR 38
A newer scan exists. See the latest report for www.pranayogastudio.ca.
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-10-19-0802
Scanned 2026-10-19 08:02:34 UTC, finished 2026-10-19 08:15:04 UTC. Found with openstreetmap overpass
Site: https://www.pranayogastudio.ca/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On October 19, 2026 the Site Spider crawled 515 pages and 1064 assets of www.pranayogastudio.ca, starting from https://www.pranayogastudio.ca/. It scored 65 out of 100, a result that needs work. 11 of 32 checks found something to fix, led by meta descriptions (338), heavy assets (199), title tags (185); 9 checks passed. Most of the points went to meta descriptions (−7.7), heavy assets (−6), title tags (−5.3). 12 checks found something the score does not count, listed as noted. 5 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
- 515
- Assets fetched
- 1064
- Status
- Completed
- Checks with issues
- 11 of 32
1,579 of 1,579 discovered URLs were fetched, 96 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. 418 link destinations on other sites have not been checked.
- Title tags185 issues185 of 338 pages have title issues. 13 noindex or canonicalized pages excluded.−5.3 points
- Meta descriptions338 issues338 of 338 pages have meta description issues. 13 noindex or canonicalized pages excluded.−7.7 points
- Headings286 issues286 of 338 pages have heading issues. 13 noindex or canonicalized pages excluded.−4.9 points
- Broken links2 issues2 internal links point at 2 broken URLs.−0.1 points
- Links to other sitesNot checkedNot checked: the crawl fetched nothing this check can look at.
- Redirects160 issues161 redirecting URLs, 0 of them chained.−1.8 points
- Non-200 responses4 issues167 URLs did not return a 2xx response. 164 of them are pages, 4 with an error status; the rest are assets or redirects.−0.1 points
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability27 issues27 of 351 indexable pages have indexability warnings.−0.8 points
- Image alt text637 issues637 of 12209 image references have no alt attribute. 3807 use an empty alt (decorative), which is fine.−0.3 points
- Heavy assets199 issues199 assets larger than 500 KB among 1064 fetched assets. 2 documents over that size are listed but not counted: downloads are not page weight.−6 points
- Orphan pages269 issues269 pages have no internal links pointing at them.−3.1 points
- Sitemap coverage275 issues10 sitemaps listing 343 URLs: 7 crawled pages missing, 0 listed URLs broken or redirecting, 268 reachable only via the sitemap.−4.7 points
- Internal link counts10 notedInternal link counts for 351 pages; 10 worth a look.
- Thin contentOK0 of 338 pages have fewer than 200 words. 13 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format77 noted77 of 515 page URLs are harder to read, share or cache than they need to be.
- Canonicals28 noted28 of 351 pages have a canonical worth checking.
- Robots directives351 noted351 pages carry a robots directive; 0 carry none.
- Anchor text143 noted143 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure44 noted44 of 338 pages could use the title, heading and snippet space better. 13 noindex or canonicalized pages excluded.
- Image weight and alt length308 noted307 images over 100 KB; 1 with alt text over 100 characters.
- Response anomalies2 noted2 URLs answered in a way worth looking at.
- HTML and head validation302 noted302 of 351 pages have HTML problems: 298 with head tags outside <head>, 0 over 2 MB.
- hreflangOKNo page declares hreflang.
- Structured dataOK351 of 338 indexable pages carry structured data: WebSite (351), Organization (351), WebPage (351), BreadcrumbList (336), ListItem (336). 0 pages with errors a rich result would fail on.
- Near duplicatesOKNo near duplicates among 314 pages with enough text to compare.
- Soft 404s4 noted4 pages answer 200 but say they are not there.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positions18 noted18 of 81 linked pages are linked only from the template, never from another page's content.
- PaginationOK7 pages in pagination sequences; 0 with problems.
- Headers and cookiesOK0 cookies set by the site; 12 response headers recorded across 1579 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 ScoreOKLink Score (internal PageRank, 0-100) for 351 pages; 303 hold almost none (10 or less).
- 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 InsightsNot checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- Spelling140 noted140 words an English dictionary does not know, on 141 pages. Product names and jargon will appear here too.
Where this scan sits among all scanned sites
2285 sites, median 79%, average 78%
www.pranayogastudio.ca scores 65%, higher than 10% of the 2285 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 website requires several important fixes to enhance its SEO health. Focus first on broken links and non-200 responses for immediate improvements, followed by titles, meta descriptions, headings, and indexability for better search visibility.
- 1
Fix Broken Links
Why: Broken links negatively impact user experience and SEO.
How: Update or remove links to the non-existent pages found at the specified URLs.
Checks: broken-links
- 2
Address Non-200 Responses
Why: These responses hinder crawlers and users from accessing content.
How: Ensure all URLs return a 200 status by fixing the broken ones or redirecting appropriately.
Checks: status-codes
- 3
Improve Title Tags
Why: Page titles are crucial for SEO and click-through rates.
How: Ensure unique title tags for at least 11 pages, using relevant keywords.
Checks: titles
- 4
Optimize Meta Descriptions
Why: Unique meta descriptions help improve click-through rates.
How: Create distinct meta descriptions for 338 pages to better reflect content.
Checks: meta-descriptions
- 5
Correct Heading Issues
Why: Proper heading structure enhances accessibility and SEO.
How: Add H1 tags to 273 pages where missing and remove duplicates.
Checks: headings
- 6
Fix Indexability Warnings
Why: Issues here may prevent search engines from indexing your pages.
How: Review and add relevant canonical tags to the 27 affected pages.
Checks: indexability
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 header issues that need attention. Notably, there is no strict transport security, content security policy, or clickjacking protection, which could expose users to risks. There is also a Google API key publicly visible. Addressing these findings will enhance your site’s security.
- 0 high
- 4 medium
- 3 low
- 1 info
- 1
Missing HTTP Strict Transport SecurityMedium
Why it matters: Lack of HSTS allows interception when users type the URL without HTTPS first.
Fix: Add `Strict-Transport-Security: max-age=31536000; includeSubDomains` to your HTTP response headers.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security PolicyMedium
Why it matters: Absence of CSP allows unrestricted loading of scripts and resources, increasing XSS risks.
Fix: Include a header like `Content-Security-Policy: default-src 'self';` to define where content can load from.
Evidence: Content Security Policy
- 3
Missing X-Frame-OptionsMedium
Why it matters: No clickjacking protection means your content could be embedded maliciously by other sites.
Fix: Add `X-Frame-Options: DENY` to your response headers to prevent framing.
Evidence: Clickjacking protection
- 4
Exposed Google API KeyMedium
Why it matters: A visible API key can be misused if not properly restricted, posing a credential risk.
Fix: Restrict this API key in the Google Cloud Console to specific referrers (your domain) and consider rotating it.
Evidence: Keys and secrets in page code
- 5
Missing X-Content-Type-OptionsLow
Why it matters: Without this header, browsers might incorrectly interpret files and execute unwanted scripts.
Fix: Add `X-Content-Type-Options: nosniff` to your HTTP headers to enhance security.
Evidence: MIME sniffing protection
- 6
Missing Referrer-Policy HeaderLow
Why it matters: Lack of a referrer policy means sensitive URL details could be sent to external sites.
Fix: Implement `Referrer-Policy: no-referrer` to prevent this leakage.
Evidence: Referrer policy
- 7
Mixed Content IssuesLow
Why it matters: Loading HTTP resources on HTTPS pages can lead to content being blocked by browsers.
Fix: Change URLs to HTTPS for all resources, e.g., replace `http://f49.8c2.myftpupload.com/...` with `https://...`.
Evidence: Mixed content
- 8
Missing Permissions-Policy HeaderInfo
Why it matters: Lack of this header does not restrict browser features that may increase risk from injected scripts.
Fix: Consider using `Permissions-Policy: geolocation=(), microphone=(), camera=()` to restrict access to sensitive features.
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.pranayogastudio.ca/ → no strict-transport-security
- https://www.pranayogastudio.ca/workshops/ → no strict-transport-security
- https://www.pranayogastudio.ca/training/ → no strict-transport-security
- https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no strict-transport-security
- https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no strict-transport-security
- https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no strict-transport-security
- https://www.pranayogastudio.ca/training/speciality-training/ → no strict-transport-security
- https://www.pranayogastudio.ca/schedule/ → no strict-transport-security
- https://www.pranayogastudio.ca/yoga/ → no strict-transport-security
- https://www.pranayogastudio.ca/classes/rates/ → no strict-transport-security
- https://www.pranayogastudio.ca/about/studio/ → no strict-transport-security
- https://www.pranayogastudio.ca/about/teachers/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 351 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.pranayogastudio.ca/ → no content-security-policy
- https://www.pranayogastudio.ca/workshops/ → no content-security-policy
- https://www.pranayogastudio.ca/training/ → no content-security-policy
- https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no content-security-policy
- https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no content-security-policy
- https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no content-security-policy
- https://www.pranayogastudio.ca/training/speciality-training/ → no content-security-policy
- https://www.pranayogastudio.ca/schedule/ → no content-security-policy
- https://www.pranayogastudio.ca/yoga/ → no content-security-policy
- https://www.pranayogastudio.ca/classes/rates/ → no content-security-policy
- https://www.pranayogastudio.ca/about/studio/ → no content-security-policy
- https://www.pranayogastudio.ca/about/teachers/ → 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.pranayogastudio.ca/ → no x-frame-options
- https://www.pranayogastudio.ca/workshops/ → no x-frame-options
- https://www.pranayogastudio.ca/training/ → no x-frame-options
- https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no x-frame-options
- https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no x-frame-options
- https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no x-frame-options
- https://www.pranayogastudio.ca/training/speciality-training/ → no x-frame-options
- https://www.pranayogastudio.ca/schedule/ → no x-frame-options
- https://www.pranayogastudio.ca/yoga/ → no x-frame-options
- https://www.pranayogastudio.ca/classes/rates/ → no x-frame-options
- https://www.pranayogastudio.ca/about/studio/ → no x-frame-options
- https://www.pranayogastudio.ca/about/teachers/ → 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.pranayogastudio.ca/ → no x-content-type-options
- https://www.pranayogastudio.ca/workshops/ → no x-content-type-options
- https://www.pranayogastudio.ca/training/ → no x-content-type-options
- https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no x-content-type-options
- https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no x-content-type-options
- https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no x-content-type-options
- https://www.pranayogastudio.ca/training/speciality-training/ → no x-content-type-options
- https://www.pranayogastudio.ca/schedule/ → no x-content-type-options
- https://www.pranayogastudio.ca/yoga/ → no x-content-type-options
- https://www.pranayogastudio.ca/classes/rates/ → no x-content-type-options
- https://www.pranayogastudio.ca/about/studio/ → no x-content-type-options
- https://www.pranayogastudio.ca/about/teachers/ → 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.pranayogastudio.ca/ → no referrer-policy
- https://www.pranayogastudio.ca/workshops/ → no referrer-policy
- https://www.pranayogastudio.ca/training/ → no referrer-policy
- https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no referrer-policy
- https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no referrer-policy
- https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no referrer-policy
- https://www.pranayogastudio.ca/training/speciality-training/ → no referrer-policy
- https://www.pranayogastudio.ca/schedule/ → no referrer-policy
- https://www.pranayogastudio.ca/yoga/ → no referrer-policy
- https://www.pranayogastudio.ca/classes/rates/ → no referrer-policy
- https://www.pranayogastudio.ca/about/studio/ → no referrer-policy
- https://www.pranayogastudio.ca/about/teachers/ → 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.pranayogastudio.ca/ → no permissions-policy
- https://www.pranayogastudio.ca/workshops/ → no permissions-policy
- https://www.pranayogastudio.ca/training/ → no permissions-policy
- https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no permissions-policy
- https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no permissions-policy
- https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no permissions-policy
- https://www.pranayogastudio.ca/training/speciality-training/ → no permissions-policy
- https://www.pranayogastudio.ca/schedule/ → no permissions-policy
- https://www.pranayogastudio.ca/yoga/ → no permissions-policy
- https://www.pranayogastudio.ca/classes/rates/ → no permissions-policy
- https://www.pranayogastudio.ca/about/studio/ → no permissions-policy
- https://www.pranayogastudio.ca/about/teachers/ → no permissions-policy
- FoundMixed contentLow
2 resources on HTTPS pages are loaded over plain HTTP.
- https://www.pranayogastudio.ca/events/event/breathwork-vibrational-me… loads image http://f49.8c2.myftpupload.com/wp-content/uploads/2017/03/trevor.jpg
- https://www.pranayogastudio.ca/events/event/breathwork-vibrational-me… loads image http://f49.8c2.myftpupload.com/wp-content/uploads/2017/03/trevor.jpg
- FoundKeys and secrets in page codeMedium
1 credential-like value found in code served to every visitor: Google API key.
- Google API key AIzaSy…mQ (39 chars) in https://www.pranayogastudio.ca/contact/: 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 3 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.)
- a.mailmunch.co (40 script tags)
- momence.com (2 script tags)
- maps.googleapis.com (13 script tags)
6 checks passed, 1 not applicable
- OKHTTPS
All 351 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.
- OKForms over HTTPS
6 forms found, all on HTTPS pages posting to HTTPS addresses.
- OKVulnerable JavaScript libraries
3 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.
- 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 www.pranayogastudio.ca
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- absarokapainandrehab.comDR 566/100 · rank 1992 · 47 pages
- opusfived.devDR 2866/100 · rank 1992 · 1 page
- www.square1coffee.caDR 2365/100 · rank 2028 · 22 pages
- www.sdireland.comDR 2765/100 · rank 2028 · 43 pages
- www.wellnessliving.comDR 8465/100 · rank 2028 · 4,999 pages
- momentumptmt.comDR 965/100 · rank 2028 · 308 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.pranayogastudio.ca from its pages as published, the way a search engine does. It shows summary figures only.
Own www.pranayogastudio.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.pranayogastudio.ca. Removal needs no account and no proof of purchase.