Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FLinksAction200 links checked, 52 healthy, 148 brokenFIX
Broken Links (50)
| Status | URL | Found in | Error |
|---|---|---|---|
| 403 | https://treas.gov/sites/default/files/favicon_1.pn... | <link> | Forbidden |
| 403 | https://treas.gov/sites/default/files/css/css_00cN... | <link> | Forbidden |
| 403 | https://treas.gov/sites/default/files/css/css_zbin... | <link> | Forbidden |
| 403 | https://treas.gov/sites/default/files/css/css_uCi-... | <link> | Forbidden |
| 403 | https://treas.gov/sites/default/files/js/js_EF_HuS... | <script> | Forbidden |
| 403 | https://treas.gov/sites/default/files/js/js_hoOrcl... | <script> | Forbidden |
| 403 | https://treas.gov/libraries/uswds/src/img/us_flag_... | <img> | Forbidden |
| 403 | https://treas.gov/libraries/uswds/src/img/icon-dot... | <img> | Forbidden |
| 403 | https://treas.gov/libraries/uswds/src/img/icon-htt... | <img> | Forbidden |
| 403 | https://treas.gov/themes/custom/hamilton/videos/fr... | <source> | Forbidden |
| 403 | https://treas.gov/themes/custom/hamilton/images/fr... | <img> | Forbidden |
| 403 | https://treas.gov/ | <a> | Forbidden |
| 403 | https://treas.gov/themes/custom/hamilton/logo.svg | <img> | Forbidden |
| 500 | https://search.usa.gov/search/advanced?affiliate=t... | <a> | Internal Server Error |
| 403 | https://treas.gov/about-treasury | <a> | Forbidden |
| 403 | https://treas.gov/about/general-information | <a> | Forbidden |
| 403 | https://treas.gov/about/general-information/role-o... | <a> | Forbidden |
| 403 | https://treas.gov/about/general-information/offici... | <a> | Forbidden |
| 403 | https://treas.gov/about/general-information/organi... | <a> | Forbidden |
| 403 | https://treas.gov/about/general-information/orders... | <a> | Forbidden |
| 403 | https://treas.gov/about/offices | <a> | Forbidden |
| 403 | https://treas.gov/about/offices/domestic-finance | <a> | Forbidden |
| 403 | https://treas.gov/about/offices/economic-policy | <a> | Forbidden |
| 403 | https://treas.gov/about/offices/general-counsel | <a> | Forbidden |
| 403 | https://treas.gov/about/offices/international-affa... | <a> | Forbidden |
| 403 | https://treas.gov/about/offices/management | <a> | Forbidden |
| 403 | https://treas.gov/about/offices/public-affairs | <a> | Forbidden |
| 403 | https://treas.gov/about/offices/tax-policy | <a> | Forbidden |
| 403 | https://treas.gov/about/offices/terrorism-and-fina... | <a> | Forbidden |
| 403 | https://treas.gov/policy-issues/tribal-affairs | <a> | Forbidden |
| 403 | https://treas.gov/services/report-fraud-waste-and-... | <a> | Forbidden |
| 403 | https://treas.gov/about/bureaus | <a> | Forbidden |
| 403 | https://treas.gov/about/budget-financial-reporting... | <a> | Forbidden |
| 403 | https://treas.gov/about/budget-financial-reporting... | <a> | Forbidden |
| 403 | https://treas.gov/about/budget-financial-reporting... | <a> | Forbidden |
| 403 | https://treas.gov/about/budget-financial-reporting... | <a> | Forbidden |
| 403 | https://treas.gov/about/budget-financial-reporting... | <a> | Forbidden |
| 403 | https://treas.gov/about/budget-financial-reporting... | <a> | Forbidden |
| 403 | https://treas.gov/about/history-overview | <a> | Forbidden |
| 403 | https://treas.gov/about/history/curator | <a> | Forbidden |
| 403 | https://treas.gov/about/history/history-overview | <a> | Forbidden |
| 403 | https://treas.gov/about/history/prior-secretaries | <a> | Forbidden |
| 403 | https://treas.gov/about/history/treasurers-of-the-... | <a> | Forbidden |
| 403 | https://treas.gov/about/history/the-treasury-build... | <a> | Forbidden |
| 403 | https://treas.gov/about/history/collection | <a> | Forbidden |
| 403 | https://treas.gov/about/history/freedmans-bank-bui... | <a> | Forbidden |
| 403 | https://treas.gov/careers | <a> | Forbidden |
| 403 | https://treas.gov/about/careers-at-treasury/career... | <a> | Forbidden |
| 403 | https://treas.gov/about/careers-at-treasury/career... | <a> | Forbidden |
| 403 | https://treas.gov/about/careers-at-treasury/top-te... | <a> | Forbidden |
DBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
D
52/100
Site name appears as
| Page title | Lock | |
| og:site_name | U.S. Department of the Treasury | |
| twitter:site | @USTreasury | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
8/15single size only
Social share image
20/20og:image + twitter:image set
Meta completeness
14/20Organization schema
0/15Contact info discoverable
5/10contact page
Findings
- Brand name differs across channels — users see inconsistent identity
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- og:title missing
- No Organization schema — Google can't render your logo in the knowledge panel
- Only partial contact info discoverable — consider adding a dedicated contact page or mailto/tel link
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.
COpen GraphActionOpen Graph tags are partially configured — some improvements recommended.REVIEW
https://home.treasury.gov/system/files/291/treasury-preview-1900x950.jpgThe og:image URL could not be fetched. Social platforms won't be able to display it.
An unreachable og:image URL (404, DNS fail, slow timeout) means social platforms cache the failure and serve no image for hours.
Learn more ▾ ▴
Social platforms (Facebook, Twitter) cache OG metadata aggressively — including failed image fetches. A momentarily-broken og:image can leave your shares imageless for hours. Test og:image URLs in Facebook's Sharing Debugger to force re-cache after fixing.
Source: Open Graph Protocol / Facebook Sharing Debugger
The og:title tag controls the title shown in social sharing previews.
Without og:title, social shares fall back to the <title> tag — usually awkwardly truncated or branded for SEO not social.
Learn more ▾ ▴
og:title controls what appears as the headline in social-share cards (Twitter, Facebook, LinkedIn, Slack, iMessage). When omitted, platforms fall back to <title>, which is usually optimized for SEO (longer, brand-suffixed) and reads badly in social context. A 50-60-character og:title gives a clean preview.
Source: Open Graph Protocol
31 charsIdeal length is 55–200 characters for social sharing previews.
55–200 charsog:description very short — provides little context in social cards.
Source: Open Graph Protocol
Preview

treas.gov
No title set
U.S. Department of the Treasury
- twitter:card — summary_large_image
- twitter:title — falling back from <title>
- twitter:description — falling back from og:description
- twitter:image — https://home.treasury.gov/system/files/291/treasury-preview-1080x1080.jpg

TREAS.GOV
No title set
U.S. Department of the Treasury
- og:title — falling back from <title>
- og:description — U.S. Department of the Treasury
- og:image — https://home.treasury.gov/system/files/291/treasury-preview-1900x950.jpg
- og:type — article
- og:url — https://home.treasury.gov/front
- og:site_name — U.S. Department of the Treasury

No title set
treas.gov
- og:title — falling back from <title>
- og:description — U.S. Department of the Treasury
- og:image — https://home.treasury.gov/system/files/291/treasury-preview-1900x950.jpg
treas.gov
No title set
U.S. Department of the Treasury

- og:title — falling back from <title>
- og:description — U.S. Department of the Treasury
- og:image — https://home.treasury.gov/system/files/291/treasury-preview-1900x950.jpg
Social preview quality
Averaged across Twitter/X, Facebook, LinkedIn, and Slack.
| Field | Twitter/X | Slack | ||
|---|---|---|---|---|
| og:title | ⚠ | ⚠ | ⚠ | |
| og:description | ||||
| og:image | ||||
| og:type | ||||
| og:url | ||||
| og:site_name | ||||
| twitter:card | — | — | — | |
| twitter:title | ⚠ | — | — | — |
| twitter:description | ⚠ | — | — | — |
| twitter:image | — | — | — |
CStructured DataActionNo structured data (JSON-LD) found.REVIEW
Adding structured data helps search engines understand your content and can enable rich results.
Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.
Learn more ▾ ▴
Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.
Source: Google Search Central / schema.org
No structured data found
Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.
Common types include:
- WebSite — your site identity and search box
- Organization — your company information
- Article — blog posts and news articles
- Product — e-commerce product pages
- BreadcrumbList — navigation paths