Scanned sites / cjtire.com

SEO report for cjtire.com

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

Latest scan

Scanned 10/5/2026, 6:00:01 AM, finished 10/5/2026, 7:06:18 AM. Found on page 3 of chatgpt for browser (api usage) results

Site: https://cjtire.com/

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

54/ 100Needs work

On October 5, 2026 the Site Spider crawled 4999 pages and 167 assets of cjtire.com, starting from https://cjtire.com/. It scored 54 out of 100, a result that needs work. 12 of 23 checks found something to fix, led by meta descriptions (3,646), indexability (2,767), broken links (1,310); 3 checks passed. Most of the points went to meta descriptions (−8), indexability (−7.6), broken links (−7.2). 8 checks 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: Medium4 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
4999
Assets fetched
167
Status
Completed
Checks with issues
12 of 23
CoverageJob finished, partial coverage

5,166 of 5,167 discovered URLs were fetched, 1 blocked by robots.txt, 56,159 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. 25 link destinations on other sites were checked.

  • Title tags1,746 issues
    1746 of 3659 pages have title issues.
    −4.8 points
  • Meta descriptions3,646 issues
    3646 of 3659 pages have meta description issues.
    −8 points
  • Headings3,652 issues
    3652 of 3659 pages have heading issues.
    −6 points
  • Broken links1,310 issues
    1310 internal links point at 1310 broken URLs.
    −7.2 points
  • Links to other sites7,329 noted
    0 destinations answered with an error, 9 could not be determined (timeouts, rate limits or refusals), of 25 destinations checked.
  • Redirects29 issues
    36 redirecting URLs, 0 of them chained.
  • Non-200 responses1,311 issues
    1354 URLs did not return a 2xx response. 1340 of them are pages, 1311 with an error status; the rest are assets or redirects.
    −3.6 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2,767 issues
    2767 of 3659 indexable pages have indexability warnings.
    −7.6 points
  • Image alt text40,955 issues
    40955 of 47223 image references have no alt attribute. 2 use an empty alt (decorative), which is fine.
    −5.2 points
  • Heavy assetsOK
    0 assets larger than 500 KB among 167 fetched assets.
  • Orphan pages116 issues
    116 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage1,048 issues
    1 sitemap listing 2749 URLs: 921 crawled pages missing, 11 listed URLs broken or redirecting, 116 reachable only via the sitemap.
    −1.7 points
  • Internal link counts39 noted
    Internal link counts for 500 pages; 39 worth a look.
  • Thin content124 issues
    124 of 3659 pages have fewer than 200 words.
    −0.3 points
  • Duplicate content477 issues
    104 groups of pages with identical HTML.
    −1 points
  • URL format1 noted
    1 of 4999 page URLs are harder to read, share or cache than they need to be.
  • Canonicals2,767 noted
    2767 of 3659 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 3659 pages are open to search engines.
  • Anchor text4,896 noted
    4896 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure266 noted
    266 of 3659 pages could use the title, heading and snippet space better.
  • Image weight and alt length3 noted
    0 images over 100 KB; 3 with alt text over 100 characters.
  • Response anomalies27 noted
    27 URLs answered in a way worth looking at.

Where this site sits among all scanned sites

2125 sites, median 79%, average 78%

cjtire.com scores 54%, higher than 3% of the 2125 scanned sites. See the full ranking.

0541080%: 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%: 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%: 1 site28%: 0 sites29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 2 sites40%: 2 sites41%: 2 sites42%: 0 sites43%: 2 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 4 sites48%: 4 sites49%: 4 sites50%: 4 sites51%: 5 sites52%: 9 sites53%: 6 sites54%: 9 sites55%: 8 sites56%: 7 sites57%: 11 sites58%: 16 sites59%: 6 sites60%: 14 sites61%: 13 sites62%: 20 sites63%: 23 sites64%: 17 sites65%: 37 sites66%: 29 sites67%: 33 sites68%: 33 sites69%: 36 sites70%: 40 sites71%: 66 sites72%: 72 sites73%: 65 sites74%: 58 sites75%: 73 sites76%: 80 sites77%: 89 sites78%: 94 sites79%: 88 sites80%: 101 sites81%: 100 sites82%: 108 sites83%: 88 sites84%: 96 sites85%: 72 sites86%: 65 sites87%: 62 sites88%: 59 sites89%: 54 sites90%: 33 sites91%: 38 sites92%: 27 sites93%: 22 sites94%: 12 sites95%: 7 sites96%: 5 sites97%: 11 sites98%: 2 sites99%: 1 site100%: 59 sites54% 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 several critical issues affecting SEO, including broken links and non-200 responses. Addressing these will improve user experience and search visibility.

  1. 1

    Fix Broken Links

    Why: Broken links hinder user navigation and SEO rankings.

    How: Identify broken links in the site and ensure they redirect correctly or replace them with working URLs.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 responses harm user accessibility and SEO performance.

    How: Review URLs returning errors (404/500) and fix or remove them; ensure they return a valid response.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Improving titles enhances click-through rates in search results.

    How: Revise titles to meet best practices by making them unique and ensuring appropriate lengths.

    Evidence: 892 pages share the title "View Our Tires | CJ's Tire & Auto", which usually means one template writes it for all of them.

    892 pages affected

    Depends on: If these pages really are the same content, the duplicate title is a symptom: canonicalise them to one URL instead.

    Checks: titles

  4. 4

    Update Meta Descriptions

    Why: Meta descriptions impact click-through rates and relevance in search results.

    How: Create unique meta descriptions for pages missing them; make sure they are compelling and relevant.

    Checks: meta-descriptions

  5. 5

    Repair Sitemap Coverage

    Why: A properly covered sitemap enhances crawl efficiency and visibility.

    How: Ensure all pages are correctly listed or reachable in the sitemap; update or fix broken listings.

    Checks: sitemap-coverage

  6. 6

    Resolve Indexability Issues

    Why: Indexability warnings can prevent search engines from crawling your pages effectively.

    How: Add canonical tags to relevant pages or consolidate duplicate content to ensure proper indexing.

    Evidence: 2767 pages flagged: No canonical.

    2,767 pages affected

    Depends on: Confirm the pages really share a cause before changing them together.

    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

Your website has several security issues that need addressing to better protect user data and enhance resilience against attacks. Most notably, there are missing security headers and cookie protections, along with server version disclosure. Implementing the recommendations will significantly improve your site's security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, initial requests over HTTP can be intercepted.

    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: Absent CSP may allow scripts to load from any source, increasing XSS risks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options for Clickjacking ProtectionMedium

    Why it matters: Without this protection, your pages can be embedded in malicious frames.

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

    Evidence: Clickjacking protection

  4. 4

    Missing Cookie FlagsMedium

    Why it matters: Cookies lacking security flags are vulnerable to attacks like XSS.

    Fix: Set the following flags: Secure, HttpOnly, SameSite=Strict for all cookies.

    Evidence: Cookie flags

  5. 5

    Missing X-Content-Type-Options for MIME Sniffing ProtectionLow

    Why it matters: Without this, browsers may incorrectly interpret file types.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-PolicyLow

    Why it matters: Without a policy, full URLs are shared, including sensitive info when navigating away.

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

    Evidence: Referrer policy

  7. 7

    Server Version DisclosureLow

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

    Fix: Consider configuring your server to display a generic server header.

    Evidence: Software version disclosure

  8. 8

    Missing Permissions-PolicyInfo

    Why it matters: Without this header, browser features are not limited and can be exploited.

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

    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://cjtire.com/ → no strict-transport-security
    • https://cjtire.com/cart/ → no strict-transport-security
    • https://cjtire.com/tires/ → no strict-transport-security
    • https://cjtire.com/tires/make/maxxis/ → no strict-transport-security
    • https://cjtire.com/price-match-guarantee/ → no strict-transport-security
    • https://cjtire.com/pages/protection-plan/ → no strict-transport-security
    • https://cjtire.com/wheels/ → no strict-transport-security
    • https://cjtire.com/schedule-appointment/ → no strict-transport-security
    • https://cjtire.com/services/ → no strict-transport-security
    • https://cjtire.com/stores/ → no strict-transport-security
    • https://cjtire.com/offers/ → no strict-transport-security
    • https://cjtire.com/loyalty-rewards/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 3659 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://cjtire.com/ → no content-security-policy
    • https://cjtire.com/cart/ → no content-security-policy
    • https://cjtire.com/tires/ → no content-security-policy
    • https://cjtire.com/tires/make/maxxis/ → no content-security-policy
    • https://cjtire.com/price-match-guarantee/ → no content-security-policy
    • https://cjtire.com/pages/protection-plan/ → no content-security-policy
    • https://cjtire.com/wheels/ → no content-security-policy
    • https://cjtire.com/schedule-appointment/ → no content-security-policy
    • https://cjtire.com/services/ → no content-security-policy
    • https://cjtire.com/stores/ → no content-security-policy
    • https://cjtire.com/offers/ → no content-security-policy
    • https://cjtire.com/loyalty-rewards/ → 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://cjtire.com/ → no x-frame-options
    • https://cjtire.com/cart/ → no x-frame-options
    • https://cjtire.com/tires/ → no x-frame-options
    • https://cjtire.com/tires/make/maxxis/ → no x-frame-options
    • https://cjtire.com/price-match-guarantee/ → no x-frame-options
    • https://cjtire.com/pages/protection-plan/ → no x-frame-options
    • https://cjtire.com/wheels/ → no x-frame-options
    • https://cjtire.com/schedule-appointment/ → no x-frame-options
    • https://cjtire.com/services/ → no x-frame-options
    • https://cjtire.com/stores/ → no x-frame-options
    • https://cjtire.com/offers/ → no x-frame-options
    • https://cjtire.com/loyalty-rewards/ → 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://cjtire.com/ → no x-content-type-options
    • https://cjtire.com/cart/ → no x-content-type-options
    • https://cjtire.com/tires/ → no x-content-type-options
    • https://cjtire.com/tires/make/maxxis/ → no x-content-type-options
    • https://cjtire.com/price-match-guarantee/ → no x-content-type-options
    • https://cjtire.com/pages/protection-plan/ → no x-content-type-options
    • https://cjtire.com/wheels/ → no x-content-type-options
    • https://cjtire.com/schedule-appointment/ → no x-content-type-options
    • https://cjtire.com/services/ → no x-content-type-options
    • https://cjtire.com/stores/ → no x-content-type-options
    • https://cjtire.com/offers/ → no x-content-type-options
    • https://cjtire.com/loyalty-rewards/ → 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://cjtire.com/ → no referrer-policy
    • https://cjtire.com/cart/ → no referrer-policy
    • https://cjtire.com/tires/ → no referrer-policy
    • https://cjtire.com/tires/make/maxxis/ → no referrer-policy
    • https://cjtire.com/price-match-guarantee/ → no referrer-policy
    • https://cjtire.com/pages/protection-plan/ → no referrer-policy
    • https://cjtire.com/wheels/ → no referrer-policy
    • https://cjtire.com/schedule-appointment/ → no referrer-policy
    • https://cjtire.com/services/ → no referrer-policy
    • https://cjtire.com/stores/ → no referrer-policy
    • https://cjtire.com/offers/ → no referrer-policy
    • https://cjtire.com/loyalty-rewards/ → 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://cjtire.com/ → no permissions-policy
    • https://cjtire.com/cart/ → no permissions-policy
    • https://cjtire.com/tires/ → no permissions-policy
    • https://cjtire.com/tires/make/maxxis/ → no permissions-policy
    • https://cjtire.com/price-match-guarantee/ → no permissions-policy
    • https://cjtire.com/pages/protection-plan/ → no permissions-policy
    • https://cjtire.com/wheels/ → no permissions-policy
    • https://cjtire.com/schedule-appointment/ → no permissions-policy
    • https://cjtire.com/services/ → no permissions-policy
    • https://cjtire.com/stores/ → no permissions-policy
    • https://cjtire.com/offers/ → no permissions-policy
    • https://cjtire.com/loyalty-rewards/ → 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: Microsoft-IIS/8.0 (181 responses)
  • FoundCookie flagsMedium

    3 of 3 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.

    • __CHARLIEAUTH (set by https://cjtire.com/) lacks Secure, HttpOnly, SameSite
    • __FORMSAUTH (set by https://cjtire.com/) lacks Secure, HttpOnly, SameSite
    • ASP.NET_SessionId (set by https://cjtire.com/offers/) lacks Secure
  • NoteThird-party scripts

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

    • cdnjs.cloudflare.com (40 script tags)
    • www.googletagmanager.com (120 script tags)
    • www.r2cthemes.com (8 script tags)
    • www.google.com (2 script tags)
    • static.ridestyler.net (1 script tag)
    • api.ridestyler.net (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: /admin/
6 checks passed
  • OKHTTPS

    All 3659 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

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

No other scans of this site yet.

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

Own cjtire.com?

cjtire.com SEO report | DIY SEO Hub