Website report
Visit sitehttps://www.trychalk.tech/
Hold ⌘⌥ and ask about anything on your Mac: chalk answers out loud and points at the real thing, one step at a time. Or say what you want to learn, and it builds you a course of interactive classes.
Audit Full discovery audit·Language English (en)·Response HTTP 200·Served by Vercel
Analysed Nov 7, 2026 · 15 categories · 89 passed · 28 warnings · 1 issue · 32 informational
Partial evidence; some observations were unavailable.
Audit score
D55/100
Mixed
- Agentic
- 100
- SEO
- 55
What we found
1Needs a fix28Could be better89Looks good32Informational- 1.Needs a fix: Your pages repeat the same titles. see checkUnique titles help visitors and search engines tell pages apart.
- 2.Could be better: Server response time: needs attention. see checkFaster pages help visitors reach your content sooner.
- 3.Could be better: Your site has no sitemap. see checkA sitemap helps search engines discover your pages.
- 4.Could be better: Your page has no preferred URL. see checkA canonical URL tells search engines which version to use.
- 5.Could be better: Your headings skip levels. see checkA clear outline makes content easier to navigate, including with a screen reader.
Built with 2 technologies· detected stack
Read from the public source and response headers of the sampled pages.
How it fits together
Next.jsFramework
VercelHosting / edge
- VercelHosting / edge
- Next.jsFramework
A framework or CDN signal describes the public response, not the origin host or private backend.
Site checks
Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.
Metadata1Needs a fix1Could be better9Looks good
77/100Needs a fix: Titles unique across pages1 title repeat across 10 indexable sampled pages, e.g.
Needs a fix · Metadata · Review suggestedCritical
Observed evidence
1 title repeat across 10 indexable sampled pages, e.g. "chalk — learn anything, anywhere" on 2 pages.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. Right now the sampled pages don't provide it.
Recommended fix
Give each distinct page a title that names what is on it. Pages that are true copies should declare a canonical URL instead.
Affected pages (2)
- https://www.trychalk.tech/
- https://www.trychalk.tech/signin
Could be better: Meta description lengthDescription is 198 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).
Could be better · Metadata · Review suggested
Observed evidence
Description is 198 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.
Recommended fix
Front-load the useful summary because Google may generate or truncate snippets by query and device.
Looks good: Page title exists
Looks good · Metadata · Measured on your page
Observed evidence
Title found: "chalk — learn anything, anywhere"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title length
Looks good · Metadata · Review suggested
Observed evidence
Title is 32 characters, inside this audit's 15–60 review range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title says what the site does
Looks good · Metadata · Measured on your page
Observed evidence
Title "chalk — learn anything, anywhere" says more than the site name.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description exists
Looks good · Metadata · Measured on your page
Observed evidence
Meta description found: "Hold ⌘⌥ and ask about anything on your Mac: chalk answers out loud and points at the real …"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Homepage isn't noindexed
Looks good · Metadata · Measured on your page
Observed evidence
No blocking robots meta tag on the homepage.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Character encoding declared
Looks good · Metadata · Measured on your page
Observed evidence
UTF-8 declared in the Content-Type header and a meta tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTML5 doctype
Looks good · Metadata · Measured on your page
Observed evidence
HTML5 doctype declared.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta keywords tag
Looks good · Metadata · Measured on your page
Observed evidence
No obsolete meta keywords tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Valid metadata order in <head>
Looks good · Metadata · Measured on your page
Observed evidence
No invalid element interrupts metadata in <head>.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Indexing2Could be better9Looks good5Informational
69/100Could be better: Sitemap existsNo sitemap found (checked https://www.trychalk.tech/sitemap.xml → 404).
Could be better · Indexing · Review suggested
Observed evidence
No sitemap found (checked https://www.trychalk.tech/sitemap.xml → 404).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.
Recommended fix
Publish a sitemap.xml and submit it in Google Search Console. Next.js: export from app/sitemap.ts — it's ~10 lines.
Could be better: Canonical URL setThe homepage has no canonical link.
Could be better · Indexing · Review suggested
Observed evidence
The homepage has no canonical link.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.
Recommended fix
Add <link rel="canonical"> (Next.js: metadata.alternates.canonical). It consolidates ranking signals when the page is reachable under several URLs (with/without query params, trailing slash…).
Not applicable: Sampled URLs have aligned indexability signalsNo sitemap was found, so there are no submitted URLs to compare against.
Not applicable · Indexing · Measured on your page
Observed evidence
No sitemap was found, so there are no submitted URLs to compare against.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.
Recommended fix
The sitemap check covers the missing file. Once one exists, this check confirms the URLs it lists are indexable.
Not applicable: robots.txt existsrobots.txt is absent.
Not applicable · Indexing · Measured on your page
Observed evidence
robots.txt is absent. A missing policy permits crawling by default.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.
Recommended fix
Optional: publish a robots policy to advertise a sitemap or restrict selected paths.
Not measured: Sitemap parses and lists URLsNo sitemap was reachable, so its contents cannot be validated.
Not measured · Indexing · Not established
Observed evidence
No sitemap was reachable, so its contents cannot be validated.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish /sitemap.xml with your canonical URLs. This check then validates the XML and the URLs it lists.
Not applicable: Sitemap declared in robots.txtNo sitemap was reachable, so robots.txt has nothing to point at.
Not applicable · Indexing · Measured on your page
Observed evidence
No sitemap was reachable, so robots.txt has nothing to point at.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.
Recommended fix
Publish the sitemap first, then add a Sitemap: line to robots.txt naming its absolute URL.
Show 10 more checks
Not applicable: Canonical is absolute and self-referencingThe page declares no canonical URL, so there is nothing to validate.
Not applicable · Indexing · Measured on your page
Observed evidence
The page declares no canonical URL, so there is nothing to validate.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.
Recommended fix
Add <link rel="canonical" href="…"> pointing at the absolute, preferred URL of the page.
Looks good: Single canonical declaration
Looks good · Indexing · Measured on your page
Observed evidence
No canonical declaration to conflict.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Noindex and canonical agree
Looks good · Indexing · Measured on your page
Observed evidence
No conflicting noindex and cross-page canonical instructions.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta-refresh redirect
Looks good · Indexing · Measured on your page
Observed evidence
No meta-refresh redirect.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No soft-404 response
Looks good · Indexing · Measured on your page
Observed evidence
No soft-404 pattern on sampled HTTP 200 pages.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical target integrity
Looks good · Indexing · Measured on your page
Observed evidence
No canonical target to validate in this check.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt doesn't block everything
Looks good · Indexing · Measured on your page
Observed evidence
The audited URL is allowed for Googlebot. HTTP 404: no available robots policy.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: www vs apex consistency
Looks good · Indexing · Measured on your page
Observed evidence
Hostname is used consistently (www.trychalk.tech).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: URLs are readable slugs
Looks good · Indexing · Measured on your page
Observed evidence
URL slugs are readable (9 sampled).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled pages expose search-access signals
Looks good · Indexing · Measured on your page
Observed evidence
No restrictive search-access signal on 10 sampled page(s). Actual indexing is not verified.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Content9Looks good2Informational
100/100Not measured: ReadabilityFlesch reading ease ≈ 72.
Not measured · Content · Not established
Observed evidence
Flesch reading ease ≈ 72.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.
Not measured: Outbound referencesSubstantial content but zero outbound links.
Not measured · Content · Not established
Observed evidence
Substantial content but zero outbound links.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Link to sources for your claims. This check reports whether outbound references are present; it does not measure content quality, retrieval, or citation outcomes.
Looks good: Crawlable content in source HTML
Looks good · Content · Measured on your page
Observed evidence
No recognized empty JavaScript application shell on 10 sampled page(s). The entered page exposes 1088 publisher word(s).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage content volume
Looks good · Content · Measured on your page
Observed evidence
The audited page has about 1088 words of main content.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Text-to-HTML ratio
Looks good · Content · Measured on your page
Observed evidence
Text-to-HTML ratio is 5.9%.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No placeholder text
Looks good · Content · Measured on your page
Observed evidence
No placeholder text detected on crawled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: No starter-template leftovers
Looks good · Content · Measured on your page
Observed evidence
No starter-template artifacts detected.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title and H1 agree
Looks good · Content · Measured on your page
Observed evidence
Title and H1 share topic words: learn, anything, anywhere.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Crawled pages aren't near-duplicates
Looks good · Content · Measured on your page
Observed evidence
No near-duplicate main content among 8 indexable sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Discovery copy is distinct across sampled pages
Looks good · Content · Measured on your page
Observed evidence
No repeated description, H1, or publisher copy across 10 sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Structured dataNot measured
Not measuredCould be better: JSON-LD presentNo JSON-LD structured data on the homepage.
Could be better · Structured data · Review suggested
Observed evidence
No JSON-LD structured data on the homepage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.
Recommended fix
Add Organization and WebSite schema. They state who publishes the site and what it is called, which is what rich results and answer engines read first.
Could be better: Organization or WebSite schemaNo Organization, WebSite or Person schema found.
Could be better · Structured data · Review suggested
Observed evidence
No Organization, WebSite or Person schema found.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.
Recommended fix
Add an identity node so search engines and AI assistants can attribute your content to a real entity.
Not applicable: JSON-LD parsesNo JSON-LD blocks were found, so there is no syntax to validate.
Not applicable · Structured data · Measured on your page
Observed evidence
No JSON-LD blocks were found, so there is no syntax to validate.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.
Recommended fix
Add a <script type="application/ld+json"> block describing the page — Organization or WebSite is the usual starting point.
Not applicable: Content-specific schemaNo content-specific schema (Article, Product, FAQPage…) detected.
Not applicable · Structured data · Measured on your page
Observed evidence
No content-specific schema (Article, Product, FAQPage…) detected.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.
Recommended fix
If you publish articles, products or FAQs, add the matching schema type — that's what makes rich results (stars, FAQs, prices) possible.
Headings1Could be better6Looks good
91/100Could be better: Heading levels don't skip1 heading level skip: H2 → H4 "Two armed camps turned an assassination in Sarajev…".
Could be better · Headings · Review suggested
Observed evidence
1 heading level skip: H2 → H4 "Two armed camps turned an assassination in Sarajev…".
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.
Recommended fix
Use the next level down for each subsection (H2 under H1, H3 under H2). If a heading level was chosen for its font size, keep the level and change the styling instead.
Looks good: H1 exists
Looks good · Headings · Measured on your page
Observed evidence
H1 found: "Learn anything,anywhere."
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Single H1
Looks good · Headings · Measured on your page
Observed evidence
Exactly one H1 on the homepage.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: H1 has real text
Looks good · Headings · Measured on your page
Observed evidence
H1 reads "Learn anything,anywhere.".
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Headings are descriptive
Looks good · Headings · Measured on your page
Observed evidence
34 headings, averaging 5.6 words — descriptive.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is sectioned with H2s
Looks good · Headings · Measured on your page
Observed evidence
9 H2 section(s) structure the page.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Element IDs are unique per document
Looks good · Headings · Measured on your page
Observed evidence
All inspected element IDs are unique within their documents.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
ImagesNot applicable
Not measuredNot applicable: Alt text coverageNo visible <img> elements on the audited page (hidden, presentational and 1×1 tracking images are not counted).
Not applicable · Images · Measured on your page
Observed evidence
No visible <img> elements on the audited page (hidden, presentational and 1×1 tracking images are not counted).
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. Any image you add later needs alt text that describes it, so this check starts scoring then.
Not applicable: Width/height attributesNo visible <img> elements to measure on the audited page.
Not applicable · Images · Measured on your page
Observed evidence
No visible <img> elements to measure on the audited page.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. Give future images explicit width and height attributes so the browser can reserve their space.
Not applicable: Modern image formatsNo raster images with a recognizable file extension were found.
Not applicable · Images · Measured on your page
Observed evidence
No raster images with a recognizable file extension were found.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. If images arrive later, serve WebP or AVIF alongside PNG/JPEG.
Not applicable: Lazy loadingOnly 0 visible image(s) on the page, too few for lazy loading to change the initial load.
Not applicable · Images · Measured on your page
Observed evidence
Only 0 visible image(s) on the page, too few for lazy loading to change the initial load.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. Once the page carries several images, add loading="lazy" to the ones below the fold.
Links6Looks good
100/100Looks good: Internal links resolve
Looks good · Links · Measured on your page
Observed evidence
All 12 sampled internal links return < 400.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Anchor text is meaningful
Looks good · Links · Measured on your page
Observed evidence
23 of 23 links have descriptive text or labels.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No dead placeholder links
Looks good · Links · Measured on your page
Observed evidence
No placeholder links on the audited page.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: External links use rel=noopener
Looks good · Links · Measured on your page
Observed evidence
All target="_blank" links carry rel="noopener".
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage links into the site
Looks good · Links · Measured on your page
Observed evidence
Homepage links to 11 distinct internal pages.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Same-page links have source targets
Looks good · Links · Measured on your page
Observed evidence
1 same-page fragment link(s) have source targets.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Mobile4Looks good2Informational
100/100Not applicable: Responsive image markupOnly 0 image(s) on the page, too few for responsive image markup to change what phones download.
Not applicable · Mobile · Measured on your page
Observed evidence
Only 0 image(s) on the page, too few for responsive image markup to change what phones download.
Why this matters
Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. When the page carries several images, give them srcset and sizes so phones fetch smaller files.
Not measured: No tiny inline font sizesNo sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Not measured · Mobile · Not established
Observed evidence
No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Check computed font sizes in a browser across mobile widths.
Looks good: Viewport meta tag
Looks good · Mobile · Measured on your page
Observed evidence
Viewport configured: "width=device-width, initial-scale=1".
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Pinch zoom not disabled
Looks good · Mobile · Measured on your page
Observed evidence
The viewport lets users zoom.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Interactive controls have source labels
Looks good · Mobile · Measured on your page
Observed evidence
235 source controls have detectable names. Browser accessibility and CSS visibility were not tested.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: ARIA references point to source elements
Looks good · Mobile · Measured on your page
Observed evidence
62 ARIA reference(s) resolve within their source documents. Rendered visibility was not tested.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Language2Looks good1Informational
100/100Not applicable: hreflang syntaxNo hreflang tags — fine for single-language sites.
Not applicable · Language · Measured on your page
Observed evidence
No hreflang tags — fine for single-language sites.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.
Recommended fix
Only add hreflang if you publish the same content in multiple languages/regions.
Looks good: html lang attribute
Looks good · Language · Measured on your page
Observed evidence
Language declared: lang="en".
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared language matches content
Looks good · Language · Measured on your page
Observed evidence
Declared language (en) matches detected content language.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Branding2Looks good2Informational
100/100Not measured: Web app manifestNo web manifest linked.
Not measured · Branding · Not established
Observed evidence
No web manifest linked.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional, but a manifest.json enables install prompts and better mobile integration.
Not measured: Theme colorNo theme-color meta tag.
Not measured · Branding · Not established
Observed evidence
No theme-color meta tag.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.
Looks good: Favicon
Looks good · Branding · Measured on your page
Observed evidence
Favicon declared via <link rel="icon"> (/favicon.ico?favicon.0h-veup-5u2c-.ico).
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Apple touch icon
Looks good · Branding · Measured on your page
Observed evidence
apple-touch-icon is declared.
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Performance
Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.
| Measure | This site | Reading |
|---|---|---|
| Server response time | 865 ms | Could be better: needs attentionThe audit received response headers after 865 ms from one test location. |
| Script/stylesheet count | — | Could be better: needs attention17 scripts + 13 stylesheets on the homepage. |
| Web fonts don't block text | — | Informational: not applicableNo Google Fonts stylesheet links detected. |
| HTML payload size | 230 KB | Looks good: goodThe page's HTML is 230 KB uncompressed: acceptable, though under 100 KB is a good target for content pages. |
| No render-blocking head scripts | — | Looks good: goodNo synchronous render-blocking scripts in <head>. |
| Inline styles are bounded | 1.0 KB | Looks good: goodInline styles total 1.0 KB. |
| HTML served compressed | — | Looks good: goodHTML is compressed with br. |
| Iframe usage | — | Looks good: goodNo iframes. |
| Source HTML weight | 229.8 KB | Informational: measured source, not transferred bytes229.8 KB of HTML on the audited page |
From a single automated fetch of the audited page. A quick reading, not a substitute for Lighthouse or field data.
Security
HTTPS, transport security and the response headers the audited pages send.
Could be better: Frame embedding protectionNo frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).
Could be better · Security · Review suggested
Observed evidence
No frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Send Content-Security-Policy: frame-ancestors 'self' (or 'none', or a list of partner origins), or X-Frame-Options: SAMEORIGIN. It stops other sites from framing your pages to trick visitors into clicking (clickjacking).
Could be better: X-Content-Type-OptionsX-Content-Type-Options: nosniff is not set.
Could be better · Security · Review suggested
Observed evidence
X-Content-Type-Options: nosniff is not set.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Add it — one header, stops MIME-sniffing attacks. Most hosts let you set headers in config (vercel.json, netlify.toml, next.config).
Could be better: Content Security PolicyNo Content-Security-Policy detected.
Could be better · Security · Review suggested
Observed evidence
No Content-Security-Policy detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Configure an enforced policy for script and resource origins; use report-only monitoring to prepare changes safely.
Could be better: Browser feature permissionsNo explicit restriction on sensitive browser features was observed.
Could be better · Security · Review suggested
Observed evidence
No explicit restriction on sensitive browser features was observed.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Disable unused camera, microphone, or geolocation access using Permissions-Policy.
Not applicable: Password forms avoid URL submissionNo enabled, named password inputs in sampled HTML.
Not applicable · Security · Measured on your page
Observed evidence
No enabled, named password inputs in sampled HTML.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.
Recommended fix
Review authentication forms separately when applicable.
Looks good: Site serves over HTTPS
Looks good · Security · Measured on your page
Observed evidence
Site serves over HTTPS.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTTP redirects to HTTPS
Looks good · Security · Measured on your page
Observed evidence
http:// permanently redirects to https://./
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HSTS header
Looks good · Security · Measured on your page
Observed evidence
HSTS is set: max-age=63072000.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Referrer policy
Looks good · Security · Measured on your page
Observed evidence
No Referrer-Policy is set, so browsers apply their default, strict-origin-when-cross-origin, which sends only the origin to other sites.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No mixed content
Looks good · Security · Measured on your page
Observed evidence
No insecure subresources detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Server technology disclosure
Looks good · Security · Measured on your page
Observed evidence
No X-Powered-By disclosure.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared form submission targets
Looks good · Security · Measured on your page
Observed evidence
1 declared form(s) submit over HTTPS to this site. Runtime submission behavior is untested.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AI answer readiness
Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.
Could be better: llms.txtllms.txt exists but looks empty or serves HTML (probably your 404 page).
Could be better · AI answer readiness · Review suggested
Observed evidence
llms.txt exists but looks empty or serves HTML (probably your 404 page).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Serve a real markdown llms.txt — a soft-404 here is worse than none because crawlers cache the junk.
Could be better: FAQ/QA schemaNo FAQPage or QAPage schema on any crawled page.
Could be better · AI answer readiness · Review suggested
Observed evidence
No FAQPage or QAPage schema on any crawled page.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
If the page answers recurring questions, use visible question-and-answer content and matching FAQPage markup. QAPage is for a single question with user-submitted answers. Google FAQ rich results are restricted to eligible authoritative government and health sites; markup does not guarantee AI citations.
Could be better: Question-style headingsOnly 14% of 116 H2/H3 headings are question-shaped.
Could be better · AI answer readiness · Review suggested
Observed evidence
Only 14% of 116 H2/H3 headings are question-shaped.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Phrase key subheadings as the questions users actually ask ("How much does X cost?"). This improves the measured question-heading signal; the audit does not guarantee citations.
Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "Hold ⌘⌥ and ask about anything on your Mac — chalk answers out loud and points a…"
Could be better · AI answer readiness · Review suggested
Observed evidence
The opening paragraph doesn't define what the site/topic is: "Hold ⌘⌥ and ask about anything on your Mac — chalk answers out loud and points a…"
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
"X is a Y that does Z for W" in the first paragraph gives answer engines a liftable definition of you. Write it once, benefit everywhere.
Could be better: Freshness signalsNo dateModified schema or visible 'updated' dates found.
Could be better · AI answer readiness · Review suggested
Observed evidence
No dateModified schema or visible 'updated' dates found.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
For content where dates matter, show the actual update date and mirror it in dateModified. Do not invent dates or change them without a substantive update. Missing dates alone do not prove stale content.
Could be better: Cites external sourcesNo outbound links on any crawled page.
Could be better · AI answer readiness · Review suggested
Observed evidence
No outbound links on any crawled page.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Cite sources for factual claims. This makes source links observable to readers and crawlers; the audit does not measure or guarantee citations or rankings.
Could be better: llms.txt links resolve to this sitellms.txt contains no Markdown links to discoverable pages.
Could be better · AI answer readiness · Measured on your page
Observed evidence
llms.txt contains no Markdown links to discoverable pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Add Markdown links such as [Pricing](/pricing) for the pages an answer engine should retrieve first.
Affected pages (1)
- https://www.trychalk.tech/
Could be better: Question headings have concise answers10/16 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Could be better · AI answer readiness · Measured on your page
Observed evidence
10/16 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Put a direct 20–500 character answer paragraph immediately after each question heading so retrieval systems can quote it cleanly.
Affected pages (2)
- https://www.trychalk.tech/privacy
- https://www.trychalk.tech/courses
Could be better: Machine-readable provenance signalsOnly 3 of 4 provenance signal types were found: contact, author, date.
Could be better · AI answer readiness · Measured on your page
Observed evidence
Only 3 of 4 provenance signal types were found: contact, author, date.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Add the missing author, date, breadcrumb, or contact signal so machines can identify provenance and site structure.
Affected pages (4)
- https://www.trychalk.tech/
- https://www.trychalk.tech/privacy
- https://www.trychalk.tech/pricing
- https://www.trychalk.tech/download
Could be better: Markdown copies of pages3 of 3 markdown URLs answered 200 but returned HTML, not markdown.
Could be better · AI answer readiness · Measured on your page
Observed evidence
3 of 3 markdown URLs answered 200 but returned HTML, not markdown.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Either serve real markdown at those URLs or return 404. A 200 that hands back the HTML page wastes a retrieval and can be cached as the markdown copy.
Affected pages (3)
- https://www.trychalk.tech/index.md
- https://www.trychalk.tech/about.md
- https://www.trychalk.tech/index.html.md
Not measured: llms-full.txtNo /llms-full.txt.
Not measured · AI answer readiness · Not established
Observed evidence
No /llms-full.txt.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional companion to llms.txt containing your full content as one markdown file — useful for sites whose pages are JS-heavy.
Not measured: Citable facts density177 concrete figures across 2245 words.
Not measured · AI answer readiness · Not established
Observed evidence
177 concrete figures across 2245 words.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Good — keep facts specific and current, and date-stamp them.
Not measured: llms.txt follows the specNo readable /llms.txt, so its structure cannot be checked.
Not measured · AI answer readiness · Not established
Observed evidence
No readable /llms.txt, so its structure cannot be checked.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish llms.txt first — the llms.txt check covers that — then this one verifies the structure.
Not applicable: Accept: text/markdown negotiationThe homepage answered Accept: text/markdown with text/html; charset=utf-8.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
The homepage answered Accept: text/markdown with text/html; charset=utf-8.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
Optional: return a stripped markdown body when the request asks for text/markdown. Some hosts and CDNs do this for you; a plain HTML answer is not a defect.
Not applicable: Advertised machine interfaces are inspectableNo OpenAPI interface was advertised by sampled HTML.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
No OpenAPI interface was advertised by sampled HTML.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
An API is optional. Add a service-desc link if you already publish a machine-readable API specification.
Looks good: AI crawler access
Looks good · AI answer readiness · Measured on your page
Observed evidence
The audited URL is allowed for evaluated answer-search crawlers.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Semantic HTML structure
Looks good · AI answer readiness · Measured on your page
Observed evidence
Semantic structure present: main×1, article×16, section×14, nav×2, header×8, footer×1, aside×4.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Answers lead the section
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs get to the point without preamble.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is chunkable
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs average 21 words, lists present — chunk-friendly.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Consistent brand entity
Looks good · AI answer readiness · Measured on your page
Observed evidence
Brand declared: og:site_name "chalk".
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Description reads as a liftable summary
Looks good · AI answer readiness · Measured on your page
Observed evidence
Meta description works as a standalone summary.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Entity identity agrees across signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
The site is consistently named "chalk" and 1 identity URL(s) stay on trychalk.tech.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AdSense readinessOptional
Publisher-policy signals, for sites that plan to carry ads. These checks do not affect the overall score or grade, and they do not measure or guarantee AdSense approval.
On its own, this site scores 44/100 for publisher readiness. Ignore this section if you do not run ads.
Could be better: Privacy policy advertising disclosuresFetched privacy policy lacks third-party/vendor disclosure signals.
Could be better · AdSense policy · Published platform ruleCritical
Observed evidence
Fetched privacy policy lacks third-party/vendor disclosure signals.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Describe data collection, sharing, and cookie use by Google and other third-party ad vendors.
Affected pages (1)
- https://www.trychalk.tech/privacy
Could be better: Sampled publisher-content coverage3/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 4209 publisher words in total.
Could be better · AdSense policy · Review suggestedCritical
Observed evidence
3/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 4209 publisher words in total. 2 of the 10 sampled pages are support or tool pages and were excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Review whether each page fully serves its purpose. Expand incomplete editorial content with useful information; keep concise navigation and tool pages when they help visitors.
Affected pages (3)
- https://www.trychalk.tech/how
- https://www.trychalk.tech/signin
- https://www.trychalk.tech/download
Could be better: Tool pages expose explanatory content2/9 tool-style screen(s) expose fewer than 80 publisher words.
Could be better · AdSense policy · Review suggested
Observed evidence
2/9 tool-style screen(s) expose fewer than 80 publisher words. Google publishes no minimum word count; this is an audit heuristic.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Explain the tool's purpose, inputs, method, limitations, and result interpretation in source HTML. Add useful material, not filler.
Affected pages (2)
- https://www.trychalk.tech/how
- https://www.trychalk.tech/signin
Could be better: Policy pages linked site-wide2/10 crawled pages don't link to the privacy policy.
Could be better · AdSense policy · Review suggested
Observed evidence
2/10 crawled pages don't link to the privacy policy.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Place the privacy link in shared navigation or footer markup so users can reach disclosures from any sampled entry page.
Affected pages (2)
- https://www.trychalk.tech/about
- https://www.trychalk.tech/download
Could be better: ads.txtads.txt exists but contains no google.com pub- line.
Could be better · AdSense policy · Review suggested
Observed evidence
ads.txt exists but contains no google.com pub- line.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add your AdSense publisher line exactly as shown in your AdSense account.
Not measured: Domain age & historyDomain age isn't visible from the site itself.
Not measured · AdSense policy · Not established
Observed evidence
Domain age isn't visible from the site itself.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Do not use age as a content-quality proxy. Verify ownership and account eligibility in AdSense; Google's general eligibility page publishes no domain-age threshold.
Not measured: Latest article has real depthNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reads the newest one.
Not measured: Latest article reads as edited workNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reviews its style signals.
Not measured: Latest article names an author and a dateNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then looks for its byline and date.
Looks good: Privacy policy page
Looks good · AdSense policy · Measured on your page
Observed evidence
Privacy policy found: https://www.trychalk.tech/privacy
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Terms page
Looks good · AdSense policy · Measured on your page
Observed evidence
Terms page found: /terms
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: About page
Looks good · AdSense policy · Measured on your page
Observed evidence
About page found: https://www.trychalk.tech/about
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Contact method
Looks good · AdSense policy · Measured on your page
Observed evidence
Contact email found: mailto:hello@trychalk.tech?subject=My%20pitch%20for%20three%20months%20of%20chalk
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: First-party contact email
Looks good · AdSense policy · Measured on your page
Observed evidence
First-party contact email found: hello@trychalk.tech.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Thin page share
Looks good · AdSense policy · Review suggested
Observed evidence
6/8 editorial pages clear the audit's publisher-content triage threshold. 2 of the 10 sampled pages are support or tool pages and were excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No ads on non-content screens
Looks good · AdSense policy · Published platform rule
Observed evidence
No Google ad code detected on sampled non-content screens.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content differs across URLs
Looks good · AdSense policy · Review suggested
Observed evidence
No high publisher-content repetition among 7 substantial sampled page(s).
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content exists in source HTML
Looks good · AdSense policy · Measured on your page
Observed evidence
No empty client-rendered publisher shell in the crawl sample.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Article-style content exists
Looks good · AdSense policy · Measured on your page
Observed evidence
Article-style content detected.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 4 more checks
Looks good: No "coming soon" or placeholder pages
Looks good · AdSense policy · Measured on your page
Observed evidence
No "coming soon", "under construction" or lorem-ipsum text on crawled pages.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Site language is AdSense-supported
Looks good · AdSense policy · Measured on your page
Observed evidence
Language "en" is AdSense-supported.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Existing ad scripts
Looks good · AdSense policy · Measured on your page
Observed evidence
No competing ad scripts on the page.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Hosting and infrastructure
Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.
| Hostname | www.trychalk.tech |
|---|---|
| Hosting | Vercel |
| IP addresses | 64.29.17.65, 216.198.79.65 |
| DNS A | 216.198.79.65 · 64.29.17.65 |
| DNS CNAME | 96ffca9cc3c788d0.vercel-dns-017.com |
| DNS CAA | {"critical":0,"type":"CAA","issue":"globalsign.com"} · {"critical":0,"type":"CAA","issue":"letsencrypt.org"} · {"critical":0,"type":"CAA","issue":"pki.goog"} · {"critical":0,"type":"CAA","issue":"sectigo.com"} |
| TLS | TLSv1.3TLS_AES_128_GCM_SHA256 |
| Certificate issuer | Let's Encrypt / YR1 |
| Certificate valid until | Jan 5 23:57:35 2027 GMT |
| Certificate validation | Passed |
Website anatomy and diagnostics
Explore links, resources, crawler access and site integrations.
Page architecture
Choose a page to explore its details and connections.
Page content
1088 publisher words
Page structure
html content
Observed discovery
Depth 0 · 8 incoming links
HTTP 200 · 229.8 KB source
Source interactions
43 controls · 0 unnamed
17 script / 13 stylesheet references
- Canonical declaration
- Not declared
- Schema types
- None observed
- Outgoing links in sampled graph
- /how · /signin · /board · /pricing · /download · /spatial · /courses · /record · /about · /terms · /privacy
Routes: / · /about · /privacy · /how · /signin · /board · /pricing · /download · /spatial · /courses
Repeated metadata in the sample
Same title: chalk — learn anything, anywhere
/ · /signin
Resource origins 1
Resources associated with your website. External resources may belong to the same organization.
- https://www.trychalk.tech/stylesheet, script · 223 references · same origin
Crawler policy by page
Review crawler access for your pages. Search, training and user-triggered services have different purposes; declared access does not guarantee discovery.
| Crawler / purpose | Page | Policy | Matched directive |
|---|---|---|---|
| Googlebotsearch | / | allowed | Declared policy for this page. |
| Googlebotsearch | /about | allowed | Declared policy for this page. |
| Googlebotsearch | /privacy | allowed | Declared policy for this page. |
| Googlebotsearch | /how | allowed | Declared policy for this page. |
| Googlebotsearch | /signin | allowed | Declared policy for this page. |
| Googlebotsearch | /board | allowed | Declared policy for this page. |
| Googlebotsearch | /pricing | allowed | Declared policy for this page. |
| Googlebotsearch | /download | allowed | Declared policy for this page. |
| Googlebotsearch | /spatial | allowed | Declared policy for this page. |
| Googlebotsearch | /courses | allowed | Declared policy for this page. |
| bingbotsearch | / | allowed | Declared policy for this page. |
| bingbotsearch | /about | allowed | Declared policy for this page. |
| bingbotsearch | /privacy | allowed | Declared policy for this page. |
| bingbotsearch | /how | allowed | Declared policy for this page. |
| bingbotsearch | /signin | allowed | Declared policy for this page. |
| bingbotsearch | /board | allowed | Declared policy for this page. |
| bingbotsearch | /pricing | allowed | Declared policy for this page. |
| bingbotsearch | /download | allowed | Declared policy for this page. |
| bingbotsearch | /spatial | allowed | Declared policy for this page. |
| bingbotsearch | /courses | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | / | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /about | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /privacy | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /how | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /signin | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /board | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /pricing | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /download | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /spatial | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /courses | allowed | Declared policy for this page. |
| PerplexityBotsearch | / | allowed | Declared policy for this page. |
| PerplexityBotsearch | /about | allowed | Declared policy for this page. |
| PerplexityBotsearch | /privacy | allowed | Declared policy for this page. |
| PerplexityBotsearch | /how | allowed | Declared policy for this page. |
| PerplexityBotsearch | /signin | allowed | Declared policy for this page. |
| PerplexityBotsearch | /board | allowed | Declared policy for this page. |
| PerplexityBotsearch | /pricing | allowed | Declared policy for this page. |
| PerplexityBotsearch | /download | allowed | Declared policy for this page. |
| PerplexityBotsearch | /spatial | allowed | Declared policy for this page. |
| PerplexityBotsearch | /courses | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | / | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /about | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /privacy | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /how | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /signin | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /board | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /pricing | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /download | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /spatial | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /courses | allowed | Declared policy for this page. |
| GPTBottraining | / | allowed | Declared policy for this page. |
| GPTBottraining | /about | allowed | Declared policy for this page. |
| GPTBottraining | /privacy | allowed | Declared policy for this page. |
| GPTBottraining | /how | allowed | Declared policy for this page. |
| GPTBottraining | /signin | allowed | Declared policy for this page. |
| GPTBottraining | /board | allowed | Declared policy for this page. |
| GPTBottraining | /pricing | allowed | Declared policy for this page. |
| GPTBottraining | /download | allowed | Declared policy for this page. |
| GPTBottraining | /spatial | allowed | Declared policy for this page. |
| GPTBottraining | /courses | allowed | Declared policy for this page. |
| ClaudeBottraining | / | allowed | Declared policy for this page. |
| ClaudeBottraining | /about | allowed | Declared policy for this page. |
| ClaudeBottraining | /privacy | allowed | Declared policy for this page. |
| ClaudeBottraining | /how | allowed | Declared policy for this page. |
| ClaudeBottraining | /signin | allowed | Declared policy for this page. |
| ClaudeBottraining | /board | allowed | Declared policy for this page. |
| ClaudeBottraining | /pricing | allowed | Declared policy for this page. |
| ClaudeBottraining | /download | allowed | Declared policy for this page. |
| ClaudeBottraining | /spatial | allowed | Declared policy for this page. |
| ClaudeBottraining | /courses | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | / | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /about | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /privacy | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /how | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /signin | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /board | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /pricing | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /download | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /spatial | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /courses | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | / | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /about | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /privacy | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /how | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /signin | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /board | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /pricing | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /download | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /spatial | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /courses | allowed | Declared policy for this page. |
Advertised APIs and machine interfaces
No supported machine interfaces were advertised in the sampled HTML. An API or MCP server is optional; undiscovered interfaces remain unknown.
Public DNS and TLS endpoint
www.trychalk.tech · observed · 64.29.17.65, 216.198.79.65
- A
- 216.198.79.65 · 64.29.17.65
- AAAA
- Unavailable for this exact hostname
- CNAME
- 96ffca9cc3c788d0.vercel-dns-017.com
- NS
- Unavailable for this exact hostname
- MX
- Unavailable for this exact hostname
- CAA
- {"critical":0,"type":"CAA","issue":"globalsign.com"} · {"critical":0,"type":"CAA","issue":"letsencrypt.org"} · {"critical":0,"type":"CAA","issue":"pki.goog"} · {"critical":0,"type":"CAA","issue":"sectigo.com"}
TLS: TLSv1.3
Certificate validation passed for the observed endpoint.
Issuer: Let's Encrypt / YR1
Certificate valid until: Jan 5 23:57:35 2027 GMT
PageSpeed measurement
Loading the PageSpeed panel…
Growth resources
Loading growth resources…
Where to take this site next
Follow-on work suggested by the observations above.
- 01
Your top fixes list is the priority order — clear the red items before creating more content.
- 02
Re-run the combined audit after each batch of fixes
Re-run after fixes to see which checks changed; score bands are guidance, not a guarantee of ranking, traffic, or approval.
Apply the recommended fixes
Hand the complete evidence to a coding agent, or take the report with you.
Report notes
- 01This report covers the sampled public pages listed above. Other pages may have different results.
- 02Browser-rendered content, private backend systems and authenticated experiences may require a separate review.
- 03Unavailable observations are identified in the report. Results do not guarantee rankings, citations, security, accessibility or advertising approval.
Pages included in this report
- https://www.trychalk.tech/
- https://www.trychalk.tech/about
- https://www.trychalk.tech/privacy
- https://www.trychalk.tech/how
- https://www.trychalk.tech/signin
- https://www.trychalk.tech/board
- https://www.trychalk.tech/pricing
- https://www.trychalk.tech/download
- https://www.trychalk.tech/spatial
- https://www.trychalk.tech/courses