Ahrefs April 2026 Updates: Grok, API Limits, and What Changed
Ahrefs’ April 2026 release added Grok to Brand Radar, expanded API capacity, and introduced reporting and workflow changes that affect AI visibility monitoring at both single-site and agency scale.
· 14 min read
Ahrefs raised Standard API capacity from 150,000 to 400,000 units and doubled Advanced capacity to 1 million units in April 2026. The Ahrefs April 2026 updates also introduced Grok in Brand Radar, giving SEO teams a practical breakdown of what changed in AI visibility monitoring, API automation, citation reporting, and client dashboards.
The release included more than the two headline changes. It covered Brand Radar reporting, API endpoints, Site Explorer, Keywords Explorer, Google Search Console reporting, and Social Media Manager. This guide separates confirmed April 2026 product changes from sensible—but unproven—workflow recommendations, so agencies, consultants, and site owners can decide which updates deserve implementation time.
The headline Ahrefs April 2026 updates
Ahrefs described eight notable updates in its April 2026 product release. The two with the clearest operational implications were Grok support in Brand Radar and higher API allowances for self-serve plans.
Grok gave Brand Radar another AI answer engine to monitor. Ahrefs confirmed that Grok was available for its Ahrefs prompt dataset and for custom prompts at the time of the April announcement. That matters to teams that need to understand whether brand entities and pages appear in more than one AI-generated answer environment.
The API changes affect a different part of the workflow. A site owner exporting one report each month may see less immediate benefit than an agency processing dozens of sites. More units and larger request sizes can reduce batching and failed or incomplete recurring exports, provided the team budgets usage before scaling automation.
The release therefore moved Ahrefs in two directions at once: broader AI-answer monitoring and easier distribution of data into reporting systems. Neither direction removes the need to validate a page’s technical condition, content quality, or business outcomes independently.
Grok in Brand Radar: the confirmed change
The confirmed April 2026 change was straightforward: Ahrefs added Grok to Brand Radar for both Ahrefs prompts and custom prompts. Ahrefs prompts are the platform’s wider prompt dataset, while custom prompts allow a user to monitor prompts they choose.
The April announcement confirms custom-prompt support, but it does not establish every possible custom-prompt setting. In particular, teams should not assume configuration options for location, refresh cadence, or every AI assistant without checking the current Brand Radar interface and documentation in their own account. Product controls can vary by plan and can change after launch.
Why another answer engine matters
AI visibility is not one universal measurement. An answer produced by Grok may differ from an answer produced by another assistant because each system can use different retrieval, ranking, citation, and response-generation processes. A brand’s inclusion in one answer engine is therefore not proof of inclusion elsewhere.
For practical monitoring, teams can use a small set of commercially meaningful questions, such as:
- Category questions: “best website audit software for SEO agencies.”
- Comparison questions: “Ahrefs alternatives for AI visibility tracking.”
- Problem questions: “how to audit pages cited by AI answers.”
- Branded questions that test product descriptions and factual accuracy.
- Expert questions relevant to a site’s core service or product category.
The result should be treated as an observation from a named answer engine and a recorded collection date, not a universal ranking. That distinction is especially relevant for client reporting: a chart should say which platform and prompt set it represents.
What Grok support does not prove
The April announcement does not demonstrate that a Grok mention produces traffic, leads, conversions, or revenue. It also does not establish that changing a page will cause it to be cited by Grok or any other AI system.
The useful role of Grok monitoring is diagnostic. It can help a team identify questions where a brand is absent, pages that competitors receive citations for, and areas where the site’s existing content may deserve closer review. Follow-up decisions still require site-level evidence, analytics, and business context.
Brand Radar citation reporting: Found in and Cited in
Brand Radar’s redesigned Cited Pages report distinguishes between Found in and Cited in. Ahrefs describes Found in as responses where a page was found or sourced during answer generation, while Cited in refers to responses where the domain was visibly cited in the AI answer.
This distinction is more useful than a single mention metric. A page that is found but not cited may have relevance to the question without being the source selected for a visible citation. Conversely, a cited page may be a strong reference for a narrow prompt set without representing broad topic authority.
Ahrefs also placed the former Cited Domains reporting within an All domains tab alongside Yours, Competitors, and Other. That interface change gives users a clearer route from a missed citation to the domains that appeared instead.
A practical review framework
A team can classify pages into four review groups:
- Found and cited: Keep these pages accurate, accessible, and technically sound. Review whether the cited topics align with commercial or strategic priorities.
- Found but not cited: Compare the page with cited alternatives and identify concrete differences in the answer, evidence, structure, or topical coverage.
- Not found: Check whether the page is crawlable, indexable, internally linked, relevant to the prompt, and sufficiently direct in addressing the underlying question.
- Competitor-cited pages: Review the cited material for useful topic gaps or evidence formats, without copying wording or making unsupported causal assumptions.
Recommendations such as clearer authorship, appropriate structured data, concise answer sections, and stronger supporting evidence are editorial and technical hypotheses—not conclusions established by the April product update. They should be tested page by page. A broader framework for evaluating evidence rather than chasing mentions appears in Brands Winning AI Search: A Practical Evidence Scorecard.
Historical citation charts are monitoring tools, not outcome metrics
Ahrefs added two Cited Pages chart modes: Found in and Position. The Found in chart displays total responses where a page was found alongside responses where it was cited. The Position chart shows average citation position over time, with thicker lines indicating that more citations support the average.
These charts make change detection easier than comparing isolated snapshots. For example, an agency can annotate a chart with the date a new evidence section, page redesign, or technical fix was published, then observe whether citation visibility changes afterward. That is an illustrative monitoring workflow, not evidence that the change caused the result.
Ahrefs also said citation-position reporting applies to chatbot models. Google AI Overviews and AI Mode retain the older views because they do not have citation positions in the same way. The April release should therefore not be read as a single uniform measurement system across every answer surface.
Citation frequency and position are not organic rankings, referral sessions, conversion data, or revenue. A responsible report should pair them with Google Search Console, web analytics, lead or sales data where available, and technical audit findings. This prevents a visibility metric from being presented as a business outcome it cannot independently substantiate.
API limits: the April 2026 numbers by plan
Ahrefs published specific API increases for Lite, Standard, and Advanced self-serve plans. Lite plans received four times the previous units allowance and 10 times the previous rows-per-request limit. The announcement did not specify Lite’s before-and-after absolute unit total.
Standard increased from 150,000 to 400,000 units and from 25 to 250 rows per request. Advanced increased from 500,000 to 1,000,000 units, while rows per request rose from 100 to 500.
| Plan | Previous units | New units | Previous rows/request | New rows/request |
|---|---|---|---|---|
| Lite | Not stated in the April announcement | 4× previous limit | Not stated | 10× previous limit |
| Standard | 150,000 | 400,000 | 25 | 250 |
| Advanced | 500,000 | 1,000,000 | 100 | 500 |
For an agency, the larger row limits can mean fewer requests when producing scheduled exports across a client portfolio. For a data team, the increase may make warehouse loads and dashboard refreshes more practical. For a single-domain owner, the benefit is mostly reduced friction when retrieving larger datasets.
The new allowances do not mean API consumption is unlimited. Usage depends on endpoints, selected fields, result volume, report frequency, and the number of projects. Before building automated reporting, a team should estimate monthly demand as clients × data pulls × refreshes, then validate actual unit consumption against Ahrefs’ current API documentation.
Brand Radar API and Looker Studio distribution
Ahrefs added Brand Radar API support for entities, including brand variations and brand websites. It also introduced POST versions of existing GET endpoints, allowing more complex request inputs to be sent in the request body rather than constrained by URL parameters.
The release also included endpoints for Brand Radar report management, including creating reports, adding prompts, and monitoring results. These capabilities are most relevant to agencies or in-house teams that want consistent onboarding across multiple brands. A reusable reporting template can reduce manual setup, though teams still need a human review of brand variants, competitors, and priority topics.
Ahrefs’ new Looker Studio connector supports historical charts for AI mentions, impressions, and AI share of voice, plus brand and platform distributions. This gives reporting teams a route to place AI visibility signals beside organic search, paid media, and analytics data.
Automation solves distribution, not interpretation. A falling chart could reflect a changed prompt set, collection change, answer-engine behavior, competitor improvement, or a genuine site issue. Reporting workflows should retain collection dates, definitions, annotations, and a path back to the affected pages.
Site Explorer updates support technical investigation
Site Explorer gained an Organic Positions report that shows every ranking URL for organic keywords. Ahrefs distinguishes it from Positions in Calendar, which focuses on keywords with daily movement. Organic Positions can be exported in both chart and table form.
The new Crawled Pages report lists pages crawled by AhrefsBot and sorts them by the most recent crawl attempt. It can provide a third-party crawler view of a site’s discoverability and recent crawl activity.
However, AhrefsBot is not Googlebot. A page shown or absent in a third-party crawler report does not conclusively prove how Google crawls, renders, indexes, or ranks it. Technical diagnosis should include server responses, robots directives, canonicalization, internal links, rendering, and Google Search Console evidence.
That order matters when visibility falls. Before rewriting content to address a perceived AI or ranking gap, teams should rule out crawl and indexing problems. Googlebot Timeouts: Diagnose a 90% Organic Traffic Drop and Discovered - Currently Not Indexed: A Diagnostic Guide That Finds the Real Blocker explain why a symptom is not enough to identify a cause.
Keywords Explorer, GSC, and Social Media Manager changes
Keywords Explorer added historical total search-volume graphs for multiple keywords and saved keyword lists. This supports topic-level demand review rather than isolated keyword analysis. For example, a retailer can compare a saved list across a 12-month period to distinguish seasonal demand changes from a potential visibility problem.
Google Search Console reporting gained Word Count and Rank Tracker status filters. Rank Tracker status replaced the former Not tracked only filter, allowing users to isolate tracked and untracked keywords while still reviewing GSC metrics. GSC Insights also became available in Portfolios, which can help agencies aggregate related properties or country sites.
Social Media Manager’s redesigned Overview includes published posts, new followers, total engagement, average engagement rate, period-over-period changes, date filtering, connected-channel status, the next five scheduled posts, and top posts by views. These are operational reporting features rather than direct SEO or AI-citation signals.
Social engagement may suggest language or questions worth researching, but the April announcement does not establish that engagement causes rankings or AI citations. Teams should avoid turning a correlation in cross-channel reporting into a performance claim.
How Ahrefs compares with AI visibility platforms
The April release makes Ahrefs more integrated for teams already using its backlink, keyword, crawl, and Search Console products. Its confirmed April strengths include Grok support in Brand Radar, citation-history views, API expansion, report-management endpoints, and Looker Studio distribution.
Standalone AI-search visibility vendors such as Profound, Peec AI, and Scrunch are also positioned around tracking brand presence in AI-generated answers. Their public product pages should be reviewed directly for current engine coverage, prompt controls, export options, pricing, and methodology; this article does not treat vendor marketing claims as an independently tested benchmark.
| Evaluation area | Ahrefs April 2026 evidence | What to verify with any alternative |
|---|---|---|
| AI monitoring | Grok added to Ahrefs and custom prompts | Current answer-engine coverage and collection method |
| SEO context | Site Explorer, Keywords Explorer, and GSC updates | Whether crawl, ranking, and indexing data are included or require another tool |
| Reporting | Looker Studio connector and Brand Radar API updates | Export limits, dashboard connectors, and report ownership |
| Automation | Higher self-serve API limits and POST endpoints | Quotas, endpoint scope, rate limits, and setup effort |
The appropriate choice depends on workflow. A team that needs an established SEO dataset and AI visibility reporting in one platform may prioritize Ahrefs. A team that needs a local-first inspection of page health can complement monitoring with Audra, which audits technical SEO, performance, accessibility, best practices, links, and AI answer-engine visibility without making a subscription dashboard the sole source of evidence. Boost Your SEO: An Audit Plan That Prioritizes Fixes provides a practical prioritization model.
Who should use these changes and what to do next
SEO consultants may benefit most from Cited Pages, custom prompts, and the ability to compare cited domains. Agencies are more likely to gain from the API increase, Brand Radar endpoints, Portfolios, and Looker Studio connector because repeated reporting tasks scale across accounts.
Site owners with one domain can begin with Cited Pages, Organic Positions, Crawled Pages, and GSC filters. These reports can turn a broad concern into a page-level investigation list, but they should not replace a direct website audit.
A measured 30-day implementation plan is:
- Choose 10 to 30 high-intent prompts across category, comparison, problem, and branded questions.
- Record the answer engine, collection date, and the exact prompt wording used.
- Review Found in and Cited in patterns, then select the highest-value page gaps.
- Check selected URLs for indexing, crawlability, internal linking, performance, accessibility, and content accuracy.
- Annotate releases, technical changes, and prompt-set edits before interpreting trend charts.
- Add API or Looker Studio automation only after the measurement definitions are stable.
This approach uses the April 2026 release as a reporting and prioritization upgrade rather than treating any individual AI visibility metric as a final performance verdict.
FAQ
What new features did Ahrefs release in April 2026?
Ahrefs announced eight April 2026 updates across Brand Radar, Site Explorer, Keywords Explorer, GSC reporting, Social Media Manager, and the API. Major items included Grok in Brand Radar, revised Cited Pages charts, higher API limits, Brand Radar API endpoints, a Looker Studio connector, Organic Positions, Crawled Pages, historical keyword-list volume charts, and GSC Portfolio Insights.
How does Grok work in Ahrefs Brand Radar?
In its April 2026 announcement, Ahrefs said Grok became available in Brand Radar for both its Ahrefs prompt dataset and custom prompts. This enables users to observe whether brands and pages appear in Grok answers for monitored questions. The announcement does not prove identical coverage, settings, or behavior across every AI system, so users should verify current account availability before client reporting.
Did Ahrefs increase its API limits, and which plans are affected?
Yes. In April 2026, Lite received four times its previous unit limit and 10 times its prior rows-per-request limit. Standard rose from 150,000 to 400,000 units and from 25 to 250 rows per request. Advanced rose from 500,000 to 1 million units and from 100 to 500 rows per request. Usage still depends on endpoint and query design.
Can Brand Radar track custom prompts as well as Ahrefs prompts?
Yes. Ahrefs confirmed in April 2026 that Brand Radar supports both the Ahrefs prompt dataset and custom prompts selected by users. The release announcement does not establish a universal formula for how prompts, platforms, locations, or checks are charged. Teams should consult their current plan details and product interface before estimating monitoring capacity.
What other Ahrefs updates were released alongside Grok and higher API limits?
The April 2026 release also added Found in and Position views for Cited Pages, Brand Radar entity and report-management API capabilities, a Looker Studio connector, Organic Positions and Crawled Pages in Site Explorer, historical total-volume charts in Keywords Explorer, GSC filters and Portfolio Insights, and a redesigned Social Media Manager Overview dashboard.