Scanned sites / wpganchor.ca

SEO report for wpganchor.ca DR 1

The latest Site Spider scan of wpganchor.ca, with 1 scan on record. Each scan is at its own address, for example /domain/wpganchor-ca/2026-11-02-0421.

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

Latest scan

Scanned 2026-11-02 04:21:31 UTC, finished 2026-11-02 04:41:26 UTC. Found on page 1 of brave web search results

Site: https://wpganchor.ca/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

88/ 100Good

On November 2, 2026 the Site Spider crawled 1 page and 103 assets of wpganchor.ca, starting from https://wpganchor.ca/. It scored 88 out of 100, a good result. 2 of 33 checks found something to fix, led by meta descriptions (1), redirects (1); 26 checks passed. Most of the points went to meta descriptions (−8), redirects (−4). 5 checks found something the score does not count, listed as noted. 4 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: Medium3 medium, 3 low and 2 info findings. See the security findings ↓

Pages crawled
1
Assets fetched
103
Status
Completed
Checks with issues
2 of 33
CoverageComplete crawl

104 of 105 discovered URLs were fetched, 1 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 6 link destinations on other sites were checked.

  • Title tagsOK
    0 of 1 page have title issues.
  • Meta descriptions1 issue
    1 of 1 page have meta description issues.
    −8 points
  • HeadingsOK
    0 of 1 page have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 noted
    0 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 6 destinations checked.
  • Redirects1 issue
    2 redirecting URLs, 1 of them chained.
    −4 points
  • Non-200 responses2 noted
    2 URLs did not return a 2xx response. 0 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 1 indexable page have indexability warnings.
  • Image alt textOK
    0 of 12 image references have no alt attribute. 4 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 103 fetched assets.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverageOK
    2 sitemaps listing 1 URL: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
  • Internal link countsOK
    Internal link counts for 1 page; none is a dead end or buried.
  • Thin contentOK
    0 of 1 page have fewer than 200 words.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 1 page URL are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 1 page have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 1 page are open to search engines.
  • Anchor text2 noted
    2 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structureOK
    0 of 1 page could use the title, heading and snippet space better.
  • Image weight and alt length4 noted
    4 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 1 page keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    1 of 1 indexable page carry structured data: WebSite (1), Organization (1), ContactPage (1), SearchAction (1). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 1 page with enough text to compare.
  • Soft 404sOK
    None of 1 page 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 positionsOK
    0 of 0 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 10 response headers recorded across 104 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 1 page; 0 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.
  • Spelling1 noted
    1 word an English dictionary does not know, on 1 page. Product names and jargon will appear here too.

Where this site sits among all scanned sites

2553 sites, median 80%, average 78%

wpganchor.ca scores 88%, higher than 83% of the 2553 scanned sites. See the full ranking.

0591180%: 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%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 9 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 12 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 31 sites66%: 37 sites67%: 39 sites68%: 38 sites69%: 48 sites70%: 48 sites71%: 74 sites72%: 72 sites73%: 76 sites74%: 76 sites75%: 78 sites76%: 92 sites77%: 103 sites78%: 115 sites79%: 103 sites80%: 118 sites81%: 111 sites82%: 116 sites83%: 116 sites84%: 118 sites85%: 95 sites86%: 80 sites87%: 85 sites88%: 66 sites89%: 71 sites90%: 47 sites91%: 56 sites92%: 39 sites93%: 28 sites94%: 20 sites95%: 13 sites96%: 15 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites88% 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

Your site has a few areas needing attention, particularly regarding redirects and meta descriptions. Addressing these issues will enhance user experience and search performance.

  1. 1

    Fix Redirect Chains

    Why: Redirect chains can slow down access to your content.

    How: Update links to point directly to https://wpganchor.ca/wp-sitemap.xml and remove the intermediate redirect.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 responses can confuse search engines and hinder usability.

    How: Make the sitemap directly accessible without redirects. Update links to point to the correct assets directly.

    Checks: status-codes

  3. 3

    Improve Meta Description

    Why: A meta description cut-off can affect click-through rates.

    How: Revise the meta description to be shorter than 160 characters to ensure it displays fully in search results.

    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

Your website has several security vulnerabilities that could expose users to risks. Key improvements include implementing HTTP Strict Transport Security, a Content Security Policy, and X-Frame-Options to protect against clickjacking. Other recommended headers include X-Content-Type-Options and Referrer-Policy, which enhance privacy and security.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without HSTS, users can be intercepted on their first request if they don't use HTTPS.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Lack of a CSP allows scripts and styles to load from any source, increasing risk of XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Absence of this header allows your site to be framed, risking clickjacking.

    Fix: Add the header: X-Frame-Options: DENY.

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this header, browsers might execute files based on their content instead of their declared type.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Not having a Referrer-Policy can expose sensitive information in referral headers.

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

    Evidence: Referrer policy

  6. 6

    Third-Party Scripts Without IntegrityLow

    Why it matters: Scripts from other domains can change how your site behaves if they are compromised.

    Fix: Consider using Subresource Integrity (SRI) for scripts from external sources or define them in a CSP.

    Evidence: Third-party scripts

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Without it, scripts could access sensitive features like the microphone or camera.

    Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(), camera=().

    Evidence: Permissions policy

  8. 8

    Private Paths in robots.txtInfo

    Why it matters: Listing private paths can guide malicious users to sensitive areas since robots.txt is public.

    Fix: Consider restricting access to /wp-admin/ with proper authentication instead.

    Evidence: Sensitive paths in robots.txt

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://wpganchor.ca/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 1 HTML page 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://wpganchor.ca/ → 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://wpganchor.ca/ → 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://wpganchor.ca/ → 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://wpganchor.ca/ → 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://wpganchor.ca/ → no permissions-policy
  • NoteThird-party scripts

    Scripts run from 1 other domain 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.)

    • cdn.usefathom.com (1 script tag)
  • 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/
6 checks passed, 2 not applicable
  • OKHTTPS

    All 1 crawled page 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.

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

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

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

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.

Earlier scans of wpganchor.ca

No other scans of this site yet.

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

Own wpganchor.ca?