ubricHelp

Exporting your data

Pull scores and failing checks into your own reporting.

Rubric exports your report as four CSV files: action-plan.csv (the ranked fixes), pages.csv (every scored page and its checks), broken-links.csv (the broken outbound links found) and sitemap-issues.csv (problems with your XML sitemap). Download them from the report header or from the matching tab, then open them in any spreadsheet. The files carry the same numbers you see on screen, so nothing is lost in the export.

In short
  • →Four CSV exports: action-plan.csv, pages.csv, broken-links.csv and sitemap-issues.csv.
  • →Download the whole set from the report header, or export one file from its matching tab.
  • →Each file is named with your domain and the crawl date, so runs stay organised and comparable over time.

What can I export from the report?

The report exports as data, not just a page you read. Four CSV files cover the ranked fixes, every scored page, your broken outbound links and your sitemap problems. Because they are plain CSV, they open in Google Sheets, Excel, Numbers or any tool that reads a comma-separated file, and they carry the same numbers the report shows on screen.

The Action Plan tab also offers a developer checklist export, which turns the ranked fixes into a hand-off document with the markup each check expects. That is covered in handing fixes to developers.

What does each CSV contain?

Each file maps to a part of the report:

FileWhat it contains
action-plan.csvThe ranked list of fixes, each with its pillar, severity, effort, how many pages it affects, the fix instruction, why it matters, and the affected page URLs
pages.csvEvery scored page, with its overall score, the three pillar scores, the six per-engine scores, word count, load time, and its failing checks split into errors and warnings
broken-links.csvEach broken outbound link, its status, how many pages link to it, and the source pages
sitemap-issues.csvSitemap problems: URLs missing from the sitemap, orphaned pages with no internal links, and URLs that are noindexed but still listed in the sitemap

Between them, pages.csv is your per-page scoreboard and action-plan.csv is your work list, while broken-links.csv and sitemap-issues.csv give a developer two clean, specific to-do lists.

Where do I download the exports?

There are two ways to get the files:

01
From the report header. The export control downloads the full set in one action, so you get all four files (whichever of them the crawl produced) together.
02
From a tab. The Action Plan, Pages, Broken links and Site structure tabs each export their own file, so you can pull just the one you need.

Each file is named with your domain and the crawl date. Keep the files from each run and you build a dated history you can compare later, which is useful when you re-crawl after a round of fixes.

How do I use the CSVs in a spreadsheet?

Open the CSV in your spreadsheet tool and it lands as a normal table. From there, a few moves make the data reportable:

  • Sort pages.csv by score to rank your pages, or filter to scores below 70 to isolate the pages an engine cannot quote.
  • Group action-plan.csv by pillar or effort to see where the work clusters, or filter to errors to work the blocking issues first.
  • Keep each run's pages.csv and compare the score column across dates to see movement after a re-crawl.
Tip
The exports are a snapshot of one crawl. To track change over time, export after each re-crawl and line the page scores up by URL in your own sheet. Exporting to CSV and Sheets shows how to build that tracker step by step.

Your data stays yours. The crawl runs on GoGoChimp's hardware and the report is private to you unless you create a share link, so exporting is simply taking a copy of your own results into your own tools.

Common questions

Did this answer your question?