← Blog

Free SEO Report API: Best Free Options, Limits, and Setup Guide

2026-11-12 · IndexNowFast Team
Free SEO Report API: Best Free Options, Limits, and Setup Guide

Quick Answer

A free SEO report API can help you collect search rankings, traffic, and technical performance data without paying for an expensive reporting platform. For websites you manage, the best starting point is Google's Search Console API. Add the Google Analytics Data API for organic visitor activity and PageSpeed Insights API for technical diagnostics. These APIs provide data, not complete downloadable reports. You must connect them, manage access permissions and quotas, and format the results yourself.

Key Takeaways

  • Best for Google search visibility: Google Search Console API provides clicks, impressions, click-through rate (CTR), and average search position for authorized websites.
  • Best for organic visitor reporting: Google Analytics Data API provides sessions, acquisition, engagement, and configured key-event measurements from Google Analytics 4 (GA4).
  • Best for technical performance: PageSpeed Insights API provides Lighthouse diagnostics and recommendations for individual pages.
  • Free does not mean unlimited. APIs have quotas, data availability limits, or other operational restrictions.
  • Website access matters. An API key alone cannot unlock another website's private Search Console or GA4 reports.
  • Competitor intelligence is different. Broad competitor rankings and backlink databases generally require additional data providers.
  • A complete report requires another layer. Your application must combine the responses, retain their dates and sources, and produce the dashboard, spreadsheet, HTML page, or PDF.

Which Free SEO Report API Should You Choose?

The right API depends on what your SEO report needs to explain.

An agency preparing monthly reports for websites it manages has different requirements from a developer building a public competitor-analysis tool. The agency may already have permission to access Search Console and GA4. The competitor-analysis developer usually does not.

An application programming interface, or API, lets software request information from another system through a documented interface. Instead of downloading performance reports manually, your application can retrieve data on a schedule and use it in a custom reporting system.

Here is how the main options compare.

APIBest reporting taskAvailable dataRequired accessAuthenticationFree-use boundaryMain limitation
Google Search Console APIGoogle search visibilityClicks, impressions, CTR, average position, query and page dimensionsAuthorized Search Console propertyOAuth authorizationFree, with request quotas and data limitsNo unrestricted competitor search data
Google Analytics Data APIOrganic traffic and visitor behaviorSessions, acquisition, engagement, events, configured key eventsAuthorized GA4 propertySupported Google authenticationQuota-limited API accessDoes not provide Search Console search impressions or query-level performance
PageSpeed Insights APITechnical page diagnosticsLighthouse results, performance measurements, improvement suggestionsPublicly accessible page URL for ordinary requestsAPI key optional for documented requestsPublic API subject to operational limitsNo organic traffic, keyword database, or backlink database
IndexNowFast APIIndexing workflow and task monitoringSubmission tasks and supported URL lifecycle statusesIndexNowFast account and credentialsBearer tokenDocumented credit-based indexing operationsNot a comprehensive free SEO reporting API

The Google API capabilities are documented in the Search Analytics reference, GA4 Data API documentation, and PageSpeed Insights API guide.

The separate IndexNowFast capabilities are described in its API documentation.

For most owned-site reporting projects, begin with Search Console. Add GA4 if you need to know what visitors do after reaching the website. Add PageSpeed Insights when technical performance belongs in the same report.

A combined reporting system is often more useful than trying to find one API that claims to do everything.

What Data Can Each Free API Actually Return?

Google Search Console API: Search visibility and keyword performance

The Search Console API is especially useful for answering questions such as:

  • How many times did our pages appear in Google Search?
  • How many clicks did they receive?
  • Which search queries generated impressions and clicks?
  • Which pages performed best during the reporting period?
  • How did performance vary by device or country?

Its Search Analytics method returns four important measurements.

Clicks count clicks from eligible Google Search results to your property. Impressions describe how often results were shown under Google's reporting rules. CTR is clicks divided by impressions. Average position describes the average position of your search results under Google's measurement definitions.

You can group results by dimensions such as query, page, country, device, and date.

For example, a monthly report could identify the landing pages receiving the most Google Search clicks, then compare their performance with the previous month.

The request needs a date range and authorized access to the Search Console property. You can also apply supported filters to narrow the analysis.

One important limitation is easy to miss: Search Console does not promise to return every underlying search-query record. Its Search Analytics documentation explains that some results are restricted by internal data availability and that returned rows favor leading results.

This matters for websites with many low-volume queries. A report containing every returned row is not necessarily a complete inventory of all searches that occurred.

Source: Google Search Console Search Analytics API.

Google Analytics Data API: What organic visitors do

Search Console measures how a website performs in Google Search. GA4 measures activity occurring on a website or app where analytics collection has been implemented.

The Google Analytics Data API allows authorized applications to generate reports from a GA4 property.

A typical SEO report might request:

  • Sessions attributed to Organic Search.
  • Users and engagement measurements.
  • Landing-page activity, where the selected dimensions and metrics are compatible.
  • Events and key events configured in the GA4 property.
  • Changes in acquisition or engagement across reporting periods.

Suppose you manage an online store and want to explain whether SEO work brings visitors who take valuable actions.

Search Console can show how the store appears in search and how many search clicks it receives. GA4 can help show organic sessions and tracked actions such as purchases or lead submissions, provided those events have been implemented correctly.

Do not treat Search Console clicks and GA4 organic sessions as interchangeable. They represent different events and use different measurement systems, attribution rules, and processing methods.

For example, one person may click a search result more than once within a period that GA4 treats as one session. Consent choices, analytics configuration, attribution, and other measurement differences may also affect reported totals.

A useful report shows the two figures separately. It does not add them together or invent a unified traffic count.

The API cannot reconstruct events that were never collected or provide access to private data from another organization's GA4 property without permission.

PageSpeed Insights API: Technical performance

The PageSpeed Insights API analyzes a specified web page and provides performance-related diagnostics.

Its response can include Lighthouse laboratory measurements, performance scores, and suggestions for improvement. Laboratory measurements are generated under controlled test conditions rather than representing every visitor's actual experience.

For example, a technical report could assess a homepage and a small selection of important landing pages, then identify pages that need closer investigation.

A performance score can be useful as a diagnostic signal, but it is not a Google ranking guarantee or a direct measurement of organic revenue.

There is also an important future-data consideration. Google has announced plans to stop including Chrome User Experience Report (CrUX) real-user data in PageSpeed Insights API responses. Developers requiring that data should investigate the dedicated CrUX API and CrUX History API.

Therefore, design your reporting application so that laboratory diagnostics and real-user field measurements are separate components. Do not assume that every current response field will remain available indefinitely.

PageSpeed Insights also cannot tell you which competitor has the most backlinks or which keywords produced your organic conversions.

Are These SEO Reporting APIs Really Free?

The word free needs a precise definition.

An API can have no direct usage charge while still limiting requests, requiring authorized accounts, restricting access to historical data, or imposing operational conditions.

There are also important differences between a permanently available free API, a recurring free allowance, a trial, and a paid credit system.

Search Console: Free with quotas and data limits

Google explicitly states that the Search Console API is free, although usage quotas apply.

Two limits deserve particular attention:

  1. The Search Analytics query method supports a rowLimit from 1 to 25,000 rows per request and a startRow parameter for pagination.
  2. Google's Search Console export documentation describes a performance-data availability limit of 50,000 rows per day per search type per property.

These are not interchangeable.

The first controls how many results an individual request asks for. The second concerns the available performance records. Neither means developers receive 50,000 API requests per day.

Google also applies request and processing-load quotas, including shorter-term and longer-term limits. Applications should consult the official quota documentation rather than assuming unrestricted request volume.

Sources: Search Console API export help and Search Analytics query reference.

GA4: Quota-limited reporting

The GA4 Data API uses quota accounting for different types of requests. Google's documentation identifies categories including Core, Realtime, and Funnel.

Consumption depends on factors such as the request's complexity. That means a developer cannot reliably estimate all usage from request count alone.

The API needs a Google Cloud project and appropriate access to the GA4 property.

For production automation, inspect current quotas, monitor consumption, and avoid repeating expensive requests unnecessarily. Request only the fields and periods your report actually needs.

Source: Google Analytics Data API limits and quotas.

PageSpeed Insights: Accessible without a key for ordinary requests

Google's documentation explains that the PageSpeed Insights API can be called with or without an API key, although a key is recommended for frequent automated queries.

That makes it attractive for simple integrations and experiments.

However, public accessibility does not establish unlimited production capacity. Developers should check the current limits and credential requirements before scheduling thousands of recurring tests.

IndexNowFast: A different, credit-based service

IndexNowFast offers an API for URL-indexing operations and associated task monitoring.

Its public API documentation describes Standard indexing at 1 credit per URL and Instant indexing at 15 credits per URL. The documented credit value at the November 12, 2026 review was ৳1.5 per credit; current account pricing should be checked before placing orders.

This is not the same category as Google's free Search Console reporting API.

An indexing-task API answers operational questions about submitted URLs and processing workflows. It does not automatically provide Google organic traffic, GA4 engagement, competitor keyword rankings, or a complete SEO performance report.

How to Build an Automated SEO Report With Free APIs

An automated report is a useful way to combine these sources. The process does not require buying a large commercial SEO data subscription when the required measurements already belong to websites you manage.

It does require a small reporting application or automation workflow.

Consider an agency preparing a monthly report for a client's website. It needs Google Search visibility, organic sessions, tracked leads, and technical diagnostics for selected pages.

Step 1: Identify the properties and secure access

First, establish which website and GA4 property belong in the report.

The client must grant the reporting application appropriate access to its Search Console and GA4 data.

For Google services, OAuth is a standard permission-based authorization system. It lets users grant an application access within defined scopes instead of giving the application their Google password.

Depending on the API and implementation, supported service-account arrangements may also be available when the relevant account or property has been granted permission.

A simple API key is not a substitute for authorization to private property-level data.

Store credentials securely, request only necessary permissions, and avoid exposing access tokens in browser-side code or public repositories.

Step 2: Configure the required APIs

Create or select a Google Cloud project and enable the relevant services using Google's official setup instructions.

Prepare the authentication method appropriate for your application, and keep each website's permitted property identifiers separate.

For a client-reporting system, the application should know which Search Console property maps to which GA4 property. Do not assume two properties correspond to the same reporting scope simply because their names look similar.

Step 3: Request Search Console performance data

Choose an explicit start date and end date.

The Search Analytics endpoint accepts a JSON request containing the requested period and dimensions.

An illustrative request body is:

``json { "startDate": "2026-10-01", "endDate": "2026-10-31", "dimensions": ["page"], "rowLimit": 1000 } ``

This body illustrates request structure only. It does not include the authorized HTTP request, property identifier, or access token required for an actual integration.

For each returned row, retain the page identifier, clicks, impressions, CTR, and average position.

If more rows are needed, use documented pagination where available. Handle partial results and data availability limitations rather than assuming pagination recovers every underlying record.

For accurate month-to-month reporting, avoid treating an incomplete current month as directly equivalent to a full preceding month.

Step 4: Request GA4 organic acquisition data

For the same reporting period, request an appropriately filtered GA4 report using the Data API's reporting methods, such as runReport.

Select dimensions and metrics supported together by the property and API.

For example, an organic acquisition section may contain sessions attributed to Organic Search, engagement metrics, and key events that the organization actually tracks.

Verify the intended acquisition dimension and attribution definition. A session-based channel breakdown should not be silently replaced with a first-user acquisition breakdown.

If no key events were configured, do not report zero business outcomes as though all important actions were measured. Mark the field as unavailable or not configured.

Step 5: Collect technical page diagnostics

Choose representative pages rather than indiscriminately testing every URL.

A useful starting set may contain the homepage, the most important service page, and selected organic landing pages.

Request PageSpeed Insights results for each page and keep the exact URL, selected strategy or test settings, and collection timestamp.

Technical diagnostics are point-in-time observations. They should not be presented as though they summarize an entire month of user experience unless the underlying measurement method supports that interpretation.

Step 6: Normalize the information

The biggest source of reporting errors is often not a failed API call. It is combining measurements that describe different things.

Before creating charts, preserve each dataset's original meaning.

Report fieldSource of truthImportant interpretation
Google Search impressionsSearch ConsoleSearch-result visibility under Google's reporting rules
Google Search clicksSearch ConsoleSearch-result clicks, not website sessions
Search CTRSearch ConsoleClicks divided by impressions
Average search positionSearch ConsoleAn aggregate search-position measurement, not a fixed keyword rank
Organic sessionsGA4Sessions attributed to the selected organic channel definition
Configured key eventsGA4Measured actions only when configured and collected
Laboratory page diagnosticsPageSpeed InsightsResults for the tested URL and test conditions
Real-user performance dataAppropriate CrUX API when requiredSubject to field-data availability and API documentation
URL indexing-workflow statusIndexNowFast, when usedOperational task status, not guaranteed Google index inclusion
Competitor SERP positionsSeparate licensed providerExternal search-result observations, not private Search Console data

A search engine results page, or SERP, is the page displaying results for a search. SERP-data services observe those results rather than reading another company's private Search Console account.

This source-of-truth table can also become a validation checklist for your reporting software.

Step 7: Define a reusable report structure

A reporting system benefits from a consistent internal data contract. That is a standard structure defining which fields every report should contain.

The following example is an illustrative application-defined JSON structure, not an official Google API response or the output of a tested integration:

``json { "report_period": { "start_date": "2026-10-01", "end_date": "2026-10-31" }, "properties": { "search_console_property": null, "ga4_property": null }, "search_visibility": { "source": "Google Search Console API", "clicks": null, "impressions": null, "ctr": null, "average_position": null }, "site_behavior": { "source": "Google Analytics Data API", "organic_sessions": null, "configured_key_events": null }, "page_diagnostics": { "source": "PageSpeed Insights API", "tested_url": null, "lighthouse_measurements": null, "collected_at": null }, "provenance": { "retrieved_at": null, "authorization_context": null, "completeness_notes": [] } } ``

The null values intentionally represent information that has not been retrieved. They are not SEO performance measurements.

A production implementation should also retain individual dataset timestamps, property identifiers, dimension definitions, errors, and source-specific reporting periods where those differ.

Step 8: Generate the report

Once the data is validated, a separate reporting layer can format it into a dashboard, spreadsheet, HTML document, or PDF.

For a client report, a clear layout might present search visibility trends first, then organic engagement and tracked outcomes, followed by technical findings and recommended actions.

Add the reporting period, the date each source was retrieved, and notes explaining important measurement limitations.

Do not let the formatting layer silently replace missing measurements with zero. Missing data and measured zero are different outcomes.

Step 9: Automate safely

A scheduled workflow can retrieve the data, validate responses, save a historical snapshot, and regenerate the report at defined intervals.

For a monthly report, the application might run after the reporting period has ended and the relevant data has become available.

Production safeguards should include:

  • Permission-error handling when access is revoked.
  • Retry policies with backoff for temporary failures and quota responses.
  • Checks for empty, delayed, or incomplete datasets.
  • Logging that avoids exposing credentials or sensitive response data.
  • Clear alerts when a source fails rather than quietly publishing stale information.
  • Source and extraction timestamps so readers can identify what was actually measured.

For Google API integrations, follow the official Search Console reference, GA4 Data API documentation, and PageSpeed Insights documentation for actual request formats and authentication requirements.

What a Free SEO Reporting API Cannot Tell You

Free access to your own search-performance data does not create unrestricted access to the rest of the internet.

That distinction matters when comparing SEO reporting APIs with products advertised as SEO intelligence platforms.

Competitor keyword rankings

Search Console gives authorized property users information about their own Google Search visibility. It cannot simply return another business's private search-performance history because a developer knows that business's domain.

If you need independent keyword rankings for competing domains, you may need a SERP API or a rank-tracking provider.

Such services collect or license observations of search results. Their coverage may vary by search engine, country, device, location, and collection time.

A provider's advertised free trial does not establish a permanently free reporting tier. Verify its official pricing, current allowances, data licensing, and acceptable use before incorporating it into a commercial product.

Comprehensive backlink profiles

Search Console's reporting API is not a replacement for a commercial backlink database, and PageSpeed Insights does not maintain one.

A backlink-analysis system needs link-discovery and crawling data from an appropriate source. Different providers may observe different portions of the web.

A report should identify its backlink-data source instead of presenting incomplete third-party observations as a universal count of every link on the internet.

Whole-site technical crawling

PageSpeed Insights tests pages. It does not automatically discover and crawl every URL on a large website to build a complete technical SEO inventory.

For site-wide checks of redirects, internal links, metadata, canonical tags, and other crawlable elements, a dedicated crawler or crawler API may be more appropriate.

PageSpeed diagnostics can complement such a crawler, but the two systems solve different problems.

Guaranteed indexing or rankings

Submitting a URL, observing an indexing-related status, and achieving higher organic rankings are separate outcomes.

For example, the IndexNowFast Google Index Checker supports checking observed Google index status for URL lists and exporting results to CSV. Its published documentation describes batches of up to 10,000 URLs.

That can be useful when your workflow needs a separate index-status snapshot.

However, a checker result is a point-in-time observation. Search engines control their own indexes, and an indexing submission cannot guarantee permanent inclusion or better rankings.

Similarly, the IndexNowFast backlink indexing workflow concerns discovery and processing of eligible public backlink URLs. It should not be confused with measuring the business impact of those links.

A useful SEO report should distinguish activities performed, observations collected, and outcomes measured.

How to Choose the Right API for Your Reporting Project

Before writing integration code, decide what the report must prove.

Your reporting goalRecommended starting pointAdditional requirement
Measure Google Search visibility for your own websiteSearch Console APIAuthorized property access
Report organic visits and tracked business actionsGA4 Data APIImplemented tracking and authorized property access
Identify performance problems on important pagesPageSpeed Insights APISelected URLs and an appropriate testing schedule
Monitor account indexing tasksIndexNowFast APIAccount credentials and applicable service credits
Track competitors in public search resultsVerified SERP-data providerRelevant geography, coverage, license, and budget
Analyze large backlink datasetsVerified backlink-data providerClear database coverage and usage terms
Produce complete branded client reportsCombined data pipelineValidation, report templates, and ongoing maintenance

For a small business that only wants monthly Google Search reporting, Search Console may be enough. Adding more APIs without a reporting need creates additional complexity.

For an agency explaining organic acquisition and lead performance, Search Console and GA4 are more useful together. The first measures visibility and search clicks; the second helps describe website activity after acquisition.

For a technical SEO consultant, PageSpeed Insights provides another layer, but it should be paired with other appropriate inspection tools when the project requires a complete site audit.

A practical selection checklist

Before adopting any API, answer these questions:

  1. Data: Does the API return the exact measurements your report requires?
  2. Access: Can your application obtain legitimate authorization for every required property?
  3. Coverage: Which URLs, dates, countries, devices, or events are included or excluded?
  4. Freshness: How often does the underlying information update, and how will you label delayed data?
  5. Limits: Can your expected workload operate within documented request, token, and row restrictions?
  6. Licensing: Does the provider permit the intended storage, reuse, and commercial presentation of data?
  7. Output: Does the API deliver raw JSON, structured reports, or finished files? What will your application need to generate?
  8. Maintenance: Who will handle authentication changes, API updates, quota failures, and broken reporting jobs?

The strongest choice is not necessarily the API returning the most fields. It is the one supplying reliable, clearly defined data for the decision your reader needs to make.

Frequently Asked Questions

Is there a completely free SEO report API?

Yes. Google's Search Console API is explicitly documented as free, subject to quotas and data limits. The GA4 Data API and PageSpeed Insights API also support reporting workflows without requiring a commercial SEO data subscription for their ordinary documented use. None should be assumed to provide unlimited access or an automatically formatted complete SEO report.

Can the Google Search Console API generate an SEO report automatically?

It can supply data to an automated reporting system. Your application still needs to request the measurements, handle authorization and response limits, and format the results into a readable report. Search Console does not automatically provide a custom branded PDF through the Search Analytics query method.

Can I retrieve SEO reports for a competitor's website?

You cannot obtain a competitor's private Search Console or GA4 reporting data without authorized access. You can use public-page diagnostics for eligible URLs and evaluate separately licensed SERP or backlink datasets, but those are not equivalent to the competitor's internal analytics.

Do I need OAuth or just an API key?

It depends on the API. Search Console performance access requires appropriate authorization, and private GA4 reporting also requires supported authenticated access. PageSpeed Insights supports ordinary requests without an API key, although Google recommends a key for frequent automated use. An API key alone does not grant permission to another website's private Google data.

What is the difference between an SEO reporting API and a SERP API?

An SEO reporting API may retrieve analytics or search-performance information for an authorized property. A SERP API retrieves observations of search engine results pages, often for specified queries and locations. A SERP API can help track public ranking positions, but it does not reveal another website's private clicks, sessions, or conversions.

Can I combine Search Console, GA4, and PageSpeed Insights in one report?

Yes. They are complementary sources for search visibility, visitor behavior, and technical diagnostics. Your application needs to preserve their separate measurement definitions, dates, and data-quality limits before presenting them together.

Does an indexing API show whether my SEO campaign is succeeding?

Not by itself. Indexing workflow information can show submission and processing activity or related observations. Campaign performance requires outcome measurements such as search visibility, relevant organic sessions, and appropriately tracked business actions.

Can I use these APIs for multiple clients?

Yes, provided you have legitimate access to each client's relevant properties and comply with the APIs' authentication, quotas, and usage requirements. A multi-client application should isolate credentials and data by client, preserve property identifiers, and handle revoked permissions safely.

Final Recommendation

For most developers and SEO teams working with websites they manage, the best free SEO report API starting point is Google Search Console. It provides the search visibility measurements that belong at the center of a Google organic performance report.

Add the Google Analytics Data API when the report needs visitor engagement and measured outcomes. Use PageSpeed Insights for selected technical diagnostics, with separate CrUX integration when suitable real-user performance data is required.

The essential distinction is between getting data and delivering a trustworthy report. Free API access solves the first part. Accurate definitions, authorized access, sensible quotas, transparent limitations, and reliable formatting solve the second.

Build around those requirements, and a useful automated SEO reporting system becomes possible without pretending that one free endpoint can measure every aspect of search performance.