Content - https://web.dev BeaverCheck Audit

D

Structured Data

Action

3 JSON-LD block(s) found — issues found that may affect search visibility.

FIX

3 JSON-LD block(s) found — issues found that may affect search visibility.

Missing required property "author" for Article

The "author" property is required for the Article schema type.

Missing required property "datePublished" for Article

The "datePublished" property is required for the Article schema type.

Missing or invalid @context in block #2

The @context should be "https://schema.org" for search engines to recognize the data.

Got: http://schema.org/ Expected: https://schema.org

Missing recommended property "image" for Article

Adding "image" can improve how search engines display your content.

Missing recommended property "publisher" for Article

Adding "publisher" can improve how search engines display your content.

Missing recommended property "dateModified" for Article

Adding "dateModified" can improve how search engines display your content.

Missing recommended property "sameAs" for Organization

Adding "sameAs" can improve how search engines display your content.

Missing recommended property "description" for WebSite

Adding "description" can improve how search engines display your content.

3 JSON-LD blocks found

The "author" property is required for the Article schema type.

Why this matters

Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.

Learn more ▾

Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.

Source: Google Search Central / schema.org

The "datePublished" property is required for the Article schema type.

Why this matters

Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.

Learn more ▾

Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.

Source: Google Search Central / schema.org

URL: http://schema.org/

The @context should be "https://schema.org" for search engines to recognize the data.

Expected: https://schema.org

Why this matters

JSON-LD without @context is invalid structured data — Google ignores the entire block.

Learn more ▾

@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.

Source: JSON-LD spec / schema.org

Adding "image" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

Adding "publisher" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

Adding "dateModified" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

Adding "sameAs" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

Adding "description" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

JSON-LD Blocks

Block 1 : Article

3 properties Valid

Missing required property: author

Missing required property: datePublished

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": ""
}

Block 2 : Organization

5 properties Valid

Missing or invalid @context

{
  "@context": "http://schema.org/",
  "@type": "Organization",
  "name": "web.dev",
  "logo": "https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/web/images/touchicon-180.png",
  "url": "https://web.dev/"
}

Block 3 : WebSite

5 properties Valid

{
  "@context": "http://schema.org",
  "@type": "WebSite",
  "name": "web.dev",
  "url": "https://web.dev/",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://web.dev/s/results?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}

B

Links

167 links checked, 162 healthy, 3 broken

REVIEW

167 links checked, 162 healthy, 3 broken

162 of 167 links are healthy

Broken link: https://www.gstatic.com

Found in <link href>. Returns HTTP 404.

Got: HTTP 404

Broken link: https://fonts.gstatic.com

Found in <link href>. Returns HTTP 404.

Got: HTTP 404

Broken link: https://fonts.googleapis.com

Found in <link href>. Returns HTTP 404.

Got: HTTP 404

Long redirect chain: https://web.dev/_d/signin?continue=https%3A%2F%... (3 hops)

Long redirect chain: https://issuetracker.google.com/issues/new?comp... (3 hops)

167 total 160 healthy 3 broken 4 redirects

Broken Links (3)

Status	URL	Found in	Error
404	https://www.gstatic.com	`<link>`	Not Found
404	https://fonts.gstatic.com	`<link>`	Not Found
404	https://fonts.googleapis.com	`<link>`	Not Found

Redirects (4)

URL	Destination	Found in
https://web.developers.google.cn/	https://web.developers.google.cn/	`<link>`
https://unpkg.com/web-vitals/dist/web-vi...	https://unpkg.com/web-vitals/dist/web-vi...	`<script>`
https://developer.chrome.com/fugu-showca...	https://developer.chrome.com/fugu-showca...	`<a>`
https://web.dev/testing-web-design-color...	https://web.dev/testing-web-design-color...	`<a>`

200 https://web.dev/_pwa/web/manifest.json <link>

200 https://apis.google.com <link>

200 https://www.google-analytics.com <link>

200 https://fonts.googleapis.com/css?family=Google+Sans:400,500|... <link>

200 https://fonts.googleapis.com/css2?family=Material+Icons&fami... <link>

200 https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d... <link>

200 https://web.dev/ <link>

200 https://web.dev/s/opensearch.xml <link>

200 https://web.dev/?hl=ar <link>

200 https://web.dev/?hl=bn <link>

200 https://web.dev/?hl=zh-cn <link>

200 https://web.dev/?hl=zh-tw <link>

200 https://web.dev/?hl=fa <link>

200 https://web.dev/?hl=fr <link>

200 https://web.dev/?hl=de <link>

200 https://web.dev/?hl=he <link>

200 https://web.dev/?hl=hi <link>

200 https://web.dev/?hl=id <link>

200 https://web.dev/?hl=it <link>

200 https://web.dev/?hl=ja <link>

200 https://web.dev/?hl=ko <link>

200 https://web.dev/?hl=pl <link>

200 https://web.dev/?hl=pt-br <link>

200 https://web.dev/?hl=es-419 <link>

200 https://web.dev/?hl=th <link>

200 https://web.dev/?hl=tr <link>

200 https://web.dev/?hl=vi <link>

200 https://web.developers.google.cn/?hl=ar <link>

200 https://web.developers.google.cn/?hl=bn <link>

200 https://web.developers.google.cn/?hl=zh-cn <link>

200 https://web.developers.google.cn/?hl=zh-tw <link>

200 https://web.developers.google.cn/?hl=fa <link>

200 https://web.developers.google.cn/?hl=fr <link>

200 https://web.developers.google.cn/?hl=de <link>

200 https://web.developers.google.cn/?hl=he <link>

200 https://web.developers.google.cn/?hl=hi <link>

200 https://web.developers.google.cn/?hl=id <link>

200 https://web.developers.google.cn/?hl=it <link>

200 https://web.developers.google.cn/?hl=ja <link>

200 https://web.developers.google.cn/?hl=ko <link>

B

Brand Presence

Site-name consistency, favicon, social image, meta tags, schema, and contact signals

REVIEW

Brand Presence

Your brand name differs across channels — visitors see inconsistent identity.

B

72/100

Site name appears as

Page title	web.dev
og:site_name	web.dev
twitter:site	@ChromiumDev
Organization.name	web.dev

Inconsistent — names differ across channels

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

20/20

og:image + twitter:image set

Meta completeness

20/20

Organization schema

15/15

has name, logo + url

Contact info discoverable

0/10

no contact info discoverable

Findings

Brand name differs across channels — users see inconsistent identity
Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
Consider adding contactPoint — helps appear in "contact us" rich results
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.

A+

Mixed Content

No mixed content detected — all resources use HTTPS.

PASS

No mixed content detected — all resources use HTTPS.

No mixed content detected — all resources use HTTPS

A+

Open Graph

Open Graph tags are well configured for social sharing.

PASS

Open Graph tags are well configured for social sharing.

og:title is short (7 characters)

Ideal length is 25–60 characters for social sharing previews.

Got: 7 chars Expected: 25–60 chars

URL: 7 chars

Ideal length is 25–60 characters for social sharing previews.

Expected: 25–60 chars

Why this matters

og:title very short — may render with awkward whitespace in social cards.

Source: Open Graph Protocol

Preview

web.dev

Guidance to build modern web experiences that work in every browser.

WEB.DEV

web.dev

Guidance to build modern web experiences that work in every browser.

web.dev

Guidance to build modern web experiences that work in every browser.