Scanned sites / www.travelingspud.com / 2026-10-03-1633

www.travelingspud.com scan from 10/3/2026, 4:33:03 PM

Scan 2026-10-03-1633

Scanned 10/3/2026, 4:33:03 PM, finished 10/4/2026, 1:59:27 AM. Found on page 1 of brave web search results

Site: https://www.travelingspud.com/

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

77/ 100Good

On October 3, 2026 the Site Spider crawled 1475 pages and 1088 assets of www.travelingspud.com, starting from https://www.travelingspud.com/. It scored 77 out of 100, a good result. 13 of 16 checks found something to fix, led by heavy assets (213), sitemap coverage (946), meta descriptions (669); 2 checks passed. Most of the points went to heavy assets (−6), sitemap coverage (−4.8), meta descriptions (−4.5). 1 check found something the score does not count, listed as noted. 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 and 2 low findings. See the security findings ↓

Pages crawled
1475
Assets fetched
1088
Status
Completed
Checks with issues
13 of 16
CoverageJob finished, partial coverage

2,563 of 2,563 discovered URLs were fetched, 26,824 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. 300 link destinations on other sites were checked, 4917 left unchecked.

  • Title tags207 issues
    207 of 946 pages have title issues. 239 noindex or canonicalized pages excluded.
    −1.7 points
  • Meta descriptions669 issues
    669 of 946 pages have meta description issues. 239 noindex or canonicalized pages excluded.
    −4.5 points
  • Headings28 issues
    28 of 946 pages have heading issues. 239 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken links98 issues
    125 internal links point at 98 broken URLs.
    −1.7 points
  • Links to other sites13 issues
    13 destinations answered with an error, 110 could not be determined (timeouts, rate limits or refusals), 4917 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.4 points
  • Redirects193 issues
    191 redirecting URLs, 16 of them chained.
    −0.7 points
  • Non-200 responses100 issues
    291 URLs did not return a 2xx response. 290 of them are pages, 100 with an error status; the rest are assets or redirects.
    −0.8 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability14 issues
    14 of 1018 indexable pages have indexability warnings. 167 pages noindex by design.
    −0.1 points
  • Image alt textOK
    0 of 16130 image references have no alt attribute. 4841 use an empty alt (decorative), which is fine.
  • Heavy assets213 issues
    213 assets larger than 500 KB among 1088 fetched assets.
    −6 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage946 issues
    1 sitemap listing 0 URLs: 946 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −4.8 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin content224 issues
    224 of 946 pages have fewer than 200 words. 239 noindex or canonicalized pages excluded.
    −1.5 points
  • Duplicate content100 issues
    2 groups of pages with identical HTML.
    −0.7 points

Where this scan sits among all scanned sites

2051 sites, median 80%, average 78%

www.travelingspud.com scores 77%, higher than 37% of the 2051 scanned sites. See the full ranking.

0521040%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 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%: 2 sites38%: 2 sites39%: 1 site40%: 2 sites41%: 3 sites42%: 0 sites43%: 1 site44%: 1 site45%: 4 sites46%: 4 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 3 sites52%: 9 sites53%: 6 sites54%: 8 sites55%: 6 sites56%: 6 sites57%: 7 sites58%: 14 sites59%: 6 sites60%: 10 sites61%: 14 sites62%: 16 sites63%: 19 sites64%: 16 sites65%: 28 sites66%: 24 sites67%: 39 sites68%: 34 sites69%: 24 sites70%: 46 sites71%: 48 sites72%: 64 sites73%: 57 sites74%: 57 sites75%: 73 sites76%: 83 sites77%: 76 sites78%: 96 sites79%: 78 sites80%: 104 sites81%: 102 sites82%: 99 sites83%: 91 sites84%: 87 sites85%: 74 sites86%: 76 sites87%: 66 sites88%: 68 sites89%: 51 sites90%: 39 sites91%: 39 sites92%: 32 sites93%: 18 sites94%: 14 sites95%: 10 sites96%: 6 sites97%: 9 sites98%: 1 site99%: 2 sites100%: 56 sites77% 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 website has several SEO issues requiring attention. Prioritize fixing broken links, improving redirects, and addressing title and meta description issues for better performance.

  1. 1

    Fix Broken Links

    Why: Addressing broken links improves user experience and keeps search engines from encountering errors.

    How: Identify and update or remove the links pointing to broken URLs. Ensure a clean internal linking structure.

    Checks: broken-links

  2. 2

    Streamline Redirects

    Why: Reducing redirects enhances page load speed and user experience.

    How: Eliminate chained redirects by updating links to point directly to the final destination.

    Checks: redirects

  3. 3

    Resolve Non-200 Responses

    Why: Fixing errors prevents users from landing on dead pages and improves indexability.

    How: Identify affected URLs, rectify issues causing non-200 responses, and ensure all pages return a 200 status.

    Checks: status-codes

  4. 4

    Improve Title Tags

    Why: Enhancing title tags is crucial for better visibility and click-through rates.

    How: Revise titles to follow SEO best practices—keep them under 60 characters and descriptive.

    Checks: titles

  5. 5

    Enhance Meta Descriptions

    Why: Well-crafted meta descriptions increase click-through rates from search results.

    How: Create unique and compelling meta descriptions for pages missing them, ensuring they are under 160 characters.

    Checks: meta-descriptions

  6. 6

    Update Sitemap

    Why: An updated sitemap ensures that all relevant pages are indexed properly.

    How: Generate a new sitemap that includes all current pages and submit it to search engines.

    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 website has several security issues that need immediate attention. Key vulnerabilities include the absence of HTTP Strict Transport Security, missing cookie security flags, and exposure of server version details. Addressing these would significantly enhance the site's security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

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

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Cookies Missing Protective FlagsMedium

    Why it matters: Cookies are vulnerable without HttpOnly, Secure, and SameSite attributes.

    Fix: Set the cookies with `Secure`, `HttpOnly`, and `SameSite=Lax` attributes.

    Evidence: Cookie flags

  3. 3

    Server Version DisclosureLow

    Why it matters: Revealing the server version can help attackers find and exploit known vulnerabilities.

    Fix: Remove or alter the `Server` and `X-Powered-By` headers. Consider using `Server: nginx` without version details.

    Evidence: Software version disclosure

  4. 4

    Third-Party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from external domains can be altered, introducing security risks without integrity checks.

    Fix: Implement Subresource Integrity (SRI) where possible or use a Content-Security-Policy that restricts scripts to trusted sources.

    Evidence: Third-party scripts

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.travelingspud.com/ → no strict-transport-security
    • https://www.travelingspud.com/about/ → no strict-transport-security
    • https://www.travelingspud.com/work-with-me/ → no strict-transport-security
    • https://www.travelingspud.com/destinations/ → no strict-transport-security
    • https://www.travelingspud.com/tag/north-america/ → no strict-transport-security
    • https://www.travelingspud.com/tag/alabama/ → no strict-transport-security
    • https://www.travelingspud.com/tag/alaska/ → no strict-transport-security
    • https://www.travelingspud.com/tag/arizona/ → no strict-transport-security
    • https://www.travelingspud.com/tag/california/ → no strict-transport-security
    • https://www.travelingspud.com/tag/canada/ → no strict-transport-security
    • https://www.travelingspud.com/tag/hawaii/ → no strict-transport-security
    • https://www.travelingspud.com/tag/florida/ → no strict-transport-security
  • FoundSoftware version disclosureLow

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

    • server: nginx (2563 responses)
    • x-powered-by: PHP/8.2.34 (1302 responses)
  • FoundCookie flagsMedium

    9 of 9 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • wordpress_test_cookie (set by https://www.travelingspud.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.travel…) lacks SameSite
    • wordpress_5f5032564d2e9af4f715dfac445cc2f5 (set by https://www.travelingspud.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.travel…) lacks Secure, HttpOnly, SameSite
    • wordpress_sec_5f5032564d2e9af4f715dfac445cc2f5 (set by https://www.travelingspud.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.travel…) lacks Secure, HttpOnly, SameSite
    • wordpress_logged_in_5f5032564d2e9af4f715dfac445cc2f5 (set by https://www.travelingspud.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.travel…) lacks Secure, HttpOnly, SameSite
    • wp-settings-0 (set by https://www.travelingspud.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.travel…) lacks Secure, HttpOnly, SameSite
    • wp-settings-time-0 (set by https://www.travelingspud.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.travel…) lacks Secure, HttpOnly, SameSite
    • wordpressuser_5f5032564d2e9af4f715dfac445cc2f5 (set by https://www.travelingspud.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.travel…) lacks Secure, HttpOnly, SameSite
    • wordpresspass_5f5032564d2e9af4f715dfac445cc2f5 (set by https://www.travelingspud.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.travel…) lacks Secure, HttpOnly, SameSite
    • wp-postpass_5f5032564d2e9af4f715dfac445cc2f5 (set by https://www.travelingspud.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.travel…) lacks Secure, HttpOnly, SameSite
  • 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.)

    • scripts.mediavine.com (40 script tags)
    • www.googletagmanager.com (40 script tags)
    • traveling-spud.kit.com (82 script tags)
    • www.travelpayouts.com (40 script tags)
12 checks passed
  • OKHTTPS

    All 1185 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 3 of 1185 pages.

  • OKClickjacking protection

    x-frame-options is set on all 1185 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 1185 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 1185 HTML pages.

  • OKPermissions policy

    permissions-policy is set on all 1185 HTML pages.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    1 library version 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.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

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

Their neighbours in the SEO rank table, which orders every scanned site by health score.

This report was produced by the DIY SEO Hub Site Spider crawling www.travelingspud.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.travelingspud.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.travelingspud.com. Removal needs no account and no proof of purchase.
www.travelingspud.com scan 2026-10-03-1633 | DIY SEO Hub