Running your first audit
To run your first Rubric audit, enter your website's URL at cited.gogochimp.com and start the crawl. No card is needed, and the free plan crawls up to 500 pages. Rubric reads each page the way an AI engine would, scores it from 0 to 100, and emails you when the report is ready.
- →No card is required. The free plan audits up to 500 pages and gives you the full score, pillars, issues and Action Plan.
- →The crawl runs on GoGoChimp's own hardware through an outbound queue, never on your machine, so you can close the tab.
- →Rubric emails you when the report is ready, then shows your citability score, the three pillars and the phased Action Plan.
How do I start an audit?
Starting an audit takes three steps and no payment details.
What happens while the crawl runs?
While the crawl runs, Rubric fetches your pages as a normal web client and reads exactly what an AI engine reads, so rendering and caching affect the result. You can watch progress as pages are scored, or close the tab and wait for the email.
The crawl runs on GoGoChimp's own hardware, reached by an outbound queue. It never connects inbound to your machine, so nothing is installed and nothing runs locally. When the crawl finishes, Rubric emails you and the report opens with your citability score, the Known, Findable and Trusted pillars, and the Action Plan.
How many pages should I crawl?
Crawl the pages that answer questions a buyer or reader would ask, not your whole archive. Your site score is the median of the pages Rubric scores, so padding the crawl with thin, low-value pages can drag the median down.
On the free plan the ceiling is 500 pages. For a larger site, point Rubric at the sections that matter: your key landing pages, your product or service pages, and the articles that answer real queries. You can always re-run a broader crawl later.
Which files does Rubric skip?
Rubric scores HTML pages, the pages an engine would actually quote. It does not score machine and data files. Skipped files include XML sitemaps and .xml, .csv, .json and .kml files, plus llms.txt and agents.md.
These files are still read where they are useful. A sitemap helps Rubric find your pages, and llms.txt is checked as an informational signal. But they are not scored as pages, so they never appear in your page list and never affect your median.
What guards run during a crawl?
Rubric applies a few guards on every crawl to keep it safe and predictable.
| Guard | What it does |
|---|---|
| URL validation | Rejects private and internal hosts, so an audit cannot be pointed at an internal network |
| Rate limit | Caps how fast a single account can crawl, to protect your server and the queue |
| Page and time ceiling | Stops any one crawl running past a hard page and time limit |
| Stale-job reclaim | Recovers a crawl that stalls, so a stuck job does not block your account |
What do I get when it finishes?
When the crawl finishes you get a full report: your citability score out of 100, a score for each of the three pillars, every issue with the evidence behind it, a Pages view you can sort against the 70 line, and a phased Action Plan that ranks fixes by how far they move your score per hour of work. From there, start with the template fixes that clear a check on every page at once, then work your weakest pillar.