MOCKUP for sign-off · Technical + Page structure wired with real data · other categories are layout placeholders
Patrick Cookman · Page Audit
2026-07-03
Page Audit — Epoch AI

AI chips topic overview

10
10 opportunities found across the two categories wired so far.
Each one is a specific, worthwhile improvement — not a warning to rank or ignore. Work through as many as you have capacity for.

Benchmarks

current state · re-measured each audit
Search clicks (last 28 days)
56
10,706 impressions · avg position 5.7
first audit — no prior
Traffic since launch
≈ flat
Launched May 2026 · 107 → 59 clicks (May → part-June)
first audit — no prior
Earned backlinks
5
external, from 4 referring domains
first audit — no prior
Keywords ranking in top 5
23
8 of them in the top 3
first audit — no prior
Cited in AI Overviews
0
not yet used as a named source
first audit — no prior
Impressions in AI answers
2,330
shown in AI-generated results (GSC, 28d)
first audit — no prior
Where visitors come from — 806 visitors (last 28 days)
internal313
direct218
search204
email40
social25
llm21

Opportunities by area

tap a category to jump to it
Technical
7 checks
3 opportunities
Page structure
11 checks
7 opportunities
Meta & markup
full build
soon
Utility & helpfulness
full build
soon
Audience
full build
soon
Queries & coverage
full build
soon
Answer optimization
full build
soon
Inbound links
full build
soon
Outbound links
full build
soon
Visual assets
full build
soon
E-E-A-T & brand
full build
soon

Technical

7 checks · 3 opportunities · 4 passing
Does the page meet Google's PageSpeed & Core Web Vitals standards?
Whether the page loads, stays stable, and responds quickly enough for real users.
Why it matters
Core Web Vitals measure how well the page loads, stays stable and responds for real users, and Google uses them as a ranking signal.
What we found
Mobile
Largest Contentful PaintPass965ms
Cumulative Layout ShiftPass0.01
Interaction to Next PaintFail456ms
Desktop
Largest Contentful PaintPass718ms
Cumulative Layout ShiftPass0.03
Interaction to Next PaintPass58ms
How to fix
Ask your web developer to check the page in Google PageSpeed Insights or Lighthouse and follow its recommendations.
Are the page's assets crawlable?
Whether the real content is visible to a crawler, or only appears after code runs in the browser.
Why it matters
A crawler has to read the content to index it, and content available only in the visitor's browser can be missed.
What we found
The 4 interactive data tables are embedded as iframes, which search engines and AI crawlers cannot read.
How to fix
Ask your web developer to render the page's main content on the server so it's in the initial HTML, and follow Google's JavaScript SEO best practices.
Has this page ever existed on another URL?
Whether the page was moved from an older address that still needs to redirect cleanly.
Why it matters
If a page was moved, search engines split its history and links across the old and new URLs, so its performance is easy to undercount unless the old URL redirects cleanly to this one.
What we found
Previously lived at another URLYes/blog/chips-topic-overview
Old URL redirects directly to this pagePass301
Internal links still routing through the redirectFail6
How to fix
Ask your web developer to make sure the old URL 301-redirects straight to this page, and to update internal links that point to the old URL so they link here directly instead of through the redirect.
Full data
N/A
✓ 4 checks passed — no action needed
Is it in the XML sitemap?
Found in the sitemap (sitemap-publications-0.xml).
Is the canonical tag correct?
Points to the page's own URL, and Google has selected that same URL.
Is the URL structure sound?
Clean and well-structured: lowercase, readable, hyphen-separated, no parameters.
Is the page indexable?
No noindex tag, not blocked, canonical points to itself, indexed by Google.

Page structure

11 checks · 7 opportunities · 4 passing
Is the H1 optimized?
The main headline — clear about what's on the page and compelling enough to draw the reader in.
Why it matters
The H1 is the most prominent headline on the page, and a clear one reassures visitors they've landed on the page that will answer what they came for, so they stay.
What we found
Patrick's analysis: the H1 could be more specific. As written it only works as a hook if the person who landed on the page is already the right reader — it doesn't do much to pull in or qualify someone on the fence.
How to fix
Write an H1 that signals what the page delivers and is compelling enough to earn attention.
Full data
N/A
Are the key takeaways easy to find in each section?
Whether each section's main point is easy to spot at a glance when scanning.
Why it matters
Most people scan instead of reading every word, so each section's key point needs to stand out for them to catch it.
What we found
Why AI companies want more chips than they can getFail
AI chips get more cost-effective every yearPass
Electricity efficiency is increasing, but so is total consumptionPass
AI chips sit at the center of progress in AIPass
How to fix
In each section, make the main point stand out at a glance — for example by bolding the key line or leading the section with it.
Full data
N/A
Does the page use tables and lists?
Whether content that suits a list or table is set as one, instead of buried in prose.
Why it matters
Lists and tables break content into scannable chunks readers can skim and search engines can read cleanly, and each item becomes a discrete point an AI answer system can lift out on its own.
What we found
ListsNone
TablesNone
How to fix
Put content that's a set of steps, items or comparisons into proper lists or tables.
Full data
Content currently in prose that would read better as a small list or table:
  • Who designs the chips (Nvidia, Google, Amazon, AMD, Huawei) vs who fabricates them (TSMC).
  • The three high-bandwidth-memory makers named mid-sentence (Samsung, SK Hynix, Micron).
  • The vendor market-share breakdown (Nvidia ~half of units and 66% of compute, Google second, Huawei ~6%).
  • The chip comparison: the newer chip costs 6× the price but does 17× the compute per dollar.
  • The full supply chain as a sequence: design → fabrication → memory → equipment.
Does the page front-load the answer?
Whether the page leads with its main answer near the top, where readers and AI systems find it.
Why it matters
A page's main point is picked up most reliably when it sits near the top, so a key answer placed high is more likely to be seen by readers and used by AI systems that pull answers from your content.
What we found
The page names both halves of its answer at the very top and delivers the short-supply half right away, but the "why they're expensive" half isn't answered where a reader expects it — its treatment is held back to the second section, and there it's turned into the opposite point (that chips are getting cheaper for the work they do), so half the promised answer isn't front-loaded.
How to fix
Put the page's main answer near the top; if a key point sits in the middle, move it up or restate it in a shorter form near the beginning.
Full data
N/A
Does the page have a logical, user-friendly heading structure?
Whether headings form a clear outline that labels each section so the page is easy to follow.
Why it matters
A logical, consistent heading structure lets readers scan and navigate the page, and clearly labels each section for search engines and AI systems too.
What we found
The headings are all meaningful and section the page, but coverage is uneven — the opening section runs about 9 to 11 unbroken paragraphs with no subheading to break it up, while the final section is only 2, so the headings don't work as a reliable way to navigate.
How to fix
Give each section a clear heading and keep the heading structure logical and consistent across the page.
Full data
N/A
Are the sections formatted to be scannable?
Whether sections are formatted to be skimmed — bold on key points, lists where they fit, short paragraphs.
Why it matters
Only a small share of readers read every word; most scan, so sections formatted to be skimmed are the ones that hold attention.
What we found
The sections read mostly as long, unbroken paragraphs with almost no bold to surface key points and no lists where list-shaped content would fit, so a skimmer has little to catch their eye between the charts.
How to fix
Break sections up with short paragraphs, bold on the key points, and lists where the content suits them.
Full data
N/A
Does the page have a table of contents?
On-page links to the page's sections so readers can jump straight to what they want.
Why it matters
It lets visitors scan the core topics quickly and jump to the part they want, and it can trigger sitelinks in search results that win more clicks.
What we found
Patrick's analysis: the page has no jump links. It should add contextual jump links at the start of the article rather than a full table of contents. If it grows into an evergreen resource they keep adding to, they should then consider a proper table of contents (e.g. in the sidebar).
How to fix
Add a short set of jump links to the top of longer pages so readers can skip to each section.
Full data
N/A
✓ 4 checks passed — no action needed
Is it clear what the page is about and who it's for without scrolling?
The topic is obvious above the fold from the H1 and standfirst; the audience is implied by the topic and writing level, which is fine here.
Is the introduction engaging?
Opens straight onto the stakes, then lays out the exact questions the page will answer.
Are the paragraphs too long for web attention?
No paragraph runs longer than the 5–6 sentence bar (the longest is 6).
Does each paragraph cover just one idea?
Each paragraph holds to a single idea.

Quick fixes

minor · unscored
A link in the closing paragraph points to the wrong place.
The reader is pointed to "the data explorers", but the "Machine Learning Hardware" link goes to the blog report instead of the data explorer. Easily repointed. closing next-step paragraph
The Nvidia photo's alt text is thin.
It identifies the subject ("An image of an Nvidia Blackwell chip.") so it passes, but it's a candidate to tighten into a fuller description. intro figure · nvidia-blackwell-chip.jpg

Competitors

optional · unscored · layout placeholder
A side-by-side of how competing pages cover the same topic. Wired in the full build.