Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FLinksAction68 links checked, 24 healthy, 44 brokenFIX
Broken Links (44)
| Status | URL | Found in | Error |
|---|---|---|---|
| 403 | https://lacity.gov/ | <link> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2281/files/202... | <link> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/themes/si... | <link> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/files/css... | <link> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/files/css... | <link> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/files/css... | <link> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/files/css... | <link> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/files/css... | <link> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/files/js/... | <script> | Forbidden |
| 403 | https://lacity.gov/modules/contrib/google_tag/js/g... | <script> | Forbidden |
| 403 | https://lacity.gov/modules/contrib/google_tag/js/g... | <script> | Forbidden |
| 403 | https://lacity.gov/myla311 | <a> | Forbidden |
| 403 | https://lacity.gov/directory | <a> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/themes/si... | <img> | Forbidden |
| 403 | https://lacity.gov/search | <a> | Forbidden |
| 403 | https://lacity.gov/residents | <a> | Forbidden |
| 403 | https://lacity.gov/business | <a> | Forbidden |
| 403 | https://lacity.gov/visitors | <a> | Forbidden |
| 403 | https://lacity.gov/jobs | <a> | Forbidden |
| 403 | https://lacity.gov/government | <a> | Forbidden |
| 403 | https://lacity.gov/tv | <a> | Forbidden |
| 403 | https://lacity.gov/neighborhoodinfo | <a> | Forbidden |
| 403 | https://lacity.gov/news/inside-hyperion-how-la-tra... | <a> | Forbidden |
| 403 | https://lacity.gov/news/new-murals-unveiled-vision... | <a> | Forbidden |
| 403 | https://lacity.gov/news/lauren-halsey-sister-dream... | <a> | Forbidden |
| 403 | https://lacity.gov/news/new-facility-will-purify-a... | <a> | Forbidden |
| 403 | https://lacity.gov/news/greening-boyle-heights-new... | <a> | Forbidden |
| 403 | https://lacity.gov/news/your-self-your-city-your-r... | <a> | Forbidden |
| 403 | https://lacity.gov/news/rattlesnakes-la-what-you-n... | <a> | Forbidden |
| 403 | https://lacity.gov/news/spaghetti-marshmallows-and... | <a> | Forbidden |
| 403 | https://lacity.gov/news/hollywood-pet-adoption-eve... | <a> | Forbidden |
| 403 | https://lacity.gov/news/youth-development-departme... | <a> | Forbidden |
| 403 | https://lacity.gov/news/hot-meals-cool-spaces-bett... | <a> | Forbidden |
| 403 | https://lacity.gov/news | <a> | Forbidden |
| 403 | https://lacity.gov/news/micro-grants-program-helpi... | <a> | Forbidden |
| 403 | https://lacity.gov/news/coffee-cop-strengthening-c... | <a> | Forbidden |
| 403 | https://lacity.gov/news/tradespeople-needed-los-an... | <a> | Forbidden |
| 403 | https://lacity.gov/news/hacla-expanding-affordable... | <a> | Forbidden |
| 403 | https://lacity.gov/public-records-request | <a> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/files/js/... | <script> | Forbidden |
| 403 | https://lacity.gov/modules/contrib/ckeditor_accord... | <script> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/files/js/... | <script> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/files/js/... | <script> | Forbidden |
| 403 | https://lacity.gov/sites/g/files/wph2451/files/js/... | <script> | Forbidden |
FOpen GraphActionOpen Graph tags need attention — social sharing previews may be incomplete.FIX
The og:description tag controls the description in social sharing previews.
No og:description means social cards either show no subtitle or scrape the first paragraph — usually unflattering.
Learn more ▾ ▴
Without og:description, social platforms either render no subtitle or pull whatever text appears first on the page. The first paragraph is rarely written for share-card context. A purpose-written 150-200 character og:description gives a polished card.
Source: Open Graph Protocol
The og:image tag provides a preview image for social sharing.
No og:image means social shares are imageless — measurably less engaging than image-cards across every major platform.
Learn more ▾ ▴
Twitter, Facebook, and LinkedIn all use og:image (or twitter:image as a fallback) for share-card thumbnails. Without one, the post renders as a text-only card. A 1200x630px image (Twitter's preferred size) covers all platforms.
Source: Open Graph Protocol
The og:url tag specifies the canonical URL for the shared content.
Without og:url, social platforms infer the canonical URL — often picking a tracking-param variant that pollutes share counts.
Learn more ▾ ▴
og:url tells the social platform which URL to count this share against. Without it, platforms use the literal URL the user pasted (which may include utm_* parameters, ref codes, etc.). Setting og:url to the canonical form keeps share-count attribution clean.
Source: Open Graph Protocol
The og:type tag helps social platforms categorize the content.
Default og:type is 'website' but the right value (article, product, profile) unlocks richer metadata fields and higher engagement.
Learn more ▾ ▴
og:type controls which other og: fields a platform respects. og:type=article enables og:article:published_time, author, and section — surfaced in news cards. og:type=product enables price/availability fields surfaced by Pinterest and shopping integrations. Default 'website' silently disables those.
Source: Open Graph Protocol
The og:site_name tag displays the website name in social previews.
Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.
Learn more ▾ ▴
og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.
Source: Open Graph Protocol
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.
Without twitter:card, Twitter renders posts as plain text — no preview image, no structured layout.
Learn more ▾ ▴
Twitter requires `<meta name="twitter:card" content="summary_large_image">` (or summary) to render share-cards at all. Without it, links appear as raw text and engagement plummets vs cards. Twitter also falls back to og:image if twitter:image isn't set, so configure both.
Source: Twitter Developer Platform
Preview
lacity.gov
Home | City of Los Angeles
No description
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from og:title
- twitter:description — falling back from <meta name=description>
- twitter:image — Add twitter:image — preview card without an image looks broken
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
LACITY.GOV
Home | City of Los Angeles
No description
- og:title — Home | City of Los Angeles
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
- og:type — Add og:type — Recommended — tells Facebook the content category
- og:url — Add og:url — Recommended — canonical URL for the share
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview
No preview image for Facebook
→ Add og:image (recommended 1200×630)
Home | City of Los Angeles
lacity.gov
- og:title — Home | City of Los Angeles
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
lacity.gov
Home | City of Los Angeles
No description
- og:title — Home | City of Los Angeles
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
No preview image — Slack unfurl will be text-only
→ Add og:image or twitter:image
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 | — | — | — |
FBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Partial brand coverage — a few channels are missing brand signals.
F
21/100
Site name appears as
| Page title | City of Los Angeles | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
8/15single size only
Social share image
0/20Meta completeness
8/20Organization schema
0/15Contact info discoverable
0/10no contact info discoverable
Findings
- Missing brand name in: og:site_name, twitter:site, Organization.name
- No social share image — shared links render as bare URLs
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- og:image missing
- twitter:card missing
- No Organization schema — Google can't render your logo in the knowledge panel
- No discoverable contact info — trust signal is weak, legal risk is higher in regulated regions
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.
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