> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/audit/batch-url-analyzer-guide.md).

# Using Batch URL Analyzer

Use Batch URL Analyzer to compare a set of pages and prioritize consolidation, updating, internal promotion, outreach, or removal decisions with multiple evidence sources in one table.

It analyzes each submitted URL separately. It does not crawl the surrounding site or decide what to do with a page automatically.

## Prepare the URL list

Open the client and choose **Audit → Batch URL Analyzer**. Paste up to 100 absolute URLs, one per line or separated by commas.

Before starting:

* remove duplicate URLs, because each submitted row counts toward the limit and usage impact;
* use the final canonical URL where possible;
* confirm that the selected client owns the GSC and GA4 data you expect to compare; and
* keep unlike page types in separate runs when they have different goals.

Rankability identifies invalid URL strings before the run. The server accepts a maximum of 100 valid URLs.

## Connected data and usage

Batch URL analysis is included in full-platform pooled usage. Larger batches have a higher on-demand impact, so remove duplicate or unnecessary URLs before starting.

Connect Google Search Console and Google Analytics 4 for the richest comparison. If either is not connected, Rankability warns you and lets you continue with backlink and organic keyword data only.

See [Connecting client Google services](/account-and-settings/connecting-client-google-services.md).

## Understand the columns

The result can include:

* **Backlinks** — links pointing to the exact submitted URL from the backlink data provider.
* **Referring Domains** — unique domains represented in those backlinks.
* **GSC Clicks and Impressions (28d)** — page-level Search Console data for the recent reporting window.
* **GA4 Sessions (28d)** — sessions matched to the page path for the recent reporting window.
* **Organic Keywords** — the number of ranking keywords returned for the URL by the search-data provider.

URL matching normalizes common protocol, `www`, case, and trailing-slash differences for connected search data. It does not mean that genuinely different paths are merged.

## Prioritize with multiple signals

Sort by any numeric column and use the URL search or data-status filters:

* **Complete data** — all expected sources returned a value.
* **Partial data** — at least one source is unavailable for the row.
* **Poor performers** — the available backlink, search, and traffic signals are zero or missing.
* **With errors** — one or more provider requests reported an error.

Do not make a deletion or redirect decision from the Poor performers filter alone. A page can still be important for conversions, navigation, paid campaigns, links not found by the provider, seasonal demand, or a query outside the current data window.

Use the table to form a shortlist, then verify the live URL, canonical, conversions, internal links, business purpose, and replacement page before acting.

## Missing data versus zero

Rankability preserves provider failures as blank values and exposes row errors when possible.

* A **zero** in a connected GSC or GA4 column means no matching activity was found in that source and window.
* A **blank** value means the source was disconnected, unavailable, or failed for that row or run.
* A provider’s zero is limited to that provider’s coverage; it is not proof that no link, keyword, click, or visit exists anywhere.

This distinction is especially important when sorting pages for consolidation.

## Previous runs and CSV export

Completed runs are saved to the client’s recent history when persistence succeeds. Open a previous run to review its stored URL list, results, and integration state. The history view retains up to the recent runs shown by the product.

Use **Export CSV** to download the currently filtered and sorted rows. The CSV contains the data columns shown by the analyzer; provider error text is reviewed in the app rather than exported as a decision label.

If Rankability completes the analysis but says the report could not be saved to history, export the current result before leaving the page.

An integration with `batch-url:read` can list saved history at `/api/agent/v1/clients/:client_id/batch-url-runs` and paginate one run at `/batch-url-runs/:run_id`. These reads preserve missing measurements as null and never analyze URLs or call providers.

## Troubleshooting

* Confirm that every line is a complete `http://` or `https://` URL.
* If GSC or GA4 is blank, verify the client connection and that the submitted URL belongs to the connected property.
* If one provider fails, use the other returned columns and rerun later rather than interpreting the blank as zero.
* If a URL has multiple variants, submit the canonical version and check whether the connected data uses the same path.

For repeated failures, contact support with the client, run time, number of URLs, affected provider, and visible error text.

## Related articles

* [Audit overview](/audit/audit-overview.md)
* [Using Site Auditor](/audit/site-auditor-guide.md)
* [Connecting client Google services](/account-and-settings/connecting-client-google-services.md)
* [Usage limits reference](/account-and-settings/credit-costs-reference.md)