Scanned sites / saskflowers.com

SEO report for saskflowers.com DR 0

The latest Site Spider scan of saskflowers.com, with 1 scan on record. Each scan is at its own address, for example /domain/saskflowers-com/2026-09-10-0432.

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

Latest scan

Scanned 2026-09-10 04:32:36 UTC, finished 2026-09-10 10:29:55 UTC

Site: https://saskflowers.com/

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

78/ 100Good

On September 10, 2026 the Site Spider crawled 215 pages and 1116 assets of saskflowers.com, starting from https://saskflowers.com/. It scored 78 out of 100, a good result. 11 of 26 checks found something to fix, led by meta descriptions (205), heavy assets (100), sitemap coverage (205); 6 checks passed. Most of the points went to meta descriptions (−7.9), heavy assets (−6), sitemap coverage (−5.9). 9 checks found something the score does not count, listed as noted. 11 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: Medium2 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
215
Assets fetched
1116
Status
Completed
Checks with issues
11 of 26
CoverageJob finished, partial coverage

1,331 of 1,332 discovered URLs were fetched, 1 blocked by robots.txt, 1,237 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. 6 link destinations on other sites were checked.

  • Title tags16 issues
    16 of 205 pages have title issues. 3 noindex or canonicalized pages excluded.
    −0.8 points
  • Meta descriptions205 issues
    205 of 205 pages have meta description issues. 3 noindex or canonicalized pages excluded.
    −7.9 points
  • Headings3 issues
    3 of 205 pages have heading issues. 3 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken links1 issue
    1 internal link point at 1 broken URL.
    −0.1 points
  • Links to other sites625 noted
    0 destinations answered with an error, 4 could not be determined (timeouts, rate limits or refusals), of 5 destinations checked.
  • Redirects6 issues
    7 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses1 issue
    8 URLs did not return a 2xx response. 7 of them are pages, 1 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability17 issues
    17 of 205 indexable pages have indexability warnings. 3 pages noindex by design.
    −0.8 points
  • Image alt textOK
    0 of 2580 image references have no alt attribute. 1416 use an empty alt (decorative), which is fine.
  • Heavy assets100 issues
    100 assets larger than 500 KB among 1116 fetched assets.
    −6 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage205 issues
    1 sitemap listing 0 URLs: 205 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.9 points
  • Internal link counts69 noted
    Internal link counts for 208 pages; 69 worth a look.
  • Thin content4 issues
    4 of 205 pages have fewer than 200 words. 3 noindex or canonicalized pages excluded.
    −0.2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format1 noted
    1 of 215 page URLs are harder to read, share or cache than they need to be.
  • Canonicals18 noted
    18 of 208 pages have a canonical worth checking.
  • Robots directives208 noted
    208 pages carry a robots directive; 0 carry none.
  • Anchor text167 noted
    167 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure201 noted
    201 of 205 pages could use the title, heading and snippet space better. 3 noindex or canonicalized pages excluded.
  • Image weight and alt length120 noted
    120 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 208 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 13 response headers recorded across 1331 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 208 pages; 112 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.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this site sits among all scanned sites

2315 sites, median 79%, average 78%

saskflowers.com scores 78%, higher than 42% of the 2315 scanned sites. See the full ranking.

0571140%: 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%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 46 sites70%: 44 sites71%: 68 sites72%: 70 sites73%: 69 sites74%: 68 sites75%: 72 sites76%: 86 sites77%: 92 sites78%: 106 sites79%: 86 sites80%: 106 sites81%: 105 sites82%: 114 sites83%: 98 sites84%: 108 sites85%: 85 sites86%: 69 sites87%: 74 sites88%: 58 sites89%: 62 sites90%: 35 sites91%: 44 sites92%: 37 sites93%: 23 sites94%: 16 sites95%: 11 sites96%: 9 sites97%: 12 sites98%: 4 sites99%: 1 site100%: 70 sites78% 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

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

There are critical SEO issues on your site including broken links, redirects, and missing meta descriptions. Addressing these will significantly improve your site's performance and visibility.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and SEO.

    How: Update the link from https://saskflowers.com/account/ to a valid URL.

    Checks: broken-links

  2. 2

    Review Redirects

    Why: Excessive redirects can confuse both users and search engines.

    How: Ensure all 301 redirects direct to the correct URLs without relying on outdated pages.

    Checks: redirects

  3. 3

    Resolve Non-200 Responses

    Why: Pages returning errors can negatively impact SEO.

    How: Fix the issues for the 8 URLs not returning 2xx responses.

    Checks: status-codes

  4. 4

    Implement Title Tags

    Why: Improved title tags enhance click-through rates.

    How: Add or rewrite title tags for 16 pages to meet optimal length and relevance.

    Checks: titles

  5. 5

    Add Meta Descriptions

    Why: Meta descriptions improve search engine results visibility.

    How: Create meaningful meta descriptions for all 205 pages.

    Checks: meta-descriptions

  6. 6

    Address Indexability Issues

    Why: Properly indexed pages rank better in search results.

    How: Add canonical tags to 17 indexable pages as required.

    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 crawl

The website saskflowers.com lacks crucial security headers, exposing it to potential interceptions, clickjacking, and MIME type sniffing. Addressing these issues is critical to enhance visitor protection. Additionally, third-party scripts could compromise site security, and sensitive paths in the robots.txt file may reveal private information.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users are vulnerable to interception if they type the address without 'https://'.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-Options HeaderMedium

    Why it matters: Lack of this header allows for clickjacking attacks where malicious sites overlay controls on your pages.

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

    Evidence: Clickjacking protection

  3. 3

    Missing X-Content-Type-Options HeaderLow

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

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

    Evidence: MIME sniffing protection

  4. 4

    Risk from Third-party ScriptsLow

    Why it matters: Scripts from external domains without Subresource Integrity can be compromised, affecting your site.

    Fix: Consider using Subresource Integrity or a Content-Security-Policy (CSP) to restrict sources.

    Evidence: Third-party scripts

  5. 5

    Sensitive Paths in robots.txtInfo

    Why it matters: Exposing private paths in robots.txt can lead potential attackers to sensitive areas.

    Fix: Implement proper access controls instead of relying on robots.txt for sensitive information.

    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://saskflowers.com/ → no strict-transport-security
    • https://saskflowers.com/account/ → no strict-transport-security
    • https://saskflowers.com/shopping-cart/ → no strict-transport-security
    • https://saskflowers.com/collections/occasion/seasonal-arrangements/ → no strict-transport-security
    • https://saskflowers.com/collections/wrapped-bouquets/ → no strict-transport-security
    • https://saskflowers.com/collections/occasion/condolences/ → no strict-transport-security
    • https://saskflowers.com/collections/occasion/ → no strict-transport-security
    • https://saskflowers.com/collections/occasion/anniversary/ → no strict-transport-security
    • https://saskflowers.com/collections/occasion/birthday/ → no strict-transport-security
    • https://saskflowers.com/collections/occasion/get-well/ → no strict-transport-security
    • https://saskflowers.com/collections/occasion/congratulations/ → no strict-transport-security
    • https://saskflowers.com/collections/occasion/just-because/ → no strict-transport-security
  • FoundClickjacking protectionMedium

    2 of 208 HTML pages send 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://saskflowers.com/ → no x-frame-options
    • https://saskflowers.com/shopping-cart/ → no x-frame-options
    • https://saskflowers.com/collections/occasion/seasonal-arrangements/ → no x-frame-options
    • https://saskflowers.com/collections/wrapped-bouquets/ → no x-frame-options
    • https://saskflowers.com/collections/occasion/condolences/ → no x-frame-options
    • https://saskflowers.com/collections/occasion/ → no x-frame-options
    • https://saskflowers.com/collections/occasion/anniversary/ → no x-frame-options
    • https://saskflowers.com/collections/occasion/birthday/ → no x-frame-options
    • https://saskflowers.com/collections/occasion/get-well/ → no x-frame-options
    • https://saskflowers.com/collections/occasion/congratulations/ → no x-frame-options
    • https://saskflowers.com/collections/occasion/just-because/ → no x-frame-options
    • https://saskflowers.com/collections/occasion/newborn/ → 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://saskflowers.com/ → no x-content-type-options
    • https://saskflowers.com/account/ → no x-content-type-options
    • https://saskflowers.com/shopping-cart/ → no x-content-type-options
    • https://saskflowers.com/collections/occasion/seasonal-arrangements/ → no x-content-type-options
    • https://saskflowers.com/collections/wrapped-bouquets/ → no x-content-type-options
    • https://saskflowers.com/collections/occasion/condolences/ → no x-content-type-options
    • https://saskflowers.com/collections/occasion/ → no x-content-type-options
    • https://saskflowers.com/collections/occasion/anniversary/ → no x-content-type-options
    • https://saskflowers.com/collections/occasion/birthday/ → no x-content-type-options
    • https://saskflowers.com/collections/occasion/get-well/ → no x-content-type-options
    • https://saskflowers.com/collections/occasion/congratulations/ → no x-content-type-options
    • https://saskflowers.com/collections/occasion/just-because/ → no x-content-type-options
  • NoteThird-party scripts

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

    • www.googletagmanager.com (40 script tags)
    • challenges.cloudflare.com (40 script tags)
  • 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/
8 checks passed, 3 not applicable
  • OKHTTPS

    All 208 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 2 of 208 pages.

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

  • OKForms over HTTPS

    196 forms found, all on HTTPS pages posting to HTTPS addresses.

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

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 saskflowers.com

No other scans of this site yet.

Sites scoring near saskflowers.com

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

Own saskflowers.com?