Scanned sites / www.wearpotatoes.com / 2026-09-15-1803

www.wearpotatoes.com scan from 2026-09-15 18:03:29 UTC DR 4

A newer scan exists. See the latest report for www.wearpotatoes.com.

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

Scan 2026-09-15-1803

Scanned 2026-09-15 18:03:29 UTC, finished 2026-09-15 18:04:09 UTC

Site: http://www.wearpotatoes.com/

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

21/ 100Poor

On September 15, 2026 the Site Spider crawled 8 pages and 58 assets of www.wearpotatoes.com, starting from http://www.wearpotatoes.com/. It scored 21 out of 100, a poor result. 9 of 26 checks found something to fix, led by broken links (6), non-200 responses (6), title tags (2); 13 checks passed. Most of the points went to broken links (−20), title tags (−10), non-200 responses (−10). 4 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: High1 high, 4 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
8
Assets fetched
58
Status
Completed
Checks with issues
9 of 26
CoverageComplete crawl

66 of 66 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript.

  • Title tags2 issues
    2 of 2 pages have title issues.
    −10 points
  • Meta descriptions2 issues
    2 of 2 pages have meta description issues.
    −8 points
  • HeadingsOK
    0 of 2 pages have heading issues.
  • Broken links6 issues
    12 internal links point at 6 broken URLs.
    −20 points
  • Links to other sitesNot checked
    Not checked: the crawl fetched nothing this check can look at.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responses6 issues
    8 URLs did not return a 2xx response. 6 of them are pages, 6 with an error status; the rest are assets or redirects.
    −10 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2 issues
    2 of 2 indexable pages have indexability warnings.
    −10 points
  • Image alt textOK
    0 of 12 image references have no alt attribute. 12 use an empty alt (decorative), which is fine.
  • Heavy assets3 issues
    3 assets larger than 500 KB among 58 fetched assets.
    −1.8 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage1 issue
    No sitemap found. Tried: http://www.wearpotatoes.com/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link countsOK
    Internal link counts for 2 pages; none is a dead end or buried.
  • Thin content2 issues
    2 of 2 pages have fewer than 200 words.
    −8 points
  • Duplicate content8 issues
    2 groups of pages with identical HTML.
    −8 points
  • URL formatOK
    All 8 page URLs are plain lowercase addresses without parameters.
  • Canonicals2 noted
    2 of 2 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 2 pages are open to search engines.
  • Anchor text2 noted
    2 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure2 noted
    2 of 2 pages could use the title, heading and snippet space better.
  • 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 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 2 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; 7 response headers recorded across 66 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 2 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 Insights2 noted
    Mobile performance 66 on average across 2 pages; 2 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2873 sites, median 80%, average 79%

www.wearpotatoes.com scores 21%, higher than 0% of the 2873 scanned sites. See the full ranking.

0751500%: 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%: 9 sites55%: 9 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%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 95 sites87%: 96 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 sites21% 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.

Your website has several critical issues that should be addressed to improve SEO. Focus on fixing broken links, adding a sitemap, enhancing title tags and meta descriptions, and addressing thin and duplicate content.

  1. 1

    Fix Broken Links

    Why: Broken links create poor user experience and impact SEO.

    How: Update or remove links to pages like /about.html and /contact.html that return 404 status.

    Checks: broken-links, status-codes

  2. 2

    Create a Sitemap

    Why: A sitemap helps search engines index your pages more effectively.

    How: Create a sitemap.xml file listing all URLs and upload it to the root directory. Link it in robots.txt.

    Checks: sitemap-coverage

  3. 3

    Enhance Title Tags

    Why: Effective title tags improve click-through rates and search rankings.

    How: Update titles for main pages to be unique and over 30 characters, e.g., 'Welcome to Wear Potatoes - Fresh & Fun Recipes'.

    Checks: titles

  4. 4

    Add Meta Descriptions

    Why: Meta descriptions effectively summarize page content and influence search results.

    How: Create relevant meta descriptions for each page, around 150-160 characters.

    Checks: meta-descriptions

  5. 5

    Address Thin Content

    Why: Improving content depth can enhance user engagement and SEO.

    How: Add informative content to pages, ensuring each has at least 200 words focusing on relevant topics.

    Checks: thin-content

  6. 6

    Resolve Duplicate Content

    Why: Duplicate content confuses search engines and dilutes your page ranking.

    How: Identify and consolidate duplicate pages or use 301 redirects to point to the primary version.

    Checks: duplicate-content

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 site has several security vulnerabilities, primarily due to the lack of HTTPS and essential headers for content protection. It's crucial to implement HTTPS and add security headers to mitigate risks. Additionally, vulnerabilities in JavaScript libraries should be addressed by updating to secure versions.

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

    Lack of HTTPSHigh

    Why it matters: Two pages are accessible over plain HTTP, exposing them to network attacks.

    Fix: Implement HTTPS by installing an SSL certificate and redirect all HTTP traffic to HTTPS.

    Evidence: HTTPS

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Without this policy, scripts and styles can load from any source, increasing the risk of XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Pages can be embedded in frames, leading to clickjacking vulnerabilities.

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

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript LibrariesMedium

    Why it matters: Outdated libraries have known vulnerabilities that could be exploited depending on usage.

    Fix: Upgrade to jQuery 3.5.0, Bootstrap 3.4.1, and Select2 4.0.6.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Exposed Google API KeyMedium

    Why it matters: An exposed API key could be misused, potentially incurring costs or service disruption.

    Fix: Restrict usage of the Google API key by configuring HTTP referrer restrictions in the Google Cloud console.

    Evidence: Keys and secrets in page code

  6. 6

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may misinterpret files and execute them as scripts.

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

    Evidence: MIME sniffing protection

  7. 7

    Missing Referrer-Policy HeaderLow

    Why it matters: Full URLs, including query strings, could be sent to other sites upon visitor navigation.

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

    Evidence: Referrer policy

  8. 8

    Missing Permissions Policy HeaderInfo

    Why it matters: This header limits features the site does not use, reducing risks from injected scripts.

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

    Evidence: Permissions policy

What the checks found

  • FoundHTTPSHigh

    2 pages answered 200 over plain HTTP with no redirect to HTTPS. Anyone on the network path can read or alter these pages.

    • http://www.wearpotatoes.com/ → 200 over http
    • http://www.wearpotatoes.com/index.html → 200 over http
  • FoundContent Security PolicyMedium

    None of the 2 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.

    • http://www.wearpotatoes.com/ → no content-security-policy
    • http://www.wearpotatoes.com/index.html → 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.

    • http://www.wearpotatoes.com/ → no x-frame-options
    • http://www.wearpotatoes.com/index.html → 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.

    • http://www.wearpotatoes.com/ → no x-content-type-options
    • http://www.wearpotatoes.com/index.html → 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.

    • http://www.wearpotatoes.com/ → no referrer-policy
    • http://www.wearpotatoes.com/index.html → 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.

    • http://www.wearpotatoes.com/ → no permissions-policy
    • http://www.wearpotatoes.com/index.html → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

    3 librarys with published vulnerabilities: jQuery 1.11.3, Bootstrap 3.3.6, Select2 4.0.2. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.11.3 in http://www.wearpotatoes.com/js/core.min.js: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • Bootstrap 3.3.6 in http://www.wearpotatoes.com/js/core.min.js: CVE-2016-10735, CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 3.4.1
    • Select2 4.0.2 in http://www.wearpotatoes.com/js/core.min.js: CVE-2016-10744 (XSS in rich selection lists); fixed in 4.0.6
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…ZM (39 chars) in http://www.wearpotatoes.com/js/script.js: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
3 checks passed, 5 not applicable
  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKThird-party scripts

    The sampled pages load no scripts from other domains.

  • Not applicableHTTP Strict Transport Security

    No page was served over HTTPS, so this header does not apply yet.

  • Not applicableCookie flags

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

  • Not applicableMixed content

    No page was served over HTTPS, so mixed content does not apply yet.

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

  • Not applicableSensitive paths in robots.txt

    No robots.txt was fetched.

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

Own www.wearpotatoes.com?

  • 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.wearpotatoes.com. Removal needs no account and no proof of purchase.