Frameboy: Atlas in Real-Time

Description is 41 characters, under this audit's 70-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.

Add useful context if the summary omits the page purpose. Do not pad it or force keywords to reach a count.

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: "Frameboy: Atlas in Real-Time"

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 28 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 "Frameboy: Atlas in Real-Time" 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: "Interactive world exploration with Atlas."

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://frameboy.worldlabs.ai/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.

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.

1 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://frameboy.worldlabs.ai/

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.

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.

og:title: "Frameboy: Atlas in Real-Time"

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: "Interactive world exploration with Atlas."

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://frameboy.worldlabs.ai/frameboy-opengraph.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.

Dimensions declared: 1200×749.

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: "Frameboy".

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.

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, viewport-fit=cover".

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 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"> (/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.