nvidia.com
Evidence collected August 31, 2026 · 85 polite, robots.txt-respecting requests · every claim cites what it saw
No letter grade — withheld, not failed
No letter grade is issued because this tool could not read this site's content structure: of the 47762 URLs in its sitemap, 34056 (71.3%) could not be classified into content sections by the reader. That is a limit of this tool's reading, not evidence that the company lacks content — a grade computed from the readable sliver would report a gap in this tool as their failure. What could be observed is scored below at reduced confidence.
Read this before the numbers
This tool was built in a few days, on a stack of stated assumptions. I didn't have the time — or the inside knowledge of what buyers in this category actually optimize for — to be certain these are the metrics that matter most. The four categories and their weights are editorial judgment, not measurement: nobody has proven that these things cause employees to post, and I don't claim otherwise.
Where the evidence comes from: three of the four categories read only what your company has published on its own public site — the part you can fix on Monday. Half of Employee & Culture comes from somewhere else: aggregate counts of how many of your people posted in the last 90 days, from a licensed third-party index of public professional-network activity. Nothing here was scraped from LinkedIn by this tool. Those counts are records in an index, not a census — they undercount, they undercount small companies most, and you can't check them yourself — so each one says so where it appears, a zero is reported as "none in the index" and never as "nobody posts," and a company with fewer than 25 people in the index gets the number reported but not scored. No individual is named anywhere in this report.
To prioritize speed, this particular report was loaded using cached data; it was generated from evidence originally collected on August 31, 2026 rather than live. Reports are cached for 30 days. Every observation below is dated and cited.
What you can hold me to: every number cites its evidence and says where it came from, nothing unseen is guessed at, robots.txt is respected on every fetch, and when this tool can't read a site it says so instead of issuing a grade.
What was found — most fixable first
Ranked by impact × ease of fixing, not by category. Counts describe the pages actually read, and each finding cites them.
Only 7 of 24 sampled pages carry a share image (og:image)
7 of 24 sampled content pages (29.2%) (sampled from the slice of the site that could be read) carry a share image (og:image); the rest do not. Without an og:image, most platforms render a shared link as a bare grey box.
Evidence — content page sample
- https://www.nvidia.cn/about-nvidia/careers/life-at-nvidia/
- https://www.nvidia.cn/webinars/220317-20768/
- https://www.nvidia.cn/webinars/220623-21799/
- https://www.nvidia.com/ja-jp/events/omniverse-hayawakari-webinar-5-japan/
- https://www.nvidia.cn/about-nvidia/press-releases/2010/sli-sandy-bridge-form-ultimate-gaming-pc-20101207/
- https://www.nvidia.cn/about-nvidia/press-releases/2011/cuda-platform-compiler-source-code-20111214/
- https://www.nvidia.cn/about-nvidia/press-releases/2011/tesla-motor-model-s-features-tegra-processors-20110104/
- https://www.nvidia.cn/about-nvidia/press-releases/2012/tesla-k20-powers-titan-worlds-fastest-supercomputing-20121029/
- … and 9 more in the sample
The fix: Add a default share image to the content template, and per-post images where you have art.
0 of 24 sampled pages carry Article structured data
None of the 24 content pages sampled (sampled from the slice of the site that could be read) carry Article structured data. Machine readers cannot tell these pages are articles, or when they were published, or by whom.
Evidence — content page sample
- https://www.nvidia.cn/case-studies/pegatron-scales-factory-operations-with-visual-ai-digital-twins/
- https://www.nvidia.cn/customer-stories/activision/
- https://www.nvidia.com/en-us/case-studies/instacart/
- https://www.nvidia.com/en-gb/case-studies/zalando-allsides-3d-digital-twins/
- https://www.nvidia.cn/about-nvidia/careers/life-at-nvidia/
- https://www.nvidia.cn/webinars/220317-20768/
- https://www.nvidia.cn/webinars/220623-21799/
- https://www.nvidia.com/ja-jp/events/omniverse-hayawakari-webinar-5-japan/
- … and 16 more in the sample
The fix: Emit Article (or BlogPosting) JSON-LD with headline, datePublished and author in the content template.
0 of 24 sampled pages name a human author
None of the 24 sampled content pages (sampled from the slice of the site that could be read) carry a named human author — no byline, no author schema, no rel=author. Content nobody signs is content nobody feels ownership of; advocacy runs on employees being visible in the work.
Evidence: content page sample — 0 of 24 sampled pages.
The fix: Add author bylines to content pages — a name, ideally with a link or an author block in the Article schema. Start with new posts; backfilling can wait.
Only 8 of 24 sampled pages carry a share description (og:description)
8 of 24 sampled content pages (33.3%) (sampled from the slice of the site that could be read) carry a share description (og:description); the rest do not. The preview card shows the title with no supporting line.
Evidence — content page sample
- https://www.nvidia.cn/webinars/220317-20768/
- https://www.nvidia.cn/webinars/220623-21799/
- https://www.nvidia.com/ja-jp/events/omniverse-hayawakari-webinar-5-japan/
- https://www.nvidia.cn/about-nvidia/press-releases/2010/sli-sandy-bridge-form-ultimate-gaming-pc-20101207/
- https://www.nvidia.cn/about-nvidia/press-releases/2011/cuda-platform-compiler-source-code-20111214/
- https://www.nvidia.cn/about-nvidia/press-releases/2011/tesla-motor-model-s-features-tegra-processors-20110104/
- https://www.nvidia.cn/about-nvidia/press-releases/2012/tesla-k20-powers-titan-worlds-fastest-supercomputing-20121029/
- https://www.nvidia.cn/about-nvidia/press-releases/2013/
- … and 8 more in the sample
The fix: Emit the post excerpt as og:description in the template.
Your job listings are invisible without JavaScript
Your careers page (https://www.nvidia.com/en-us/about-nvidia/careers) returns HTML, but the job listings are injected client-side — a plain reader sees a page with no roles on it. Machine readers that do not execute JavaScript (many crawlers and AI assistants) cannot see that you are hiring.
Evidence — careers page probes
- https://www.nvidia.com/en-us/about-nvidia/careers
The fix: Server-render at least the role titles and locations, or publish jobs in structured data (schema.org JobPosting).
Only 2 of 24 sampled pages carry a visible share control
2 of 24 sampled content pages (8.3%) (sampled from the slice of the site that could be read) carry a visible share control; the rest do not. Nothing on the page invites a reader — or an employee — to share it.
Evidence — content page sample
- https://www.nvidia.cn/case-studies/pegatron-scales-factory-operations-with-visual-ai-digital-twins/
- https://www.nvidia.cn/customer-stories/activision/
- https://www.nvidia.com/en-us/case-studies/instacart/
- https://www.nvidia.com/en-gb/case-studies/zalando-allsides-3d-digital-twins/
- https://www.nvidia.cn/about-nvidia/careers/life-at-nvidia/
- https://www.nvidia.cn/webinars/220317-20768/
- https://www.nvidia.cn/webinars/220623-21799/
- https://www.nvidia.com/ja-jp/events/omniverse-hayawakari-webinar-5-japan/
- … and 14 more in the sample
The fix: Add share links or buttons to the content template. Plain links to the platform share endpoints work without any tracking script.
What's already working
All tracked AI user-agents may read your site
robots.txt permits all 25 tracked AI user-agents at the site root, so AI search engines and assistants that honor robots.txt can read and cite you.
Evidence: robots.txt.
Your homepage share card is complete
The homepage carries og:title, og:description and og:image, so a shared homepage link renders a full preview card.
Evidence: homepage HTML.
Content is localized across 44 locales
44,093 URLs are localized variants across 44 locales. I count each piece of content once (localization is maturity, not volume), but a multi-language surface is real evidence of marketing investment — and gives non-English-speaking employees something to share.
Evidence: sitemap URL classification.
What could not be seen
Anything the reader could not observe is listed here rather than guessed at or silently skipped.
The reader could not classify most of your site
Of the 47,762 URLs in your sitemap, 34,056 (71.3%) could not be sorted into content sections by the path-based classifier — the unread majority sits under paths like /geforce (18435), /on-demand (4366), /data-center (2512), /networking (1307), /gtc (848), /nvidia (783). That is a limit of this tool's reading, not evidence you lack content, so no letter grade is issued and the volume-based scores below are floors, not measurements.
Evidence — sitemap URL classification
- /geforce — 18435 URL(s) that could not be classified
- /on-demand — 4366 URL(s) that could not be classified
- /data-center — 2512 URL(s) that could not be classified
- /networking — 1307 URL(s) that could not be classified
- /gtc — 848 URL(s) that could not be classified
- /nvidia — 783 URL(s) that could not be classified
- /design-visualization — 588 URL(s) that could not be classified
- /ai-data-science — 538 URL(s) that could not be classified
For the record
llms.txt is present
An llms.txt file is served. Reported for completeness: Google has said it does not support llms.txt, no major AI vendor has confirmed consuming it, and large-scale studies found no correlation with AI citations. I record it and weight it at zero.
Evidence: llms.txt fetch.
How the numbers break down
Weights: Content Supply 30% · Shareability 25% · Employee & Culture 25% (half what the site says, half what employees do) · AI Discoverability 20%. The weights are editorial judgment about what an advocacy program draws on — not the result of a study. Every row cites the observation behind it and says whether it was read from your site or from the licensed index.
Content Supply — 66.6/100 (reduced confidence)
| Signal | Points | What was observed |
|---|---|---|
| Volume floor | 34/40 | 2012 shareable pages after collapsing localized duplicates and excluding 28 non-shareable page(s) (terms, sweepstakes, registration and similar) |
| Section diversity | 27/30 | 6 shareable section(s): case_study, resource, news_press, event_webinar, podcast_video, culture |
| Shareable share | 4.9/30 | 12.2% of the canonical inventory is shareable content |
| Recency adjustment | 0.7/8 | 13990 of 47732 dated URLs updated in the last year (29%) |
Low-coverage caveat: 34056 of 47762 sitemap URLs (71.3%) could not be classified, so this score describes only the 2012 page(s) that could be read and section-sorted. It is a floor, not a measurement of the whole site.
Shareability — 29.2/100 (reduced confidence)
| Signal | Points | What was observed |
|---|---|---|
| Open Graph image — without one, a shared link renders as a bare grey box | 10.2/35 | 7 of 24 sampled pages (29.2%) |
| Open Graph title on the shared card | 8.1/15 | 13 of 24 sampled pages (54.2%) |
| Open Graph description on the shared card | 5/15 | 8 of 24 sampled pages (33.3%) |
| A visible share control on the page | 2.5/30 | 2 of 24 sampled pages (8.3%) |
| Twitter/X card tags (near-zero weight: X falls back to Open Graph) | 1.4/3 | 11 of 24 sampled pages (45.8%) |
| Canonical URL (near-zero weight: SEO hygiene, not a sharing condition) | 2/2 | 24 of 24 sampled pages (100%) |
Low-coverage caveat: 34056 of 47762 sitemap URLs (71.3%) could not be classified, so this score describes only the 2012 page(s) that could be read and section-sorted. It is a floor, not a measurement of the whole site.
Employee & Culture — 46/100 (reduced confidence)
| Signal | Points | What was observed |
|---|---|---|
| What the site says (50 of 100) | ||
| Culture / life-at pages | 6/15 | 2 culture page(s) in the canonical inventory |
| Careers page reachable | 7.5/7.5 | A careers page was found and retrieved |
| Careers depth | 0/7.5 | 0 careers URL(s) in the sitemap |
| Named authors on content | 0/12.5 | 0% of sampled pages carry a named author |
| Employee-story signals | 7.5/7.5 | 3 of 3 sampled culture URL(s) match employee-story patterns (life-at, employee spotlight, meet-the-team) |
| What employees do (50 of 100) | ||
| Employees posting (last 90 days) | 11.8/25 | 3961 of 43574 indexed employees posted in the last 90 days (9.1%). licensed third-party index (not independently verifiable); 43574 of 51530 employees covered. |
| Decision-makers posting | 3.3/15 | 407 decision-makers posted in the last 90 days (0.9% of indexed employees). licensed third-party index (not independently verifiable). |
| Company page posting cadence | 10/10 | 219 company post(s) in the last 90 days in the index. licensed third-party index (not independently verifiable). |
A qualitative read of the careers page (boilerplate vs. real human stories) is not included in this number.
Half of this category is measured from employee posting activity in a licensed third-party index (43574 of 51530 employees covered). Those counts are records in a third-party index, a lower bound the visitor cannot verify independently; the other half is what the website itself shows.
Low-coverage caveat: 34056 of 47762 sitemap URLs (71.3%) could not be classified, so this score describes only the 2012 page(s) that could be read and section-sorted. It is a floor, not a measurement of the whole site.
AI Discoverability — 68/100
| Signal | Points | What was observed |
|---|---|---|
| AI crawler access | 45/45 | All 25 tracked AI user-agents are permitted at the site root |
| Content-Signal coherence | 15/15 | Content-Signal "ai-train=yes, search=yes, ai-input=yes" is consistent with the crawl directives. |
| Structured data | 8/40 | 3 schema.org type(s) on the homepage; 0% of sampled content pages carry Article schema |
| llms.txt | 0/0 | Present. Scored at zero weight deliberately: Google has said it does not support llms.txt, no major AI vendor has confirmed consuming it, and large-scale studies found no correlation with AI citations. |
robots.txt compliance is voluntary and advisory. This reports the declared policy; it is not a claim that any crawler was actually blocked.