Scanned sites / www.avenuedentalcares.com / 2026-10-25-1735

www.avenuedentalcares.com scan from 2026-10-25 17:35:00 UTC DR 0

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

Scan 2026-10-25-1735

Scanned 2026-10-25 17:35:00 UTC, finished 2026-10-25 17:42:22 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.

84/ 100Good

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

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

318 of 318 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 300 image references have no alt attribute. 121 use an empty alt (decorative), which is fine.
  • Heavy assets8 issues
    8 assets larger than 500 KB among 229 fetched assets.
    −4.8 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 length5 noted
    5 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
    1 cookie set by the site; 13 response headers recorded across 318 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

2315 sites, median 79%, average 78%

www.avenuedentalcares.com scores 84%, higher than 69% of the 2315 scanned sites. See the full ranking.

0581150%: 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%: 105 sites81%: 105 sites82%: 115 sites83%: 98 sites84%: 108 sites85%: 85 sites86%: 69 sites87%: 74 sites88%: 59 sites89%: 61 sites90%: 35 sites91%: 44 sites92%: 37 sites93%: 23 sites94%: 16 sites95%: 11 sites96%: 9 sites97%: 12 sites98%: 4 sites99%: 1 site100%: 70 sites84% 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 a good health score but needs immediate attention on broken links and meta descriptions. Addressing these will improve user experience and search visibility.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and SEO performance.

    How: Replace or remove the links that point to the 404 pages listed in the crawl.

    Checks: broken-links

  2. 2

    Address Non-200 Responses

    Why: Pages that don't respond correctly can hurt your site's credibility.

    How: Check the URLs listed for errors and fix them to return a 200 status.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Improving title tags enhances click-through rates and better reflects page content.

    How: Revise the 22 title tags to ensure uniqueness and correct length.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Missing meta descriptions can lead to lower search rankings.

    How: Create concise, engaging meta descriptions for the 34 pages lacking them.

    Checks: meta-descriptions

  5. 5

    Resolve Orphan Pages

    Why: Orphan pages lack visibility and don’t contribute to SEO.

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

    Checks: orphan-pages

  6. 6

    Reduce Heavy Assets

    Why: Large assets can slow down your site, impacting user experience and SEO.

    How: Optimize large media files or move them to load only when necessary.

    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

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 immediate attention, including the lack of critical response headers that protect users from various attacks. Implementing these fixes can significantly enhance the security posture of your site.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted if they type the URL without https://.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    No Content Security Policy (CSP)Medium

    Why it matters: Without CSP, the browser restricts no sources for scripts, potentially allowing malicious content.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Absence of this header exposes your site to clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Leaked Google API KeyMedium

    Why it matters: Exposing API keys can lead to unauthorized usage and resource access.

    Fix: Limit the key’s usage to specific HTTP referrers in the Google Cloud console.

    Evidence: Keys and secrets in page code

  5. 5

    No X-Content-Type-OptionsLow

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

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

    Evidence: MIME sniffing protection

  6. 6

    Absence of Referrer PolicyLow

    Why it matters: Not having a referrer policy can expose users' full URLs to external sites.

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

    Evidence: Referrer policy

  7. 7

    Server Banner DisclosureLow

    Why it matters: Exposing server technology can assist attackers in targeting known vulnerabilities.

    Fix: Remove or mask the X-Powered-By header.

    Evidence: Software version disclosure

  8. 8

    Third-Party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from third-party domains can be compromised, affecting your site’s security.

    Fix: Implement a Content-Security-Policy that specifies trusted domains.

    Evidence: Third-party scripts

  9. 9

    Missing Permissions PolicyInfo

    Why it matters: Absence of this header allows scripts to potentially access unnecessary browser features.

    Fix: Add the header: Permissions-Policy: autoplay=(), camera=(), geolocation=()

    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://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
  • 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 (318 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 (1 script tag)
    • cdn.userway.org (40 script tags)
7 checks passed
  • OKHTTPS

    All 86 crawled pages were served over HTTPS.

  • OKCookie flags

    All 1 cookie carry Secure, HttpOnly and SameSite flags.

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