Scanned sites / www.branderco.ca / 2026-11-02-1712

www.branderco.ca scan from 2026-11-02 17:12:17 UTC DR 0

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

Scan 2026-11-02-1712

Scanned 2026-11-02 17:12:17 UTC, finished 2026-11-02 17:32:10 UTC. Found on page 3 of brave web search results

Site: https://www.branderco.ca/

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

57/ 100Needs work

On November 2, 2026 the Site Spider crawled 125 pages and 89 assets of www.branderco.ca, starting from https://www.branderco.ca/. It scored 57 out of 100, a result that needs work. 11 of 33 checks found something to fix, led by title tags (26), meta descriptions (26), sitemap coverage (62); 12 checks passed. Most of the points went to title tags (−9.6), meta descriptions (−7.7), sitemap coverage (−6). 10 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, 4 low and 1 info findings. See the security findings ↓

Pages crawled
125
Assets fetched
89
Status
Completed
Checks with issues
11 of 33
CoverageComplete crawl

214 of 214 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 8 link destinations on other sites were checked.

  • Title tags26 issues
    26 of 26 pages have title issues. 1 noindex or canonicalized page excluded.
    −9.6 points
  • Meta descriptions26 issues
    26 of 26 pages have meta description issues. 1 noindex or canonicalized page excluded.
    −7.7 points
  • Headings11 issues
    11 of 26 pages have heading issues. 1 noindex or canonicalized page excluded.
    −2.4 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites57 noted
    0 destinations answered with an error, 5 could not be determined (timeouts, rate limits or refusals), of 8 destinations checked.
  • Redirects45 issues
    89 redirecting URLs, 0 of them chained.
    −4 points
  • Non-200 responses11 issues
    100 URLs did not return a 2xx response. 98 of them are pages, 11 with an error status; the rest are assets or redirects.
    −4.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability1 issue
    1 of 27 indexable pages have indexability warnings.
    −0.4 points
  • Image alt textOK
    0 of 130 image references have no alt attribute. 4 use an empty alt (decorative), which is fine.
  • Heavy assets9 issues
    9 assets larger than 500 KB among 89 fetched assets.
    −5.4 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage62 issues
    9 sitemaps listing 82 URLs: 0 crawled pages missing, 60 listed URLs broken or redirecting, 2 reachable only via the sitemap.
    −6 points
  • Internal link countsOK
    Internal link counts for 27 pages; none is a dead end or buried.
  • Thin content1 issue
    1 of 26 pages have fewer than 200 words. 1 noindex or canonicalized page excluded.
    −0.3 points
  • Duplicate content11 issues
    1 group of pages with identical HTML.
    −3.3 points
  • URL format54 noted
    54 of 125 page URLs are harder to read, share or cache than they need to be.
  • Canonicals1 noted
    1 of 27 pages have a canonical worth checking.
  • Robots directives27 noted
    27 pages carry a robots directive; 0 carry none.
  • Anchor text45 noted
    45 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure1 noted
    1 of 26 pages could use the title, heading and snippet space better. 1 noindex or canonicalized page 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 validation27 noted
    27 of 27 pages have HTML problems: 27 with head tags outside <head>, 0 over 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    27 of 26 indexable pages carry structured data: WebSite (27), Organization (27), BreadcrumbList (26), ListItem (26), WebPage (18). 0 pages with errors a rich result would fail on.
  • Near duplicates5 noted
    5 pages in 2 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 27 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 positions6 noted
    6 of 25 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; 12 response headers recorded across 214 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 27 pages; 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.
  • Spelling3 noted
    3 words an English dictionary does not know, on 6 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2633 sites, median 80%, average 78%

www.branderco.ca scores 57%, higher than 4% of the 2633 scanned sites. See the full ranking.

0611210%: 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%: 5 sites46%: 5 sites47%: 5 sites48%: 5 sites49%: 8 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 10 sites55%: 10 sites56%: 7 sites57%: 15 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 31 sites66%: 39 sites67%: 39 sites68%: 37 sites69%: 48 sites70%: 48 sites71%: 75 sites72%: 73 sites73%: 79 sites74%: 77 sites75%: 83 sites76%: 95 sites77%: 106 sites78%: 118 sites79%: 107 sites80%: 121 sites81%: 117 sites82%: 120 sites83%: 118 sites84%: 121 sites85%: 98 sites86%: 88 sites87%: 88 sites88%: 71 sites89%: 72 sites90%: 48 sites91%: 56 sites92%: 41 sites93%: 28 sites94%: 22 sites95%: 14 sites96%: 16 sites97%: 15 sites98%: 7 sites99%: 2 sites100%: 69 sites57% 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 significant SEO issues that need to be resolved, including redirects, title and meta description issues, and indexability warnings. Prioritize these fixes for improved performance.

  1. 1

    Fix Redirects

    Why: Redirecting URLs can create unnecessary page loading times and negatively affect SEO.

    How: Update the URLs to prevent unnecessary redirects, linking to the final URLs directly.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: 100 URLs not returning 2xx status can result in a poor user experience and lower rankings.

    How: Evaluate and fix the URLs that return errors or create a redirection chain.

    Checks: status-codes

  3. 3

    Add Title Tags

    Why: Missing or long title tags can hurt search visibility and click-through rates.

    How: Create concise title tags for all 25 pages with issues, ensuring they are under 60 characters.

    Checks: titles

  4. 4

    Implement Meta Descriptions

    Why: Missing meta descriptions can reduce click-through rates from search results.

    How: Craft unique meta descriptions for the 25 pages currently lacking them, under 160 characters.

    Checks: meta-descriptions

  5. 5

    Add H1 Headings

    Why: Missing H1 headings prevent proper content hierarchy and may affect SEO.

    How: Include relevant H1 headings on the 11 pages that currently lack them.

    Checks: headings

  6. 6

    Shrink Heavy Assets

    Why: Large assets impact load times, which can affect user experience and SEO.

    How: Compress or optimize the 9 large assets to improve loading speed.

    Evidence: 33.6 KB of script, loaded by 27 pages, so every visitor to any of them downloads it.

    27 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    Checks: heavy-assets

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 website lacks essential security headers, exposing it to various vulnerabilities such as interception and clickjacking. Immediate implementation of HTTP Strict Transport Security, Content Security Policy, X-Frame-Options, and other headers is crucial for enhancing security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users typing the site address without HTTPS can be intercepted on the first request.

    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: Absence of CSP allows unrestricted loading of scripts, styles, and frames, increasing XSS risks.

    Fix: Add a CSP header such as: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options (Clickjacking Protection)Medium

    Why it matters: Without this protection, your pages can be embedded in frames on other sites, risking clickjacking.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options (MIME Sniffing Protection)Low

    Why it matters: Omitting this header may allow a browser to execute files based on content types rather than declared types.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Lack of a referrer policy exposes full page addresses to sites users navigate to.

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

    Evidence: Referrer policy

  6. 6

    Server Version DisclosureLow

    Why it matters: The server response reveals its version, which can be exploited by attackers for known vulnerabilities.

    Fix: To reduce exposure, consider using: Server: [your web server name, omitting version]

    Evidence: Software version disclosure

  7. 7

    Mixed Content IssuesLow

    Why it matters: Loading resources over HTTP on HTTPS pages can lead to security warnings and potential man-in-the-middle attacks.

    Fix: Change the URLs of these resources to HTTPS.

    Evidence: Mixed content

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Absence of this policy leaves browser features like camera or geolocation available to potentially harmful scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(), 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://www.branderco.ca/ → no strict-transport-security
    • https://www.branderco.ca/services/ → no strict-transport-security
    • https://www.branderco.ca/just-starting-up/ → no strict-transport-security
    • https://www.branderco.ca/up-and-running/ → no strict-transport-security
    • https://www.branderco.ca/well-established/ → no strict-transport-security
    • https://www.branderco.ca/transitioning-to-retirement/ → no strict-transport-security
    • https://www.branderco.ca/about-us/ → no strict-transport-security
    • https://www.branderco.ca/about-us/meet-the-team/ → no strict-transport-security
    • https://www.branderco.ca/about-us/client-testimonials/ → no strict-transport-security
    • https://www.branderco.ca/about-us/careers/ → no strict-transport-security
    • https://www.branderco.ca/category/blog/ → no strict-transport-security
    • https://www.branderco.ca/contact-us/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 27 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.branderco.ca/ → no content-security-policy
    • https://www.branderco.ca/services/ → no content-security-policy
    • https://www.branderco.ca/just-starting-up/ → no content-security-policy
    • https://www.branderco.ca/up-and-running/ → no content-security-policy
    • https://www.branderco.ca/well-established/ → no content-security-policy
    • https://www.branderco.ca/transitioning-to-retirement/ → no content-security-policy
    • https://www.branderco.ca/about-us/ → no content-security-policy
    • https://www.branderco.ca/about-us/meet-the-team/ → no content-security-policy
    • https://www.branderco.ca/about-us/client-testimonials/ → no content-security-policy
    • https://www.branderco.ca/about-us/careers/ → no content-security-policy
    • https://www.branderco.ca/category/blog/ → no content-security-policy
    • https://www.branderco.ca/contact-us/ → 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.branderco.ca/ → no x-frame-options
    • https://www.branderco.ca/services/ → no x-frame-options
    • https://www.branderco.ca/just-starting-up/ → no x-frame-options
    • https://www.branderco.ca/up-and-running/ → no x-frame-options
    • https://www.branderco.ca/well-established/ → no x-frame-options
    • https://www.branderco.ca/transitioning-to-retirement/ → no x-frame-options
    • https://www.branderco.ca/about-us/ → no x-frame-options
    • https://www.branderco.ca/about-us/meet-the-team/ → no x-frame-options
    • https://www.branderco.ca/about-us/client-testimonials/ → no x-frame-options
    • https://www.branderco.ca/about-us/careers/ → no x-frame-options
    • https://www.branderco.ca/category/blog/ → no x-frame-options
    • https://www.branderco.ca/contact-us/ → 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.branderco.ca/ → no x-content-type-options
    • https://www.branderco.ca/services/ → no x-content-type-options
    • https://www.branderco.ca/just-starting-up/ → no x-content-type-options
    • https://www.branderco.ca/up-and-running/ → no x-content-type-options
    • https://www.branderco.ca/well-established/ → no x-content-type-options
    • https://www.branderco.ca/transitioning-to-retirement/ → no x-content-type-options
    • https://www.branderco.ca/about-us/ → no x-content-type-options
    • https://www.branderco.ca/about-us/meet-the-team/ → no x-content-type-options
    • https://www.branderco.ca/about-us/client-testimonials/ → no x-content-type-options
    • https://www.branderco.ca/about-us/careers/ → no x-content-type-options
    • https://www.branderco.ca/category/blog/ → no x-content-type-options
    • https://www.branderco.ca/contact-us/ → 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.branderco.ca/ → no referrer-policy
    • https://www.branderco.ca/services/ → no referrer-policy
    • https://www.branderco.ca/just-starting-up/ → no referrer-policy
    • https://www.branderco.ca/up-and-running/ → no referrer-policy
    • https://www.branderco.ca/well-established/ → no referrer-policy
    • https://www.branderco.ca/transitioning-to-retirement/ → no referrer-policy
    • https://www.branderco.ca/about-us/ → no referrer-policy
    • https://www.branderco.ca/about-us/meet-the-team/ → no referrer-policy
    • https://www.branderco.ca/about-us/client-testimonials/ → no referrer-policy
    • https://www.branderco.ca/about-us/careers/ → no referrer-policy
    • https://www.branderco.ca/category/blog/ → no referrer-policy
    • https://www.branderco.ca/contact-us/ → 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.branderco.ca/ → no permissions-policy
    • https://www.branderco.ca/services/ → no permissions-policy
    • https://www.branderco.ca/just-starting-up/ → no permissions-policy
    • https://www.branderco.ca/up-and-running/ → no permissions-policy
    • https://www.branderco.ca/well-established/ → no permissions-policy
    • https://www.branderco.ca/transitioning-to-retirement/ → no permissions-policy
    • https://www.branderco.ca/about-us/ → no permissions-policy
    • https://www.branderco.ca/about-us/meet-the-team/ → no permissions-policy
    • https://www.branderco.ca/about-us/client-testimonials/ → no permissions-policy
    • https://www.branderco.ca/about-us/careers/ → no permissions-policy
    • https://www.branderco.ca/category/blog/ → no permissions-policy
    • https://www.branderco.ca/contact-us/ → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: Apache/2 (214 responses)
  • FoundMixed contentLow

    2 resources on HTTPS pages are loaded over plain HTTP.

    • https://www.branderco.ca/up-and-running/ loads image http://www.branderco.ca/wp-content/uploads/2017/03/brander-client-2.jpg
    • https://www.branderco.ca/well-established/ loads image http://www.branderco.ca/wp-content/uploads/2017/03/brander-client-3.jpg
  • NoteThird-party scripts

    Scripts run from 4 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.)

    • c0.wp.com (88 script tags)
    • www.googletagmanager.com (54 script tags)
    • stats.wp.com (27 script tags)
    • www.google.com (1 script tag)
5 checks passed, 2 not applicable
  • OKHTTPS

    All 27 crawled pages were served over HTTPS.

  • OKForms over HTTPS

    1 form found, all on HTTPS pages posting to HTTPS addresses.

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

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

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

Own www.branderco.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.branderco.ca. Removal needs no account and no proof of purchase.