Scanned sites / www.pranayogastudio.ca / 2026-11-10-0403

www.pranayogastudio.ca scan from 2026-11-10 04:03:13 UTC DR 37

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

Scan 2026-11-10-0403

Scanned 2026-11-10 04:03:13 UTC, finished 2026-11-10 04:10:54 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.

65/ 100Needs work

On November 10, 2026 the Site Spider crawled 514 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 (200), title tags (189); 8 checks passed. Most of the points went to meta descriptions (−7.7), heavy assets (−6), title tags (−5.4). 13 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
514
Assets fetched
1064
Status
Completed
Checks with issues
11 of 32
CoverageJob finished, partial coverage

1,578 of 1,578 discovered URLs were fetched, 85 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. 413 link destinations on other sites have not been checked.

  • Title tags189 issues
    189 of 338 pages have title issues. 13 noindex or canonicalized pages excluded.
    −5.4 points
  • Meta descriptions338 issues
    338 of 338 pages have meta description issues. 13 noindex or canonicalized pages excluded.
    −7.7 points
  • Headings288 issues
    288 of 338 pages have heading issues. 13 noindex or canonicalized pages excluded.
    −4.9 points
  • Broken links1 issue
    1 internal link point at 1 broken URL.
    −0.1 points
  • Links to other sitesNot checked
    Not checked: the crawl fetched nothing this check can look at.
  • Redirects160 issues
    161 redirecting URLs, 0 of them chained.
    −1.8 points
  • Non-200 responses3 issues
    166 URLs did not return a 2xx response. 163 of them are pages, 3 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability27 issues
    27 of 351 indexable pages have indexability warnings.
    −0.8 points
  • Image alt text638 issues
    638 of 11615 image references have no alt attribute. 3805 use an empty alt (decorative), which is fine.
    −0.3 points
  • Heavy assets200 issues
    200 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 pages272 issues
    272 pages have no internal links pointing at them.
    −3.1 points
  • Sitemap coverage277 issues
    10 sitemaps listing 344 URLs: 6 crawled pages missing, 0 listed URLs broken or redirecting, 271 reachable only via the sitemap.
    −4.7 points
  • Internal link counts9 noted
    Internal link counts for 351 pages; 9 worth a look.
  • Thin contentOK
    0 of 338 pages have fewer than 200 words. 13 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format77 noted
    77 of 514 page URLs are harder to read, share or cache than they need to be.
  • Canonicals28 noted
    28 of 351 pages have a canonical worth checking.
  • Robots directives351 noted
    351 pages carry a robots directive; 0 carry none.
  • Anchor text141 noted
    141 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure43 noted
    43 of 338 pages could use the title, heading and snippet space better. 13 noindex or canonicalized pages excluded.
  • Image weight and alt length305 noted
    304 images over 100 KB; 1 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.
  • HTML and head validation303 noted
    303 of 351 pages have HTML problems: 299 with head tags outside <head>, 0 over 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    351 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 duplicates2 noted
    2 pages in 1 group read almost the same as another page (95% alike or more).
  • Soft 404s5 noted
    5 pages answer 200 but say they are not there.
  • 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 positions17 noted
    17 of 78 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    6 pages in pagination sequences; 0 with problems.
  • Headers and cookiesOK
    0 cookies set by the site; 12 response headers recorded across 1578 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 351 pages; 296 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 InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling143 noted
    143 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

2884 sites, median 80%, average 79%

www.pranayogastudio.ca scores 65%, higher than 9% of the 2884 scanned sites. See the full ranking.

0761510%: 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%: 1 site37%: 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%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 53 sites70%: 47 sites71%: 80 sites72%: 76 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 131 sites79%: 112 sites80%: 129 sites81%: 125 sites82%: 133 sites83%: 119 sites84%: 130 sites85%: 105 sites86%: 96 sites87%: 94 sites88%: 82 sites89%: 74 sites90%: 56 sites91%: 59 sites92%: 43 sites93%: 30 sites94%: 25 sites95%: 16 sites96%: 19 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 151 sites65% 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

The crawl revealed several areas needing improvement, primarily around broken links, redirects, title tags, and meta descriptions. Addressing these will enhance both user experience and SEO ranking.

  1. 1

    Fix Broken Link

    Why: A broken link can harm user experience and SEO.

    How: Update the internal link found in the crawl to point to the correct URL.

    Checks: broken-links

  2. 2

    Reduce Redirects

    Why: Excessive redirects can slow down page loading and dilute link equity.

    How: Minimize the number of redirects by linking directly to the final URLs instead.

    Checks: redirects

  3. 3

    Update Title Tags

    Why: Optimized title tags improve visibility in search results.

    How: Create unique and relevant title tags for the affected pages according to best practices.

    Checks: titles

  4. 4

    Revise Meta Descriptions

    Why: Unique meta descriptions can increase click-through rates.

    How: Craft unique meta descriptions for each page instead of using a generic one.

    Checks: meta-descriptions

  5. 5

    Address Heading Issues

    Why: Proper heading structure helps SEO and improves readability.

    How: Add a single H1 tag to pages currently missing it and remove extra H1s from others.

    Checks: headings

  6. 6

    Ensure Sitemap Completeness

    Why: Missing pages in your sitemap can lead to indexing issues.

    How: Add the missing URLs to your sitemap file.

    Checks: sitemap-coverage

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 security review reveals several important findings that need addressing, particularly the lack of key security headers. Implementing these protections can significantly enhance the site's resilience against common threats, including data exposure and script vulnerabilities.

  • 0 high
  • 4 medium
  • 3 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on initial connections if they type the URL without https://.

    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: A missing CSP allows unrestricted loading of scripts and resources, increasing the risk of XSS attacks.

    Fix: Add the header: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, your pages could be embedded in frames on other sites, making you vulnerable to clickjacking.

    Fix: Add the header: X-Frame-Options: DENY or SAMEORIGIN

    Evidence: Clickjacking protection

  4. 4

    Leaked Google API KeyMedium

    Why it matters: Exposing API keys in code can lead to misuse if not properly restricted in the developer console.

    Fix: Restrict the API key usage by setting referrer restrictions in the Google Cloud console and remove it from public code.

    Evidence: Keys and secrets in page code

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: The absence of this header may allow browsers to execute files as scripts based on their content, leading to potential exploitation.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-Policy HeaderLow

    Why it matters: Without a Referrer-Policy, full URLs (including sensitive data) are sent to outbound links, risking data exposure.

    Fix: Add the header: Referrer-Policy: no-referrer

    Evidence: Referrer policy

  7. 7

    Mixed Content IssuesLow

    Why it matters: Resources on HTTPS pages loaded over HTTP can lead to man-in-the-middle attacks, compromising the security of the site.

    Fix: Ensure all resources use HTTPS; update URLs in the code to use HTTPS instead of HTTP.

    Evidence: Mixed content

  8. 8

    Missing Permissions-Policy HeaderInfo

    Why it matters: Lacking this header could allow unauthorized access to browser features on your site.

    Fix: Add the header: Permissions-Policy: interest-cohort=(), camera=(), microphone=(), geolocation=()

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

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.