Scanned sites / www.avenuedentalcares.com / 2026-11-04-0334

www.avenuedentalcares.com scan from 2026-11-04 03:34:56 UTC DR 0

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

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

Scan 2026-11-04-0334

Scanned 2026-11-04 03:34:56 UTC, finished 2026-11-04 03:51:34 UTC. Found with openstreetmap overpass

Site: https://www.avenuedentalcares.com/

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

83/ 100Good

On November 4, 2026 the Site Spider crawled 89 pages and 280 assets of www.avenuedentalcares.com, starting from https://www.avenuedentalcares.com/. It scored 83 out of 100, a good result. 11 of 33 checks found something to fix, led by heavy assets (10), meta descriptions (34), title tags (22); 12 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−3.2), title tags (−2.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: Medium5 medium and 4 low findings. See the security findings ↓

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

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

  • Title tags22 issues
    22 of 86 pages have title issues.
    −2.6 points
  • Meta descriptions34 issues
    34 of 86 pages have meta description issues.
    −3.2 points
  • HeadingsOK
    0 of 86 pages have heading issues.
  • Broken links2 issues
    2 internal links point at 2 broken URLs.
    −0.5 points
  • Links to other sites3 issues
    3 destinations answered with an error, 6 could not be determined (timeouts, rate limits or refusals), of 26 destinations checked.
    −1.2 points
  • Redirects1 issue
    2 redirecting URLs, 0 of them chained.
  • Non-200 responses2 issues
    9 URLs did not return a 2xx response. 3 of them are pages, 2 with an error status; the rest are assets or redirects.
    −0.2 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 86 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 366 image references have no alt attribute. 174 use an empty alt (decorative), which is fine.
  • Heavy assets10 issues
    10 assets larger than 500 KB among 280 fetched assets.
    −6 points
  • Orphan pages22 issues
    22 pages have no internal links pointing at them.
    −1 points
  • Sitemap coverage22 issues
    9 sitemaps listing 86 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 22 reachable only via the sitemap.
    −1.5 points
  • Internal link countsOK
    Internal link counts for 86 pages; none is a dead end or buried.
  • Thin content4 issues
    4 of 86 pages have fewer than 200 words.
    −0.4 points
  • Duplicate content2 issues
    1 group of pages with identical HTML.
    −0.2 points
  • URL format2 noted
    2 of 89 page URLs are harder to read, share or cache than they need to be.
  • CanonicalsOK
    0 of 86 pages have a canonical worth checking.
  • Robots directives86 noted
    86 pages carry a robots directive; 0 carry none.
  • Anchor text3 noted
    3 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure34 noted
    34 of 86 pages could use the title, heading and snippet space better.
  • Image weight and alt length6 noted
    6 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies1 noted
    1 URL answered in a way worth looking at.
  • HTML and head validationOK
    All 86 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data2 noted
    86 of 86 indexable pages carry structured data: BreadcrumbList (86), ListItem (86), WebSite (86), WebPage (86), ImageObject (40). 2 pages with errors a rich result would fail on.
  • Near duplicates11 noted
    11 pages in 3 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 86 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 positions11 noted
    11 of 64 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
    2 cookies set by the site; 13 response headers recorded across 369 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 86 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.
  • Spelling44 noted
    44 words an English dictionary does not know, on 18 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2836 sites, median 80%, average 79%

www.avenuedentalcares.com scores 83%, higher than 61% of the 2836 scanned sites. See the full ranking.

0711420%: 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%: 6 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 16 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 33 sites66%: 42 sites67%: 42 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 79 sites72%: 76 sites73%: 81 sites74%: 79 sites75%: 87 sites76%: 96 sites77%: 108 sites78%: 129 sites79%: 112 sites80%: 125 sites81%: 123 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 94 sites87%: 95 sites88%: 79 sites89%: 74 sites90%: 54 sites91%: 57 sites92%: 42 sites93%: 28 sites94%: 25 sites95%: 14 sites96%: 17 sites97%: 15 sites98%: 7 sites99%: 3 sites100%: 142 sites83% 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

Several critical SEO issues were identified. Fixing broken links, improving title tags, and addressing meta descriptions should be prioritized to enhance site performance and user experience.

  1. 1

    Fix Broken Links

    Why: Broken links can harm user experience and SEO rankings.

    How: Update or remove the links pointing to the broken URLs.

    Checks: broken-links

  2. 2

    Correct Title Tag Issues

    Why: Proper title tags improve visibility and user engagement.

    How: Revise 22 pages with incorrect titles to ensure uniqueness and relevance.

    Checks: titles

  3. 3

    Add Missing Meta Descriptions

    Why: Meta descriptions enhance click-through rates from search results.

    How: Write unique meta descriptions for 34 pages lacking them.

    Checks: meta-descriptions

  4. 4

    Reduce Heavy Assets

    Why: Large assets can slow down your site, affecting rankings.

    How: Optimize or reduce the size of heavy assets identified.

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

    38 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

  5. 5

    Link to Orphan Pages

    Why: Orphan pages are inaccessible to users, hindering traffic.

    How: Create internal links from relevant pages to the 22 orphan pages.

    Checks: orphan-pages

  6. 6

    Address Thin Content Issues

    Why: Thin content can negatively impact rankings.

    How: Enhance content on 4 pages to exceed 200 words and provide value.

    Checks: thin-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 website lacks several important security measures that could expose user data to risks. Key findings include missing HTTP headers to protect against attacks and insecure cookie settings. Immediate action is required to enhance the site's security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, HTTP requests may be intercepted, exposing users to attacks.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Lack of Content-Security-PolicyMedium

    Why it matters: Without a CSP, the site is vulnerable to Cross-Site Scripting (XSS) attacks.

    Fix: Implement a CSP header: Content-Security-Policy: default-src 'self'; script-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Absence of X-Frame-Options allows embedding in frames, increasing clickjacking risks.

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

    Evidence: Clickjacking protection

  4. 4

    Insecure Cookie FlagsMedium

    Why it matters: Cookies lacking Secure, HttpOnly, and SameSite flags increase session hijacking risks.

    Fix: Set cookies with the following attributes: Secure; HttpOnly; SameSite=Lax.

    Evidence: Cookie flags

  5. 5

    Leaked API KeyMedium

    Why it matters: Publicly exposed API keys can lead to unauthorized usage and potential charges.

    Fix: Restrict the key in the Google Cloud console by HTTP referrer.

    Evidence: Keys and secrets in page code

  6. 6

    Lack of MIME Sniffing ProtectionLow

    Why it matters: Without this header, browsers may misinterpret file types, leading to potential security issues.

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

    Evidence: MIME sniffing protection

  7. 7

    Missing Referrer PolicyLow

    Why it matters: No referrer policy exposes complete URLs to third-party sites during navigation.

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

    Evidence: Referrer policy

  8. 8

    Server Banner ExposureLow

    Why it matters: Disclosing the technology framework can help attackers exploit specific vulnerabilities.

    Fix: Consider removing the X-Powered-By header or limiting its information.

    Evidence: Software version disclosure

  9. 9

    Third-Party Scripts without Subresource IntegrityLow

    Why it matters: Absence of integrity checks on scripts increases the risk of injected malicious code.

    Fix: Use Subresource Integrity (SRI) or implement a CSP that restricts these external scripts.

    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.avenuedentalcares.com/ → no strict-transport-security
    • https://www.avenuedentalcares.com/spokane-valley-wa/ → no strict-transport-security
    • https://www.avenuedentalcares.com/spokane-wa/ → no strict-transport-security
    • https://www.avenuedentalcares.com/terms-conditions/ → no strict-transport-security
    • https://www.avenuedentalcares.com/privacy-policy-2026/ → no strict-transport-security
    • https://www.avenuedentalcares.com/accessibility-commitment/ → no strict-transport-security
    • https://www.avenuedentalcares.com/privacy-policy/ → no strict-transport-security
    • https://www.avenuedentalcares.com/spokane-valley-wa/new-patients/special-offers/ → no strict-transport-security
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/ → no strict-transport-security
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-our-doctors/ → no strict-transport-security
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-the-team/ → no strict-transport-security
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/office-gallery/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 86 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.avenuedentalcares.com/ → no content-security-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/ → no content-security-policy
    • https://www.avenuedentalcares.com/spokane-wa/ → no content-security-policy
    • https://www.avenuedentalcares.com/terms-conditions/ → no content-security-policy
    • https://www.avenuedentalcares.com/privacy-policy-2026/ → no content-security-policy
    • https://www.avenuedentalcares.com/accessibility-commitment/ → no content-security-policy
    • https://www.avenuedentalcares.com/privacy-policy/ → no content-security-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/new-patients/special-offers/ → no content-security-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/ → no content-security-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-our-doctors/ → no content-security-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-the-team/ → no content-security-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/office-gallery/ → 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.avenuedentalcares.com/ → no x-frame-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/ → no x-frame-options
    • https://www.avenuedentalcares.com/spokane-wa/ → no x-frame-options
    • https://www.avenuedentalcares.com/terms-conditions/ → no x-frame-options
    • https://www.avenuedentalcares.com/privacy-policy-2026/ → no x-frame-options
    • https://www.avenuedentalcares.com/accessibility-commitment/ → no x-frame-options
    • https://www.avenuedentalcares.com/privacy-policy/ → no x-frame-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/new-patients/special-offers/ → no x-frame-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/ → no x-frame-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-our-doctors/ → no x-frame-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-the-team/ → no x-frame-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/office-gallery/ → 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.avenuedentalcares.com/ → no x-content-type-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/ → no x-content-type-options
    • https://www.avenuedentalcares.com/spokane-wa/ → no x-content-type-options
    • https://www.avenuedentalcares.com/terms-conditions/ → no x-content-type-options
    • https://www.avenuedentalcares.com/privacy-policy-2026/ → no x-content-type-options
    • https://www.avenuedentalcares.com/accessibility-commitment/ → no x-content-type-options
    • https://www.avenuedentalcares.com/privacy-policy/ → no x-content-type-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/new-patients/special-offers/ → no x-content-type-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/ → no x-content-type-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-our-doctors/ → no x-content-type-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-the-team/ → no x-content-type-options
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/office-gallery/ → 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.avenuedentalcares.com/ → no referrer-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/ → no referrer-policy
    • https://www.avenuedentalcares.com/spokane-wa/ → no referrer-policy
    • https://www.avenuedentalcares.com/terms-conditions/ → no referrer-policy
    • https://www.avenuedentalcares.com/privacy-policy-2026/ → no referrer-policy
    • https://www.avenuedentalcares.com/accessibility-commitment/ → no referrer-policy
    • https://www.avenuedentalcares.com/privacy-policy/ → no referrer-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/new-patients/special-offers/ → no referrer-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/ → no referrer-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-our-doctors/ → no referrer-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-the-team/ → no referrer-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/office-gallery/ → 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.avenuedentalcares.com/ → no permissions-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/ → no permissions-policy
    • https://www.avenuedentalcares.com/spokane-wa/ → no permissions-policy
    • https://www.avenuedentalcares.com/terms-conditions/ → no permissions-policy
    • https://www.avenuedentalcares.com/privacy-policy-2026/ → no permissions-policy
    • https://www.avenuedentalcares.com/accessibility-commitment/ → no permissions-policy
    • https://www.avenuedentalcares.com/privacy-policy/ → no permissions-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/new-patients/special-offers/ → no permissions-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/ → no permissions-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-our-doctors/ → no permissions-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/meet-the-team/ → no permissions-policy
    • https://www.avenuedentalcares.com/spokane-valley-wa/about-us/office-gallery/ → no permissions-policy
  • FoundCookie flagsMedium

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

    • 04 Nov 2026 04:18:58 GMT (set by https://www.avenuedentalcares.com/spokane-valley-wa/wp-content/uploads/sites/2/…) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 04:19:01 GMT (set by https://www.avenuedentalcares.com/spokane-wa/wp-content/uploads/sites/3/2026/02…) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 04:19:18 GMT (set by https://www.avenuedentalcares.com/wp-content/uploads/2024/03/accent_shapes_virt…) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 04:18:54 GMT (set by https://www.avenuedentalcares.com/spokane-wa/our-services/restorative-dentistry…) lacks Secure, HttpOnly, SameSite
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…7s (39 chars) in https://www.avenuedentalcares.com/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (369 responses)
    • x-powered-by: WP Engine (104 responses)
  • 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.)

    • fd.cleantalk.org (2 script tags)
    • cdn.userway.org (40 script tags)
6 checks passed
  • OKHTTPS

    All 86 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    1 library version recognised, none with known vulnerabilities.

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

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