Scanned sites / www.avenuedentalcares.com / 2026-10-29-2124

www.avenuedentalcares.com scan from 2026-10-29 21:24:18 UTC DR 0

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

Scan 2026-10-29-2124

Scanned 2026-10-29 21:24:18 UTC, finished 2026-10-29 21:35:02 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 October 29, 2026 the Site Spider crawled 89 pages and 414 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
414
Status
Completed
Checks with issues
11 of 33
CoverageComplete crawl

503 of 503 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 310 image references have no alt attribute. 129 use an empty alt (decorative), which is fine.
  • Heavy assets10 issues
    10 assets larger than 500 KB among 414 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 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
    2 cookies set by the site; 13 response headers recorded across 503 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

2344 sites, median 79%, average 78%

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

0591170%: 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%: 4 sites52%: 10 sites53%: 6 sites54%: 9 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 72 sites73%: 70 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 107 sites79%: 85 sites80%: 107 sites81%: 104 sites82%: 117 sites83%: 101 sites84%: 107 sites85%: 88 sites86%: 70 sites87%: 73 sites88%: 59 sites89%: 65 sites90%: 35 sites91%: 46 sites92%: 39 sites93%: 24 sites94%: 16 sites95%: 12 sites96%: 12 sites97%: 12 sites98%: 5 sites99%: 2 sites100%: 68 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

The site has several SEO issues needing attention, primarily related to broken links, meta descriptions, title tags, and heavy assets. Focusing on these will enhance user experience and search visibility.

  1. 1

    Fix Broken Links

    Why: Broken links hinder user experience and SEO performance.

    How: Update or remove the internal links to destinations that return a 404 status.

    Checks: broken-links

  2. 2

    Correct Non-200 Responses

    Why: Pages returning errors can harm rankings and user access.

    How: Resolve issues leading to 404 and 301 errors, ensuring URLs load properly.

    Checks: status-codes

  3. 3

    Improve Meta Descriptions

    Why: Missing or poorly optimized meta descriptions can impact click-through rates.

    How: Write compelling meta descriptions for all 34 affected pages.

    Evidence: 34 pages have no meta description at all.

    34 pages affected

    Checks: meta-descriptions

  4. 4

    Fix Title Tag Issues

    Why: Duplicate or overly long title tags can confuse search engines.

    How: Revise the titles of 22 pages to ensure uniqueness and proper length.

    Checks: titles

  5. 5

    Compress Heavy Assets

    Why: Large files can slow down page load times, affecting user experience.

    How: Optimize or reduce the file size of 10 heavy assets.

    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

  6. 6

    Link to Orphan Pages

    Why: Orphan pages are not discoverable, limiting traffic and SEO benefits.

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

    Checks: orphan-pages

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 security review identified several critical issues that need immediate attention, including missing security headers, cookie protections, and exposed credentials. Implement these recommendations to enhance your site's resilience against common attacks.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors typing the URL without HTTPS can be intercepted.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    No Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows scripts and resources to load from any source, increasing XSS risk.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without X-Frame-Options, the site can be embedded in frames, risking clickjacking.

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

    Evidence: Clickjacking protection

  4. 4

    Cookies Lack Security FlagsMedium

    Why it matters: Most cookies are missing critical flags, making them vulnerable.

    Fix: Set cookies with flags: Secure; HttpOnly; SameSite=Lax.

    Evidence: Cookie flags

  5. 5

    Exposed Google API KeyMedium

    Why it matters: An exposed API key may allow unauthorized access unless restricted.

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

    Evidence: Keys and secrets in page code

  6. 6

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Absence of this header may allow browsers to interpret files incorrectly.

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

    Evidence: MIME sniffing protection

  7. 7

    Missing Referrer-Policy HeaderLow

    Why it matters: Lack of a referrer policy exposes the full page address when navigating away.

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

    Evidence: Referrer policy

  8. 8

    X-Powered-By Header Discloses FrameworkLow

    Why it matters: This header can disclose framework information, aiding attackers.

    Fix: Remove or modify the X-Powered-By header to obscure the framework.

    Evidence: Software version disclosure

  9. 9

    Third-Party Scripts Lack Subresource IntegrityLow

    Why it matters: Scripts from external domains can change if compromised, risking the site.

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

    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

    202 of 204 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.

    • 29 Oct 2026 21:54:33 GMT (set by https://www.avenuedentalcares.com/) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:36 GMT (set by https://www.avenuedentalcares.com/sitemap.xml) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:39 GMT (set by https://www.avenuedentalcares.com/spokane-valley-wa/) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:40 GMT (set by https://www.avenuedentalcares.com/spokane-wa/) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:42 GMT (set by https://www.avenuedentalcares.com/terms-conditions/) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:44 GMT (set by https://www.avenuedentalcares.com/accessibility-commitment/) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:45 GMT (set by https://www.avenuedentalcares.com/sitemap_index.xml) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:47 GMT (set by https://www.avenuedentalcares.com/privacy-policy/) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:48 GMT (set by https://www.avenuedentalcares.com/favicon-32x32.png) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:49 GMT (set by https://www.avenuedentalcares.com/wp-content/uploads/2025/12/avenue_dental_care…) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:50 GMT (set by https://www.avenuedentalcares.com/wp-content/uploads/2025/12/homepageBan1920.jp…) lacks Secure, HttpOnly, SameSite
    • 29 Oct 2026 21:54:51 GMT (set by https://www.avenuedentalcares.com/wp-content/plugins/cleantalk-spam-protect/css…) 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 (503 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)
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.