What a check reads

  • Pages are read by SearchlarkBot. It obeys your robots.txt, including crawl delays, and waits between requests. Pages robots.txt blocks are never read.
  • Pages per check: 100 on Starter, 250 on Growth, 500 on Agency, and 10 during the free trial.
  • 33 checks cover indexing, titles and descriptions, content, images and site setup. Each finding is an error, a warning or a notice.

To keep SearchlarkBot out of your whole site, add this to robots.txt:

robots.txt
User-agent: SearchlarkBot
Disallow: /

How often

  1. Open your site in Searchlark and choose Site health. Click Run first check. It usually takes 1 to 5 minutes, and you can leave the page.
  2. After that, a check runs every 7 days. Click Run check now for an extra one; you can start one every 10 minutes.
  3. History lists every check, with the score and what changed since the check before: new issues, issues that came back, and issues you fixed.

Editors, admins and owners can run checks and act on fixes. Viewers can read them.

Problems and issues

  • An issue is one finding: one check on one page, or on the whole site. Every issue says why it matters and lists steps to fix it.
  • A problem groups issues that share a cause, for example every page built from the same template, or a value repeated across the site. Fixing the cause once clears all of them.
  • The Issues page is grouped by problem. Click Show every issue to see the full list, and filter it by severity, area or status.
  • If an issue or problem doesn't apply to your site, ignore it. It leaves your open totals, and your score leaves it out from the next check. You can restore it later.

The fix plan

The Overview opens with the fix plan: your open problems in priority order, biggest wins first. Each row shows how many findings it clears, its share of the total, the kind of fix (one template change, one setting, page by page, or writing) and who usually does it (a developer, site settings, or content).

Search Console connection opens soon. Once connected, problems on pages that get search impressions will move up the plan.

On paid plans, an AI summary of the plan sits above it, and a template problem can come with a suggested title and description pattern to copy.

Open a problem to see:

  • Why it matters and how to fix it.
  • Steps for your platform. We detect it when we can (for example WordPress, Shopify, Webflow, Ghost or Next.js), and you can switch to another.
  • The impact, the template behind it, examples and the pages affected.

Fixes

For page titles, meta descriptions and image alt text, AI can draft new values. Click Draft a fix with AI on an issue. Drafts appear under Fixes. Nothing changes on your site until you approve one.

  1. Open Fixes. Edit a draft if you like, then approve it or click Reject.
  2. WordPress with the Searchlark plugin 0.4.0 or later: click Approve and apply. The plugin writes the value to Yoast SEO, Rank Math, SEOPress or All in One SEO, or prints it itself when none is installed. Alt text goes to the Media Library and the post. Click Undo to put the previous value back. See the WordPress setup.
  3. Any other site: click Approve, then Copy value, paste it into your site, and click I've made this change.
  4. We then read the live page. Within about 2 minutes the fix shows as verified and its issues close. If the old value is still there, it shows as not verified: check the page shows the new value, then tell us again.

Other issues, such as broken links or pages left out of the sitemap, have step-by-step instructions to follow on your site.

During the free trial, each issue offers a copy-ready fix. AI-drafted fixes come with a paid plan. Paid plans open soon; you can compare them on the pricing page.

Re-check a problem

After you fix a problem, open it and click Re-check these pages. We read up to 25 of its pages again and close the findings that are fixed. When none are left, the problem closes. You can re-check a problem once every 10 minutes. The next full check also picks up every fix.

Hand a problem to an AI coding agent

If your site is code you or a developer can change, an AI coding agent can do the fix.

  • On a problem page, the Fix with an AI coding agent card has two options. Copy a prompt gives a prompt with the evidence, the steps for your platform and how to verify the fix. Paste it into your agent.
  • Connect over MCP works with the Searchlark MCP server. The agent loads the problem itself and re-checks the pages when the fix is deployed. In Claude Code, the card shows a ready command that runs the fix_health_problem prompt.
  • On the Overview, Copy agent prompt on the fix plan hands over the whole plan. Over MCP, the fix_health_plan prompt does the same: it works through the problems one at a time, biggest wins first.

To set up the MCP server, see Connect AI apps. The same data is in the API.

Related guides