OrganiqSEO site audit in Claude and ChatGPT: issues ranked by Search Console impressions
· Organiq · third-party facts carry source and date in the text
Organiq (organiqgeo.com) crawls the HTML of your own site, runs the checks and returns two health scores with their formula and the issues ordered by the Search Console impressions of the affected pages. The assistant, Claude or ChatGPT, reads it through the connector.
What does the site audit check?
48 checks: 18 errors, 22 warnings and 8 notices. They cover HTTP status, titles and descriptions, canonicals, redirects, hreflang, JSON-LD, internal links, robots.txt, the sitemap and access of AI crawlers. 5 of the 48 look at the whole site and are listed apart from the scores. No check can be switched off, so a score does not rise without a fix.
How are the two health scores calculated?
Page health is the share of crawled pages with no error. Traffic health is the share of Search Console impressions of the last 28 days that land on pages with no error. Errors alone count: warnings, notices and site-wide issues are listed and stay out of the calculation. With no impressions in the period there is no traffic score. The text below is the formula as the tool returns it.
Page health = 100 × internal HTML pages crawled with no error ÷ internal HTML pages crawled. Traffic health = 100 × Search Console impressions (last 28 days) of pages with no error ÷ impressions of the crawled pages; with no impressions in the period there is no traffic score. Warnings, notices and site-wide issues are listed and do not enter the calculation.
In what order do the problems come?
get_site_audit sorts the issues by the Search Console impressions, in the last 28 days, of the pages they affect, from the largest down; ties go to the issue with more pages. Severity is shown in each row but does not set the order. Each row has code, severity, title, fix, pages, impressions and clicks. get_audit_issue then lists the pages of one issue, also by impressions.
How do you run a site audit in Claude or ChatGPT?
Connect Organiq to Claude or ChatGPT and ask which problems of a property to fix, in what order. The assistant calls get_site_audit; get_audit_issue and find_internal_link_opportunities give the pages and the links to add. request_site_audit queues a new crawl: it needs the write scope and is refused if the last audit finished less than 24 hours ago. An audit also runs every 7 days. With site: "demo" the read tools answer with fictional data, no account.
What does a real site audit look like?
On November 9, 2026, the audit of organiqgeo.com crawled 81 pages in 35 seconds: page health 100 and traffic health 100, 0 pages with an error, 37 with a warning and 1 with a notice. The most frequent warning was a title over 60 characters, on 34 pages.
| Measured on November 9, 2026 | organiqgeo.com |
|---|---|
| Pages crawled | 81 |
| Crawl time (seconds) | 35 |
| Page health / traffic health | 100 / 100 |
| Pages with an error | 0 |
| Pages with a warning | 37 |
| Pages with a notice | 1 |
| Pages with a title over 60 characters (warning) | 34 |
A score of 100 means no crawled page had an error; it does not say the pages have nothing to improve, as the 37 pages with warnings show. This is one audit of our own site, a measurement and not an average of sites.
How many pages does it crawl, and how often?
Pages crawled per audit: 100 on Free, 500 on Starter and 2,000 on Agency. While the launch is open, every account crawls up to 2,000 pages per audit, the Agency limit; the plan limits below apply afterwards. The audit runs every 7 days; a new one can be requested 24 hours after the last finished. The response states the pages crawled, the plan limit and whether the crawl was cut by it.
The crawler follows rules you can check: it identifies itself as OrganiqAudit/1.0 (+https://organiqgeo.com) and obeys robots.txt (a User-agent: OrganiqAudit group blocks it), and a crawl-delay of up to 10 seconds. It makes one request at a time, at most 4 per second, reads up to 1,000,000 bytes of each page and follows links up to 10 clicks from the home page.
What does the site audit not do?
It reads HTML and does not run JavaScript: a page rendered on the server is read normally; content a script adds after loading is not seen. It crawls URLs of a property you verified in Search Console, not competitors. It does not check links to other sites or edit your pages. And it promises no position: the checks find technical issues, and the effect of fixing them is read later in Search Console.
Is there a free site audit?
Yes. The Free plan (1 property) includes the audit, with up to 100 pages crawled per audit, the same checks, the same two scores and the same tools as the paid plans; the plan changes the pages crawled per audit (500 on Starter, 2,000 on Agency).
While the launch is open, every account crawls up to 2,000 pages per audit, the Agency limit; the plan limits below apply afterwards. Prices are on the pricing page. The property has to be verified in Search Console.
How does it differ from Screaming Frog, Sitebulb, Ahrefs and Semrush?
Read on November 10, 2026 from each vendor's own pages. The four run JavaScript and have larger URL limits than Organiq. The difference is one score and one order, with the exceptions below.
- Factor: a second health score weighted by real Search Console impressions, and an issue list ordered by the impressions of the affected pages; both formulas are written in the tool answer.
- Comparison and exception: on the pages read on November 10, 2026, none describes a score weighted by impressions or a list ordered by impressions. Screaming Frog: no single score on the issues page, issues carry a High, Medium or Low priority label, and Search Console data enters as columns and filters (configuration guide, read in part). Sitebulb: an Audit Score described as based on the number, type and importance of Hints and the share of URLs affected, with Hints labeled Critical, High, Medium, Low and Insight; exact weights not found, and the score and Hints descriptions were seen in search-result summaries. Ahrefs: Health Score is internal URLs with no error divided by internal URLs, formula published (help article). Semrush: Site Health with no published formula, and the audit can be crossed with Google Analytics (Site Audit, configuration). The absence is on the pages read, not proof that nothing exists. Exceptions: all four run JavaScript and Organiq reads HTML; Screaming Frog and Sitebulb declare more than 300 checks against 48; their URL limits are larger; they crawl any site, with no verified property; Screaming Frog and Sitebulb label each issue by priority (three and five levels), while Organiq shows three severities (error, warning, notice); Screaming Frog adds GA4, command line and scheduling at any interval. Parity: a page-based score with a published formula (Ahrefs publishes the same calculation) and a read of the audit by an agent through MCP (Screaming Frog, Sitebulb and Ahrefs have an MCP server).
- Where to see it: the two scores at the top of the
get_site_auditanswer, with the formula just below, and the impressions column in the issue list.
Is Organiq the right tool for a site audit?
For whom: someone with a site verified in Search Console who wants an assistant to list the technical issues in the order of the impressions they touch. Not for whom: someone whose pages are written by JavaScript, who needs more than 48 checks or who crawls sites that are not theirs; for that, Screaming Frog or Sitebulb are the alternatives, with the exceptions in the previous section.
How was this page made, and what is missing?
Counts, limits and crawler rules come from the code of Organiq; the case is one real audit, run on November 9, 2026. On November 10, 2026 we opened the vendor pages linked above. Not read in full: the Screaming Frog configuration guide; for Sitebulb, the Hints page and score descriptions were seen in search summaries and its score method was not found; the Ahrefs article was read through a search result. Corrections with a source: youssefpmat@gmail.com.
Frequently asked questions
How do I run an SEO site audit with Claude?
Connect Organiq to Claude and ask for the audit of a property. Claude calls get_site_audit, which returns two health scores with the formula and the issues ordered by the Search Console impressions of the affected pages. The site has to be verified in Search Console.
Can ChatGPT do a technical SEO audit of my site?
With a connector, yes: ChatGPT calls the same tools as Claude (get_site_audit, get_audit_issue, find_internal_link_opportunities, request_site_audit) and reads the audit Organiq ran. The crawl is done by Organiq, not by the chat.
How is the site health score calculated?
Page health = 100 × internal HTML pages crawled with no error ÷ internal HTML pages crawled. Traffic health = 100 × Search Console impressions (last 28 days) of pages with no error ÷ impressions of the crawled pages; with no impressions in the period there is no traffic score. Warnings, notices and site-wide issues are listed and do not enter the calculation.
Does the site audit run JavaScript?
No. It reads the HTML of each page, so text written by a script is not seen.
Is there a free site audit?
Yes. The Free plan includes it, with up to 100 pages crawled per audit.
How often does the audit run?
Every 7 days, and a new one can be requested through the assistant when the last finished at least 24 hours ago (write scope).