Countnest

Site audit, SEO and GEO tools

Start an audit

Open your website in the dashboard, then SEO → Site audit. A weekly crawl runs automatically. Re-run now starts one manually (once an hour at most). Large sites resume from a saved queue across cron runs every 15 minutes. Health also shows the latest completed audit and its fix list.

All tools are included in every plan. Starter crawls up to 500 pages a week and follows 10 rank keywords, Growth 2,000 pages and 50 keywords, Agency 10,000 pages and 250 keywords. Webhook alerts use the existing Growth and Agency webhook feature; email alerts are on every plan.

What CountnestBot reads

CountnestBot requests public HTML pages, robots.txt and sitemaps on the domain you added. It identifies itself as CountnestBot/1.0 (+https://countnest.com/docs/site-audit). Each crawl obeys robots.txt rules for CountnestBot, or the * group when no specific group exists. Disallowed pages are skipped. Outbound requests and redirects are checked to stop requests to private or internal addresses.

Requests use a short pause and at most two concurrent connections (one if Crawl-delay is present). If robots.txt cannot be read because of a server error or rate limit, or Crawl-delay is above 5 seconds, CountnestBot does not start the audit. Redirects and sitemap files are checked against the same rules. CountnestBot does not execute JavaScript. Pages that require login or render everything in the browser may not be audited fully.

To exclude the whole site, add this to robots.txt:

User-agent: CountnestBot Disallow: /

This affects CountnestBot only, not Google or AI crawlers. To allow auditing, remove that group or use an empty Disallow rule. Never use robots.txt to protect private information; require authentication instead.

Fixes first

The audit lists broken internal links, error status codes, missing and duplicate titles and descriptions, redirect chains, canonical issues, missing image alt text, thin pages and sitemap pages with no internal links. An orphan finding is only within the audited pages; a capped crawl may not see every link. External links are not checked. We keep extracted page facts for the two latest completed audits, not full HTML copies.

SEO tools

  • Internal links: pages that mention the same topic or receive impressions for the same query but do not link to each other.
  • Cannibalisation: queries where two or more of your pages receive impressions. These are candidates to review, not proof that rankings are harmed. Connect Search Console first; query and page pairs cover the latest 28 days and refresh daily.
  • Content refresh: pages with at least 10 clicks in the previous 28 days that lost more than 30%, and pages whose sitemap or visible modified date is over 12 months old. Optional weekly emails are off by default. Every email respects alert preferences and has an unsubscribe link.
  • Schema generator: choose a crawled page for Article, FAQ, Product, LocalBusiness or HowTo JSON-LD. Check every value against what is visible before publishing. Never invent prices, stock or business details. Google limits FAQ rich results and no longer shows HowTo rich results; valid markup does not guarantee a rich result or an AI mention.
  • Indexing: Search Console URL Inspection, using the same webmasters.readonly permission. This reports Google's indexed copy, not a live test or an indexing request. We cache checks for a week and spread them throughout the day, currently at most 600 per site per day, below Google's roughly 2,000 per-property quota. Other tools using the property share Google's quota.
  • Rank tracker: follow keywords from Search Console. Position is Google's impression-weighted average, not an independent live rank check. Daily data is about three days behind; the chart also groups by week or month.

GEO tools

  • AI answer readiness: a content checklist, not a promise of citations. Look for a direct opening answer, structured data, useful question headings, a clear heading hierarchy, dates, author and llms.txt. It combines this checklist with AI crawler hits and AI landing visits already recorded by Countnest. Install the optional server crawler snippet to see crawler hits.
  • AI crawler access: daily robots.txt and llms.txt checks. The monitor reports access to the homepage for each named bot, not every path. It alerts on a change from allowed to blocked for GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Google-Extended, Googlebot, Bingbot and Applebot. Network errors are marked unknown, not treated as a new block. Turn emails off here or through the email's unsubscribe link. llms.txt is a proposed convention, not a requirement.
  • Citation clues: AI landing visits, a matching AI crawl followed by AI visits within 14 days, and question-style Search Console queries. Every row is a clue from your own data. A crawl followed by a visit does not prove causation or a citation; mentions without clicks are invisible. No paid APIs are used.

Data and control

These tools use your public pages and the search and traffic data already connected to your Countnest site. They do not store IP addresses. Adding a site instructs CountnestBot to audit it; robots.txt controls page access. Privacy policy and DPA describe data and retention. Remove the site to delete its audit and tool data.

See your own numbers in minutes

30-day free trial, no card required. Then from $14 a month. Cancel anytime.

Start free for 30 days