Alysis Code — AI Coding Agent with an Open-Source Engine

Description is 162 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.

A meta keywords tag is present ("Alysis Code, AI coding agent, open source AI agent, autonomo…").

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.

You can remove it. Google has ignored meta keywords since 2009, so the tag does nothing for search and shows competitors the terms you target.

Title found: "Alysis Code — AI Coding Agent with an Open-Source Engine"

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 56 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 "Alysis Code — AI Coding Agent with an Open-Source Engine" 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: "Alysis is a powerful, open-source AI agent for desktop and terminal. Work with files, plan…"

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.

One canonical declaration found.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No conflicting noindex and cross-page canonical instructions.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No meta-refresh redirect.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No soft-404 pattern on sampled HTTP 200 pages.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

Canonical is a valid https URL. Its host is checked by the canonical consistency check.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

Indexability signals align across 9 sampled URL(s).

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

The audited page has about 0 words of main content (navigation, header and footer excluded).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. Right now the sampled pages don't provide it.

Add substance: what the site is, who it's for, what problems it solves. This audit measures visible HTML; it does not measure rankings, traffic, or content originality. Note: if your content renders only via client-side JS, crawlers without JS (and this checker) can't see it — prefer server rendering.

9 sampled page(s) expose fewer than 30 publisher words and an empty application root with script references.

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.

Server-render or statically render the page's primary content. Google can render JavaScript, but rendering can fail or be delayed and other crawlers may not execute it.

• https://alysiscode.com/
• https://alysiscode.com/legal/privacy
• https://alysiscode.com/docs
• https://alysiscode.com/enterprise
• https://alysiscode.com/pricing
• https://alysiscode.com/feedback
• https://alysiscode.com/pricing/limits
• https://alysiscode.com/legal/terms
• https://alysiscode.com/legal/notice

Visible text is 0.0% of the HTML markup (scripts and styles excluded).

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.

Text-to-HTML ratio is not a ranking factor, but a very low value often means deeply nested markup or content that only appears after JavaScript runs. Check the source-content checks before changing anything.

Not enough English prose to estimate readability (it needs about 100 words in three or more sentences).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.

Nothing to change for this check.

Need both a <title> and an H1 to compare them.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.

Add whichever is missing — the metadata and headings checks name it — then this check confirms the two describe the same topic.

Fewer than two indexable sampled pages carry more than 50 words of main content, so there is nothing to compare.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.

Nothing to change for this check.

og:title: "Alysis Code — AI Coding Agent with an Open-Source Engine"

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: "Alysis is a powerful, open-source AI agent for desktop and terminal. Work with files, plan…"

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://alysiscode.com/og-main-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.

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.

og:site_name: "Alysis Code".

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.

None of the 8 crawled inner pages declare BreadcrumbList schema.

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 BreadcrumbList to inner pages — Google shows breadcrumbs in results and it clarifies site structure.

• https://alysiscode.com/legal/privacy
• https://alysiscode.com/docs
• https://alysiscode.com/enterprise
• https://alysiscode.com/pricing
• https://alysiscode.com/feedback
• https://alysiscode.com/pricing/limits
• https://alysiscode.com/legal/terms
• https://alysiscode.com/legal/notice

2 JSON-LD block(s) found on the homepage.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Nothing to do here.

All 18 JSON-LD block(s) parse cleanly.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Nothing to do here.

Identity schema present: Organization.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Nothing to do here.

Content schema found: Offer, SoftwareApplication.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Nothing to do here.

The audited page has no <h1>.

Headings are the outline every parser and screen reader follows to find the answer. Right now the sampled pages don't provide it.

Add one <h1> stating what the page is about, usually the hero headline. Search engines, screen readers and answer engines use it as the page's main heading.

No H1 exists to check for uniqueness.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing main heading.

The page has no headings, so there is nothing further to assess.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing headings. Add an H1 and descriptive H2 sections.

No H1 text exists to inspect.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing main heading.

The page has no headings, so there is nothing further to assess.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing headings. Add an H1 and descriptive H2 sections.

The page has no headings, so there is nothing further to assess.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing headings. Add an H1 and descriptive H2 sections.

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.

No visible <img> elements on the audited page (hidden, presentational and 1×1 tracking images are not counted).

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.

Nothing to change here. Any image you add later needs alt text that describes it, so this check starts scoring then.

No visible <img> elements to measure on the audited page.

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.

Nothing to change here. Give future images explicit width and height attributes so the browser can reserve their space.

No raster images with a recognizable file extension were found.

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.

Nothing to change here. If images arrive later, serve WebP or AVIF alongside PNG/JPEG.

Only 0 visible image(s) on the page, too few for lazy loading to change the initial load.

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.

Nothing to change here. Once the page carries several images, add loading="lazy" to the ones below the fold.

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.

No links were found on the audited page.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. This check does not apply to the features observed in this sample.

Link to your main pages from the homepage. Crawlers and readers both need a path in, and this check then reviews the anchor text.

No same-page fragment links to check.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. This check does not apply to the features observed in this sample.

Keep section links connected to stable IDs.

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.

Only 0 image(s) on the page, too few for responsive image markup to change what phones download.

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

Nothing to change here. When the page carries several images, give them srcset and sizes so phones fetch smaller files.

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.

No source-level interactive controls were found.

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

Inspect browser-rendered controls separately if the page adds interactions with JavaScript.

No ARIA ID references found in the sampled HTML.

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

Verify rendered accessibility separately.

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

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.

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.

Not enough text on the page to tell which language it is written in.

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.

Nothing to change for this check. Confirm the lang attribute names the language most of the page is written in.

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.

No theme-color meta 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 <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.

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

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

Nothing to do here.

apple-touch-icon is declared.

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

Nothing to do here.

Web manifest links and parses correctly.

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

Nothing to do here.