Nock: a notch for Windows

Description is 186 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).

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.

Front-load the useful summary because Google may generate or truncate snippets by query and device.

Fewer than two indexable pages with a title were sampled, so titles can't be compared.

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.

Link your main pages from the homepage so crawlers (including this one) can find them.

Title found: "Nock: a notch for Windows"

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Title is 25 characters, inside this audit's 15–60 review range.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Title "Nock: a notch for Windows" says more than the site name.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Meta description found: "A native notch and top bar for Windows (with a Linux preview), written in Rust. About 1 MB…"

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

No sitemap found (checked https://nock.akhileshvarute.me/sitemap.xml → 404).

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.

Publish a sitemap.xml and submit it in Google Search Console. Next.js: export from app/sitemap.ts — it's ~10 lines.

No sitemap was found, so there are no submitted URLs to compare against.

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.

The sitemap check covers the missing file. Once one exists, this check confirms the URLs it lists are indexable.

robots.txt is absent. A missing policy permits crawling by default.

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.

Optional: publish a robots policy to advertise a sitemap or restrict selected paths.

No sitemap was reachable, so its contents cannot be validated.

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.

Publish /sitemap.xml with your canonical URLs. This check then validates the XML and the URLs it lists.

No sitemap was reachable, so robots.txt has nothing to point at.

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.

Publish the sitemap first, then add a Sitemap: line to robots.txt naming its absolute URL.

The crawl reached no inner URLs, so URL readability cannot be assessed.

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.

Link your inner pages from the homepage so they can be crawled. This check then reviews their path structure.

Title ("Nock: a notch for Windows") and H1 ("The top of your screen is doing nothing.") share no significant words.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.

Align them around the same core topic — mixed signals confuse both rankers and readers.

Flesch reading ease ≈ 73.

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.

60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.

Only one page was sampled, so there is nothing to compare.

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.

Link your main pages from the homepage so the audit can sample and compare them.

Only one distinct content page was sampled, so repeated discovery copy cannot be compared.

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.

Sample at least two substantial URLs so repeated descriptions, H1s, and publisher text can be checked.

No recognized empty JavaScript application shell on 1 sampled page(s). The entered page exposes 557 publisher word(s).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

The audited page has about 557 words of main content.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

No og:site_name tag.

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.

Add it. Share cards use it to label the publisher; consistent naming also gives this audit a measurable entity signal. It does not measure or guarantee citations, rankings, or traffic.

og:title: "Nock: a notch for Windows in 1 MB of Rust"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:description: "Tasks, a focus timer, music, clipboard history and system dropdowns in a native notch. No …"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:image is set: "https://nock.akhileshvarute.me/og.png"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:image returns 200 (image/png).

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

Dimensions declared: 1200×630.

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:url and og:type ("website") are set.

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

twitter:card is "summary_large_image".

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

No JSON-LD structured data on the homepage.

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.

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.

No Organization, WebSite or Person schema found.

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.

Add an identity node so search engines and AI assistants can attribute your content to a real entity.

No JSON-LD blocks were found, so there is no syntax to validate.

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.

Add a <script type="application/ld+json"> block describing the page — Organization or WebSite is the usual starting point.

No inner pages crawled.

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.

Not applicable until inner pages exist.

No content-specific schema (Article, Product, FAQPage…) detected.

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.

If you publish articles, products or FAQs, add the matching schema type — that's what makes rich results (stars, FAQs, prices) possible.

H1 found: "The top of your screen is doing nothing."

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

Exactly one H1 on the homepage.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

Heading hierarchy is sequential across 10 headings.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

H1 reads "The top of your screen is doing nothing.".

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

10 headings, averaging 3.9 words — descriptive.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

6 H2 section(s) structure the page.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

All inspected element IDs are unique within their documents.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

All 5 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Nothing to do here.

All 5 visible images declare dimensions or are sized by their container.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Nothing to do here.

4 of 4 raster images have a WebP/AVIF source or come from a format-negotiating image service.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Nothing to do here.

4/5 images are lazy-loaded.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Nothing to do here.

The homepage links to only 0 distinct internal page(s).

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.

Link generously to your key pages from the homepage — it's how crawlers discover them and how PageRank flows.

No internal links were probed.

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.

Add internal links from your homepage.

18 of 18 links have descriptive text or labels.

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.

Nothing to do here.

No placeholder links on the audited page.

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.

Nothing to do here.

All target="_blank" links carry rel="noopener".

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.

Nothing to do here.

2 same-page fragment link(s) have source targets.

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.

Nothing to do here.

None of the 5 images use srcset.

Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.

Serve smaller variants to phones with srcset/sizes (next/image handles this) — mobile users shouldn't download desktop-sized images.

No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.

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.

Check computed font sizes in a browser across mobile widths.

Viewport configured: "width=device-width, initial-scale=1".

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

The viewport lets users zoom.

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

42 source controls have detectable names. Browser accessibility and CSS visibility were not tested.

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

9 ARIA reference(s) resolve within their source documents. Rendered visibility was not tested.

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

No hreflang tags — fine for single-language sites.

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.

Only add hreflang if you publish the same content in multiple languages/regions.

Language declared: lang="en".

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

Declared language (en) matches detected content language.

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

No apple-touch-icon link.

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.

Add a 180×180 apple-touch-icon so iOS home-screen bookmarks show your logo instead of a screenshot.

No web manifest linked.

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.

Optional, but a manifest.json enables install prompts and better mobile integration.

Favicon declared via <link rel="icon"> (icon.png).

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Nothing to do here.

theme-color is "#0a0a0b".

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Nothing to do here.