Skip to main content
fimo site check reads your site the way search engines and AI assistants do, and lists what to fix: missing or repeated titles and descriptions, broken links, images without alt text, pages missing from the sitemap, and more. Fimo’s SEO, GEO, Content, Quality and Compliance agents run the same checks. It reads the hosted preview of your current Branch, so run fimo deploy first if you have none. Nothing on the site changes.

Check a few pages

Name the pages a change touches:
Paths, bare names (pricing) and full URLs all work, up to 50 pages per run. Limit the check to the topics you care about:

Check the whole site

--all reads the home page, the sitemap, llms.txt and every page they link to, up to 300 pages. Some problems only show across the whole site, so only --all finds them: two pages with the same title, titles that do not follow the shape most of your titles share, pages nothing links to, pages too many clicks from the home page, and pages missing from the sitemap.

Topics

Without --topic, every topic runs. The other topics read each page’s HTML. When a page’s HTML has no content before JavaScript runs, as on a client-rendered site such as a React Router site with ssr: false, the check reads that page in a real browser instead, and the output says how many pages it read that way. --browser renders every page in a real browser. Both need agent-browser installed.

Read the results

Each finding names the page and says what is wrong. It is marked:
  • auto: the fix has one right answer, such as a missing description written from the page’s own words.
  • suggest: a person decides, such as a title too long for Google or a title that already names your site.
  • note: worth knowing, nothing to fix.
When a page cannot be read, the output says so: “could not tell” is not the same as clean. With --json, the report is in data.output.
Lists every link on the named pages and the status of each target, so you can see where a broken link points.

Other targets

  • A Branch other than the current one: --branch <name>. The prod Branch has no hosted preview; check main or the published address.
  • Any address, such as your local dev server or the published site: --url <origin>.
If the hosted preview is still building, the command waits up to 90 seconds before it stops and asks you to run it again.