NeovaAdvanced SEO Platform

Import Instead of Connecting

Your company’s policy or IT rules keep Neova from connecting to Google Search Console, Google Analytics 4, Bing Webmaster Tools, Microsoft Clarity or your servers? That’s fine: import the data instead. Export it there, choose the file in Neova, and the same checks run on it, on your computer.

5sources by file: Search Console, Analytics 4, Bing, Clarity and server logs
8kinds of server and CDN logs, found from the lines themselves
0accounts to connect, and nothing uploaded
1import per site: used by its next crawls until you remove it

How It Works

ExportIn Search Console, Analytics, Bing, Clarity, your host or an SEO tool that holds the data: the steps for each are below.
Import a File…In Neova, Settings, Connections, Search Console, Analytics, Bing and Clarity by File. Logs: Tools, Server Log.
Check the MatchNeova shows each table of the file, the columns it read and the rows it will write.
ImportThe checks run again on the open crawl, and the file is kept for the site’s next crawls.

Pick Your Source

Export Step by Step

Google Search Console

Performance reportCSV, Excel, Google Sheets1,000 rows a table

Search Console’s own Export is the quickest: one download holds every table of the Performance report. For more than 1,000 rows, or searches by page, use one of the other ways below.

The Performance Report

  1. Open the property, then Performance (Search results).
  2. Choose the date range: Neova reads it from the export’s Filters table. Add filters if you need them; the export keeps them.
  3. Click Export and choose CSV (a .zip with one file per table) or Excel (one sheet per table).
  4. In Neova: Settings, Connections, Search Console, Analytics, Bing and Clarity by File, then Import a File… and choose the file as you downloaded it (a .zip too). Neova shows each table and what it read from it before anything is written.

All the Rows, Searches by Page

  • Looker Studio, Search Console connector, the URL Impression table: a table chart with Landing Page, Query, Url Clicks, Impressions and Average Position (add Device for clicks by device). In view mode, the chart’s menu, Export, CSV: up to 750,000 rows.
  • Bulk data export to BigQuery (Settings, Bulk data export): query searchdata_url_impression and save the result as CSV with url, query, device, clicks, impressions and sum_position. Neova turns sum_position into the average position as Google says: the sum over the impressions, plus 1. The export starts the day it is set up, with no earlier days.
  • A Google Sheets add-on or an SEO tool that holds your Search Console data: grouped by page and query, then File, Download, CSV. See Already in Another Tool.
Comes Across

Pages with their clicks, impressions, CTR and position; searches by page and clicks by device when the file has them (Looker Studio, BigQuery, an API export); search appearance; the dates. The pages of a file of searches by page are added up when it has no table of pages.

Does Not

URL Inspection, which has no export: its checks say not checkable. The Queries, Countries and Dates tables of the Performance export (searches without their pages, which no check reads). A table cut at 1,000 pages is said, and the check for indexable pages with no impressions waits for a full list.

Search Console: exporting report data · the Performance report · data export (Google Search Central) · bulk data export tables · Looker Studio: Search Console · Looker Studio: export a chart, read November 18, 2026

Google Analytics 4

Landing pagesCSV, TSVViewer role

Neova reads sessions by landing page: from Organic Search, and from AI assistants (chatgpt.com, perplexity.ai, copilot.microsoft.com, gemini.google.com, claude.ai and others). One exploration gives both; a report gives one at a time.

An Exploration: Organic and AI in One File

  1. Explore, then a blank (free form) exploration.
  2. Dimensions: Landing page + query string, Session default channel group and Session source. Metrics: Sessions, Engaged sessions, Average engagement time per session and Key events. Set the date range.
  3. Put the dimensions in Rows and the metrics in Values, then Export data, CSV or TSV: the export holds every row of the table, not only those on screen.
  4. In Neova: Settings, Connections, Search Console, Analytics, Bing and Clarity by File, then Import a File… and choose the file as you downloaded it (a .zip too). Neova reads the Organic Search rows as organic and the AI assistants’ sources as AI-referred.

The Landing Page Report

  1. Reports, Engagement, Landing page, with a filter on Session default channel group: Organic Search.
  2. Share this report, Download File, Download CSV: up to 100,000 rows. A Viewer can download.
  3. In Neova: Settings, Connections, Search Console, Analytics, Bing and Clarity by File, then Import a File… and choose the file as you downloaded it (a .zip too). The file does not say which traffic it holds: choose Organic Search only when Neova asks.

Organic Sessions by Day

For the check on a drop in organic sessions: an exploration with Date, Session default channel group and Sessions, at least 47 days, exported the same way.

Comes Across

Sessions, engaged sessions, engagement time and key events by landing page, organic and AI-referred; organic sessions by day.

Does Not

Scroll events, so the scroll depth check says not checkable on an import. An exploration over 10 million events can be sampled: GA4 shows it on the exploration.

GA4: download report data · explorations · the Landing page report · data limits in explorations, read November 18, 2026

Bing Webmaster Tools

Search PerformanceAI PerformanceCSV, Excel

Two reports, each with its own download. A read-only user sees every report.

Search Performance

  1. Open the site, then Search Performance.
  2. On the Pages tab, click Download (CSV). Do the same on the Keywords tab.
  3. In Neova: Settings, Connections, Search Console, Analytics, Bing and Clarity by File, then Import a File… and choose the file as you downloaded it (a .zip too). Import each file. If Neova takes a file for Search Console, choose Bing Webmaster Tools under The file comes from.

AI Performance

  1. Open AI Performance and choose the date range: 7 days, 30 days, 3 months or your own.
  2. Download the view you need (grounding queries, pages, or the days), as CSV or Excel. The download follows the filter you set.
  3. In Neova: Settings, Connections, Search Console, Analytics, Bing and Clarity by File, then Import a File… and choose the file as you downloaded it (a .zip too). Neova knows each view by its columns.
Comes Across

Pages with their Bing clicks and impressions, keywords, and AI Performance: citations by page, grounding queries, topics and days.

Does Not

Crawl and index data (Site Explorer, URL Inspection), which Bing documents no download for.

Bing: Search Performance · AI Performance · user roles, read November 18, 2026

Microsoft Clarity

DashboardData Export APICSV, JSON

A table of pages with Clarity’s numbers: visits, dead clicks, rage clicks, quick backs, scroll depth. With a project admin’s token, connect Clarity instead: Neova then keeps every day, which a file cannot.

From the Dashboard

  1. Open the project’s Dashboard and set the date range and filters you want.
  2. On a widget that lists pages, use its download button, then Download CSV; or the download button of the Filters bar for the whole dashboard.
  3. In Neova: Settings, Connections, Search Console, Analytics, Bing and Clarity by File, then Import a File… and choose the file as you downloaded it (a .zip too). Neova shows the columns it found before anything is written.

From the Data Export API

The JSON the API answers for dimension1=URL, saved as a .json file, is read as it comes.

Comes Across

Per page: visits, dead clicks, rage clicks, quick backs, excessive scrolling, script errors, scroll depth and engagement time, as the file holds them; pages cited in AI answers from a table of cited pages. The Visitor Behavior checks run on them.

Does Not

Days: a file holds the period it was made for, never Neova’s daily archive. Visits by device, unless the file has them. A table without a page column.

Clarity: Download dashboard · Data Export API, read November 18, 2026

Server Log Files

8 log sources.log, .gz, .zip, JSON, CSVOn your computer

A log shows what Googlebot, Bingbot and the AI crawlers really requested. Neova finds the format from the lines themselves, like Screaming Frog’s Log File Analyser: no setting to choose. Each line needs the time, the URL, the status code and the user agent, and the address of the request, which is how a bot is verified.

Formats Neova Reads

FromWhat it isA line, shortened
Apache, Nginxcombined: the default of both, and of cPanel’s and Plesk’s raw logs; a virtual host in front is fine66.249.66.1 - - [10/Nov/2026:13:55:36 -0600] "GET /a HTTP/1.1" 200 2326 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; …)"
IISW3C extended: the #Fields: line names the columns; spaces in the user agent written as +#Fields: date time … cs-uri-stem cs-uri-query … c-ip cs(User-Agent) … sc-status …
Amazon CloudFrontstandard logs: W3C fields, tab separated, the user agent encoded#Fields: date time x-edge-location sc-bytes c-ip cs-method cs(Host) cs-uri-stem sc-status …
Amazon load balancersApplication Load Balancer and Classic Load Balancer access logs, as .gz from the S3 buckethttps 2026-11-10T19:55:36.000000Z app/… 66.249.66.1:2817 … 200 200 … "GET https://www.example.com:443/a HTTP/1.1" "Mozilla/5.0 …"
CloudflareLogpush http_requests, JSON one object a line: ClientIP, ClientRequestHost, ClientRequestURI, EdgeResponseStatus, ClientRequestUserAgent, EdgeStartTimestamp (date text or Unix time)Or connect Cloudflare in Neova: it keeps only crawler requests, in your own Cloudflare account.
Google Cloudload balancing logs, JSON: httpRequest (remoteIp, requestUrl, status, userAgent) and timestamp
AkamaiDataStream JSON: cliIP, reqTimeSec, reqHost, reqPath, queryStr, statusCode, UA
Fastly and othersJSON or CSV whose fields have the usual names: client_ip or remote_addr, timestamp, url or request_uri, status, user_agentFastly lets you choose the fields: include those five.

Several files: put them in one .zip, each file plain or .gz. Apache’s common format has no user agent, so no bot can be told: Neova says so and asks for the combined format.

Where the Files Are

  • cPanel: Metrics, Raw Access, a .gz per domain.
  • Plesk: Websites & Domains, the domain, Logs, Manage Log Files.
  • Amazon: the S3 bucket the load balancer or CloudFront writes to, once access logging is on (it is off until turned on).
  • Google Cloud: Cloud Logging, once logging is on for the load balancer’s backend service.
  • Anyone else: in Neova, Tools, Server Log, Ask for the Log… writes the request for you: the last 30 days, the crawler lines only, with their addresses, so nothing about your visitors.

In Neova

  1. Open the crawl of the site, then Tools, Server Log.
  2. Choose Log File…, then Run Log Analysis. The file is read where it is and never leaves your computer.
  3. A bot counts only when its address is on the list its company publishes (Google, Microsoft, OpenAI, Anthropic, Perplexity, Meta); turn on reverse DNS to also accept Google’s and Microsoft’s by their DNS names, as their help describes.
Comes Across

Every request of the verified search engine and AI crawlers: visits, refusals (429 and 403) and the last visit per URL, the pages Googlebot never asked for, and the URLs bots ask for that the crawl did not find.

Does Not

A log without addresses: no bot can be verified, so none is counted. Requests for the zone’s other sites in a CDN log, which are left out and counted. Per-URL hit counts that another tool made from your logs: they hold no requests.

Screaming Frog Log File Analyser: user guide · requesting logs · Apache log formats · Nginx · IIS W3C logging · CloudFront standard logs · ALB access logs · Cloudflare http_requests · Google Cloud load balancing logs · Akamai DataStream · cPanel Raw Access · Plesk log files · verifying Googlebot · verifying Bingbot, read November 18, 2026

Already in Another Tool

Search ConsoleGA4Logs: ask for the raw files

Your company may keep its Search Console and Analytics data in an SEO tool already: export it from there. Neova finds the URL and the Search Console or Analytics columns by their names, with a tool’s prefix too (GA4 Sessions, Search Console Clicks), and shows what it read before the import. None of these tools documents keeping Bing Webmaster Tools data: export it from Bing.

ToolHoldsExportNeova reads
Screaming Frog SEO SpiderSearch Console and GA4, pulled at crawl time (Configuration, API Access)its documentationThe Internal tab, filter All, Export: the Search Console columns (Clicks, Impressions, CTR, Position) and the GA4 columns come with it.Search Console by page; GA4 sessions by page (say which traffic when Neova asks)
SitebulbSearch Console and Google Analytics by URLits documentationURL Explorer or a URL List, Add/Remove Columns to add the Search Console and Analytics columns, then Export to CSV or Excel (up to 1 million URLs).Search Console by page; Analytics sessions by page
BotifySearch Console (RealKeywords), GA4 and its LogAnalyzerits documentationIn an Explorer, Export to CSV; the file waits in Reports, DataExports for 29 days. One export holds 1 million rows and 10 columns.Search Console by page, or by page and keyword; GA4 sessions by page. LogAnalyzer’s export counts hits per URL: ask for the raw logs instead.
OncrawlSearch Console, GA4 and log monitoringits documentationData Explorer, the Pages dataset with the Search Console and Analytics columns, Export data (large files in the Download center for 30 days).Search Console by page; GA4 SEO sessions by page. The Logs monitoring datasets count hits: ask for the raw logs instead.
JetOctopusSearch Console through its API, past the 1,000-row limit, and its log analyzerits documentationAny data table of its Search Console report exports to CSV, Excel or Google Sheets.Search Console by page, by page and query, by page and device
ConductorSearch Console and Analytics in Intelligence; Search Console by page in Monitoringits documentationThe Pages report exports up to 1 million rows; Search Console Analytics exports the full set, more than it shows.Search Console by page
LumarSearch Console and GA4 by URL; log summariesits documentationIts export steps are not in its public help: a CSV of the URLs with their Search Console or Analytics columns imports the same way.Search Console by page; Analytics by page (check the match Neova shows)
AhrefsSearch Console in Site Audit and Ahrefs Webmaster Toolsits documentationSite Audit, Page Explorer, Columns to add the Search Console data, then Export to CSV.Search Console by page (its column names are not published: check the match)
SemrushOrganic Traffic Insights: GA4 and Search Console for the top 50 landing pagesits documentationOrganic Traffic Insights exports its landing pages to Excel or CSV. Site Audit holds only Analytics page views, which no Neova check reads.Search Console by page, for those 50 pages
SEOTestingSearch Console, kept over timeits documentationThe All Pages report downloads as CSV.Search Console by page
Google Sheets add-onsSearch Analytics for Sheets (Search Console), GA4 Reports Builder (GA4, from Google)its documentationGroup by page (and query), or a report with landingPage, sessionDefaultChannelGroup and sessions; then File, Download, CSV.Search Console by page and query; GA4 landing pages

Each tool’s own documentation, read November 18, 2026. A crawl from these tools imports too: Import a Crawl From Another Tool.

Your File Not Read?

Neova says why for each table: no column it knows, a page column without clicks, sessions or views beside it, or which traffic a GA4 file holds. Under The file comes from, choose the source if Neova guessed another. Send the first lines of the file, without its numbers if you prefer, to hello@neova.app, and we will make Neova read it.

Google Search Console, Google Analytics, Looker Studio, BigQuery and Google Sheets are trademarks of Google LLC; Bing is a trademark of Microsoft; the other tools’ names are trademarks of their owners, used only to name their products. Neova Labs is not affiliated with, endorsed by or sponsored by any of them. Menus and limits change: what is here was read in each vendor’s documentation on November 18, 2026. NEOVA™ is a trademark of Neova LLC.