Living Brain

Title is only the site name: "Living Brain".

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.

Add a short descriptor after the name, for example "Brand — what it does for whom". People who do not know the name yet search for what you do.

Title "Living Brain" is 12 characters, under this audit's 15-character review point (a heuristic, not a Google minimum).

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.

Make the title descriptive enough to identify the page topic and purpose without padding it to a target count.

Description is 167 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 ("Living Brain,AI Memory,Living Memory,Persistent Memory,AI Br…").

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: "Living Brain"

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 persistent and evolving intelligence layer that connects your context, surfaces non-obvi…"

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://livingbrain.com/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.

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.

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.

Repeated discovery copy found: description "A persistent and evolving intelligence layer that connects your context, surface…" on https://livingbrain.com/ and https://livingbrain.com/about-us and https://livingbrain.com/privacy-policy and https://livingbrain.com/pricing and https://livingbrain.com/workspace and https://livingbrain.com/terms-of-service.

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.

Give each content page a distinct description, H1, and opening copy. If the pages intentionally represent one resource, consolidate them with a canonical or redirect.

• https://livingbrain.com/
• https://livingbrain.com/about-us
• https://livingbrain.com/privacy-policy
• https://livingbrain.com/pricing
• https://livingbrain.com/workspace
• https://livingbrain.com/terms-of-service

Visible text is 2.2% 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.

Flesch reading ease ≈ 31.

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.

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.

No recognized empty JavaScript application shell on 8 sampled page(s). The entered page exposes 721 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 721 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.

og:image:width / og:image:height are missing.

This is what your link looks like when someone drops it into a chat or a feed. It is there, but weaker than this check expects.

Declare them (1200×630 recommended) so platforms render the preview immediately on first share instead of after re-scraping.

og:title: "Living Brain"

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: "A persistent and evolving intelligence layer that connects your context, surfaces non-obvi…"

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://livingbrain.com/og/living-brain-og.jpg"

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/jpeg).

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: "Living Brain".

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.

None of the 7 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://livingbrain.com/about-us
• https://livingbrain.com/contact
• https://livingbrain.com/privacy-policy
• https://livingbrain.com/pricing
• https://livingbrain.com/stories
• https://livingbrain.com/workspace
• https://livingbrain.com/terms-of-service

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.

The H1 has no text, alt text or label (often a logo image with an empty alt).

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

Put descriptive text in the H1. If it wraps a logo, give the image alt text naming the site, or move the H1 to the hero headline.

H1 found: ""

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 35 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.

35 headings, averaging 2.3 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.

12 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 14 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 14 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.

10 of 10 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.

14/14 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.

11 external link(s) open in a new tab without rel="noopener".

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.

Current browsers already treat target="_blank" as noopener, so the remaining risk is limited to older browsers. Adding rel="noopener" keeps the opened page from controlling yours there too.

All 8 sampled internal links return < 400.

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.

29 of 30 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.

Homepage links to 7 distinct internal pages.

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.

1 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.

8 of 310 source controls lack a detectable name.

Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.

Give each control visible text, a connected label, aria-label or aria-labelledby. Placeholder and neighboring text alone do not name an input. Verify the browser accessibility tree after fixing.

• https://livingbrain.com/
• https://livingbrain.com/about-us
• https://livingbrain.com/contact
• https://livingbrain.com/privacy-policy
• https://livingbrain.com/pricing
• https://livingbrain.com/stories
• https://livingbrain.com/terms-of-service

ARIA references point at IDs that do not exist on 2 sampled page(s), e.g. aria-labelledby="powered-by-heading", aria-labelledby="powerful-agents", aria-labelledby="powered-by-heading".

Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.

Connect ARIA references to unique existing IDs. If JavaScript adds the targets, verify the rendered accessibility tree.

• https://livingbrain.com/
• https://livingbrain.com/about-us

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.

9/14 images ship responsive srcset variants.

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.

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"> (/icon.png?icon.f3fae57e.png).

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

Nothing to do here.