Clear for visitors, hard to read for AI crawlers
Start with these 3
In brief
What works
- The offer is clear in 5 seconds
- Encrypted connection with HSTS
- Fast server response
What blocks
- 14 of 25 pages look empty without JavaScript
- No structured data
- Not cited in any market answer
Your site, seen from outside
On Google
https://www.atelier-lumen.example/
Atelier Lumen
Quotes and schedules for tradespeople, on your phone. Write a quote in two minutes and get it signed on site.
Built from the page's tags: Google can rewrite them.
When someone shares it
What an AI crawler reads, without JavaScript
https://www.atelier-lumen.example/
620 words readable
Your quotes and your jobs, on one screen. Write a quote in two minutes and get it signed on site.
What an AI crawler reads, without JavaScript
https://www.atelier-lumen.example/features/quotes
31 words nearly empty
You need to enable JavaScript to run this app.
What AI assistants answer
Market answers citing you: 0 of 4
Cited in your place
- Competitor A3
- Competitor B2
- Competitor D2
- Competitor C1
The number of market answers naming each one. This run is a snapshot: answers vary.
Q1Which quoting and scheduling software should a UK tradesperson choose?
Recommends three products and a press comparison
Relies on two buying guides that do not mention the brand
Q2How can a tradesperson write quotes on their phone?
Lists mobile apps, Atelier Lumen is not one of them
Quotes a competitor's help page
Q3What is Atelier Lumen?
Describes the product correctly, but repeats the older customer figure
Correct description, taken from the home page
The 10 most useful fixes
Site detected Next.js · Nginx
4 ready files are in the fixes/ folder next to this report. They are drafts to read before use: nothing has been changed on the site.
Score today: 5.0. With all these fixes confirmed: up to 10.0.
Your ticks stay in this browser and only give an estimate, on the audit's score and not on any ranking. To confirm them, ask Claude to recheck this audit.
Claude can apply 9 of these 16 fixes in the code of your site
On a branch of its own, one commit per fix, tested on your machine. Nothing goes online without you. The others need your facts or are settled off the code. Paste this in Claude Code and fill in the two folders:
Fix my site with this audit. The audit is in: [folder of this report]. The code of the site is in: [folder of your site].
Fixes waiting for your answers: 4
Answer what you can, leave the rest empty, and paste it in Claude Code: it applies these fixes with your words, on the same branch.
Here are my answers, to finish the fixes of this audit. The audit is in: [folder of this report]. The code of the site is in: [folder of your site]. C3 · Answer buyers' real questions - Who buys from you, and what do they ask before deciding? → - What exactly do you offer them, and how does it work? → - Can prices or price ranges be published? → C4 · Make the next step obvious - What is the one action a visitor should take first? → - What can you offer someone who is not ready yet (a guide, a trial, a call)? → C5 · Add proof and trust - Which clients can be named, with their agreement? → - Which figures have a source? → - Who signs the testimonials (full name and role)? → C6 · Make the entity easy to identify - Exact name, year founded, address, and who leads it? → - Which public profiles are yours (LinkedIn, directories...)? → - Which old pages or profiles should be removed or redirected? →
The product pages are React pages rendered in the browser: pre-render them with the framework's static export, so the text is in the HTML received. Most AI crawlers do not run JavaScript
Where The pages and layouts of the site
How Keep the text in server components, without "use client" at the top of the page. Move only what is interactive to a small client component.
curl <page> shows the main text of the pageSend the security headers the site does not send yet, and hide the server version if it shows
Where The server block of the site
How Add the lines below, then run nginx -t and reload.
Ready file fixes/security-headers.nginx.conf
# Draft from the audit: read it before using it. The Content-Security-Policy only reports for now: once nothing legitimate shows up as blocked in the browser console, rename it Content-Security-Policy. add_header X-Frame-Options "SAMEORIGIN" always; add_header Referrer-Policy "strict-origin-when-cross-origin" always; add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always; add_header Content-Security-Policy-Report-Only "default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; frame-ancestors 'self'" always;
Give each page a unique title of 65 characters at most, a description of 140 to 160 characters, and a complete share preview (title, description, image)
Today
https://www.atelier-lumen.example/features/quotes
Atelier Lumen
After the fix
https://www.atelier-lumen.example/features/quotes
Quotes on your phone for tradespeople · Atelier Lumen
Where metadata in the layout and the pages
How Keep the site's name in the layout's template only, and give each page its own short title.
// app/layout.tsx
export const metadata = {
title: { default: "Atelier Lumen", template: "%s · Atelier Lumen" },
}
// in a page: the template adds the name
export const metadata = { title: "The topic of the page" }Ready file fixes/titles-to-fix.csv
Page,Current title,Length,Problem,Suggested title,Description length https://www.atelier-lumen.example/,Atelier Lumen,13,same title as another page,,109 https://www.atelier-lumen.example/features/quotes,Atelier Lumen,13,same title as another page; no description,,0 https://www.atelier-lumen.example/about,About · Atelier Lumen · Atelier Lumen,37,a name repeated; no description,About · Atelier Lumen,0
Add an Organization block with sameAs on the home page, then Product, Service, Article or FAQPage according to the page type
Where The root layout
How Add the block below to the page, check its content, and add Product, Service, Article or FAQPage on the matching pages.
<script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(organization) }} />Ready file fixes/organization-jsonld.html
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Atelier Lumen",
"url": "https://www.atelier-lumen.example",
"description": "Quotes and schedules for tradespeople, on your phone. Write a quote in two minutes and get it signed on site.",
"logo": "https://www.atelier-lumen.example/TODO-logo.png",
"sameAs": [
"https://www.linkedin.com/company/atelier-lumen"
]
}
</script>
Look at the sources AI cites on your market questions, then publish equivalent pages and get listed in those guides and comparisonsVerified when the same questions, asked 3 times each, cite the brand in at least 2 runs out of 3
Redirect http and the other host (www or not) with a 301 to the main address, add a canonical tag to every page, and link the translations of each page with hreflang
Where The server block of the site
How Send the other address to the main one, then add a canonical tag to the page template.
server {
listen 80;
server_name your-domain.com www.your-domain.com;
return 301 https://your-domain.com$request_uri;
}Fix or redirect the pages in error, and make unknown addresses answer with a 404 codeVerified when a new crawl finds no page in error and an unknown address answers 404
Follow the top opportunities listed by PageSpeed: lighter images, less JavaScript, fewer third-party scriptsVerified when PageSpeed on mobile reaches 90, median of 3 runs
Keep exactly one H1 per page, in a logical order, and add a space around each line break inside headingsVerified when the crawl counts 0 pages with no H1, several H1 or glued words
Add pages that answer the questions and intents of the audience: use cases, comparisons, pricing, FAQ
- Who buys from you, and what do they ask before deciding?
- What exactly do you offer them, and how does it work?
- Can prices or price ranges be published?
6 more, less urgent
Show one main call to action on each key page, and add an intermediate offer for visitors who are not ready (guide, trial, webinar)
- What is the one action a visitor should take first?
- What can you offer someone who is not ready yet (a guide, a trial, a call)?
Show named customers, sourced figures, testimonials, named authors, legal information and a real contact
- Which clients can be named, with their agreement?
- Which figures have a source?
- Who signs the testimonials (full name and role)?
Fix the contrasts, alternative texts, form labels and keyboard focus flagged by PageSpeed and WAVEVerified when PageSpeed accessibility reaches 90 and WAVE shows no error
Allow OAI-SearchBot, Claude-SearchBot and PerplexityBot, the crawlers that decide citations, and publish an llms.txt that sums up the key facts. Allowing training crawlers (GPTBot, ClaudeBot) is a separate choice
Where The public/ folder (static/ with Gatsby)
How Put llms.txt there and publish: it must answer at /llms.txt. Check that robots.txt does not block OAI-SearchBot, Claude-SearchBot or PerplexityBot.
Ready file fixes/llms.txt
# Atelier Lumen > Quotes and schedules for tradespeople, on your phone. Write a quote in two minutes and get it signed on site. ## Main pages - [Atelier Lumen](https://www.atelier-lumen.example/): Quotes and schedules for tradespeople, on your phone. Write a quote in two minutes and get it signed on site. - [Atelier Lumen](https://www.atelier-lumen.example/features/quotes) - [About · Atelier Lumen](https://www.atelier-lumen.example/about) - [Pricing · Atelier Lumen](https://www.atelier-lumen.example/pricing): Plans for sole traders and small building firms, with a free trial.
Write a complete "about" page (legal name, address, year, leaders), and create or correct the Wikidata entry and public profiles
- Exact name, year founded, address, and who leads it?
- Which public profiles are yours (LinkedIn, directories...)?
- Which old pages or profiles should be removed or redirected?
Enable Brotli or gzip, and send Cache-Control with a long duration on versioned static filesVerified when the response has a Content-Encoding header and PageSpeed no longer flags the cache
The 30 criteria
2 correct · 1 partial · 0 missing or wrong · NV not verifiable, excluded from the score
| # | Criterion | Score | Evidence | Source |
|---|---|---|---|---|
| A. Crawling and indexing · 6.3 / 10 | ||||
| A1 | Robot access | 2 | robots.txt answers 200; Googlebot allowed; addresses in the sitemap: 64; pages in noindex: 0 | automatic |
| A2 | One version of the site | 1 | http answers 301; atelier-lumen.example: 301; pages without canonical: 9 of 25 | automatic |
| A3 | HTTP codes | 1 | pages in error: 1 of 26; an unknown address answers 200 | automatic |
| A4 | Rendering | 1 | pages that look empty without JavaScript: 14 of 25; the first page is readable | automatic |
| A5 | Structure | NV | not checked | |
| B. Performance and front-end · 5.0 / 10 | ||||
| B1 | Real-user Core Web Vitals | NV | not checked | |
| B2 | Mobile performance | 1 | PageSpeed on mobile: 58 / 100, one run | automatic |
| B3 | Images | NV | not checked | |
| B4 | Code | NV | not checked | |
| B5 | Mobile | NV | not checked | |
| C. Server, security and privacy · 6.3 / 10 | ||||
| C1 | Encryption | 2 | address in https; HSTS present | automatic |
| C2 | Security headers | 0 | security headers present: 1 of 5; server version shown: nginx/1.18.0; Mozilla Observatory: D (35 / 100) | automatic |
| C3 | Transport | 1 | compression: gzip; Cache-Control on the first page: none (static files are not checked in quick mode) | automatic |
| C4 | Response time | 2 | median TTFB of 410 ms, measured from one location | automatic |
| C5 | Privacy | NV | not checked | |
| D. Content and editorial SEO · 3.3 / 10 | ||||
| D1 | Titles, descriptions and sharing | 0 | pages with a defect: 16 of 25. Without description: 16; title repeating a name: 0; title over 65 characters: 3; title duplicated within a language: 4; incomplete share preview: 25 | automatic |
| D2 | Headings | 1 | pages without exactly one H1, or with glued words: 6 of 25 | automatic |
| D3 | Depth | 1 | The product pages explain the features, but no page answers "which software should I choose?" or shows prices clearly | read by Claude |
| D4 | Accuracy | NV | not checked | |
| D5 | Freshness and languages | NV | not checked | |
| E. Experience, accessibility and conversion · 6.3 / 10 | ||||
| E1 | The 5 seconds | 2 | The home page says what it is and for whom in its first lines: "quotes and schedules for tradespeople, on your phone" | read by Claude |
| E2 | Call to action and intermediate offer | 1 | A free trial button on each key page, but nothing for visitors who are not ready to try | read by Claude |
| E3 | Form | NV | not checked | |
| E4 | Proof and trust | 1 | Testimonials without surnames, and two different customer figures | read by Claude |
| E5 | Accessibility | 1 | PageSpeed accessibility: 84 / 100 (automatic checks only catch part of WCAG) | automatic |
| F. GEO and authority · 2.5 / 10 | ||||
| F1 | Structured data | 0 | no JSON-LD found | automatic |
| F2 | AI access | 1 | AI search crawlers blocked: none; llms.txt answers 404 | automatic |
| F3 | Entity | 1 | "about" page: found; Wikidata: not found | automatic |
| F4 | Citable content and authority | NV | not checked | |
| F5 | Presence in answers | 0 | market answers citing the site: 0 of 4 | AI panel |
Measures you can repeat
- PageSpeed Insights: performance 58 / 100, accessibility 84 / 100
- Mozilla HTTP Observatory: D · 35 / 100
- Security Headers
- Rich Results Test
What this quick audit does not cover
It reads at most 25 pages, runs each test once, and has no screenshot as evidence for each finding. Speed comes from one PageSpeed run, and visitors' real data only when Google has it. It does not replace Search Console, and it promises no ranking and no citation.
To go further
Run the full audit for screenshots as evidence, the complete AI panel, every criterion and a report ready to present: /audit-seo-geo:audit-seo-geo full https://www.atelier-lumen.example/, or ask for a detailed audit in your own words.