Feature 06 / Search

Can a model actually read your site?

Half of AI visibility is technical: files a model looks for, schema it trusts, pages it can parse. ZwayRank checks them weekly and creates what is missing.

What you see

Crawl audit: broken links, redirect chains, thin pages, missing titles and descriptions, duplicate content.

Schema coverage: which pages carry Organization, Article, FAQ and Product schema, and which do not.

Files: sitemap, robots, llms.txt and the crawler rules for AI bots, present or missing.

Speed and readability: Lighthouse scores per page, and a plain check of whether the main content is reachable without JavaScript.

The technical round: crawl audit, schema coverage, speed and readability per page
What the crew does on its own
  • Runs the round weekly and files each problem as a suggestion with the fix
  • Creates missing schema, sitemap, robots and llms.txt on connected sites, as a commit you can review
  • Fixes broken internal links in the pages it manages
  • Re-checks after a fix and closes the alert with the reason
What waits for you
  • Approve site commits, unless the brand is on auto
  • Fix anything on a site ZwayRank cannot write to; the suggestion tells you exactly what

The files a model looks for before your homepage

A model's crawler reads robots first, then the sitemap, then llms.txt if you have one. A site that blocks AI crawlers by accident, or has no sitemap, is invisible in a way no amount of content fixes. The round checks these every week and creates them where the site is connected.

Schema is how a model trusts a fact

Organization schema tells a model who you are. FAQ schema gives it question and answer pairs it can lift. Product schema gives it prices it can quote. ZwayRank checks coverage per page and adds what is missing to the pages it manages.

Readability is the check nobody runs

Some sites render everything with JavaScript and show a crawler a blank page. The readability check fetches your pages the way a model does and tells you whether the text was there. If it was not, that is the first thing to fix, and the suggestion says how.

Speed from Google's own tool

Lighthouse runs on your key against your key pages. Slow pages get cited less and rank lower; the round shows which pages and what weighs them down.

Which sites can it write to?

Astro sites on GitHub, static mirror sites that build from a repo, and sites whose blog is a data file in a repo. Everything else gets the fix as a suggestion you apply.

See it on your own brand.

Add one brand. The first scan is free and takes a few minutes. Then you decide whether the crew gets to work.

Seven days. One brand. Your keys after the first scan.