Skip to content

Skill S16 · Vitrine — SEO Auditor

/seo-auditor

Audits on-page SEO page by page — titles, descriptions, headings, semantic HTML, internal links, alt text and search intent — and writes the exact fix for each.

Before launch, when pages aren't showing up for the searches they should, or after a redesign changed every template.

This is about what each page says and how it is structured. For crawling, sitemaps, canonicals and structured data, run /technical-seo-audit. Nothing here guarantees rankings; it removes the reasons a good page gets misread.

0. Inventory first

  • List every indexable route (from the sitemap, the router, or a crawl). For each, record: URL, <title>, meta description, h1, the h2 outline, word count, and inbound internal links.
  • Put it in a table. Most problems are only visible side by side: duplicate titles, empty descriptions, orphan pages.

1. Search intent, per page

  • For each page write one line: who searches for this, with what words, wanting what? ("a developer searching 'react glass button' wants a copyable component and its code").
  • Pass when the h1, the first paragraph and the first screen answer that intent directly. A page that needs scrolling before it says what it is fails.
  • If two pages answer the same intent, merge them or make one clearly different. They compete with each other otherwise.

2. Titles

  • 50–60 characters, unique per page, the page's subject first, brand last: Silk Field — React WebGL background · Vitrine.
  • Generated pages (products, components, posts) build the title from real data, never a fixed string. Check that 100 generated pages give 100 different titles.
  • Fix format: write the new title for every failing page, not a rule.

3. Meta descriptions

  • 120–160 characters, a plain sentence describing what's on the page and what you can do there. No keyword lists, no "Welcome to".
  • Unique per page. On generated pages use the item's own description; fall back to a template only if it includes the item's name and category.

4. Headings and semantics

  • Exactly one h1, which matches the page's subject (it can differ from the title in wording).
  • h2/h3 form an outline you could read alone. Never skip levels for styling; style the right level instead.
  • Landmarks exist: header, nav, main, footer. Lists are ul/ol, navigation is links (<a href>), actions are buttons. Search engines and screen readers read the same structure.
  • Content that matters is in the HTML on first load, not only after a click or a client-side fetch.

5. Internal links

  • Every important page is reachable in ≤ 3 clicks from the home page and has at least 2 inbound links from relevant pages.
  • Anchor text describes the target ("glass buttons", not "click here" or "more").
  • Related pages link to each other (a component links to its category and to recipes that use it; a category links to its components).
  • Find orphans: pages in the sitemap with zero inbound internal links.

6. Images

  • Informative images have alt text that says what the image shows in context. Decorative images (backgrounds, flourishes) have alt="".
  • Use descriptive file names and real width/height so they don't shift layout.

7. Content hierarchy

  • The most important thing on the page is the most visible, and appears first in the source order.
  • Thin pages (a heading and a widget) get a sentence or two of real explanation: what it is, when to use it, what makes it different.

Output

A table: URL · problem · current value · replacement. Then apply the fixes, re-run the inventory, and confirm every row passes.

Featured

01Glassbreak ButtonA solid plate that fractures from one impact point, cracks racing outward as the shards drift apart.04Liquid GlassA capsule of glass that bends what's behind it, carries a specular highlight around its rim toward your pointer, and squashes like a drop of liquid when pressed.07Phosphor Glass ButtonA liquid-glass pill that senses you coming: its rim light turns to face the cursor and the pill leans in to meet it.08Iris ShutterAn async button with a camera iris for a status light — blades close and turn while it works, then open onto the result.
81Atmosphere CardSmoked-glass link cards: colour pooled in the corners, slow contour currents underneath, a field that leans toward you.93Eclipse Event CardAn editorial event plate with an oversized date and an orbital eclipse bleeding in from the right, alive with slow drift.94Specimen CardAn object mounted under glass: hover lifts the pane with a sweep of reflection and swings out a paper catalogue tag.
95Silk FieldDomain-warped light that pours like liquid silk, with an optional glass lens that refracts the flow under your cursor.106IsobarA living weather map — contour lines traced over a drifting pressure field, with your cursor as a system of its own.
151Prompt ComposerA chat composer where attached files tuck into its top edge like tabs in a folder — they rise from behind it when added and sink back when removed. Send turns into stop while the reply streams.157Aura FieldA writing field where colour only exists while the AI is touching your text: the edge becomes a turning band of light and the words are rewritten in place, one by one, out of a soft blur.
205Halftone CTAA tall CTA banner where slow gold paint drifts beneath a fixed halftone grid, visible only through the dots.
212Nocturne Sign-inA single quiet column on near-black with a breathing seam of frost light behind it — email, password, magic link, nothing more.222Sigil Sign-inA split sign-in whose left half grows a geometric mark from your email — the same address always draws the same sigil.
275Voices CarouselA testimonial exhibition: one large quote at a time on frosted glass, crossfading between voices without ever resizing.
279Feral TitleA brutal condensed wordmark — heartbeat in the dark, letters slam in, a gash tears through and the word bleeds.
301 components