Scanned sites / partnershiphealthcenter.org
SEO report for partnershiphealthcenter.org DR 36
The latest Site Spider scan of partnershiphealthcenter.org, with 1 scan on record. Each scan is at its own address, for example /domain/partnershiphealthcenter-org/2026-09-12-0532.
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Latest scan
Scanned 2026-09-12 05:32:06 UTC, finished 2026-09-12 12:35:48 UTC
Site: https://partnershiphealthcenter.org/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 12, 2026 the Site Spider crawled 366 pages and 1111 assets of partnershiphealthcenter.org, starting from https://partnershiphealthcenter.org/. It scored 73 out of 100, a result that needs work. 13 of 26 checks found something to fix, led by heavy assets (18), meta descriptions (122), title tags (86); 5 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−3.4), title tags (−3). 8 checks found something the score does not count, listed as noted. 11 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: High1 high, 5 medium and 2 low findings. See the security findings ↓
- Pages crawled
- 366
- Assets fetched
- 1111
- Status
- Completed
- Checks with issues
- 13 of 26
1,477 of 1,482 discovered URLs were fetched, 8,221 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. 298 link destinations on other sites were checked.
- Title tags86 issues86 of 134 pages have title issues. 154 noindex or canonicalized pages excluded.−3 points
- Meta descriptions122 issues122 of 134 pages have meta description issues. 154 noindex or canonicalized pages excluded.−3.4 points
- Headings22 issues22 of 134 pages have heading issues. 154 noindex or canonicalized pages excluded.−0.5 points
- Broken links31 issues41 internal links point at 31 broken URLs.−2.2 points
- Links to other sites12 issues12 destinations answered with an error, 203 could not be determined (timeouts, rate limits or refusals), of 289 destinations checked.−1.7 points
- Redirects48 issues48 redirecting URLs, 2 of them chained.−0.7 points
- Non-200 responses31 issues82 URLs did not return a 2xx response. 78 of them are pages, 31 with an error status; the rest are assets or redirects.−1.1 points
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability44 issues44 of 256 indexable pages have indexability warnings. 32 pages noindex by design.−1.5 points
- Image alt text1,536 issues1536 of 3283 image references have no alt attribute. 1394 use an empty alt (decorative), which is fine.−2.8 points
- Heavy assets18 issues18 assets larger than 500 KB among 1111 fetched assets. 23 documents over that size are listed but not counted: downloads are not page weight.−6 points
- Orphan pages28 issues28 pages have no internal links pointing at them.−0.4 points
- Sitemap coverage134 issues1 sitemap listing 0 URLs: 134 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.−2.8 points
- Internal link counts110 notedInternal link counts for 288 pages; 110 worth a look.
- Thin contentOK0 of 134 pages have fewer than 200 words. 154 noindex or canonicalized pages excluded.
- Duplicate content31 issues2 groups of pages with identical HTML.−0.9 points
- URL format129 noted129 of 366 page URLs are harder to read, share or cache than they need to be.
- Canonicals154 noted154 of 288 pages have a canonical worth checking.
- Robots directives288 noted288 pages carry a robots directive; 0 carry none.
- Anchor text138 noted138 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure58 noted58 of 134 pages could use the title, heading and snippet space better. 154 noindex or canonicalized pages excluded.
- Image weight and alt length48 noted43 images over 100 KB; 5 with alt text over 100 characters.
- Response anomalies4 noted4 URLs answered in a way worth looking at.
- HTML and head validationNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- hreflangNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Structured dataNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Near duplicatesNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Soft 404sOKNone of 288 pages answering 200 reads like an error page.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positionsNot checkedNot checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
- PaginationNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Headers and cookiesOK0 cookies set by the site; 12 response headers recorded across 1477 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 288 pages; 217 hold almost none (10 or less).
- JavaScript renderingNot checkedNot 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 checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- SpellingNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
Where this site sits among all scanned sites
2347 sites, median 79%, average 78%
partnershiphealthcenter.org scores 73%, higher than 26% of the 2347 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsWritten from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.
Several issues require attention to improve your website's technical SEO. Focus on fixing broken links, optimizing titles and meta descriptions, and ensuring proper indexability. These enhancements will boost user experience and search visibility.
- 1
Fix Broken Links
Why: 41 broken internal links can hurt user experience and SEO.
How: Locate all broken links in your content and update or remove them.
Checks: broken-links
- 2
Resolve Redirect Issues
Why: 48 redirects, including chained ones, can slow down site performance.
How: Simplify redirects to point directly from old URLs to new ones.
Checks: redirects
- 3
Address Non-200 Response Codes
Why: 82 URLs returning non-200 responses can harm user access and SEO.
How: Identify and fix these URLs as necessary or remove them.
Checks: status-codes
- 4
Optimize Title Tags
Why: 86 pages have titles that can be better optimized for SEO.
How: Shorten long titles to under 60 characters and ensure uniqueness.
Checks: titles
- 5
Improve Meta Descriptions
Why: 122 pages lack effective meta descriptions, impacting click-through rates.
How: Create engaging meta descriptions under 160 characters for affected pages.
Checks: meta-descriptions
- 6
Enhance Indexability
Why: 44 pages show indexability warnings that can hinder search visibility.
How: Review and adjust the settings for these pages to promote proper indexing.
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 crawlThe website has multiple security issues, primarily related to serving pages over plain HTTP instead of HTTPS. This exposes user data to potential attacks. The site lacks several important security headers, and there are forms that transmit data insecurely. These findings should be addressed to improve user security.
- 1 high
- 5 medium
- 2 low
- 0 info
- 1
HTTP Pages ExposedHigh
Why it matters: 48 pages served over HTTP can be intercepted, allowing data theft.
Fix: Redirect all HTTP traffic to HTTPS. Implement a 301 redirect for all pages.
Evidence: HTTPS
- 2
Missing HSTS HeaderMedium
Why it matters: Lack of HSTS makes initial requests vulnerable to interception.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.
Evidence: HTTP Strict Transport Security
- 3
Absence of Content Security PolicyMedium
Why it matters: No restrictions on resource loading increases risk of XSS attacks.
Fix: Add a Content-Security-Policy header to regulate sources, e.g., Content-Security-Policy: default-src 'self'.
Evidence: Content Security Policy
- 4
Missing Clickjacking ProtectionMedium
Why it matters: Without X-Frame-Options, pages can be embedded in an attacker's frame.
Fix: Add the header: X-Frame-Options: DENY.
Evidence: Clickjacking protection
- 5
Forms Sending Data Over HTTPMedium
Why it matters: Forms on HTTP pages can lead to data interception.
Fix: Serve all forms over HTTPS. Redirect traffic and update form action URLs.
Evidence: Forms over HTTPS
- 6
Leaked API KeyMedium
Why it matters: Exposed Google API key can lead to unauthorized usage.
Fix: Restrict the API key usage within the Google Cloud console to specific referrers.
Evidence: Keys and secrets in page code
- 7
Missing MIME Sniffing ProtectionLow
Why it matters: Absence of X-Content-Type-Options can lead to dangerous MIME type execution.
Fix: Add the header: X-Content-Type-Options: nosniff.
Evidence: MIME sniffing protection
- 8
Mixed Content IssuesLow
Why it matters: Loading resources over HTTP from HTTPS pages may lead to privacy issues.
Fix: Ensure all resources are loaded over HTTPS; update URLs in HTML.
Evidence: Mixed content
What the checks found
- FoundHTTPSHigh
48 pages answered 200 over plain HTTP with no redirect to HTTPS, while 240 were served over HTTPS. Anyone on the network path can read or alter these pages.
- http://partnershiphealthcenter.org/appointments/ → 200 over http
- http://partnershiphealthcenter.org/mychart/ → 200 over http
- http://partnershiphealthcenter.org/pay-my-bill/ → 200 over http
- http://partnershiphealthcenter.org/careers/ → 200 over http
- http://partnershiphealthcenter.org/stories/ → 200 over http
- http://partnershiphealthcenter.org/our-services/ → 200 over http
- http://partnershiphealthcenter.org/services/ → 200 over http
- http://partnershiphealthcenter.org/forms/ → 200 over http
- http://partnershiphealthcenter.org/financial-assistance/ → 200 over http
- http://partnershiphealthcenter.org/providers/ → 200 over http
- http://partnershiphealthcenter.org/about/ → 200 over http
- http://partnershiphealthcenter.org/about/mission-vision-values-and-history/ → 200 over http
- 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://partnershiphealthcenter.org/ → no strict-transport-security
- https://partnershiphealthcenter.org/donate/ → no strict-transport-security
- https://partnershiphealthcenter.org/contact/ → no strict-transport-security
- https://partnershiphealthcenter.org/appointments/ → no strict-transport-security
- https://partnershiphealthcenter.org/providers/ → no strict-transport-security
- https://partnershiphealthcenter.org/pay-my-bill/ → no strict-transport-security
- https://partnershiphealthcenter.org/online-scheduling/ → no strict-transport-security
- https://partnershiphealthcenter.org/careers/ → no strict-transport-security
- https://partnershiphealthcenter.org/our-services/medical/ → no strict-transport-security
- https://partnershiphealthcenter.org/our-services/pharmacy/ → no strict-transport-security
- https://partnershiphealthcenter.org/our-services/innovations/ → no strict-transport-security
- https://partnershiphealthcenter.org/our-services/behavioral-health/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 288 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://partnershiphealthcenter.org/ → no content-security-policy
- http://partnershiphealthcenter.org/appointments/ → no content-security-policy
- http://partnershiphealthcenter.org/mychart/ → no content-security-policy
- http://partnershiphealthcenter.org/pay-my-bill/ → no content-security-policy
- http://partnershiphealthcenter.org/careers/ → no content-security-policy
- https://partnershiphealthcenter.org/donate/ → no content-security-policy
- https://partnershiphealthcenter.org/contact/ → no content-security-policy
- http://partnershiphealthcenter.org/stories/ → no content-security-policy
- http://partnershiphealthcenter.org/our-services/ → no content-security-policy
- http://partnershiphealthcenter.org/services/ → no content-security-policy
- http://partnershiphealthcenter.org/forms/ → no content-security-policy
- http://partnershiphealthcenter.org/financial-assistance/ → 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://partnershiphealthcenter.org/ → no x-frame-options
- http://partnershiphealthcenter.org/appointments/ → no x-frame-options
- http://partnershiphealthcenter.org/mychart/ → no x-frame-options
- http://partnershiphealthcenter.org/pay-my-bill/ → no x-frame-options
- http://partnershiphealthcenter.org/careers/ → no x-frame-options
- https://partnershiphealthcenter.org/donate/ → no x-frame-options
- https://partnershiphealthcenter.org/contact/ → no x-frame-options
- http://partnershiphealthcenter.org/stories/ → no x-frame-options
- http://partnershiphealthcenter.org/our-services/ → no x-frame-options
- http://partnershiphealthcenter.org/services/ → no x-frame-options
- http://partnershiphealthcenter.org/forms/ → no x-frame-options
- http://partnershiphealthcenter.org/financial-assistance/ → 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://partnershiphealthcenter.org/ → no x-content-type-options
- http://partnershiphealthcenter.org/appointments/ → no x-content-type-options
- http://partnershiphealthcenter.org/mychart/ → no x-content-type-options
- http://partnershiphealthcenter.org/pay-my-bill/ → no x-content-type-options
- http://partnershiphealthcenter.org/careers/ → no x-content-type-options
- https://partnershiphealthcenter.org/donate/ → no x-content-type-options
- https://partnershiphealthcenter.org/contact/ → no x-content-type-options
- http://partnershiphealthcenter.org/stories/ → no x-content-type-options
- http://partnershiphealthcenter.org/our-services/ → no x-content-type-options
- http://partnershiphealthcenter.org/services/ → no x-content-type-options
- http://partnershiphealthcenter.org/forms/ → no x-content-type-options
- http://partnershiphealthcenter.org/financial-assistance/ → no x-content-type-options
- FoundMixed contentLow
2100 resources on HTTPS pages are loaded over plain HTTP.
- https://partnershiphealthcenter.org/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2023/01/Orange.svg
- https://partnershiphealthcenter.org/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2023/01/Yellow.svg
- https://partnershiphealthcenter.org/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2023/01/Teal.svg
- https://partnershiphealthcenter.org/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2023/01/PHC-Mark-Navy-blue.svg
- https://partnershiphealthcenter.org/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2022/12/PHC-Icon.svg
- https://partnershiphealthcenter.org/donate/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2023/01/Orange.svg
- https://partnershiphealthcenter.org/donate/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2023/01/Yellow.svg
- https://partnershiphealthcenter.org/donate/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2023/01/Teal.svg
- https://partnershiphealthcenter.org/donate/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2023/01/PHC-Mark-Navy-blue.svg
- https://partnershiphealthcenter.org/donate/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2022/12/PHC-Icon.svg
- https://partnershiphealthcenter.org/donate/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2024/09/PHC-Gives-1024x284.webp
- https://partnershiphealthcenter.org/contact/ loads image http://partnershiphealthcenter.org/wp-content/uploads/2023/01/Orange.svg
- FoundForms over HTTPSMedium
26 forms would send what visitors type over plain HTTP, where it can be read or changed on the way.
- http://partnershiphealthcenter.org/appointments/ has 2 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/mychart/ has 2 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/pay-my-bill/ has 2 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/careers/ has 3 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/stories/ has 3 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/our-services/ has 2 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/services/ has 2 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/forms/ has 2 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/financial-assistance/ has 2 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/providers/ has 2 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/about/ has 2 forms on a page served over plain HTTP
- http://partnershiphealthcenter.org/about/mission-vision-values-and-history/ has 2 forms on a page served over plain HTTP
- FoundKeys and secrets in page codeMedium
1 credential-like value found in code served to every visitor: Google API key.
- Google API key AIzaSy…T8 (39 chars) in https://partnershiphealthcenter.org/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
- NoteThird-party scripts
Scripts run from 5 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.)
- cdn-cookieyes.com (40 script tags)
- maps.googleapis.com (10 script tags)
- unpkg.com (10 script tags)
- code.jquery.com (2 script tags)
- www.google.com (2 script tags)
4 checks passed, 3 not applicable
- OKSoftware version disclosure
The Server header names a product without a version, and there is no X-Powered-By header.
- OKVulnerable JavaScript libraries
3 library versions 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.
- Not applicableReferrer policy
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicablePermissions policy
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicableCookie flags
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
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 partnershiphealthcenter.org
No other scans of this site yet.
Sites scoring near partnershiphealthcenter.org
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- www.okeeffeattorneys.comDR 4573/100 · rank 1677 · 1,153 pages
- www.felicecafe.caDR 2373/100 · rank 1677 · 21 pages
- masterrooter.comDR 3173/100 · rank 1677 · 517 pages
- bonavistaphysio.caDR 473/100 · rank 1677 · 160 pages
- bluemountainbb.comDR 1473/100 · rank 1677 · 667 pages
- burtonshair.comDR 473/100 · rank 1677 · 38 pages
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 partnershiphealthcenter.org from its pages as published, the way a search engine does. It shows summary figures only.
Own partnershiphealthcenter.org?
- 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 partnershiphealthcenter.org. Removal needs no account and no proof of purchase.